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 418755 - crash in Power Manager: closing lid
crash in Power Manager: closing lid
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-15 22:11 UTC by veldema
Modified: 2007-03-20 21:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description veldema 2007-03-15 22:11:16 UTC 
What were you doing when the application crashed?
closing lid



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.2987.fc7 #1 SMP Wed Mar 14 17:53:49 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 309161984 vsize: 309161984 resident: 9732096 share: 6250496 rss: 9732096 rss_rlim: 18446744073709551615
CPU usage: start_time: 1173995380 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912528396304 (LWP 2864)]
(no debugging symbols found)
0x0000003ba920d805 in waitpid () from /lib64/libpthread.so.0

+ Trace 118955

Thread 1 (Thread 46912528396304 (LWP 2864))

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




----------- .xsession-errors (28 sec old) ---------------------
Checking for XComposite extension               : passed (v0.3)
Checking for XDamage extension                  : passed
Checking for RandR extension                    : passed
Checking for XSync extension                    : passed
Checking Screen 0 ...
Checking for GLX_SGIX_fbconfig                  : passed
Checking for GLX_EXT_texture_from_pixmap        : passed
Checking for non power of two texture support   : passed
Checking maximum texture size                   : passed (4096x4096)
Reloading options
DCOP: register 'anonymous-3294' -> number of clients is now 2
DCOP:  'anonymous-3294' now known as 'kwin'
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-15 22:23:22 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Richard Hughes 2007-03-20 21:17:18 UTC 

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