Bug 430601 – crash in System Log: Datei mail.info ueber da...

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 430601 - crash in System Log: Datei mail.info ueber da...


Summary:	crash in System Log: Datei mail.info ueber da...


Status:	RESOLVED DUPLICATE of bug 402754

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-04-17 09:35 UTC by matrox
Modified:	2007-04-18 02:18 UTC

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

Description matrox 2007-04-17 09:35:02 UTC

Version: 2.16.1

What were you doing when the application crashed?
Datei mail.info ueber das dateimenue geschlossen.


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

Memory status: size: 58454016 vsize: 0 resident: 58454016 share: 0 rss: 16228352 rss_rlim: 0
CPU usage: start_time: 1176802377 rtime: 0 utime: 90 stime: 0 cutime:86 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 -1224742720 (LWP 5269)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128475

Thread 1 (Thread -1224742720 (LWP 5269))

#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 ??
from /usr/lib/libgthread-2.0.so.0
#6 ??
#7 ??
#8 ??
from /usr/lib/libgthread-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 ??
#13 ??
#14 __pthread_mutex_unlock_usercnt
from /lib/tls/i686/cmov/libpthread.so.0
#15 ??
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 __pthread_mutex_unlock_usercnt
from /lib/tls/i686/cmov/libpthread.so.0
#18 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
#24 ??
#25 _IO_stdin_used
#26 ??
#27 ??
#0 __kernel_vsyscall

Comment 1 Pedro Villavicencio 2007-04-18 02:18:03 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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