Bug 301599 – Subject line crashing evolution mail editor

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 301599 - Subject line crashing evolution mail editor


Summary:	Subject line crashing evolution mail editor


Status:	RESOLVED DUPLICATE of bug 273945

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.2.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-04-22 15:37 UTC by Stanislav Brabec
Modified:	2013-09-10 14:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Stanislav Brabec 2005-04-22 15:37:23 UTC

Steps to reproduce:
1. Create a new mail, fill any recipient
2. Fill following subject: "X ě" (LATIN CAPITAL LETTER X, SPACE, LATIN SMALL
LETTER E WITH CARON)
3. Send it -> Crash


Stack trace:
Backtrace was generated from '/opt/gnome/bin/evolution-2.2'

(no debugging symbols found)
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
(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)
(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)
0x00002aaaaf905eca in waitpid () from /lib64/tls/libpthread.so.0

+ Trace 58559

#0 waitpid
from /lib64/tls/libpthread.so.0
#1 gnome_init_with_popt_table
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 main



Other information:
Bug can be repeated in SuSE Linux 9.3 (AMD64) and Debian Sid (i386)

Comment 1 Kjartan Maraas 2005-04-23 10:06:17 UTC

The backtrace is pretty incomplete and without good symbol information. Could
you run it in gdb and do a 'bt full' or something like that?

Comment 2 Stanislav Brabec 2005-04-25 13:56:37 UTC

eolution --disable-crash-dialog does not work, attaching cut'n'paste from
bug-buddy after installation of debuginfo. Bug should be simply repeatable by
entering three characters upper mentioned characters into subject line.

Backtrace was generated from '/opt/gnome/bin/evolution'

Using host libthread_db library "/lib64/tls/libthread_db.so.1".
0x00002aaaaf905eca in waitpid () from /lib64/tls/libpthread.so.0

+ Trace 58692

#0 waitpid
from /lib64/tls/libpthread.so.0
#1 gnome_init_with_popt_table
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 segv_redirect
at main.c line 428
#3 funlockfile
from /lib64/tls/libpthread.so.0
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 stpncpy
from /lib64/tls/libc.so.6
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
from /opt/gnome/lib64/libcamel-1.2.so.0
#19 ??
#20 ??
#21 __check_rhosts_file
from /lib64/tls/libc.so.6
#22 ??
#23 ??
#24 ??
#25 strcasecmp
from /lib64/tls/libc.so.6
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 g_cclosure_marshal_VOID__BOXED
from /opt/gnome/lib64/libgobject-2.0.so.0
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 g_closure_ref
from /opt/gnome/lib64/libgobject-2.0.so.0
#42 ??
#43 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 ??
#51 ??
#52 ??
#53 ??
#54 ??
#55 ??
#56 ??
#57 ??
#58 ??
#59 ??
#60 ??
#61 ??
#62 ??
#63 ??
#64 ??
#65 ??
#66 ??
#67 ??
#68 ??
#69 ??
#70 ??
#71 ??
#72 ??
#73 ??
#74 ??
#75 ??
#76 ??
#77 ??
#78 ??
#79 ??
#80 ??
#81 ??
#82 ??
#83 ??
#84 ??
#85 ??
#86 ??
#87 ??
#88 ??
#89 ??
#90 ??
#91 ??
#92 ??
#93 ??
#94 ??
#95 ??
#96 ??
#97 ??
#98 ??
#99 ??
#100 ??
#101 ??
#102 ??
#103 ??
#104 ??
#105 ??
#106 ??
#107 ??
#108 _dl_rtld_di_serinfo
from /lib64/ld-linux-x86-64.so.2
#109 _dl_rtld_di_serinfo
from /lib64/ld-linux-x86-64.so.2
#110 rfc2047_encode_word
at camel-mime-utils.c line 1184

Comment 3 Kjartan Maraas 2005-04-25 16:24:03 UTC

Crashes here on FC4test and a normal Pentium M laptop:

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209092416 (LWP 3397)]
[New Thread -1272124496 (LWP 5840)]
[New Thread -1258689616 (LWP 5839)]
[New Thread -1247310928 (LWP 3492)]
[New Thread -1233200208 (LWP 3490)]
[New Thread -1222706256 (LWP 3457)]
[New Thread -1212216400 (LWP 3456)]
0x00bb1402 in ?? ()

+ Trace 58698

Thread 1 (Thread -1209092416 (LWP 3397))

#0 ??
#1 ??
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 741

Comment 4 JP Rosevear 2005-04-28 12:29:21 UTC

This is already patched in CVS, did you file this downstream as well?  Patch is
in main bug (273945 - trace is different but it should be the same issue and the
fix prevents the problem)

*** This bug has been marked as a duplicate of 273945 ***