GNOME Bugzilla – Bug 373638
crash in Configuration Editor: searching Gconf-editor ...
Last modified: 2007-04-06 13:33:27 UTC
Version: 2.16.0 What were you doing when the application crashed? searching Gconf-editor (both search options checked) for "samba", after a search for smb. Two instances of Gconf-editor were open. 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.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- (gnome-panel:2725): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Thank you for using tvtime. Running tvtime 1.0.1. Reading configuration from /etc/tvtime/tvtime.xml Reading configuration from /root/.tvtime/tvtime.xml Thank you for using tvtime. Running tvtime 1.0.1. Reading configuration from /etc/tvtime/tvtime.xml Reading configuration from /root/.tvtime/tvtime.xml ** (bug-buddy:22865): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 305516544 vsize: 305516544 resident: 14819328 share: 8658944 rss: 14819328 rss_rlim: -1 CPU usage: start_time: 1163206943 rtime: 700 utime: 640 stime: 60 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gconf-editor' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496412352 (LWP 22352)] (no debugging symbols found) 0x0000003ec760d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 85242
Thread 1 (Thread 46912496412352 (LWP 22352))
*** Bug 380213 has been marked as a duplicate of this bug. ***
confirming as per duplicate
*** This bug has been marked as a duplicate of 361137 ***
*** Bug 407588 has been marked as a duplicate of this bug. ***
*** Bug 411864 has been marked as a duplicate of this bug. ***