GNOME Bugzilla – Bug 355418
crash: canceling gpg encrypt after declining meeting request
Last modified: 2013-09-13 00:53:46 UTC
declined the meeting request in bug 272932, option "send reply to sender" enabled. a pop up asked me for my gpg key. i pressed "cancel". evolution 2.7.92 crashed. does not look 100% reproducible. (after restarting evolution, the meeting is added to my calendar though i declined, so i can confirm bug 272932 here.) Backtrace was generated from '/opt/gnome/libexec/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1237095968 (LWP 10801)] [New Thread -1424909408 (LWP 11231)] [New Thread -1858995296 (LWP 11198)] [New Thread -1634501728 (LWP 11161)] [New Thread -1625347168 (LWP 10811)] [New Thread -1608369248 (LWP 10809)] [New Thread -1434084448 (LWP 10807)] [New Thread -1416512608 (LWP 10806)] [New Thread -1408078944 (LWP 10803)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72103
Thread 1 (Thread -1237095968 (LWP 10801))
*** Bug 466549 has been marked as a duplicate of this bug. ***
Changing the version as it appeared in Evolution 2.11.90
*** Bug 469583 has been marked as a duplicate of this bug. ***
Please look into the error dialog attached in below bug id http://bugzilla.gnome.org/show_bug.cgi?id=469583
and then?
I mentioned comment#4 because bug 469538 has been closed as duplicate and before crash occurred,error window popped up for me.This error window is not relevant because i am accepted meeting,obviously my account is active,then why this error window pops up.When any developer will look into the crasher,he can look into error dialog also. Andre , hope it is sufficient reason for mentioning bug in comment#4 ;-)
bug 362428 might be a duplicate of this bug.
*** Bug 362428 has been marked as a duplicate of this bug. ***
Should be fixed with bug #468427 The code place/reason is all the same as bug #468427
OK, should be fixed in 2.22.0. If somebody can still reproduce this, please reopen this bug 355418.
*** Bug 551644 has been marked as a duplicate of this bug. ***