Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#2749 - libgnomecanvas 2.10.1: Evolution crashes
Attached to Project:
Arch Linux
Opened by Sascha Erni (nggalai) - Friday, 20 May 2005, 12:21 GMT
Last edited by Dale Blount (dale) - Saturday, 21 May 2005, 02:07 GMT
Opened by Sascha Erni (nggalai) - Friday, 20 May 2005, 12:21 GMT
Last edited by Dale Blount (dale) - Saturday, 21 May 2005, 02:07 GMT
|
DetailsWith the latest upgrade to libgnomecanvas-2.10.1-1, Evolution crashes when trying to send messages including a PGP key and/or a signature. After the first such crash, Evolution didn't start up until I removed ~/.evolution and opened a new profile.
Falling back to libgnomecanvas-2.10.0-1 solved this issue. |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 01 June 2005, 07:15 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with new release of libgnomecanvas and gal.
Wednesday, 01 June 2005, 07:15 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with new release of libgnomecanvas and gal.
I can't reproduce this issue on my own system with the testcase you described.
This does only happen with 2.10.1; 2.10.0 works flawlessly, here. Killing the environment services did not solve the problem, only a fallback did.
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbfff810c in ?? ()
#2 0x00000000 in ?? ()
#3 0xbfff8040 in ?? ()
#4 0xb6dcf03b in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#5 0xb7a1acd8 in libgnomeui_segv_handle () from /opt/gnome/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 0xb71fa727 in gnome_canvas_shape_destroy () from /opt/gnome/lib/libgnomecanvas-2.so.0
#8 0xb72037ab in gnome_canvas_re_destroy () from /opt/gnome/lib/libgnomecanvas-2.so.0
#9 0xb6c7e9b6 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
#10 0xb6c685a9 in g_type_class_meta_marshal () from /usr/lib/libgobject-2.0.so.0
#11 0xb6c682ab in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#12 0xb6c7d29c in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0
#13 0x00000000 in ?? ()
#14 0x00000001 in ?? ()
#15 0xbfff86e0 in ?? ()
#16 0xbfff85b8 in ?? ()
#17 0x00000000 in ?? ()
#18 0xbfff8738 in ?? ()
#19 0xb6c7e292 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Got the bug, now I can reproduce it. Will be fixed with the 2.10.1-2 package.