Nautilus crashes/fails to launch when 1st gen iPhone is plugged in.

Bug #580177 reported by Paul Neiland
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

When a first generation iPhone is plugged into the machine via USB, nautilus either crashes for fails to launch. After attempting to launch for the first time after plugging the phone in, the application opens for a few seconds and then crashes. Any further attempts to launch nautilus result in it just not opening at all. The following output is given on the console in both cases:

Initializing nautilus-gdu extension

(nautilus:10626): GLib-CRITICAL **: g_strdelimit: assertion `string != NULL' failed

(nautilus:10626): GConf-CRITICAL **: gconf_escape_key: assertion `arbitrary_text != NULL' failed
**
ERROR:nautilus-directory.c:621:nautilus_directory_add_file: assertion failed: (file->details->name != NULL)
Aborted

If the phone is plugged in following the opening of a nautilus session, the window closes after a few seconds. If multiple windows are open, they are all closed simultaneously.

If desktop icons are enabled, nautilus (presumably) gets stuck in an infinite loop attempting to opening windows that say "starting file manager." The windows don't ever open, but the longer the loop goes, the more that fill up the task bar. After the iphone is unplugged, the "windows" in the taskbar go away, one by one.

Relatedly, Rhythmbox fails to recognize that there is an iPhone plugged into the machine. It does not show the iPhone nor does give any other indication that the device exists.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu May 13 12:55:59 2010
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nautilus

Revision history for this message
Paul Neiland (paul-neiland) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Maxime R. (max.r) wrote :

Hi, I'm also affected by this bug (since a while).
I attached the running nautilus process to gdb, continued and got the following message when plugging in my iphone :

Program received signal SIGSEGV, Segmentation fault.
__strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:39
39 ../sysdeps/i386/i686/multiarch/../strcmp.S: Aucun fichier ou dossier de ce type.
 in ../sysdeps/i386/i686/multiarch/../strcmp.S

Used backtrace to get the attached stacktrace.

That bug may be related to bug #657351 : https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/657351

I am running Ubuntu 10.10 with the latest updates. Thanks.

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

Other bug subscribers

Remote bug watches

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