"Send to..." can't work

Bug #27651 reported by Cynthia Qin
30
Affects Status Importance Assigned to Milestone
nautilus-sendto (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

1.Open FileBrowser by click "Places"->"Home Folder";
2.Keep focus on file "test.txt";
3.Click menu "Edit"->"Send to...";
4..One error message box pop up, saying:
 The application "nautilus" has quit unexpectedly.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. Which version of Ubuntu and nautilus do you use? If
this is reproducible, could you please attach all the information the bug-buddy
dialog has (Inform Developers)?

Revision history for this message
Cynthia Qin (qinxie) wrote :
Download full text (6.4 KiB)

My pleasure.
What I used is Ubuntu Dapper, and my nautilus is 2.13.3.
Followed is the bug-buddy information:
Backtrace was generated from '/usr/bin/nautilus-sendto'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1223682368 (LWP 13039)]
(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)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7ae0483 in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7f0d226 in libgnomeui_module_info_get ()
   from /usr/lib/li...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

*** Bug 27854 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the crash:

 nautilus-sendto (0.5-0ubuntu2) dapper; urgency=low
 .
   * debian/control.in:
     - don't build with bluetooth to workaround the crash with it
       (Ubuntu: #27651)

Changed in nautilus-sendto:
assignee: dholbach → desktop-bugs
status: Unconfirmed → Fix Released
Revision history for this message
Tom von Schwerdtner (tvon) wrote :

Is this a temporary fix? I was using it with bluetooth last week without any problems (granted, I have working bluetooth) and it was pretty nice to have.

Revision history for this message
Sebastien Bacher (seb128) wrote :

It's not a fix but a workaround as indicated to the changelog :) It will be reactivated when the crash is fixed. I've forwarded the issue upstream: http://bugzilla.gnome.org/show_bug.cgi?id=327876

Revision history for this message
Sebastien Bacher (seb128) wrote :

Those uploads fix the issue:

 libbtctl (0.6.0-0ubuntu2) dapper; urgency=low
 .
   * debian/patches/01_fix_nautilus-sendto_crasher.patch:
     - fix a crasher when nautilus-sendto is built with bluetooth option,
       patch from the fedora package

 nautilus-sendto (0.5-0ubuntu2) dapper; urgency=low
 .
   * debian/control.in:
     - don't build with bluetooth to workaround the crash with it
       (Ubuntu: #27651)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Wrong nautilus-sendto upload mentionned, there is a build issue atm but it'll be fixed soon

Revision history for this message
Sebastien Bacher (seb128) wrote :

that upload fixes the issue:

 nautilus-sendto (0.5-0ubuntu3) dapper; urgency=low
 .
   * debian/control.in:
     - Build-Depends on libbtctl2-dev to build with bluetooth option

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.