Public bug reported:
Binary package hint: nautilus
**Problem:-
- Several instances of Nautilus are opened directly after start up elevating
CPU usage to +90%.
- Nautilus becomes completely non-responsive yielding "(nautilus:10975):
Unique-DBus-WARNING **: Error while sending message: Message did not receive a
reply (timeout by message bus)" for any command such as "nautilus -q"
- To respond again, it has to be killed, "killall nautilus", several times as
well.
***What was expected:-
- Normal start up with a responding Nautilus.
***What happened instead:-
- See in problem details.
_______________
**Environment:-
- Nautilus 1:2.27.92-0ubuntu1.
- GNOME 2.27.92
- Ubuntu 9.10 Alpha 5 i386. (upgraded from Jaunty 9.04 stable using
"update-manager -d")
- 2.6.31-10-generic Linux kernel.
______________
**Attachments:
Xsession-error + 2 screenshots of how the gnome-panel looked like. (in
Files.tar.gz, see below)
______________
**Hypothesis:
- As you might notice in the xsession error log, nautilus extensions are being
initialized then shut down repeatedly. So, I suppose the problem is somehow
related to nautilus extensions. I tried removing
"/usr/lib/nautilus/extensions-2.0" components and rebooted but the same
behaviour was observed.
The extension folder contains:-
"libnautilus-gksu.so libnautilus-python.so libnautilus-wallpaper.so
libnautilus-open-terminal.so libnautilus-sendto.so python
libnautilus-python.la libnautilus-share.so"
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: 9.10 karmic nautilus
--
Several Nautilus instances at start up.
https://bugs.launchpad.net/bugs/430097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
