Bug 49648 - Cheap thrills with new Nautilus
Summary: Cheap thrills with new Nautilus
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nautilus   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Mason
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-22 19:05 UTC by Michal Jaegermann
Modified: 2007-04-18 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-22 19:05:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michal Jaegermann 2001-07-22 19:05:32 UTC
Description of Problem:

On the first try on a non-root acount Nautilus went first for a long
grind, totally screwed irreversibly my background without asking any
questions, opened some windowns and left some catathonic windows
with sliders which do not slide and other leftovers with any function
but to mess things around and non-updating icons.  What is worse it turned
that these windows cannot be removed, or killed with 'xkill'.  Restarting
a Gnome session was also of no use even after kicking out all Nautilus
processes with a help of process list in "Control Center".

Running nautilus-clean.sh also resulted only in a message
"nautilus-clean: No stale processes found." or trying 'killall nautilus'
also failed to get rid of all this detritus.

After a while empty window (only a gray background) with a title "Cancel
open?" poped out in the centre of my screen and could not be closed by any
normal means.  Only 'xkill' eventually removed it.

Rerunnning after deleting ~/.gconf and ~/.gconfd did not change very
much (well ~/.gconfd/saved_state was no longer empty but 6012 bytes

Aftef cleaning up all nautilus junk from ~/.gnome/session manually,
restarting and trying to restart nautilus manually I got in a terminal
window an unending stream of messages like this:

esd: Failed to fix mode of /tmp/.esd to 1777.
Try -trust to force esd to start.
esd: Esound sound daemon unable to create unix domain socket:
The socket is not accessible by esd.

Checking with 'find /tmp/.esd -ls' revealed this:

112520    1 drwxrwxrwt   2 root     root         1024 Jul 21 16:52
112521    0 srwxrwxrwx   1 root     root            0 Jul 21 16:52

Why these attempt to create something which already exists, and seems
to be - wonders of wonders - even accesible, your guess is as good
as mine.

What a great stuff!!  I am all thrilled.

Comment 1 Havoc Pennington 2001-07-22 21:10:51 UTC
The only thing in here I can reproduce is that Nautilus hangs due to some esound
hosage; this was a bug in libesd. It should be fixed in current rawhide esd

If you still have problems with rawhide gnome-vfs, esd, Nautilus, etc., please
be more specific about exactly what happens and file a separate report for each
issue. ;-)

Comment 2 Michal Jaegermann 2001-07-22 21:56:09 UTC
I have no idea with what specific underlying packages I may have problems.
I can only see that I brought this turkey into the picture and things are
going downhill pretty fast.  To expect from me to understand deep 
interdependencies in the whole system is a bit too much.

Note You need to log in before you can comment on or make changes to this bug.