Bug 421314 – crash in Power Manager: unlocking the screensave...

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 421314 - crash in Power Manager: unlocking the screensave...


Summary:	crash in Power Manager: unlocking the screensave...


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-22 02:51 UTC by bcwise
Modified:	2007-03-23 22:38 UTC

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

Description bcwise 2007-03-22 02:51:11 UTC

What were you doing when the application crashed?
unlocking the screensaver


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

Memory status: size: 85131264 vsize: 85131264 resident: 6131712 share: 4390912 rss: 6131712 rss_rlim: 4294967295
CPU usage: start_time: 1174527306 rtime: 8 utime: 5 stime: 3 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 -1208830240 (LWP 3019)]
0x00a9b402 in __kernel_vsyscall ()

+ Trace 120993

Thread 1 (Thread -1208830240 (LWP 3019))

#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 (475 sec old) ---------------------
(gnome-terminal:3264): Vte-WARNING **: Can not find appropiate font for character U+ac00.
(gnome-terminal:3264): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:3264): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:3264): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:3264): Vte-WARNING **: Can not find appropiate font for character U+ac10.
error getting update info:  global name 'dlpkgs' is not defined
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-23 22:38:04 UTC


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