GNOME Bugzilla – Bug 115730
gthumb crashes in several folders while reading thumbnails
Last modified: 2004-12-22 21:47:04 UTC
Package: gthumb Severity: major Version: 2.1.2 Synopsis: gthumb crashes in several folders while reading thumbnails Bugzilla-Product: gthumb Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.1) Description: Description of Problem: gthumb crashes while reading thumbnails in imagefolder. strace gives something like "file not found" on a socket /tmp/.X11-unix/X0 Steps to reproduce the problem: 1. start gthumb 2. change to a directory with images (in my case: 56 images downloaded with gtkam from canon digital ixus 400) 3. crashes while reading/building the thumbs Actual Results: crash. Expected Results: showing thumbs How often does this happen? every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gthumb' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 830)] [New Thread 32769 (LWP 831)] [New Thread 16386 (LWP 832)] [New Thread 32771 (LWP 833)] [New Thread 49156 (LWP 834)] [New Thread 65541 (LWP 835)] [New Thread 81926 (LWP 836)] [New Thread 98311 (LWP 837)] [New Thread 114696 (LWP 839)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40eeeaf9 in wait4 () from /lib/libc.so.6
+ Trace 38063
Thread 1 (Thread 16384 (LWP 830))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-22 14:07 ------- The original reporter (jens@gecius.de) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, paolo.bacch@tin.it.
Appears to be a unique stack trace, according to the simple-dup-finder. Marking priority->high & severity->critical (it's a crasher), adding bugsquad keyword, and marking as new.