Ubuntu
nautilus package

nautilus is failing to start, with segmentation fault

Bug #865536 reported by Nicolás Abel Carbone on 2011-10-03

This bug report is a duplicate of: Bug #865567: ubuntuone-client-gnome needs to install gsettings schemas. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

After recent updates, nautilus is not starting. This is the output when trying to open it in the terminal:

nicolas@nicolas-lap-lin:~$ nautilus
** (nautilus:7319): DEBUG: SyncDaemon already running, initializing SyncdaemonDaemon object
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 0.6.8
Initializing nautilus-gdu extension

(nautilus:7319): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed

(nautilus:7319): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
Violación de segmento (`core' generado)
nicolas@nicolas-lap-lin:~$

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Mon Oct 3 14:07:30 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
SourcePackage: nautilus
UpgradeStatus: Upgraded to oneiric on 2011-10-01 (2 days ago)

Tags:

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2011-10-03:

Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (115 bytes, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (356 bytes, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-10-03:

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.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

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.