GNOME Bugzilla – Bug 252935
evo-1.5 sometime crashes when click on the message list
Last modified: 2004-09-29 20:43:02 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: evo-1.5 crashes when click on the message list Steps to reproduce the problem: 1. Select message list ( at that time preview bane is opened) 2. To select someone's message, click on a subject or sender or date 3. Evo crashes Actual Results: Expected Results: How often does this happen? sometimes Additional Information: Backtrace was generated from '/usr/bin/evolution-1.5' [New Thread 1024 (LWP 19087)] [New Thread 2049 (LWP 19094)] [New Thread 1026 (LWP 19095)] [New Thread 2051 (LWP 19096)] [New Thread 8196 (LWP 19124)] [New Thread 4101 (LWP 19115)] [New Thread 9222 (LWP 19196)] [New Thread 6151 (LWP 19117)] 0x41680909 in __wait4 () at __wait4:-1 in __wait4
+ Trace 43279
This problem happens with evo-1.5.0 to 1.5.2 with GNOME-2.5.2
*** bug 251928 has been marked as a duplicate of this bug. ***
*** bug 253004 has been marked as a duplicate of this bug. ***
Retargeting 1.5.3->1.5.4 bug reports. Sorry for the spam.
I resolved this problem by the infomation which I've forgotten the source, sorry! To solve this, Select "Assistive Technology" from GNOME Control-Center, then check off the button "Enable Assistive Technology". After re-login, no trouble with clicking list.
Thanks for your information. Sun hackers, ping?
reassign to myself
*** bug 255534 has been marked as a duplicate of this bug. ***
Bug reproduced, 1. start evolution with a11y enabled 2. goto a mail folder 3. click on the message. 4. switch to other folders, after switch several folder, evolution very easily goto crash.
More easily way to reproduce this bug: 1. start evolution with a11y enabled 2. goto a mail folder with few messages 3. click on the message. 4. switch to another folder which contains a lot of messages, click to the message list several times, then evolution will goto crash at most times. The bug is caused by the following reason: the cell_data pointer (used to the retrieve the AtkObject of table cell) is initialize the first folder is accessed, when switched to another folder, the cell_data pointer keeps the original value ( The cell_data pointer's value should change, but it didn't. ) Then if we access a message out of the first folder's range(in another folder), the AtkObject which we get via cell_data pointer is invalid, and a SIGSEGV signal is raised...
Duplicates still arriving. Any forecast in sight?
*** bug 256278 has been marked as a duplicate of this bug. ***
*** bug 257139 has been marked as a duplicate of this bug. ***
*** bug 257229 has been marked as a duplicate of this bug. ***
*** bug 257313 has been marked as a duplicate of this bug. ***
*** bug 257316 has been marked as a duplicate of this bug. ***
*** bug 257364 has been marked as a duplicate of this bug. ***
Moving to blocker due to the amount of duplicates.
Created attachment 43608 [details] [review] A patch to fix this bug.
reopen if there are still problems