Crash: a virtual machine I was running locked up and froze. I was forced to
power down the system to get it working again.
How do I check on dbus?
Nautilus opens correctly from command line.
Thanks,
Eric
On Mon, Mar 16, 2009 at 9:14 AM, Sebastien Bacher
wrote:
> thank you for your bug report, what do you call crash exactly? is dbus
> running on your system? can you run nautilus on a command line after the
> session start, does it work normally there?
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>
> --
> Nautilus crashes on Boot
> https://bugs.launchpad.net/bugs/342950
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nautilus” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: nautilus
>
> I am running Ubuntu 8.10. I had a rough shutdown and was forced to power
> down my laptop. I have a Dell XPS M1530.
>
> Now, each time I start my computer, I get the following errors:
>
> ERROR 1:
>
> An error occurred while loading or saving configuration information for
> Nautilus. Some of your configuration settings may not work properly.
>
> Details: Failed to contact configuration server; some possible causes are
> that you need to enable TCP/IP networking for ORBit, or you have stale NFS
> locks due to a system crash. See http://www.gnome.org/projects/gconf/ for
> information. (Details - 1: Could not send message to gconf daemon: Did not
> receive a reply. Possible causes include: the remote application did not
> send a reply, the message bus security policy blocked the reply, the reply
> timeout expired, or the network connection was broken.)
>
> ERROR 2:
>
> An error occurred while loading or saving configuration information for
> gnome-panel. Some of your configuration settings may not work properly.
>
> Failed to contact configuration server; some possible causes are that you
> need to enable TCP/IP networking for ORBit, or you have stale NFS locks due
> to a system crash. See http://www.gnome.org/projects/gconf/ for
> information. (Details - 1: Could not send message to gconf daemon: Did not
> receive a reply. Possible causes include: the remote application did not
> send a reply, the message bus security policy blocked the reply, the reply
> timeout expired, or the network connection was broken.)
>
--
Nautilus crashes on Boot
https://bugs.launchpad.net/bugs/342950
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
