Bug 351528 – crash on Evolution

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 351528 - crash on Evolution


Summary:	crash on Evolution


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-15 20:19 UTC by hp
Modified:	2013-09-13 00:54 UTC

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

Description hp 2006-08-15 20:19:03 UTC

What were you doing when the application crashed?
opening my groupwise calendar


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 277143552 vsize: 0 resident: 277143552 share: 0 rss: 49135616 rss_rlim: 0
CPU usage: start_time: 1155668948 rtime: 0 utime: 3982 stime: 0 cutime:3849 cstime: 0 timeout: 133 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 -1231513936 (LWP 10775)]
[New Thread -1377834080 (LWP 10863)]
[New Thread -1359328352 (LWP 10818)]
[New Thread -1284744288 (LWP 10790)]
[New Thread -1310409824 (LWP 10788)]
[New Thread -1302017120 (LWP 10787)]
[New Thread -1293624416 (LWP 10786)]
[New Thread -1276351584 (LWP 10784)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70511

Thread 1 (Thread -1231513936 (LWP 10775))

#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 ??
from /usr/lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgthread-2.0.so.0
#13 ??
from /usr/lib/libgthread-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgthread-2.0.so.0
#16 procfd.7283
from /lib/tls/i686/cmov/libc.so.6
#17 ??
from /usr/lib/libgthread-2.0.so.0
#18 ??
from /usr/lib/libecal-1.2.so.7
#19 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-08-17 19:30:41 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Karsten Bräckelmann 2006-09-21 01:27:36 UTC

Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on certain distros. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue.


If you can reproduce this crash, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.


Also, please feel free to report any further bugs you find.  Thanks!


[1] debugging packages for evolution and evolution-data-server, plus debugging
    packages for some basic GNOME libs. More details can be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions