Bug 401468 – crash in Screen Resolution: opening screen resolutio...

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 401468 - crash in Screen Resolution: opening screen resolutio...


Summary:	crash in Screen Resolution: opening screen resolutio...


Status:	RESOLVED INCOMPLETE

Product:	gnome-control-center
Classification:	Core
Component:	Display
Version:	2.17.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-27 21:11 UTC by romstev
Modified:	2007-02-28 21:13 UTC

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

Description romstev 2007-01-27 21:11:39 UTC

Version: 2.17.90

What were you doing when the application crashed?
opening screen resolution tool in new Gnome Control Center




Distribution: Fedora Core release 6.90 (Rawhide)
Gnome Release: 2.17.90 2007-01-21 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2914.fc7 #1 SMP Fri Jan 26 18:42:25 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled

Memory status: size: 54145024 vsize: 0 resident: 54145024 share: 0 rss: 11333632 rss_rlim: 0
CPU usage: start_time: 1169932161 rtime: 0 utime: 14 stime: 0 cutime:10 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-display-properties'

(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 -1208346400 (LWP 4293)]
(no debugging symbols found)
0x0090b402 in __kernel_vsyscall ()

+ Trace 105775

Thread 1 (Thread -1208346400 (LWP 4293))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libgtk-x11-2.0.so.0
#5 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#6 ??
from /lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /lib/libgobject-2.0.so.0
#8 ??
from /lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#26 ??
from /lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /lib/libgobject-2.0.so.0
#28 ??
from /lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#30 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#36 ??
from /lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /lib/libgobject-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#40 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#47 ??
from /lib/libgobject-2.0.so.0
#48 g_closure_invoke
from /lib/libgobject-2.0.so.0
#49 ??
from /lib/libgobject-2.0.so.0
#50 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#51 g_signal_emit
from /lib/libgobject-2.0.so.0
#52 gtk_widget_show
from /usr/lib/libgtk-x11-2.0.so.0
#53 main
#0 __kernel_vsyscall



----------- .xsession-errors (9 sec old) ---------------------
closing
closing
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5a00003 (Yum Extend)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
** (GNOME Control Center:4288): WARNING **: key not found [/desktop/gnome/applications/main-menu/cc_actions_list]
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------

Comment 1 Jens Granseuer 2007-01-27 21:15:49 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!

We'd need debugging symbols for control-center, gtk+, and glib.

Comment 2 Bruno Boaventura 2007-02-28 21:13:25 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!