Bug 408738 – crash in System Log:

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 408738 - crash in System Log:


Summary:	crash in System Log:


Status:	RESOLVED DUPLICATE of bug 364106

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-02-16 22:06 UTC by dinrandir
Modified:	2007-02-18 13:35 UTC

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

Description dinrandir 2007-02-16 22:06:05 UTC

Version: 2.16.1

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 32890880 vsize: 0 resident: 32890880 share: 0 rss: 14012416 rss_rlim: 0
CPU usage: start_time: 1171663276 rtime: 0 utime: 31 stime: 0 cutime:27 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224681280 (LWP 9657)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 111362

Thread 1 (Thread -1224681280 (LWP 9657))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 ??
#6 _IO_stdin_used
#7 ??
#8 ??
#0 __kernel_vsyscall

Comment 1 Susana 2007-02-16 23:01:13 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!

Comment 2 dinrandir 2007-02-18 01:19:14 UTC

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 33423360 vsize: 0 resident: 33423360 share: 0 rss: 14544896 rss_rlim: 0
CPU usage: start_time: 1171760798 rtime: 0 utime: 30 stime: 0 cutime:28 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225201472 (LWP 12522)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 111644

Thread 1 (Thread -1225201472 (LWP 12522))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 string_get_date_string
at logrtns.c line 136
#5 log_read_dates
at logrtns.c line 253
#6 log_open
at logrtns.c line 422
#7 log_open
at logrtns.c line 431
#8 logview_add_logs_from_names
at logview.c line 251
#9 main
at main.c line 179
#10 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#11 _start
#0 __kernel_vsyscall

Comment 3 André Klapper 2007-02-18 13:35:54 UTC

nice trace, thanks a lot!
this is the same issue as bug 364106


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