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 421201 - crash in Power Manager: unlocking the screen (us...
crash in Power Manager: unlocking the screen (us...
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-21 20:20 UTC by m.manuta
Modified: 2007-03-23 22:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description m.manuta 2007-03-21 20:20:15 UTC 
What were you doing when the application crashed?
unlocking the screen (using screen saver)


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

System: Linux 2.6.20-1.2999.fc7 #1 SMP Mon Mar 19 20:20:42 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: 51888128 vsize: 51888128 resident: 9764864 share: 7094272 rss: 9764864 rss_rlim: 4294967295
CPU usage: start_time: 1174506543 rtime: 16 utime: 11 stime: 5 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 -1208981792 (LWP 2580)]
(no debugging symbols found)
0x00c7a402 in __kernel_vsyscall ()

+ Trace 120901

Thread 1 (Thread -1208981792 (LWP 2580))

  • #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 (13 sec old) ---------------------
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
** Message: Found best visual for GL: 0x25
(evolution:2670): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-23 22:37:44 UTC 

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