Thank you all for noticing this, but we need more information to debug this.
The easiest thing to do is:
1) create a file named: "~/nautilus-debug-log.conf"
2) edit it and add:
[debug log]
max lines = 1000
enable domains = async
3) when nautlus crashes, attach the file "~/nautilus-debug-log.txt" to this bug report.
Thank you all for noticing this, but we need more information to debug this. debug-log. conf" debug-log. txt" to this bug report.
The easiest thing to do is:
1) create a file named: "~/nautilus-
2) edit it and add:
[debug log]
max lines = 1000
enable domains = async
3) when nautlus crashes, attach the file "~/nautilus-
If that doesn't work, we would need a complete backtrace to properly debug this (one without ?? in it). wiki.ubuntu. com/DebuggingPr ogramCrash
The instructions are here:
http://
specifically follow: /wiki.ubuntu. com/DebuggingPr ogramCrash# Hardy%20Heron% 208.04, %20Intrepid% 20Ibex% 208.10, %20and% 20Jaunty% 20Jackalope% 209.04
https:/
then: /wiki.ubuntu. com/Backtrace , but follow the instructions of a program already running
https:/