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 355418 - crash: canceling gpg encrypt after declining meeting request
crash: canceling gpg encrypt after declining meeting request
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.12.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 362428 466549 469583 551644 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-11 11:14 UTC by André Klapper
Modified: 2013-09-13 00:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description André Klapper 2006-09-11 11:14:53 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 ()

Thread 1 (Thread -1237095968 (LWP 10801))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 867
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 view_response_cb
    at itip-formatter.c line 1592
  • #6 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #7 IA__g_closure_invoke
    at gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #9 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #10 IA__g_signal_emit
    at gsignal.c line 2241
  • #11 button_clicked_cb
    at itip-view.c line 724
  • #12 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #13 IA__g_closure_invoke
    at gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #16 IA__g_signal_emit
    at gsignal.c line 2241
  • #17 IA__gtk_button_clicked
    at gtkbutton.c line 889
  • #18 gtk_real_button_released
    at gtkbutton.c line 1484
  • #19 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #20 g_type_class_meta_marshal
    at gclosure.c line 567
  • #21 IA__g_closure_invoke
    at gclosure.c line 490
  • #22 signal_emit_unlocked_R
    at gsignal.c line 2368
  • #23 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #24 IA__g_signal_emit
    at gsignal.c line 2241
  • #25 IA__gtk_button_released
    at gtkbutton.c line 881
  • #26 gtk_button_button_release
    at gtkbutton.c line 1377
  • #27 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #28 g_type_class_meta_marshal
    at gclosure.c line 567
  • #29 IA__g_closure_invoke
    at gclosure.c line 490
  • #30 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #31 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #32 IA__g_signal_emit
    at gsignal.c line 2241
  • #33 gtk_widget_event_internal
    at gtkwidget.c line 3901
  • #34 IA__gtk_widget_event
    at gtkwidget.c line 3707
  • #35 IA__gtk_propagate_event
    at gtkmain.c line 2187

Comment 1 Chenthill P 2007-08-22 18:12:26 UTC
*** Bug 466549 has been marked as a duplicate of this bug. ***
Comment 2 Akhil Laddha 2007-08-23 03:20:58 UTC
Changing the version as it appeared in Evolution 2.11.90
Comment 3 Akhil Laddha 2007-08-23 13:13:06 UTC
*** Bug 469583 has been marked as a duplicate of this bug. ***
Comment 4 Akhil Laddha 2007-08-23 13:26:26 UTC
Please look into the error dialog attached in below bug id
http://bugzilla.gnome.org/show_bug.cgi?id=469583

Comment 5 André Klapper 2007-08-23 14:26:22 UTC
and then?
Comment 6 Akhil Laddha 2007-08-27 05:37:11 UTC
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 ;-)
Comment 7 Chenthill P 2007-09-04 06:15:35 UTC
bug 362428 might be a duplicate of this bug.
Comment 8 Chenthill P 2007-09-04 06:18:23 UTC
*** Bug 362428 has been marked as a duplicate of this bug. ***
Comment 9 Srinivasa Ragavan 2008-02-20 17:14:41 UTC
Should be fixed with bug #468427

The code place/reason is all the same as bug #468427
Comment 10 André Klapper 2008-09-10 17:30:23 UTC
OK, should be fixed in 2.22.0.
If somebody can still reproduce this, please reopen this bug 355418.
Comment 11 André Klapper 2008-09-10 17:30:48 UTC
*** Bug 551644 has been marked as a duplicate of this bug. ***