Bug#558351: Nautilus exits (crashes?) when moving icons on a 2nd screen

Adam Majer adamm at zombino.com
Sat Nov 28 17:48:47 UTC 2009


On Sat, Nov 28, 2009 at 08:12:57AM +0100, Josselin Mouette wrote:
> Le vendredi 27 novembre 2009 à 23:46 -0600, Adam Majer a écrit : 
> > When on a second screen (another X instance, different adapter, same X
> > session), nautilus will restarts when trying to move an icon. It works
> > just fine on the main screen.
> 
> Could you please obtain a gdb backtrace? Please install nautilus-dbg and
> attach gdb to the running nautilus process:
> gdb /usr/bin/nautilus $(pidof nautilus)
> … blah blah blah
> (gdb) cont
> [ Do something that makes nautilus crash ]
> (gdb) thread apply all bt full
> 
> And send the output to the bug report.

I cannot get you the gdb backtrace because stupid nautilus just exits
with status 1 instead of crashing. The nautilus crap out is 100%
repeatable. From the strace it seems it has something to do with X
error message,

open("/usr/share/X11/XErrorDB", O_RDONLY) = 33
fstat(33, {st_mode=S_IFREG|0644, st_size=41481, ...}) = 0
read(33, "! $Xorg: XErrorDB,v 1.3 2000/08/"..., 41481) = 41481
close(33)                               = 0
write(2, "The program 'nautilus' received "..., 570) = 570
writev(16, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12
close(16)                               = 0
writev(14, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12
close(14)                               = 0
close(13)                               = 0
close(12)                               = 0


Found a cool trick to redirect descriptors with debugger :) And the
stderr printed from nautilus is,

The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 17866 error_code 8 request_code 142 minor_code 2)
  (Note to programmers: normally, X errors are reported
  asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
   function.)

Ok, so let's follow what the error says to do, except there is no such
thing as gdk_x_error. At least that's what gdb reports. Seems there is
some errors in gdk or someplace that displays the *wrong* message!


The only other error I get is on start,
  * (nautilus:8138): WARNING **: Unable to add monitor: Not supported


Anyway, any idea regarding the gdk_x_error and where the new X errors
are caught?

- Adam






More information about the pkg-gnome-maintainers mailing list