Bug#396872: nautilus: crashes soon after it is called

[Francesco Potorti`]

>> Maybe I should set a breakpoint on gdk_x_error, as suggested by the
>> crash message?
>
> Yes, thanks.

Does not seem to be enough.  Still I see nothing:

Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (gdk_x_error) pending.
(gdb) r --sync /home/pot/cng
Starting program: /usr/bin/nautilus --sync /home/pot/cng
[Thread debugging using libthread_db enabled]
[New Thread 46912593872624 (LWP 6855)]
Breakpoint 2 at 0x2aaaabd4b560: file gdkmain-x11.c, line 598.
Pending breakpoint "gdk_x_error" resolved
[New Thread 1074006368 (LWP 6858)]
[New Thread 1082726752 (LWP 6864)]
[New Thread 1091447136 (LWP 6865)]
[New Thread 1100167520 (LWP 6866)]
[Thread 1082726752 (LWP 6864) exited]
[Thread 1100167520 (LWP 6866) exited]
[Thread 1091447136 (LWP 6865) exited]
[New Thread 1091447136 (LWP 6869)]
[New Thread 1100167520 (LWP 6870)]
[New Thread 1082726752 (LWP 6871)]
[New Thread 1108887904 (LWP 6872)]
[New Thread 1117608288 (LWP 6873)]
[New Thread 1126328672 (LWP 6874)]
The application 'nautilus' lost its connection to the display :1.0;
most likely the X server was shut down or you killed/destroyed
the application.

Program exited with code 01.
(gdb) thread apply all bt full
(gdb) bt
No stack.