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 247694 - evolution freeze when setting summary preference
evolution freeze when setting summary preference
Status: VERIFIED INCOMPLETE
Product: evolution
Classification: Applications
Component: Do Not Use
1.5.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Ettore Perazzoli
Evolution QA team
Depends on:
Blocks: 246841
 
 
Reported: 2003-08-18 08:14 UTC by Ben Li
Modified: 2013-09-13 12:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ben Li 2003-08-18 08:14:39 UTC
Description of Problem:
evolution freeze when setting  summary preference

The evolution version I used is v1.5

Steps to reproduce the problem:
1. Tools->Settings->Summary Preference
2. Change the summary preference settings, such as "News need", "wheather",
etc.
3. 

Actual Results:
   evolution freezes and no response.

Expected Results:


How often does this happen? 
   always

Additional Information:
Comment 1 Ben Li 2003-08-18 09:09:30 UTC
The bug does not happen always, there a small mistake in bug
description above, :-)

And this bug is not related to accessibility.
Comment 2 Gerardo Marin 2003-08-19 17:55:53 UTC
Can you get a backtrace when this happens?
Comment 3 Ben Li 2003-08-21 02:28:37 UTC
No, I can't get the backtrace.
Comment 4 Ben Li 2003-08-26 04:03:02 UTC
This bug can be reproduced in Redhat9 with gnome2.4
Comment 5 Ben Li 2003-08-26 04:04:10 UTC
When evolution got frozen, it said:


(evolution:4038): evolution-mail-WARNING **: Cannot activate
OAFIID:GNOME_Spell_Dictionary:0.3
 
** (evolution:4038): CRITICAL **: file utils.c: line 100
(html_utils_get_accessible): assertion `o != NULL' failed
Comment 6 Gerardo Marin 2003-08-26 19:06:55 UTC
If you can reproduce this, at freeze
1. Dig out evolution pid (ps -feax | grep evolution)
2. Start gdb in a terminal window
3. At gdb prompt write attach [evolution_pid from 1]
4. After libraries/symbols are loaded,at gdb prompt type: where
5. Paste output to this report.

Otherwise we can't pintpoint the problem.
Comment 7 Gerardo Marin 2003-11-17 20:40:38 UTC
Closed due to lack of response. Presumed fixed.  Please reopen if
otherwise.