Comment 102 for bug 150471

I did it again!

This time I used (like the first time) directories full of *.desktop files.
After copying and changing ownership of a bunch of files (procedure described in earlier messages), nautilus went crazy again. It did not happen the first time, I had to repeat the trick 3 or 4 times.

I suppose desktop files are particularly difficult to show: nautilus has to read contents to show 'Name' and 'Icon' instead of the real file name and default document type icon.

Next follows the relevant section of .xsession-errors (Lines not coming from the XSu instance which launched the root_user_nautilus edited out):
{
#### XSu-12288. BEGIN.
XSu-12288.CmdLine: >XSu DefaultFileSystemBrowser /<
XSu-12288: (nautilus:12367): GnomeUI-WARNING **: While connecting to session manager:
XSu-12288: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
XSu-12288: ** (nautilus:12367): WARNING **: No description found for mime type "x-special/socket" (file is ".gnome-system-monitor.manolo"), please tell the gnome-vfs mailing list.
XSu-12288: /home/common/bin/DefaultFileSystemBrowser: line 590: 12367 Killed $Application $Options "$@"
#### XSu-12288. END.
}
As you can see nautilus went crazy again without giving any error messages.

The last line shows when I killed the rogue nautilus process (It was originally invoked with a switchboard shell script: DefaultFileSystemBrowser) from the root terminal.

The root_user_nautilus' window went blank like the first time.

Th mail account I used to register (several years ago) is chockful with spam. If you want details please use glesialoAtgmailDotcom.

Saludos,
Manolo.