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 419859 - crash in Power Manager: Downloading xen kernel
crash in Power Manager: Downloading xen kernel
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 19:57 UTC by timothy_force
Modified: 2007-03-20 21:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description timothy_force 2007-03-18 19:57:38 UTC 
What were you doing when the application crashed?
Downloading xen kernel


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 49713152 vsize: 49713152 resident: 6062080 share: 4395008 rss: 6062080 rss_rlim: 4294967295
CPU usage: start_time: 1174242870 rtime: 18 utime: 9 stime: 9 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 -1209100576 (LWP 2983)]
(no debugging symbols found)
0x00aa7402 in __kernel_vsyscall ()

+ Trace 119824

Thread 1 (Thread -1209100576 (LWP 2983))

  • #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 (921 sec old) ---------------------
Checking deps for libstdc++.i386 0-4.1.2-4 - None
Checking deps for cpp.i386 0-4.1.2-4 - None
Checking deps for java-1.5.0-gcj.i386 0-1.5.0.0-4.fc7 - u
Checking deps for sinjdoc.i386 0-0.5-1.fc7 - u
Checking deps for libgcc.i386 0-4.1.2-5 - u
Checking deps for gcc.i386 0-4.1.2-5 - u
Checking deps for libstdc++-devel.i386 0-4.1.2-5 - u
Checking deps for gcc-c++.i386 0-4.1.2-4 - None
Checking deps for libgcj.i386 0-4.1.2-4 - None
Checking deps for libstdc++.i386 0-4.1.2-5 - u
Checking deps for cpp.i386 0-4.1.2-5 - u
Checking deps for libgomp.i386 0-4.1.2-5 - u
Checking deps for libgfortran.i386 0-4.1.2-5 - u
Checking deps for gcc-gfortran.i386 0-4.1.2-5 - u
Checking deps for libstdc++-devel.i386 0-4.1.2-4 - None
--------------------------------------------------
Comment 1 Christian Kirbach 2007-03-18 20:03:10 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:10:44 UTC 

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