Bug 400267 – crash in System Log: running mythtv

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 400267 - crash in System Log: running mythtv


Summary:	crash in System Log: running mythtv


Status:	RESOLVED DUPLICATE of bug 366458

Product:	gnome-utils
Classification:	Deprecated
Component:	logview
Version:	2.16.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-01-24 16:47 UTC by dzien
Modified:	2007-01-24 18:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description dzien 2007-01-24 16:47:01 UTC

Version: 2.16.0

What were you doing when the application crashed?
running mythtv


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 81317888 vsize: 0 resident: 81317888 share: 0 rss: 10719232 rss_rlim: 0
CPU usage: start_time: 1169657260 rtime: 0 utime: 10 stime: 0 cutime:8 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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 -1208882976 (LWP 3273)]
(no debugging symbols found)
0x00abe402 in __kernel_vsyscall ()

+ Trace 104892

Thread 1 (Thread -1208882976 (LWP 3273))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_main_quit
#5 gtk_main_quit
#6 gtk_main_quit
#7 gtk_main_quit
#8 gtk_main_quit
#9 gtk_main_quit
#10 __libc_start_main
from /lib/libc.so.6
#11 gtk_main_quit
#0 __kernel_vsyscall

Comment 1 palfrey 2007-01-24 18:46:20 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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