[Pkg-audacious-maintainers] Bug#523916: Must be doing something wrong

[Chris Dos]

I'm trying to get you the backtrace.  I've installed the debug packages for audacious and I'm running this:

gdb /usr/bin/audacious
run

Output is as follows when I hit play and have the OSD enabled:

This GDB was configured as "i486-linux-gnu".
(gdb) run
Starting program: /usr/bin/audacious
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb726f750 (LWP 10542)]
[New Thread 0xb7009b90 (LWP 10545)]
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi-plug(i_backend.c:i_backend_load:107): loading backend '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so'
amidi-plug(i_backend.c:i_backend_load:145): backend /usr/lib/audacious/Input/amidi-plug/ap-alsa.so (name
'alsa') successfully loaded
[New Thread 0xb52eeb90 (LWP 10553)]
[New Thread 0xb121cb90 (LWP 10554)]
[New Thread 0xb0950b90 (LWP 10557)]
[New Thread 0xabffeb90 (LWP 10558)]
The program 'audacious' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 21 error_code 11 request_code 53 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.


bt
No stack.



So it looks like it's not outputting the backtrace.  What am I doing wrong so I can get you the correct
information?

	Chris