After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697532 - Crash after clicking the Music ▸ button
Crash after clicking the Music ▸ button
Status: RESOLVED DUPLICATE of bug 697915
Product: rhythmbox
Classification: Other
Component: general
2.99
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-08 04:42 UTC by Jeremy Bicha
Modified: 2013-04-12 23:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
crash report (200.00 KB, text/plain)
2013-04-08 05:23 UTC, Jeremy Bicha 		Details

Description Jeremy Bicha 2013-04-08 04:42:47 UTC 
Rhythmbox 2.99 on Ubuntu 13.04

1. Open Rhythmbox
2. Click the ▸ button next to Music in the sidebar.

What happens:
Rhythmbox crashes

(rhythmbox:3621): Gdk-ERROR **: The program 'rhythmbox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 4513 error_code 129 request_code 131 minor_code 40)
  (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 GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
Comment 1 Jonathan Matthew 2013-04-08 04:59:45 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Jeremy Bicha 2013-04-08 05:00:12 UTC 
This happens with the ▾ buttons in the sidebar too.
Comment 3 Jeremy Bicha 2013-04-08 05:23:11 UTC 
Created attachment 240925 [details]
crash report
Comment 4 Jonathan Matthew 2013-04-12 23:34:16 UTC 

*** This bug has been marked as a duplicate of bug 697915 ***