Bug 420895 – crash in Power Manager: crash after unlock scree...

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 420895 - crash in Power Manager: crash after unlock scree...


Summary:	crash in Power Manager: crash after unlock scree...


Status:	RESOLVED DUPLICATE of bug 420419

Product:	gnome-power-manager
Classification:	Deprecated
Component:	gnome-power-manager
Version:	2.17.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Power Manager Maintainer(s)
QA Contact:	GNOME Power Manager Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-21 08:28 UTC by sszzz
Modified:	2007-03-21 19:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description sszzz 2007-03-21 08:28:26 UTC

What were you doing when the application crashed?
crash after unlock screen


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.18.0 2007-03-19 (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: Tango

Memory status: size: 69910528 vsize: 69910528 resident: 5877760 share: 4362240 rss: 5877760 rss_rlim: 4294967295
CPU usage: start_time: 1174464315 rtime: 13 utime: 8 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 -1208224032 (LWP 2690)]
(no debugging symbols found)
0x0082b402 in __kernel_vsyscall ()

+ Trace 120665

Thread 1 (Thread -1208224032 (LWP 2690))

#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 (1000 sec old) ---------------------
(gnome-terminal:2904): Vte-WARNING **: Can not find appropiate font for character U+ac00.
(gnome-terminal:2904): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:2904): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:2904): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:2904): Vte-WARNING **: Can not find appropiate font for character U+ac10.
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-21 19:57:15 UTC


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