Bug 395994 – crash in System Log: Just started it after a ...

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 395994 - crash in System Log: Just started it after a ...


Summary:	crash in System Log: Just started it after a ...


Status:	RESOLVED DUPLICATE of bug 356211

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-13 03:34 UTC by sultnwoz
Modified:	2007-01-13 12:35 UTC

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

Description sultnwoz 2007-01-13 03:34:58 UTC

Version: 2.16.1

What were you doing when the application crashed?
Just started it after a fresh logon!


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

Memory status: size: 36724736 vsize: 0 resident: 36724736 share: 0 rss: 13852672 rss_rlim: 0
CPU usage: start_time: 1168659258 rtime: 0 utime: 151 stime: 0 cutime:139 cstime: 0 timeout: 12 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 -1225546064 (LWP 5055)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 101705

Thread 1 (Thread -1225546064 (LWP 5055))

#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 ??
#7 ??
#8 g_free
from /usr/lib/libglib-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#0 __kernel_vsyscall

Comment 1 Bruno Boaventura 2007-01-13 12:35:08 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 356211 ***