Comment 4 for bug 75303

Revision history for this message
Sven Herzberg (herzi) wrote : Re: [edgy] Crashes

There won't be a backtrace: totem prints this on stderr:

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 48 error_code 11 request_code 141 minor_code 19)
  (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.)

However, starting totem with --sync doesn't help as totem complains like this:
Option '--sync' is unknown and was ignored

Not pretty useful, heh?