GNOME Bugzilla – Bug 501115
crash in System Log: This was one of my first...
Last modified: 2007-12-03 16:28:32 UTC
Version: 2.20.0.1 What were you doing when the application crashed? This was one of my first attempts to run Gnome. I had selected from the top menu Applications/System Tools/System Log, and was trying to look at the maillog Distribution: Unknown Gnome Release: 2.20.1 2007-11-30 (FreeBSD GNOME Project) BugBuddy Version: 2.20.1 System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Tue Aug 14 20:37:02 SAST 2007 mlawrie@58havenvillage.dyndns.org:/usr/src/sys/i386/compile/HENNOPS i386 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 42908 vsize: 42908 resident: 15884 share: 40958080 rss: 15884 rss_rlim: 3971 CPU usage: start_time: 0 rtime: 1408 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 128 Backtrace was generated from '/usr/local/bin/gnome-system-log' (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)...(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 LWP 100135] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100135] 0x8908d6cd in wait4 () from /lib/libc.so.6
+ Trace 180467
----------- .xsession-errors --------------------- Initializing gnome-mount extension ** (nautilus:28136): WARNING **: Cannot connect to system bus: org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory ** (nautilus:28136): WARNING **: Could not initialize hal context Shutting down gnome-mount extension seahorse nautilus module initialized glibtop: geom_stats_open(): Permission denied (gnome-system-log:28521): Gtk-CRITICAL **: _gtk_tree_view_find_path: assertion `node != NULL' failed warning: Unable to get location for thread creation breakpoint: generic error /usr/local/share/bug-buddy/gdb-cmd:2: Error in sourced command file: Previous frame inner to this frame (corrupt stack?) --------------------------------------------------
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 488119 ***