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 324790 - evolution 2.5.5.1 crashes within 5 mins of startup on FC5 rawhide
evolution 2.5.5.1 crashes within 5 mins of startup on FC5 rawhide
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Shell
2.6.x
Other All
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-12-22 10:58 UTC by Peter Robinson
Modified: 2013-09-13 00:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Peter Robinson 2005-12-22 10:58:32 UTC
Steps to reproduce:
everytime

Stack trace:
Distribution: Fedora Core 5 rawhide
Package: Evolution
Priority: Normal
Version: GNOME2.13.3 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution 2.5.3 crashes within 5 mins of startup on FC5 rawhide
Bugzilla-Product: Evolution
Bugzilla-Component: Shell
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.13.0)
Description:
Description of the crash:
evolution 2.5.3 runs fine checks and downloads the mail using evolution
connector talking to a exchange 2003 server and works as expected then
after around 5 minutes just crashes. Here is the install with the
evolution-*-debuginfo rpms installed. If you want any further info or
other debug stuff installed let me know.

Steps to reproduce the crash:
1. Start evolution
2. wait
3. crash happens

Expected Results:
It should keep running

How often does this happen?
everytime

Additional Information:



Debugging Information:

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

Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208166736 (LWP 6767)]
[New Thread -1381340240 (LWP 6797)]
[New Thread -1370842192 (LWP 6795)]
[New Thread -1359959120 (LWP 6793)]
[New Thread -1349469264 (LWP 6792)]
[New Thread -1338979408 (LWP 6791)]
[New Thread -1285395536 (LWP 6790)]
[New Thread -1274905680 (LWP 6789)]
[New Thread -1264415824 (LWP 6788)]
[New Thread -1253524560 (LWP 6785)]
0x00339402 in __kernel_vsyscall ()

Thread 7 (Thread -1285395536 (LWP 6790))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_36
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 pthread_mutex_destroy
    from /lib/libpthread.so.0
  • #6 segv_redirect
    at main.c line 433
  • #7 <signal handler called>
  • #8 camel_object_cast
    at camel-object.c line 1078



Other information:
Comment 1 Poornima 2006-01-09 08:53:53 UTC
Not reproducible on suse 9.3
Comment 2 Peter Robinson 2006-01-09 09:19:41 UTC
I wonder if its got something to do with the gcc 4.1 that rawhide is using. Even with 2.5.4 and all the latest updates this is still happening. 2.4.x on FC4 was fine on this laptop.
Comment 3 Peter Robinson 2006-01-30 10:44:21 UTC
Still seeing this with evolution 2.5.5.1 on the latest rawhide for FC5-> this is the current backtrace with evolution*debuginfo packages installed. Let me know if you need more information.


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

Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208907584 (LWP 2797)]
[New Thread -1358623840 (LWP 2910)]
[New Thread -1348129888 (LWP 2905)]
[New Thread -1337246816 (LWP 2897)]
[New Thread -1326756960 (LWP 2896)]
[New Thread -1290335328 (LWP 2877)]
[New Thread -1279845472 (LWP 2876)]
[New Thread -1269281888 (LWP 2875)]
[New Thread -1258792032 (LWP 2874)]
[New Thread -1248289888 (LWP 2872)]
[New Thread -1237267552 (LWP 2871)]
0x0098e402 in __kernel_vsyscall ()

Thread 8 (Thread -1269281888 (LWP 2875))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_105
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 pthread_mutex_destroy
    from /lib/libpthread.so.0
  • #6 segv_redirect
    at main.c line 434
  • #7 <signal handler called>
  • #8 camel_object_cast
    at camel-object.c line 1080

Comment 4 Peter Robinson 2006-01-30 10:45:58 UTC
Also not sure whether this may be something to do with the evolution-exchange-storage process as sometimes it goes to quite high cpu usage.
Comment 5 Poornima 2006-05-02 09:24:09 UTC
is this reproducible with evolution 2.6 as 2.5.x was development version. if yes and stack traces are not exactly same update this bug with latest stack trace.
Comment 6 Peter Robinson 2006-05-26 09:07:41 UTC
Seems to be fixed for me now with 2.6 now so assigning bug to fixed.