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 421481 - crash in Power Manager: unlocking the screensave...
crash in Power Manager: unlocking the screensave...
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-22 13:44 UTC by bcwise
Modified: 2007-03-23 22:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bcwise 2007-03-22 13:44:21 UTC 
What were you doing when the application crashed?
unlocking the screensaver


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

System: Linux 2.6.20-1.3003.fc7 #1 SMP Wed Mar 21 18:57:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 88125440 vsize: 88125440 resident: 9728000 share: 6471680 rss: 9728000 rss_rlim: 4294967295
CPU usage: start_time: 1174565514 rtime: 18 utime: 11 stime: 7 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 -1208166688 (LWP 3734)]
0x00e2f402 in __kernel_vsyscall ()

+ Trace 121132

Thread 1 (Thread -1208166688 (LWP 3734))

  • #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 (855 sec old) ---------------------
Repository updates-testing is listed more than once in the configuration
Repository extras-development-debuginfo is listed more than once in the configuration
Repository core-source is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository updates-testing-debuginfo is listed more than once in the configuration
Repository updates is listed more than once in the configuration
Repository legacy-updates is listed more than once in the configuration
Repository updates-testing-source is listed more than once in the configuration
Repository legacy-testing is listed more than once in the configuration
Repository development-source is listed more than once in the configuration
Repository development is listed more than once in the configuration
Repository core-debuginfo is listed more than once in the configuration
** (gnome-system-monitor:8051): WARNING **: SELinux was found but is not enabled.
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-23 22:38:50 UTC 

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