rhythmbox exits suddenly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rhythmbox |
Invalid
|
Undecided
|
Unassigned | ||
rhythmbox (Ubuntu) |
Invalid
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: rhythmbox
~$ rhythmbox --sync
** (rhythmbox:10848): CRITICAL **: atk_object_
** (rhythmbox:10848): CRITICAL **: atk_object_
(<unknown>:10866): GLib-WARNING **: g_set_prgname() called multiple times
(<unknown>:10870): GLib-WARNING **: g_set_prgname() called multiple times
(<unknown>:10874): GLib-WARNING **: g_set_prgname() called multiple times
(<unknown>:10878): GLib-WARNING **: g_set_prgname() called multiple times
(<unknown>:10882): GLib-WARNING **: g_set_prgname() called multiple times
(<unknown>:10886): GLib-WARNING **: g_set_prgname() called multiple times
The program 'rhythmbox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 24244 error_code 3 request_code 20 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.)
-------
My system is Ubuntu 9.10 x86 on Acer Aspire 5920,rhythmbox 0.12.6 with compiz
Plz help as i really love rhythmbox a lot!
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http:// wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.