GNOME Bugzilla – Bug 430717
crash in Services: start the service from g...
Last modified: 2007-04-22 12:08:17 UTC
Version: 2.14.0 What were you doing when the application crashed? start the service from gnome services menu Distribution: Unknown Gnome Release: 2.16.3 2007-02-19 (FreeBSD GNOME Project) BugBuddy Version: 2.16.1 System: FreeBSD 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #0: Wed Mar 14 17:25:45 ART 2007 sebastian@amd.vtechnologies.com.ar:/usr/obj/usr/src/sys/VTGENERIC amd64 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled Memory status: size: 4308992 vsize: 4308992 resident: 21549056 share: 49987988 rss: 21549056 rss_rlim: 5261 CPU usage: start_time: 0 rtime: 528564 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 1000000 Backtrace was generated from '/usr/local/bin/services-admin' (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 100115] (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)...[Switching to LWP 100115] 0x000000080511b3ca in wait4 () from /lib/libc.so.6
+ Trace 128552
----------- .xsession-errors --------------------- (services-admin:1325): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (services-admin:1325): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (bug-buddy:1926): WARNING **: Couldn't load icon for Bonobo Component Browser ** (bug-buddy:1926): WARNING **: Couldn't load icon for Open Folder This libgtop was compiled on FreeBSD 6.2-RELEASE amd64 If you see strange problems caused by it, you should recompile libgtop and dependent applications warning: Unable to get location for thread creation breakpoint: generic error /usr/local/share/gnome/bug-buddy/gdb-cmd:1: Error in sourced command file: Error accessing memory address 0x800000000000: Bad address. --------------------------------------------------
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 359286 ***