Bug 418604 – crash in Power Manager: Recovering from a blank ...

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 418604 - crash in Power Manager: Recovering from a blank ...


Summary:	crash in Power Manager: Recovering from a blank ...


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-15 15:12 UTC by Tanmay Kumar
Modified:	2007-03-20 21:17 UTC

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

Description Tanmay Kumar 2007-03-15 15:12:13 UTC

What were you doing when the application crashed?
Recovering from a blank screen after a period of inactivity.


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.2986.fc7 #1 SMP Tue Mar 13 17:11:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 49094656 vsize: 49094656 resident: 9060352 share: 6590464 rss: 9060352 rss_rlim: 4294967295
CPU usage: start_time: 1173969577 rtime: 20 utime: 15 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 -1208383776 (LWP 4454)]
(no debugging symbols found)
0x00941402 in __kernel_vsyscall ()

+ Trace 118846

Thread 1 (Thread -1208383776 (LWP 4454))

#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 (1379 sec old) ---------------------
Checking deps for dialog.i386 0-1.1-1.20070227svn.fc7 - u
Checking deps for gnome-screensaver.i386 0-2.18.0-1.fc7 - u
Checking deps for policycoreutils.i386 0-2.0.7-2.fc7 - None
Checking deps for xen-libs.i386 0-3.0.4-9.fc7 - u
Checking deps for gnome-screensaver.i386 0-2.17.8-1.fc7 - None
Checking deps for tomcat5-jsp-2.0-api.i386 0-5.5.17-6jpp.2 - None
Checking deps for evolution-data-server-devel.i386 0-1.10.0-1.fc7 - None
Checking deps for nc.i386 0-1.84-12.fc7 - u
Checking deps for firstboot.noarch 0-1.4.32-1.fc7 - u
Checking deps for ed.i386 0-0.5-1 - u
Checking deps for redhat-rpm-config.noarch 0-8.0.45-12.fc7 - None
Checking deps for evolution-data-server.i386 0-1.10.0-1.fc7 - None
Checking deps for a2ps.i386 0-4.13b-65.fc7 - u
Checking deps for ghostscript.i386 0-8.15.4-1.fc7 - u
libGL warning: 3D driver claims to not support visual 0x67
--------------------------------------------------

Comment 1 Richard Hughes 2007-03-15 16:47:50 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:17:20 UTC


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