GNOME Bugzilla – Bug 608717
Segmentation fault when I press delete button
Last modified: 2015-12-17 15:24:53 UTC
Open a picture and press delete button closes the application: gthumb[22750]: segfault at 0 ip 00007f117baac249 sp 00007fff22458470 error 4 in libfile_manager.so[7f117baa6000+d000]
In the browser view "Move to trash" context menu or delete button do the same thing
I cannot reproduce the problem you describe and without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
While trying to manage the stack trace I can add, that my trash bin is disabled in nautilus. So when I delete something it disappears.
how did you disable the trash bin?
Starting program: /usr/bin/gthumb [Thread debugging using libthread_db enabled] [New Thread 0x7fffe6fec710 (LWP 11657)] [New Thread 0x7fffe6f6b710 (LWP 11658)] [New Thread 0x7fffe6eea710 (LWP 11659)] [New Thread 0x7fffe6e69710 (LWP 11660)] [New Thread 0x7fffe6cfc710 (LWP 11661)] [New Thread 0x7fffe64fb710 (LWP 11662)] [New Thread 0x7fffe5cfa710 (LWP 11663)] [Thread 0x7fffe64fb710 (LWP 11662) exited] [New Thread 0x7fffe64fb710 (LWP 11664)] [Thread 0x7fffe64fb710 (LWP 11664) exited] [New Thread 0x7fffe64fb710 (LWP 11665)] [Thread 0x7fffe64fb710 (LWP 11665) exited] [New Thread 0x7fffe64fb710 (LWP 11667)] [Thread 0x7fffe64fb710 (LWP 11667) exited] [New Thread 0x7fffe64fb710 (LWP 11668)] [Thread 0x7fffe64fb710 (LWP 11668) exited] [New Thread 0x7fffe5c59710 (LWP 11669)] [New Thread 0x7fffe64fb710 (LWP 11670)] Error: Directory NikonPreview with 8224 entries considered invalid; not read. [Thread 0x7fffe64fb710 (LWP 11670) exited] Program received signal SIGSEGV, Segmentation fault. 0x00007fffe980b249 in notify_files_delete () from /usr/lib/gthumb/extensions/libfile_manager.so (gdb) bt
+ Trace 220371
I don't remember how did I disable it. When I delete something in nautilus I have a message "Cannot move file to the wastebasket, do you want to delete immediately?" I press Yes and it deletes.
Thank you for your report, the problem you described is fixed now in the current development version and the fix will available in the next public release which will be named 2.11.2
Re-opening: this downstream report has a backtrace showing the same problem with 2.11.3. http://bugzilla.redhat.com/show_bug.cgi?id=597006
+ Trace 222303
Thread 1 (Thread 7825)
I get a segfault in thumbnail view if I delete two successive thumbnails. Deleting under other circumstances seems safe though.
Steven, What version are you using?
v2.12.2 running on Fedora 14. I tried to reproduce the problem today and paid careful attention to the sequence of keystrokes. I think I realized what was causing the problem. Here's what happens in detail: 1. Get a thumbnail view of a photo directory 2. click once on a thumbnail near the middle of the list to highlight it 3. hit the delete key 4. hit enter to confirm 5. hit the delete key again to delete next image 6. hit enter again to confirm 7. segfault What I noticed is that after step 4, gthumb does NOT automatically highlight the next successive image any more. Instead there is no image highlighted after the delete. On step 5, the text of the second confirmation dialog reads "Are you sure you want to move to the trash the 0 selected files?". So if I'd been paying careful attention, I would have seen what was happening. The ideal fix would cause give the focus to the next successive image after a delete. But another reasonable focus might be to at least have the delete function check to see if it's deleting 0 images and abort before it segfaults.
This crash is 100% reproducible in the gthumb-2-12 git branch, but seems to be fixed in git master (2.13.x). - Mike