shotwell hangs on send to
Submitted by an unknown user
Link to original bug (#718280)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-09-25 13:04:00 -0700 ----
Original Redmine bug id: 4181
Original URL: http://redmine.yorba.org/issues/4181
Searchable id: yorba-bug-4181
Original author: Dominik Holler
Original description:
multiple photos are selected, File->send to invoked, desired resolution acknowledge, shotwell hangs
Related issues:
- related to shotwell - 5827: SendTo email multiple photos only sends one photo (Fixed)
- related to shotwell - 4098: Import hangs (Invalid)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:45:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 2 years ago
- Description updated (diff)
What operating system version are you running? What version of Shotwell are you running?
Comment 2
Updated by Dominik Holler about 2 years ago
shotwell 0.11.2-1~natty from yorba ppa on Ubuntu 11.04, thx
Comment 3
Updated by Dominik Holler about 2 years ago
- Subject changed from shotwell hangs on export to shotwell hangs on send to
Comment 4
Updated by Jim Nelson about 2 years ago
- Category set to 4
- Priority changed from Normal to High
- Target version set to 0.12
The problem is that the background library scanner is running while you're doing the export. The two processes -- scanning your library for missing files (and perhaps installing the library monitors) and exporting the photos -- are competing for time.
How large is your library? How many photos are you trying to send? Do you have library monitoring turned on (Edit -> Preferences -> Watch library for new files)?
We have other problems related to this patch of code. I'm going to bump up to 0.12 for consideration, as this issue could manifest itself in a number of ways.
As far as a workaround, I can only suggest waiting for the background scan to complete before sending a lot of photos.
Comment 5
Updated by Dominik Holler about 2 years ago
Thx for replying.
The library is big, guess around 70k pictures.
While creating this problem, library monitoring was not turned on, but now I am switching to turn it on (importing all photos takes some days).
I have removed files, which may be referenced in the shotwells database.
Nice to hear that the issue will be fixed in next version.
Comment 6
Updated by Jim Nelson about 2 years ago
70K tells me that the initial startup scan will take a while. That's contributing to the problem.
BTW, I don't mean to say you should turn in library monitoring, I was just asking if you had it turned on.
Finally, we can't guarantee this will be fixed in the next release, I'm merely promoting it for consideration.
Comment 7
Updated by Adam Dingle over 1 year ago
-
Target version deleted (
<strike>
_0.12_</strike>
)
Comment 8
Updated by Jim Nelson 11 months ago
- Target version set to 0.14.0
Comment 9
Updated by Jim Nelson 11 months ago
- Category set to library-mode
- Status changed from Open to Need Information
Dominik, a few months ago we found a nasty bug in the Send To logic. I'm wondering if it has some relevance with your problem here. Could you try upgrading to the Shotwell in our Daily Build PPA and report back if you're still seeing the problem? Thanks!
https://launchpad.net/~yorba/+archive/daily-builds/
Comment 10
Updated by Jim Nelson 8 months ago
- Target version changed from 0.14.0 to 0.15.0
Comment 11
Updated by Jim Nelson 8 months ago
- Status changed from Need Information to 5
- Resolution set to invalid
Closing as this ticket has been Need Information for almost 90 days now. Please re-open if this problem is discovered again or more information comes to light.
Comment 12
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:56 UTC ---
This bug was previously known as bug 4181 at http://redmine.yorba.org/show_bug.cgi?id=4181 Imported an attachment (id=262289) Imported an attachment (id=262290)
Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.15.0
Resolution: RESOLVED INVALID