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 420091 - crash in Power Manager: Machine running idle, lo...
crash in Power Manager: Machine running idle, lo...
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-19 12:25 UTC by Jan Kratochvil
Modified: 2007-03-20 21:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jan Kratochvil 2007-03-19 12:25:48 UTC
What were you doing when the application crashed?
Machine running idle, locked screen - black screensaver.


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.19-1.2898.2.3.fc7xen #1 SMP Wed Jan 24 21:28:28 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 67080192 vsize: 67080192 resident: 5824512 share: 4902912 rss: 5824512 rss_rlim: 4294967295
CPU usage: start_time: 1174226153 rtime: 60 utime: 33 stime: 27 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208744224 (LWP 3309)]
0x00268402 in __kernel_vsyscall ()

Thread 1 (Thread -1208744224 (LWP 3309))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 IA__g_cclosure_marshal_VOID__BOOLEAN
    at gmarshal.c line 111
  • #6 IA__g_closure_invoke
    at gclosure.c line 490
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #8 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #9 IA__g_signal_emit
    at gsignal.c line 2243
  • #10 ??
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #13 IA__g_closure_invoke
    at gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #16 IA__g_signal_emit
    at gsignal.c line 2243
  • #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 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #21 g_main_context_iterate
    at gmain.c line 2677
  • #22 IA__g_main_loop_run
    at gmain.c line 2881
  • #23 main
  • #0 __kernel_vsyscall




----------- .xsession-errors (38540 sec old) ---------------------
(gnome-terminal:3724): Vte-WARNING **: Can not find appropiate font for character U+2c22.
(gnome-terminal:3724): Vte-WARNING **: Can not find appropiate font for character U+2c5b.
(gnome-terminal:8495): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:3724): Vte-WARNING **: Can not find appropiate font for character U+4c20.
(gnome-terminal:3724): Vte-WARNING **: Can not find appropiate font for character U+2920.
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-19 12:34:17 UTC
Can you install the gnome-power-manager-debuginfo package and then reproduce please? I'm desparate for someone to provice a proper stacktrace for this bug.

Thanks!

Richard.
Comment 2 Richard Hughes 2007-03-20 21:10:09 UTC

*** This bug has been marked as a duplicate of 420419 ***
Comment 3 Jan Kratochvil 2007-03-20 21:29:54 UTC
Install but I have no reproducible testcase anyway.
It is a pity and surprising to me that the Gnome Bug submitted does not store the core file (by the GDB `gcore' command). :-(