Description of problem: Just firing up shotwell and waiting some seconds results in the application completely hanging for me, while trying to import new photos. Looks like a deadlock. I then manually sent SIGABRT to shotwell in a terminal, so that this report could be automatically generated. This renders shotwell completely unusable for me. I tried completely emptying the folder with the Photo library, and also deleting .local/share/shotwell, but it did not help. Version-Release number of selected component: shotwell-0.19.0-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: shotwell crash_function: syscall executable: /usr/bin/shotwell kernel: 3.16.1-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 7 (8 frames) #0 syscall at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 g_cond_wait at gthread-posix.c:1390 #2 abstract_semaphore_wait at /usr/src/debug/shotwell-0.19.0/src/threads/Semaphore.vala:70 #3 background_job_notify at /usr/src/debug/shotwell-0.19.0/src/threads/BackgroundJob.vala:220 #4 prepare_files_job_real_execute at /usr/src/debug/shotwell-0.19.0/src/BatchImport.vala:1736 #5 workers_thread_start at /usr/src/debug/shotwell-0.19.0/src/threads/Workers.vala:96 #6 _workers_thread_start_gfunc at /usr/src/debug/shotwell-0.19.0/src/threads/Workers.vala:31 #8 g_thread_proxy at gthread.c:764
Created attachment 931160 [details] File: backtrace
Created attachment 931161 [details] File: cgroup
Created attachment 931162 [details] File: core_backtrace
Created attachment 931163 [details] File: dso_list
Created attachment 931164 [details] File: environ
Created attachment 931165 [details] File: limits
Created attachment 931166 [details] File: maps
Created attachment 931167 [details] File: open_fds
Created attachment 931168 [details] File: proc_pid_status
Created attachment 931169 [details] File: var_log_messages
Proposed as a Blocker for 21-final by Fedora user catanzaro using the blocker tracking app because: My understanding is that this bug makes Shotwell unusable. Proposing as a final blocker: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test."
shotwell-0.19.0-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/shotwell-0.19.0-2.fc21
Proposing as a F21 Alpha freeze exception, based on the criteria outlined in comment #11.
Using updated version of comment 12, it works like a charm ...
Package shotwell-0.19.0-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing shotwell-0.19.0-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-10302/shotwell-0.19.0-2.fc21 then log in and leave karma (feedback).
Discussed at 2014-09-10 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-09-10/f21-blocker-review.2014-09-10-16.07.log.txt . Accepted as a freeze exception issue - this is a function people are likely to test on lives or immediately post-install, hence it would be good to make sure it works.
shotwell-0.19.0-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.