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 353335 - Trying to attach document on Samba mounted drive causes crash
Trying to attach document on Samba mounted drive causes crash
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-08-29 02:36 UTC by conrad.cset
Modified: 2006-08-29 08:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description conrad.cset 2006-08-29 02:35:57 UTC
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Trying to attach document on Samba mounted drive causes crash.

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: major
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: Trying to attach document on Samba mounted drive causes crash.
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Composing a new message, a file was dragged from a Samba mounted drive
on another server to the composition window and the program crashes
immediately with an error.

Steps to reproduce the crash:
1. Connect to a Windows share on another PC.
2. Compose a new message.
3. Drag file from Samba mount to composition window.

Expected Results:
Either an error message saying the operation couldn't be completed or
the attachment being successful.

How often does this happen?
Each time

Additional Information:



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 -1231812384 (LWP 6276)]
[New Thread -1350800464 (LWP 6562)]
[New Thread -1268479056 (LWP 6484)]
[New Thread -1331188816 (LWP 6293)]
[New Thread -1308124240 (LWP 6287)]
[New Thread -1299649616 (LWP 6285)]
[New Thread -1291256912 (LWP 6284)]
[New Thread -1259689040 (LWP 6282)]
[New Thread -1251255376 (LWP 6280)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1231812384 (LWP 6276))

  • #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-08-29 02:36 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.

Comment 1 André Klapper 2006-08-29 08:13:03 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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