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 419547 - crash in Power Manager: downloading sw
crash in Power Manager: downloading sw
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-17 23:05 UTC by timothy_force
Modified: 2007-03-20 21:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description timothy_force 2007-03-17 23:05:57 UTC 
What were you doing when the application crashed?
downloading sw


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.2990.fc7 #1 SMP Thu Mar 15 19:22:31 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: 49696768 vsize: 49696768 resident: 6049792 share: 4395008 rss: 6049792 rss_rlim: 4294967295
CPU usage: start_time: 1174169368 rtime: 18 utime: 10 stime: 8 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 -1208826144 (LWP 2953)]
(no debugging symbols found)
0x00fda402 in __kernel_vsyscall ()

+ Trace 119566

Thread 1 (Thread -1208826144 (LWP 2953))

  • #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 (2320 sec old) ---------------------
Repository core is listed more than once in the configuration
Repository development-debuginfo is listed more than once in the configuration
Repository updates-source is listed more than once in the configuration
Repository extras-development is listed more than once in the configuration
Repository extras-development-source is listed more than once in the configuration
Repository updates-testing-debuginfo is listed more than once in the configuration
Repository extras-development-debuginfo is listed more than once in the configuration
Repository updates-testing is listed more than once in the configuration
Repository extras is listed more than once in the configuration
Repository 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 extras-debuginfo is listed more than once in the configuration
Repository core-debuginfo is listed more than once in the configuration
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-17 23:20:31 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:12:20 UTC 

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