Nautilus fails to start with segmentation fault.[Ubuntu - 9.10]

Bug #488699 reported by RodGer
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

It happens from time to time but after rebooting the problem is gone. Since now I just couldn't start nautilus sometimes and I just rebooted hoping that it will be ok. This time I tried to call nautilus using the terminal to see if any error message comes up. This is the output in the terminal:
$ nautilus

(nautilus:2454): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
Initializing nautilus-gdu extension
** Message: Initializing gksu extension...

** (nautilus:2454): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:2454): WARNING **: No marshaller for signature of signal 'DownloadFinished'

** (nautilus:2454): WARNING **: No marshaller for signature of signal 'ShareCreateError'

** (nautilus:2454): CRITICAL **: nautilus_directory_file_monitor_add: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed

(nautilus:2454): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:2454): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(nautilus:2454): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:2454): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

** (nautilus:2454): CRITICAL **: nautilus_directory_file_monitor_add: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed

(nautilus:2454): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:2454): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(nautilus:2454): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:2454): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

** (nautilus:2454): CRITICAL **: nautilus_directory_get_uri: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed
Segmentation fault

-------------------------------------------------------------------------

Of course it is not a problem that affects everybody. Maybe this bug shows up under very specific conditions thus it's difficult to reproduce but when it happens, it seems to be a pretty serious bug. I hope somebody more experienced will get to find the source of the problem.

ProblemType: Bug
Architecture: i386
Date: Thu Nov 26 13:07:12 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: nautilus 1:2.28.1-0ubuntu2
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-15-generic i686

Revision history for this message
RodGer (rodger) wrote :
tags: added: fails fault nautilus segmentation
summary: - Nautilus fails to start with segmentation fault.
+ Nautilus fails to start with segmentation fault.[Ubuntu - 9.10]
Revision history for this message
Sebastien Bacher (seb128) 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):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Sergiy Matrunchyk (sergiy.matrunchyk) wrote :

I confirm this bug. It's affect me too.

Revision history for this message
milad-hero (miladbashiri) wrote :

I had the same problem, and fixed it by deleting the folder ~/.local/share/gvfs-metadata

Revision history for this message
David Robert Lewis (afrodeity) wrote :

I have same problem. Nautilus unresponsive. Deleting the gvfs-metadata didn't help either.

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.