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

2006-11-07 Thread Francesco Potorti`
> Weird. Could you try two times in a row (by running "run" a second > time), it seems like nautilus fails connecting to X?!? Nothing changes. See below. More things: - I don't know how to make sure that the debugging version of nautilus is indeed being used - before dying, nautilus draws a

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

2006-11-06 Thread Francesco Potorti`
>> 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. > > Weird. Could you try two times in a row (by running "run" a second > time), it seems like nautilus fails connecting to X?!? I will and r

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

2006-11-05 Thread Loïc Minier
On Sat, Nov 04, 2006, Francesco Potorti` wrote: > 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. Weird. Could you try two times in a row (by running "run" a second time), it seems like nauti

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

2006-11-03 Thread 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 Startin

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

2006-11-03 Thread Loïc Minier
On Fri, Nov 03, 2006, Francesco Potorti` wrote: > Maybe I should set a breakpoint on gdk_x_error, as suggested by the > crash message? Yes, thanks. -- Loïc Minier <[EMAIL PROTECTED]>

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

2006-11-03 Thread Francesco Potorti`
> backtrace by running "gdb /usr/bin/nautilus" and running: >run --sync >(wait for crash) >thread apply all bt full Done, but the last line gives no output. The gdb prompt just returns. Issuing just "bt" gives "No stack.". Maybe I should set a breakpoint on gdk_x_error, as suggested

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

2006-11-03 Thread Loïc Minier
Hi, On Fri, Nov 03, 2006, Francesco Potorti` wrote: > ~$ nautilus ~/cng & disown > [1] 2816 > --- after a couple of minutes I get this on the terminal: > > ~$ The program 'nautilus' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadPixm

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

2006-11-03 Thread Francesco Potorti`
Package: nautilus Version: 2.14.3-3 Severity: normal ~$ nautilus ~/cng & disown [1] 2816 --- after a couple of minutes I get this on the terminal: ~$ The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadPixmap (invalid Pixmap p