Bug 500369 – crash in System Log: I think I accidentally d...

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 500369 - crash in System Log: I think I accidentally d...


Summary:	crash in System Log: I think I accidentally d...


Status:	RESOLVED DUPLICATE of bug 355887

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-11-29 07:21 UTC by peterchong888
Modified:	2007-11-30 00:42 UTC

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

Description peterchong888 2007-11-29 07:21:40 UTC

Version: 2.18.1

What were you doing when the application crashed?
I think I accidentally dragged "messages" and the viewer just crashed


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 93237248 vsize: 93237248 resident: 70811648 share: 17096704 rss: 70811648 rss_rlim: 4294967295
CPU usage: start_time: 1188453951 rtime: 2140 utime: 2064 stime: 76 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 -1208138016 (LWP 3116)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 180055

Thread 1 (Thread -1208138016 (LWP 3116))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strrchr
from /lib/libc.so.6
#5 logview_repaint
#6 logview_select_log
#7 ??
#8 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 ??
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 ??
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#21 g_signal_emit
from /lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgdk-x11-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_loop_run
from /lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 main
#0 __kernel_vsyscall

Comment 1 Susana 2007-11-30 00:42:12 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 355887 ***