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 312692 - Random Crash on regular basis.
Random Crash on regular basis.
Status: RESOLVED INCOMPLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.0.x
Other other
: Normal normal
: ---
Assigned To: Sankar P
Evolution QA team
: 312965 315787 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-08-05 16:10 UTC by joseph.stephens
Modified: 2006-05-12 07:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description joseph.stephens 2005-08-05 16:10:31 UTC
Distribution: SuSE Linux 9.3 (i586)
Package: Evolution
Priority: Normal
Version: GNOME2.10.0 2.2.1
Gnome-Distributor: SUSE
Synopsis: Random Crash on regular basis. 
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.2.1
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
When reading email, evolution crashes. It seems to crash on a regular
basis while just useing or it simply running idle (from a user
perspective) Could be something to do with the under the covers
operations like auto mail update or something.

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

Expected Results:


How often does this happen?
It's up to many times a day. More than 10 times a day now.


Additional Information:
This is happening on several different servers running SuSE 9.2 and 9.3
connecting to an exchange server for it's email. I'm not sure how to
duplicate this at all. I would be happy to work with anyone who would
like to try and figure this out. The can email me at joseph DOT stephens
AT capgeminienergy DOT com



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-2.2'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1094961376 (LWP 10451)]
[New Thread 1170115504 (LWP 15132)]
[Thread debugging using libthread_db enabled]
[New Thread 1094961376 (LWP 10451)]
[New Thread 1170115504 (LWP 15132)]
[New Thread 1125120944 (LWP 13887)]
[New Thread 1123019696 (LWP 13860)]
[New Thread 1127222192 (LWP 11537)]
[New Thread 1116715952 (LWP 11536)]
[New Thread 1120918448 (LWP 11533)]
[New Thread 1118817200 (LWP 11529)]
[New Thread 1114221488 (LWP 10475)]
[Thread debugging using libthread_db enabled]
[New Thread 1094961376 (LWP 10451)]
[New Thread 1170115504 (LWP 15132)]
0xffffe410 in ?? ()




------- Bug moved to this database by unknown@gnome.bugs 2005-08-05 16:10 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was joseph.stephens@capgeminienergy.com.

Comment 1 Not Zed 2005-08-08 09:10:32 UTC
moving to connector.  although the trash is probably not much use in helping to
find the problems.
Comment 2 Sarfraaz Ahmed 2005-08-30 11:27:05 UTC
This is really not much info in this trace that can help us track the problem.
Probably it is the evolution-exchange process that is crashing and you might
have to get the traces for that.
Comment 3 Sushma Rai 2006-02-07 05:26:07 UTC
*** Bug 312965 has been marked as a duplicate of this bug. ***
Comment 4 Sushma Rai 2006-02-07 05:27:09 UTC
*** Bug 315787 has been marked as a duplicate of this bug. ***
Comment 5 Sushma Rai 2006-05-12 07:02:10 UTC
Can you please try 2.6.x?
Also, if any of you still facing the issue, please try 
providing gdb traces for evolution-exchange-storage.
Please re-open the bug with the stack traces.