After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 419771 - crash in Power Manager: PC was sitting idle. Af...
crash in Power Manager: PC was sitting idle. Af...
Status: RESOLVED DUPLICATE of bug 420419
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.17.x
Other All
: High critical
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-03-18 16:12 UTC by pleasesendmespamhere
Modified: 2007-03-20 21:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description pleasesendmespamhere 2007-03-18 16:12:23 UTC
What were you doing when the application crashed?
PC was sitting idle.  After long enough idle time, display went black.  Upon touching the mouse to resume, bug tool popped.


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.18.0 2007-03-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.2997.fc7 #1 SMP Fri Mar 16 22:29:02 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 64581632 vsize: 64581632 resident: 5861376 share: 4280320 rss: 5861376 rss_rlim: 4294967295
CPU usage: start_time: 1174233035 rtime: 12 utime: 8 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-power-manager'

(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 -1208564000 (LWP 2946)]
(no debugging symbols found)
0x005eb402 in __kernel_vsyscall ()

Thread 1 (Thread -1208564000 (LWP 2946))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 ??
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 ??
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #13 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #18 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #19 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 ??
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 main
  • #0 __kernel_vsyscall




----------- .xsession-errors (1194 sec old) ---------------------
** (nm-applet:2934): WARNING **: <WARN>  hal_net_physdev_cb(): dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.Hal was not provided by any .service files
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
(gnome-panel:2912): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell'
(gnome-panel:2912): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed
error getting update info:  Cannot find a valid baseurl for repo: development
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-20 21:12:00 UTC

*** This bug has been marked as a duplicate of 420419 ***