© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
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-
(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-
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.