Bug 422710 – crash in System Log: my computer get locked w...

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 422710 - crash in System Log: my computer get locked w...


Summary:	crash in System Log: my computer get locked w...


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-03-25 17:58 UTC by alvaro
Modified:	2007-03-27 20:31 UTC

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

Description alvaro 2007-03-25 17:58:21 UTC

Version: 2.16.1

What were you doing when the application crashed?
my computer get locked with the log viewer and a terminal open. I restarted by unplugging the cable and now any time I start the program it crashes.


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

Memory status: size: 30855168 vsize: 0 resident: 30855168 share: 0 rss: 11382784 rss_rlim: 0
CPU usage: start_time: 1010062248 rtime: 0 utime: 51 stime: 0 cutime:47 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 -1225111360 (LWP 5120)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 122125

Thread 1 (Thread -1225111360 (LWP 5120))

#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 Susana 2007-03-27 20:31:16 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 364106 ***