GNOME Bugzilla – Bug 726097
Editing or adding a new appointment often hangs evolution.
Last modified: 2014-11-18 13:57:19 UTC
Created attachment 271509 [details] Adding a new appointment. Often, when I try to add a new appointment in the evolution calendar the appointment summary window opens but remains invisible and locked, blocking the entire application (evolution). This happens by adding an appointment either from the menu bar or with a right click on the calendar. Sometimes it happens that everything works on the first try, but if I close the appointment summary window (from the menu or close button makes no difference) and try again returns the bug (the second, third or subsequent attempt). I also tried to kill evolution-calendar-factory, but the situation is the same. This also happens if I try to edit an appointment.
Created attachment 271510 [details] Editing an appointment.
Thanks for a bug report. This is new to me, I do not recall I ever saw this before. In case you can still reproduce it, could you try to install debuginfo packages for evolution-data-server and evolution, then reproduce the issue, and while the window will be stuck, get a backtrace of running evolution, which you can do with the following gdb command: $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only). The backtrace will show in which state is evolution stuck. I would guess it's stuck on the evolution-calendar-factory communication, but as you said you tried to kill it and nothing happened, then I'm not that sure.
Hello Milan Crha, I installed evolution-debuginfo and evolution-data-server-debuginfo, and later graphite2-debuginfo (missed and required by the infos in the bt.txt file). I am sending you three bt.txt files for three attempts: - bt.1.txt: opening evolution, opening and closing appointment (successfully), re-opening of the appointment with the locked interface, attempt to activate the invisible appointment window, backtrace; - bt.2.txt: opening evolution, opening and closing appointment (successfully), re-opening of the appointment with the locked interface, backtrace; - bt.3.txt: opening evolution, opening and closing appointment (successfully), re-opening of the appointment with the locked interface, killing the evolution-calendar-factory process, attempt to activate the invisible appointment window, backtrace. I hope this is helpful. Bye, Mario
Created attachment 290841 [details] first backtrace opening evolution, opening and closing appointment (successfully), re-opening of the appointment with the locked interface, attempt to activate the invisible appointment window, backtrace.
Created attachment 290842 [details] second backtrace opening evolution, opening and closing appointment (successfully), re-opening of the appointment with the locked interface, backtrace.
Created attachment 290843 [details] third backtrace opening evolution, opening and closing appointment (successfully), re-opening of the appointment with the locked interface, killing the evolution-calendar-factory process, attempt to activate the invisible appointment window, backtrace.
Thanks for the update. I thought this is related to the saving of the changes, like the application waiting for an evolution-calendar-factory, but the backtraces show that this is caused by a false GSettings notifications, which do a flood of the change propagation. There had been done multiple fixes which tried to avoid this condition, namely at least within bug #698275 and bug #730886. I'll mark this as a duplicate of the former. The evolution 3.12.8 is better, as far as I can tell, thus once your distribution will provide it to you you might have this fixed too. *** This bug has been marked as a duplicate of bug 698275 ***