[Pkg-xfce-devel] Bug#470227: Bug#470227: Bug#470227: xfce4-mcs-manager: panels disappear when selecting screen for panel to use

[Vincent.McIntyre at csiro.au]

>
> Hmhm, this reminds me of a bug with gtk 2.11/2.12. This was fixed in
> 4.4.2, but you don't have (at least you shouldn't) have gtk 2.12.
>

% apt-show-versions |grep libgtk
libgtksourceview-common/etch uptodate 1.8.3-1
libgtkhtml3.8-15/etch uptodate 3.12.1-2
libgtk2-perl/etch uptodate 1:1.140-1
libgtksourceview1.0-0/etch uptodate 1.8.3-1
libgtk2.0-common/etch uptodate 2.8.20-7
libgtk1.2-common/etch uptodate 1.2.10-18
libgtk2.0-bin/etch uptodate 2.8.20-7
libgtk2.0-dev/etch uptodate 2.8.20-7
libgtk1.2/etch uptodate 1.2.10-18
libgtk2.0-0/etch uptodate 2.8.20-7

> Can you try to make a backtrace? See
> http://wiki.debian.org/HowToGetABacktrace

I tried this but could not get anything particularly useful, see below.
I'm probably doing something wrong and didn't have time to dig far.

The wiki page is quite helpful but could use a couple of additions;
 - how does one verify that the binaries in the new package _have_ debug
   symbols in them? 'strings'? 'nm?' It seems that if one gets a lot of
   output from 'nm /usr/bin/xfce4-panel |less' you have got debugging
   symbols, but is there a better diagnostic than this?

 - how exactly does one set a break point for gdk_x_error()?

Cheers
Vince

------------------------------- log ------------------------------
# as before, kill xfce4-panel by trying to move panel 2 to a different
# screen. The panel appears briefly on monitor 1, then the program
# exits.
# Then we open a terminal and run as follows:

% gdb /usr/bin/xfce4-panel
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db
library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) set pagination 0
(gdb) run --sync
Starting program: /usr/bin/xfce4-panel --sync
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1218181440 (LWP 29743)]
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 38057 error_code 8 request_code 56 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.)

Program exited with code 01.
(gdb) bt
No stack.
(gdb)  thread apply all bt
(gdb) run --sync
Starting program: /usr/bin/xfce4-panel --sync
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1218603328 (LWP 29758)]
The program 'xfce4-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 37088 error_code 8 request_code 56 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.)

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