Bug 506590 – crash in System Log: Setting Display configra...

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 506590 - crash in System Log: Setting Display configra...


Summary:	crash in System Log: Setting Display configra...


Status:	RESOLVED DUPLICATE of bug 442846

Product:	gnome-utils
Classification:	Deprecated
Component:	logview
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-utils Maintainers
QA Contact:	gnome-utils Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-31 16:02 UTC by hnhn
Modified:	2008-02-13 10:26 UTC

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

Description hnhn 2007-12-31 16:02:34 UTC

Version: 2.18.0

What were you doing when the application crashed?
Setting Display configration from system panel


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 48726016 vsize: 48726016 resident: 17862656 share: 11034624 rss: 17862656 rss_rlim: 4294967295
CPU usage: start_time: 1199116320 rtime: 107 utime: 99 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/sbin/gnome-system-log'

(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 -1208211744 (LWP 3097)]
(no debugging symbols found)
0x00657402 in __kernel_vsyscall ()

+ Trace 183642

Thread 1 (Thread -1208211744 (LWP 3097))

#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 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
from /usr/lib/libgnomeui-2.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 ??
from /usr/lib/libgnomeui-2.so.0
#11 _SmcProcessMessage
from /usr/lib/libSM.so.6
#12 IceProcessMessages
from /usr/lib/libICE.so.6
#13 ??
from /usr/lib/libgnomeui-2.so.0
#14 ??
from /lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_loop_run
from /lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 main
#0 __kernel_vsyscall

Comment 1 Gianluca Borello 2008-02-13 10:26:13 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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