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 562250 - Evolution Mail and Calendar: Az Evolution összeomlik ...
Evolution Mail and Calendar: Az Evolution összeomlik ...
Status: RESOLVED DUPLICATE of bug 560329
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-11-25 18:00 UTC by Gergely Máté
Modified: 2008-11-26 12:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Gergely Máté 2008-11-25 18:00:28 UTC 
Az Evolution összeomlik és kilép, ha a "Naptárak" gombot megnyomom. Így a teljes Naptárak funkció nem érhető el.
(Evolution crashes when clicking "Calendars". Therefore the whole Calendars feature is unavailable.)


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1
Comment 1 André Klapper 2008-11-25 23:28:50 UTC 
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 2008-11-26 05:17:54 UTC 
check in case you have accessibility enabled, see bug 560329
Comment 3 Gergely Máté 2008-11-26 11:35:51 UTC 
Yes, it seems it is the same as bug 560329. I have created a stack trace, and it is quite similar to that (crash in libatk-bridge.so).

There I continnue...
Comment 4 Akhil Laddha 2008-11-26 12:37:12 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 560329 ***