maybe, closing the bug for now then. Feel free to reopen if you get the
bug again
** Changed in: nautilus (Ubuntu)
Status: Needs Info = Rejected
--
nautilus fails in sudo mode
https://launchpad.net/bugs/73586
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Le jeudi 07 décembre 2006 à 23:32 +, 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
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
according to that debug session you closed nautilus normally, did you
the lock problem?
--
nautilus fails in sudo mode
https://launchpad.net/bugs/73586
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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.
--
nautilus fails in sudo mode
https://launchpad.net/bugs/73586
--
ubuntu-bugs mailing list
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
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.
--
nautilus fails in sudo mode
https://launchpad.net/bugs/73586
--
ubuntu-bugs mailing list
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:
[EMAIL PROTECTED]:~$ sudo
