Version-Release number of selected component: shotwell-0.15.1-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: shotwell '/home/tcfxfzoi/Documents/studentData/102_2/\xe8\xb3\x87\xe8\xa8\x8a\xe7\xae\xa1\xe7\x90\x86\xe5\xb0\x88\xe9\xa1\x8c\xe7\xa0\x94\xe8\xa8\x8e/\xe5\xa0\xb1\xe5\x91\x8a\xe9\xa0\x86\xe5\xba\x8f.jpg' crash_function: poll_for_event executable: /usr/bin/shotwell kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 poll_for_event at xcb_io.c:271 #5 poll_for_response at xcb_io.c:289 #6 _XEventsQueued at xcb_io.c:363 #7 XPending at Pending.c:55 #8 gdk_event_source_check at /lib64/libgdk-3.so.0 #9 ?? #10 g_main_context_check at gmain.c:3557 #12 g_main_context_iteration at gmain.c:3774 #13 g_application_run at gapplication.c:1635 #14 application_start at /usr/src/debug/shotwell-0.15.1/src/Application.vala:170 Potential duplicate: bug 1093308
Created attachment 901043 [details] File: backtrace
Created attachment 901044 [details] File: cgroup
Created attachment 901045 [details] File: core_backtrace
Created attachment 901046 [details] File: dso_list
Created attachment 901047 [details] File: environ
Created attachment 901048 [details] File: limits
Created attachment 901049 [details] File: maps
Created attachment 901050 [details] File: open_fds
Created attachment 901051 [details] File: proc_pid_status
Created attachment 901052 [details] File: var_log_messages
Another user experienced a similar problem: I just opened a file and I rotated it. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: shotwell '/home/marcos/fam\xc3\xadlia 017.jpg' crash_function: poll_for_event executable: /usr/bin/shotwell kernel: 3.14.4-200.fc20.x86_64 package: shotwell-0.15.1-1.fc20 reason: shotwell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Rotating an image 4 times Open an image Rotate it 3 - 4 times reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: shotwell '/home/casep/Downloads/la foto 1.JPG' crash_function: poll_for_event executable: /usr/bin/shotwell kernel: 3.14.8-200.fc20.x86_64 package: shotwell-0.15.1-1.fc20 reason: shotwell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This' the image of the issue https://dl.dropboxusercontent.com/u/1789502/la%20foto%201.JPG
Rotating JPEG every time.
Another user experienced a similar problem: I am not sure. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: shotwell '/home/alex/Downloads/photo 1.JPG' crash_function: poll_for_event executable: /usr/bin/shotwell kernel: 3.16.3-200.fc20.x86_64 package: shotwell-0.15.1-1.fc20 reason: shotwell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Attempted to rotate a photo with shotwell, it froze for a couple seconds, shotwell force closed. Re-opened same photo, attempted the same and happened again. Only happened with one photo, other photos taken same date, same time, same camera, same SDCard and moved to computer by inserting SDCard into computer card reader, rotated just fine. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: shotwell '/home/viruz/Pictures/eBay/Samsung Tablet/IMG_2911.JPG' crash_function: poll_for_event executable: /usr/bin/shotwell kernel: 3.16.7-200.fc20.x86_64 package: shotwell-0.15.1-1.fc20 reason: shotwell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Got it with shotwell-0.15.1-1.fc20.x86_64 kernel-3.18.7-100.fc20.x86_64 Tried only once.
Created attachment 995240 [details] typscript of gdb session Tried a gdb of shotwell showing the bug.
Tried again, intending to issue "thread all bt". Rotate worked normally!
Another user experienced a similar problem: I clicked on Rotate on a photo and got this crash reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: shotwell /home/diego/img009.jpg crash_function: poll_for_event executable: /usr/bin/shotwell kernel: 3.18.7-100.fc20.i686 package: shotwell-0.15.1-1.fc20 reason: shotwell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1001
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.