Nautilus failed to start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm not sure this is reliably reproducible, but maybe there's something helpful in the logs. I can't seem to start up Nautilus and if I click on the folder icon next to a downloaded file in the Downloads drop-down in Firefox then Firefox freezes. It was working fine and then after I had closed it I couldn't start it again when I tried later.
If I run Nautilus in Terminal it hangs for a while and then the following appears in Terminal before it gives up:
(nautilus:15487): GLib-GIO-CRITICAL **: g_dbus_
(nautilus:15487): GLib-GIO-CRITICAL **: g_dbus_
Could not register the application: Timeout was reached
(nautilus:15487): Gtk-CRITICAL **: gtk_icon_
(nautilus:15487): GLib-GObject-
(nautilus:15487): GLib-GObject-
The Nautilus process was still running (which it does normally). After I Ended the process in System Monitor I was able to start it up again and now it works fine, I'm able to open and close the app again. Something went wrong though and, though this is not easily reproducible, stuff like this shouldn't happen in the first place!
Probably because I Ended the process and then started Nautilus again, the 'File, Edit, View,...' menus now come up inside the window rather than in the Indicator Applet Appmenu in the panel (I'm sure it'll work fine if I restart the computer).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.18.
ProcVersionSign
Uname: Linux 4.4.0-25-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME-Flashback
Date: Sat Jun 18 15:56:43 2016
GsettingsChanges:
b'org.
b'org.
InstallationDate: Installed on 2016-04-26 (52 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
summary: |
- Nautilus fails to start + Nautilus failed to start |
Status changed to 'Confirmed' because the bug affects multiple users.