Nautilus fails to start with segmentation fault.[Ubuntu - 9.10]
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
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_
(nautilus:2454): GLib-GObject-
(nautilus:2454): GLib-GObject-
(nautilus:2454): GLib-GObject-
(nautilus:2454): GLib-GObject-
** (nautilus:2454): CRITICAL **: nautilus_
(nautilus:2454): GLib-GObject-
(nautilus:2454): GLib-GObject-
(nautilus:2454): GLib-GObject-
(nautilus:2454): GLib-GObject-
** (nautilus:2454): CRITICAL **: nautilus_
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=
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: nautilus
Uname: Linux 2.6.31-15-generic i686
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.