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 347955 - evolution 2.6 crash on drag and drop attachment
evolution 2.6 crash on drag and drop attachment
Status: RESOLVED DUPLICATE of bug 342242
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-07-18 20:10 UTC by dja
Modified: 2006-07-18 20:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description dja 2006-07-18 20:10:54 UTC
Subject: evolution 2.6 crash on drag and drop attachment
Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.14.2 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: evolution 2.6 crash on drop attachement
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
reply to a text only email, drag and drop 2 attachements from a gnome
samba mounted network place. evolution crashes. files to be attached are
<45 characters long, microsoft excel xls.

Steps to reproduce the crash:
1. use gnome to create a smb mounted network place, and connect to it
2. reply to an email
3. select 2 files, drag and drop into the email composer window to
attach

Expected Results:
should attach the files. i have attached files be this same method many
times. i have not ascertained if the crash is due to the fact that i'm
attaching multiple files, the length of the file name, etc.

How often does this happen?
always.

Additional Information:
ambauen at gmail dot com


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231636800 (LWP 16455)]
[New Thread -1363600464 (LWP 16500)]
[New Thread -1355129936 (LWP 16499)]
[New Thread -1336747088 (LWP 16479)]
[New Thread -1328354384 (LWP 16478)]
[New Thread -1317827664 (LWP 16475)]
[New Thread -1309434960 (LWP 16474)]
[New Thread -1300522064 (LWP 16472)]
[New Thread -1292117072 (LWP 16470)]
[New Thread -1269826640 (LWP 16469)]
[New Thread -1259361360 (LWP 16462)]
[New Thread -1250931792 (LWP 16460)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1231636800 (LWP 16455))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 camel_mime_part_get_content_type
    from /usr/lib/libcamel-1.2.so.0
  • #6 e_attachment_new
    from /usr/lib/evolution/2.6/libemiscwidgets.so.0
  • #7 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 e_attachment_build_remote_file
    from /usr/lib/evolution/2.6/libemiscwidgets.so.0
  • #13 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #14 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-07-18 20:11 -------

Comment 1 Damien Durand 2006-07-18 20:31:18 UTC
I think this bug is duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=342242 but the stacktrace is not the same. I fix this bug to duplicate of 342242. If it is  not correct, reopen this report.



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