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 600971 - Evolution: It is very difficult to ...
Evolution: It is very difficult to ...
Status: RESOLVED DUPLICATE of bug 599627
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-06 14:20 UTC by kennedy
Modified: 2009-12-18 03:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description kennedy 2009-11-06 14:20:30 UTC
It is very difficult to add a task without crashing Evolution. If I click to add a task, type in the task, and then click somewhere else in the task pane or press ENTER, Evolution almost always crashes.


Distribution: Ubuntu 9.10 (karmic)
Gnome Release: 2.28.1 2009-10-23 (Ubuntu)
BugBuddy Version: 2.28.0
Comment 1 Fabio Durán Verdugo 2009-11-06 15:50:12 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Akhil Laddha 2009-12-18 03:55:08 UTC
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 bug 599627 ***