At 1181292539 time_t, Simon Huggins wrote: > If you rebuild libxfcegui4, libxfce4util and the panel removing dh_strip > from debian/rules and ensuring they have -g and -Wall in CFLAGS then you > should be able to get a trace by running killing xfce4-panel and running > it in gdb. > > If you then move it to the screen that kills it and post the log here we > can have a look.
Ok, but bt in gdb won't return anything. 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 8511 error_code 8 request_code 7 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.) (gdb) bt No stack. I'll try to set a breakpoint somewhere... If you have a hint.. Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD
signature.asc
Description: Digital signature
_______________________________________________ Pkg-xfce-devel mailing list Pkg-xfce-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-xfce-devel
