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 327678 - evolution crashes when attaching file named with 8bit characters from smb share
evolution crashes when attaching file named with 8bit characters from smb share
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-19 08:55 UTC by svenole
Modified: 2013-09-13 00:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description svenole 2006-01-19 08:55:39 UTC
Distribution: Fedora Core release 4 (Rawhide)
Package: Evolution
Priority: Normal
Version: GNOME2.13.5 2.5.4-6
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution mailer crashes when attaching file
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.5.4-6
BugBuddy-GnomeVersion: 2.0 (2.13.2)
Description:
Description of the crash:
Evolution crashes when editing a new email and attaching a file named
with 8 bit characters.

Steps to reproduce the crash:
1. Mount a smb filesystem from a server (I am mounting a filesystem from 
a windows server)
2. Create a file named with an 8bit character (ex: \xE6\xE5\xF8) on this filesystem
3. Edit a new mail and attach this file to the mail dragging the file 
from nautilus

Expected Results:
File is attached

How often does this happen?
always

Additional Information:
Attaching the file works when the filename does not contain norwegian
(8bit) characters) or the file is located on local disk

I am running:
evolution-2.5.4-6
evolution-connector-2.5.4-1
evolution-data-server-1.5.4-4



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208227648 (LWP 11250)]
[New Thread -1367958624 (LWP 11578)]
[New Thread -1338405984 (LWP 11375)]
[New Thread -1342178400 (LWP 11374)]
[New Thread -1327916128 (LWP 11268)]
[New Thread -1317426272 (LWP 11265)]
[New Thread -1306543200 (LWP 11263)]
[New Thread -1296053344 (LWP 11262)]
[New Thread -1285563488 (LWP 11260)]
[New Thread -1275073632 (LWP 11259)]
[New Thread -1264583776 (LWP 11258)]
[New Thread -1252832352 (LWP 11257)]
[New Thread -1242334304 (LWP 11256)]
(no debugging symbols found)




------- Bug created by bug-buddy at 2006-01-19 08:55 -------


Unknown version 2.5.4-6 in product Evolution.  Setting version to "unspecified".

Comment 1 André Klapper 2006-01-19 09:29:29 UTC
Thanks for the bug report; adding version number. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance very much.
Comment 2 svenole 2006-01-20 13:06:38 UTC
Evolution version in use:
evolution-connector-2.5.4-1
evolution-2.5.4-10
evolution-data-server-1.5.4-4

I am not able to get trace using the hints specified. I am using gdb as specified. Please instruct me if you want me to do more testing here. 
Comment 3 Poornima 2006-01-25 05:16:10 UTC
Svenole: Start evolution using gdb, paste stack traces of evolution when it crashes. If the stack traces are still same, install evolution with debugging symbols from ftp://ftp.ximian.com and then paste the stack traces here.
Comment 4 André Klapper 2006-05-11 21:23:10 UTC
svenole: run evolution in gdb by running "gdb evolution", if evo crashes, type "thread apply all bt". paste the output here, and reopen this bug report.
thanks very much in advance!
Comment 5 Poornima 2006-08-19 16:11:36 UTC
Svenole: Closing this bug as there is no update on this bug. Please reopen if you get the traces with debug information