Linux Mint Forums • [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawable

Page 1 of 1

[CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawable

Posted: Thu Aug 23, 2012 12:03 pm

by äxl

Since I haven't read anything so far about it the following could be a problem with my sources: MATE + Debian {Wheezy} (http://forums.linuxmint.com/viewtopic.p ... 9&t=101920; see also my signature).

Caja and MATE-Terminal crash constantly sometimes alone, sometimes together. .xsession-errors shows:

Code: Select all

The program 'mate-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 384693 error_code 9 request_code 149 minor_code 4)
  (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.)
The program 'caja' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 3962131 error_code 4 request_code 55 minor_code 0)
  (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.)

Always with same error_code, request_code and minor_code.
Also much of this (though I don't think it has something to do with the crash):

Code: Select all

** (caja:2168): CRITICAL **: mate_bg_crossfade_start: assertion `fade->priv->fading_pixmap != NULL' failed

Maybe this is related: https://github.com/mate-desktop/mate-fi ... /issues/29
Should I try apport?

I tried to delete .mateconf: http://forums.linuxmint.com/viewtopic.php?f=47&t=78634
And tried this:
https://bugs.launchpad.net/ubuntu/+sour ... /+bug/5823
For Composite, Xinerama and ARGB I get this in Xorg.0.log:

Code: Select all

[    22.393] (**) Option "Xinerama" "False"
[    22.405] (**) Extension "Composite" is disabled
[    22.405] (WW) Ignoring unrecognized extension "AddARGBGLXVisuals"
[    22.695] (II) Initializing built-in extension XINERAMA
[    22.695] (II) Initializing built-in extension COMPOSITE

I tried debugging as following:

Code: Select all

~ $ cat gdb-caja.sh
#!/bin/bash
gdb -ex "set breakpoint pending on" -ex "break gdk_x_error" -ex run --args caja --sync | tee /media/DAT/dbg/caja-gdb.log

In Startup Applications I have "mate-terminal --tab -e /home/user/caja-gdb.sh --tab" and after Caja crashes:

Code: Select all

~ $ cat /media/DAT/dbg/caja-gdb.log
GNU gdb (GDB) 7.4-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/caja...Reading symbols from /usr/lib/debug/usr/bin/caja...done.
done.
Breakpoint 1 (gdk_x_error) pending.
Starting program: /usr/bin/caja computer:/// --sync
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffee482700 (LWP 2356)]
[New Thread 0x7fffecda1700 (LWP 2357)]
Initializing caja-open-terminal extension
[Thread 0x7fffecda1700 (LWP 2357) exited]
...
[Thread 0x7ffff7fbe980 (LWP 2353) exited]
[Inferior 1 (process 2353) exited with code 01]
(gdb) thread apply all bt
(gdb) bt
(gdb) backtrace
(gdb) thread apply all backtrace

Nothing.
Process 2353 was the original caja which also manages my desktop. /apps/caja/preferences/show_desktop is set to true.
Maybe that's the issue but w/o it what would draw my desktop other than Compiz which I don't want to use.
The only backtrace I can get is when it seems that Caja sometimes loses it's history. After I stop it with Ctrl+c it shows:

Code: Select all

GNU gdb (GDB) 7.4-debian
...
[New Thread 0x7fffee482700 (LWP 3214)]
...
Program received signal SIGINT, Interrupt.
0x00007ffff2b5acc3 in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) thread apply all bt

Thread 2 (Thread 0x7fffee482700 (LWP 3214)):
#0  0x00007ffff2b5acc3 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff3dd0b36 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff3dd0f9a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff54068f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007ffff3df2435 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff2e1ab50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007ffff2b6590d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffff7fbe980 (LWP 3211)):
#0  0x00007ffff2b5acc3 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff3dd0b36 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff3dd0f9a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff5ca0a77 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#4  0x000000000043361c in main (argc=1, argv=0x7fffffffe998) at caja-main.c:574

That's the first mentioning of LWP 3211 ... which is I assume x-caja-desktop ...?

Finally Caja and MATE-Terminal (shortly after Caja losing history) crashing and quitting together so no bt:

Code: Select all

Program received signal SIGHUP, Hangup.
[Switching to Thread 0x7fffee487700 (LWP 2549)]
0x00007ffff2959cc3 in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) Error detected on fd 0
error detected on stdin
A debugging session is active.

	Inferior 1 [process 2541] will be killed.

Quit anyway? (y or n) EOF [assumed Y]

With crash and the ability to get a bt:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff3eac630 in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
(gdb) 
(gdb) thread apply all bt

Thread 2 (Thread 0x7fffee487700 (LWP 12337)):
#0  0x00007ffff2959cc3 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff3bccb36 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff3bccf9a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff52028f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007ffff3bee435 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff2c19b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007ffff296490d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffff7fbe980 (LWP 12334)):
#0  0x00007ffff3eac630 in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#1  0x0000000000464900 in fill_menu (window=0x9f6000, menu=0xa02860, back=1) at caja-navigation-action.c:151
#2  0x00007ffff3e8a73a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x00007ffff3ea2fb1 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4  0x00007ffff3ea3ab2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x00007ffff5ab3baf in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#6  0x00007ffff5ab3eb8 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#7  0x00007ffff5a9f538 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#8  0x00007ffff3e8a512 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x00007ffff3e9b5e1 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff3ea35ee in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007ffff3ea3ab2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff5bb8451 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x00007ffff5a9d6c3 in gtk_propagate_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#14 0x00007ffff5a9da23 in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#15 0x00007ffff57091ec in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#16 0x00007ffff3bcc853 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff3bccba0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff3bccf9a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff5a9ca77 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x0000000000451ee3 in main (argc=1, argv=0x7fffffffe978) at caja-main.c:574
(gdb) c
Continuing.
[Thread 0x7ffff7fbe980 (LWP 12334) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) thread apply all bt
(gdb)

And I don't know how to debug mate-terminal:

Code: Select all

~ $ gdb mate-terminal
...
Reading symbols from /usr/bin/mate-terminal...(no debugging symbols found)...done.

There's no mate-terminal-dbg and I have the MATE's core and lib packages installed.

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Tue Sep 04, 2012 2:55 pm

by äxl

This output in .xsession-errors after a Caja crash is new:

Code: Select all

X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  149 (RENDER)
  Minor opcode of failed request:  4 (RenderCreatePicture)
  Resource id in failed request:  0x4600002
  Serial number of failed request:  19860
  Current serial number in output stream:  19862

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Thu Sep 06, 2012 10:08 am

by äxl

Seems this is from a Conky crash:

Code: Select all

X Error of failed request:  BadDamage (invalid Damage parameter)
  Major opcode of failed request:  153 (DAMAGE)
  Minor opcode of failed request:  3 (XDamageSubtract)
  Serial number of failed request:  175781
  Current serial number in output stream:  175782

Caja crash from dmesg:

Code: Select all

caja[2310]: segfault at 7f1a00000006 ip 00007f1a0323063c sp 00007fffcc2421b0 error 4 in libgobject-2.0.so.0.3200.2[7f1a031fd000+4e000]

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Thu Sep 06, 2012 10:34 am

by zerozero

hi äxl

libgobject-2.0.so.0.3200.2

takes me to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673211 might be completely unrelated

the BadDrawable error has several bugs and topics over the net (some quiet old) and is either assigned to opengl or xorg (one hit mentions openSSH http://www.openssh.com/faq.html#3.13)
https://www.google.com/search?q=X+Error ... HwCg&gbv=2

don't know, yours is a very special setup

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Sun Sep 09, 2012 3:17 am

by äxl

zerozero wrote:
libgobject-2.0.so.0.3200.2

Thanks, zerozero. But I get this error much more often with operapluginwrapper (Caja only twice since June 25).

the BadDrawable error has several bugs and topics over the net (some quiet old) and is either assigned to opengl or xorg

Since Nouveau doesn't have OpenGL (right?) and Conky crashes similar I guess this is really a X error ...

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Fri Sep 14, 2012 6:49 am

by äxl

Even MATE Settings Daemon:

Code: Select all

The program 'mate-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 26061 error_code 8 request_code 15 minor_code 0)
  (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.)

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Sun Sep 16, 2012 10:31 am

by äxl

Code: Select all

The program 'caja' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 49630 error_code 4 request_code 55 minor_code 0)
  (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.)
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  66 (X_PolySegment)
  Resource id in failed request:  0x4000002
  Serial number of failed request:  240695
  Current serial number in output stream:  240706

Re: [CRASH] Caja, MATE-Terminal break w/ BadPixmap, BadDrawa

Posted: Wed Sep 26, 2012 9:53 am

by äxl

Code: Select all

The program 'caja' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 116191 error_code 4 request_code 55 minor_code 0)
  (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.)
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  135 (DOUBLE-BUFFER)
  Minor opcode of failed request:  3 (DBESwapBuffers)
  Resource id in failed request:  0x4800001
  Serial number of failed request:  155153
  Current serial number in output stream:  155163