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 334633 - clicking to mailer window often crashes
clicking to mailer window often crashes
Status: RESOLVED DUPLICATE of bug 335203
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-03-15 10:42 UTC by Stanislav Brabec
Modified: 2008-08-07 09:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12

Attachments
random_crash.txt (75.92 KB, text/plain)
2006-03-15 10:43 UTC, Stanislav Brabec 		Details

Description Stanislav Brabec 2006-03-15 10:42:57 UTC 
Steps to reproduce:
1. Use Evolution for some time
2. Let Evolution running while not using it
3. Click to mail drawer at right or mail drawer contents


Stack trace:
Too long. Will be attached.

Other information:
I want to see, if there are interesting new mails in some mailboxes. During this
clicking, it crashes several times a day.
Comment 1 Stanislav Brabec 2006-03-15 10:43:49 UTC 
Created attachment 61283 [details]
random_crash.txt

Backtrace.
Comment 2 André Klapper 2006-03-20 01:16:06 UTC 
unique stacktrace. which evo version is this exactly?
Comment 3 Stanislav Brabec 2006-03-20 11:29:46 UTC 
SuSE Linux 10.1 beta 7 AMD64, evolution-2.5.92-6, evolution-data-server-1.5.92-5
Comment 4 Matthew Barnes 2008-03-11 00:25:36 UTC 
Bumping version to a stable release.
Comment 5 Kandepu Prasad 2008-08-07 09:23:02 UTC 
Traces look similar to bug 326123 which is dup of bug 335203.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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