GNOME Bugzilla – Bug 393467
crash in gtk_file_info_get_is_folder
Last modified: 2007-01-31 10:28:35 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 System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:31:29 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors (8925 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... -------------------------------------------------- Memory status: size: 125300736 vsize: 0 resident: 125300736 share: 0 rss: 26099712 rss_rlim: 0 CPU usage: start_time: 1168081310 rtime: 0 utime: 3455 stime: 0 cutime:3185 cstime: 0 timeout: 270 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/glade-2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208600880 (LWP 28922)] (no debugging symbols found) 0x005da402 in __kernel_vsyscall ()
+ Trace 99827
Thread 1 (Thread -1208600880 (LWP 28922))
*** Bug 395938 has been marked as a duplicate of this bug. ***
looks like a gtk+ issue
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 363472 ***