GNOME Bugzilla – Bug 318562
Evolution calendar crashes when right click on meetings
Last modified: 2006-08-12 13:11:14 UTC
To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Evolution calendar crashes when right click on meetings Distribution: Ubuntu 5.10 (breezy) Package: Evolution Severity: Normal Version: GNOME2.12.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Evolution calendar crashes when right click on meetings Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Evolution crashes when I right click on a meeting to edit it. Steps to reproduce the crash: 1. Start evolution calendar 2. Right click on an scheduled meeting 3. Expected Results: Crash How often does this happen? Always Additional Information: System Ubuntu Breezy 5.10 kernel 2.6.12-9-k7 / Evolution 2.4.1 Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230005344 (LWP 14201)] [New Thread -1236255824 (LWP 14203)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 63478
Thread 1 (Thread -1230005344 (LWP 14201))
-- Dr. Pascual Mu\xF1oz Mu\xF1oz - Telecommunication Engineer Optical Communications Group - iTEAM Research Institute pascual@ieee.org - www.gco.upv.es - www.upv.es ------- Bug moved to this database by unknown@gnome.bugs 2005-10-11 11:19 UTC -------
adding version number
*** This bug has been marked as a duplicate of 312460 ***
I don't feel is a duplicate.
*** Bug 318639 has been marked as a duplicate of this bug. ***
chen: Even i feel this bug is not duplicate of #312460. Bug 312460 is to occur when u is to represent unaccepted meeting as bold. That code is not there at present i beleive. This bug occurs in ubuntu whenever u right click on any appointment.
I had marked it as duplicate as i had fixed a memory corruption *double free* in itip_get_comp_attendee function. Both the bugs show the crash at the same function. As its a utility function, it can be called at many places. It does occur after that fix. A single fix can solve many issues. Do you still feel its not a duplicate ? :)
Why is that bug NEEDINFO now? Ubuntu bug with a matching backtrace: http://bugzilla.ubuntu.com/show_bug.cgi?id=17244
Since i have already fixed it.
And i marked it as a duplicate. But it was reopened, so i wanted to ensure if it was still happening.
I am using Evolution 2.4.2.1 under Debian, and the exact same bug is still happening to me: right-clicking on an appointment or a task makes evolution to crash, but a right-click anywhere else works perfectly. In what version is this bug corrected?
I am also having the same problem under debian. Evolution version 2.4.2.1 as well. How can I provide more information so that this bug can be fixed? (or has it been fixed already?)
*** Bug 337767 has been marked as a duplicate of this bug. ***
okay, so when evolution 2.6 hits debian, this definitely should be retested again.
Good news: I upgraded to Evolution 2.6.1 on Debian testing today, and the bug has disappeared :) Cheers, -- Steph
I just upgraded today. Unfortunately the bug has not disappeared for me yet.
James: Stack traces of crash u r observing now is same as one pasted in this bug ?
It looks like the bug has been fixed - I can't reproduce it any longer. :)
closing as fixed then - thanks a lot for the feedback, and please reopen if it still appears.