GNOME Bugzilla – Bug 421188
crash in Power Manager: I was away from my compu...
Last modified: 2007-03-21 19:55:28 UTC
What were you doing when the application crashed? I was away from my computer, I came back unlocked the screen (screensaver activated) and this showed up. Distribution: Unknown Gnome Release: 2.18.0 2007-03-20 (FreeBSD GNOME Project) BugBuddy Version: 2.18.0 System: FreeBSD 7.0-CURRENT FreeBSD 7.0-CURRENT #4: Mon Mar 12 22:20:38 EDT 2007 sean@chester.taint:/usr/obj/usr/src/sys/CHESTER i386 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 44528 vsize: 44528 resident: 14676 share: 39690172 rss: 14676 rss_rlim: 3669 CPU usage: start_time: 0 rtime: 266 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/bin/gnome-power-manager' (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)...(no debugging symbols found)...[New LWP 100121] (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)...[Switching to LWP 100121] 0x290d4b19 in wait4 () from /lib/libc.so.7
+ Trace 120890
Thread 1 (LWP 100121)
Output of custom script "gnome-power-bugreport.sh": Distro version: Kernel version: 7.0-CURRENT HAL version: 0.5.8 System manufacturer: missing System version: missing System product: missing AC adapter present: no Battery present: no Laptop panel present: no CPU scaling present: no Battery Information: ----------- .xsession-errors (998774 sec old) --------------------- Window manager warning: The application 'gnome-panel' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. The application 'nautilus' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. (gnome-panel:1230): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:1230): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:1230): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
*** This bug has been marked as a duplicate of 420419 ***