GNOME Bugzilla – Bug 389087
2.16: crash in in strcmp / gtk_hsv_new
Last modified: 2007-09-28 15:11:09 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 124952576 vsize: 0 resident: 124952576 share: 0 rss: 13737984 rss_rlim: 0 CPU usage: start_time: 1166925115 rtime: 0 utime: 18 stime: 0 cutime:16 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208498480 (LWP 3078)] (no debugging symbols found) 0x00cec402 in __kernel_vsyscall ()
+ Trace 96596
Thread 1 (Thread -1208498480 (LWP 3078))
*** Bug 389088 has been marked as a duplicate of this bug. ***
*** Bug 389089 has been marked as a duplicate of this bug. ***
*** Bug 389090 has been marked as a duplicate of this bug. ***
Unfortunately, the stack traces are missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could someone of the reporters please help fixing this by installing some debugging packages [1], start nautilus as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for nautilus, glib, gtk, pango, gnome-vfs and libgnome(ui), as far as provided by your distributor. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 416130 has been marked as a duplicate of this bug. ***
*** Bug 417346 has been marked as a duplicate of this bug. ***
*** Bug 434808 has been marked as a duplicate of this bug. ***
*** Bug 416286 has been marked as a duplicate of this bug. ***
only 2.16 crashes so far, this is most probably the same issue as bug 377443. *** This bug has been marked as a duplicate of 377443 ***
*** Bug 480741 has been marked as a duplicate of this bug. ***