Bug 357378 – crash in Evolution: opened in fwvm

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 357378 - crash in Evolution: opened in fwvm


Summary:	crash in Evolution: opened in fwvm


Status:	RESOLVED DUPLICATE of bug 353430

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Harish Krishnaswamy
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-23 21:44 UTC by weka
Modified:	2006-09-23 22:14 UTC

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

Description weka 2006-09-23 21:44:17 UTC

What were you doing when the application crashed?
opened in fwvm


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 99164160 vsize: 0 resident: 99164160 share: 0 rss: 25042944 rss_rlim: 0
CPU usage: start_time: 1159047822 rtime: 0 utime: 116 stime: 0 cutime:110 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

(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 -1233221968 (LWP 30161)]
[New Thread -1290540128 (LWP 30210)]
[New Thread -1259709536 (LWP 30209)]
[New Thread -1268139104 (LWP 30179)]
[New Thread -1251316832 (LWP 30176)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73089

Thread 1 (Thread -1233221968 (LWP 30161))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
#11 ??
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
#12 ??
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
#13 ??
#14 ??
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
#15 ??
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
#16 ??
#17 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#18 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-gif.so
#19 ??
#20 ??
#21 ??
#22 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-23 22:13: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 353430 ***

Comment 2 Karsten Bräckelmann 2006-09-23 22:14:55 UTC

Also, since Evo crashed on start for you:  If you need some pointers how to get out of a crashing loop (crashing every time on starting Evo most likely is caused by displaying a mail), just poke me. I already added some short notes and a link to a few bugs recently, outlining this. :)