Bug 411814 – crash in System Log: running foxfox and gaim

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 411814 - crash in System Log: running foxfox and gaim


Summary:	crash in System Log: running foxfox and gaim


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-02-25 06:59 UTC by piggestpig
Modified:	2007-02-25 13:04 UTC

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

Description piggestpig 2007-02-25 06:59:21 UTC

Version: 2.16.1

What were you doing when the application crashed?
running foxfox and gaim


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

Memory status: size: 73441280 vsize: 0 resident: 73441280 share: 0 rss: 14528512 rss_rlim: 0
CPU usage: start_time: 1172386637 rtime: 0 utime: 103 stime: 0 cutime:86 cstime: 0 timeout: 17 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 -1224755008 (LWP 4595)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113704

Thread 1 (Thread -1224755008 (LWP 4595))

#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-02-25 13:04:00 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 ***