nautilus fails in sudo mode

Thank you for your bug. What do you call "screen will lock"? DO you have to restart your computer? Are the keyboard and mouse still working? If the bug is with nautilus only, could you install libglib2.0-0-dbg libgtk2.0-0-dbg libgnomevfs2-0-dbg nautilus-dbg and get a backtrace of the hang?
- sudo gdb nautilus
(gdb) run
... get the hang, do <Ctrl-C> on the gdb prompt then
(gdb) thread apply all bt

Only the window with the gksudo nautilus session running becomes unresponsive. Everything else works. It does not require a restart. I will attempt to install and run the debug packages you requested.

OK, I have run the debug as you requested. After the screen became unresponsive requiring a force quit, (gdb) produced the following:
Program exited normally.
(gdb) Quit
(gdb) thread apply all bt
(gdb)

Here is the output of the entire session in the terminal window:

marty@tux:~$ sudo gdb nautilus
Password:
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread -1226762576 (LWP 15847)]

(nautilus:15847): libgnomevfs-WARNING **: Failed to open session DBUS connection: 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.
Volume monitoring will not work.
Initializing nautilus-open-terminal extension

Program exited normally.
(gdb) Quit
(gdb) thread apply all bt
(gdb)

 The warning about the DBUS connection is something I always see when running nautilus in sudo mode. It was there in Dapper also. It did not start with this problem.

according to that debug session you closed nautilus normally, did you the lock problem?

Yes, the lock problem occurred during this debug session. I had to click the close window button several times until a force quit dialog appeared. Debug did not seem to find anything unusual though.

Le jeudi 07 décembre 2006 à 23:32 +0000, Martin G Miller a écrit :
> Yes, the lock problem occurred during this debug session. I had to
> click the close window button several times until a force quit dialog
> appeared. Debug did not seem to find anything unusual though.

don't click the close window button when you get the lock, go to gdb and
get a backtrace

I just tried for several minutes to reproduce the problem in debug mode and could not. I navigated throughout my file system to areas owned by both user and root. I copied and pasted files owned by root to my user desktop and did not experience any unusual behavior. When I first reported this bug, I could reproduce it within seconds. I did install more than 30 updates in the last 2 days. Perhaps something in them has fixed this problem?

maybe, closing the bug for now then. Feel free to reopen if you get the bug again