Bug 459224 – crash in System Log: Clicked on "cron"

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 459224 - crash in System Log: Clicked on "cron"


Summary:	crash in System Log: Clicked on "cron"


Status:	RESOLVED DUPLICATE of bug 449164

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-07-22 06:47 UTC by john
Modified:	2007-07-27 00:28 UTC

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

Description john 2007-07-22 06:47:32 UTC

Version: 2.18.1

What were you doing when the application crashed?
Clicked on "cron"


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.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 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: 46022656 vsize: 46022656 resident: 22056960 share: 16986112 rss: 22056960 rss_rlim: 4294967295
CPU usage: start_time: 1185085329 rtime: 1304 utime: 1224 stime: 80 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 -1208817952 (LWP 4546)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 149740

Thread 1 (Thread -1208817952 (LWP 4546))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gtk_main_quit
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 gtk_main_quit
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 gtk_main_quit
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_main_quit
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_main_quit
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_main_quit
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_main_quit
from /lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 gtk_main_quit
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 gtk_main_quit
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 gtk_main_quit
from /usr/lib/libgdk-x11-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 gtk_main_quit
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 Pedro Villavicencio 2007-07-27 00:28:22 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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