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 552796 - Rhythmbox failed to create output image buffer 60x60 - No playback
Rhythmbox failed to create output image buffer 60x60 - No playback
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: playback
0.11.x
Other All
: Normal major
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-18 16:29 UTC by Ben Hall
Modified: 2009-08-22 09:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
output from GST_DEBUG=xvimagesink:5 rhythmbox (8.53 KB, text/plain)
2009-08-22 08:53 UTC, Charles Haynes
Details
output from lshw (10.12 KB, text/plain)
2009-08-22 08:57 UTC, Charles Haynes
Details

Description Ben Hall 2008-09-18 16:29:06 UTC
Please describe the problem:
Originally logged through Ubuntu's LaunchPad, they insisted that someone affected log it here.  The full thread can be found here:

https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/236201

The bug seems to only affect users with a Via Chrome driver.  If you have their driver and launch Rythmbox, it locks up (but doesn't crash) when you attempt tp playback MP3s.  Here are some details from the LaunchPad bug:

System: HP Mini-Note 2133

No music plays, but album art appears in bottom left corner as expected.

ProblemType: Bug
Architecture: i386
Date: Fri May 30 18:48:13 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.11.5-0ubuntu6
PackageArchitecture: i386
SourcePackage: rhythmbox
Uname: Linux 2.6.24-16-generic i686



Steps to reproduce:
1. Have a Via Chrome driver (used in the HP 2133 mini note, say)
2. Open Rythmbox
3. Try to play an MP3


Actual results:
You see the following error looping:
Rhythmbox failed to create output image buffer 60x60

The program becomes unresponsive but doesn't crash

Expected results:
Play MP3s.

Does this happen every time?
Yes, until you disable the visualization plugin (not that it was invoked - it's mere pressence triggers this behaviour.)

Other information:
My workaround from the experience (Found in the Ubuntu Launchpad bug)


I, too, had this problem on my HP 2133 with a Via Chrome driver. I can confirm that fiddling with the visualizations did indeed allow me to play MP3s.

Since I don't like visualizations anyway, I found that just disabling them with the gconf editor worked. Here's what I changed:

1) Open terminal
2) Run gconf-editor
3) Go to /apps/rhythmbox/plugins/visualizer/
4) Unchecked Active, checked hidden
5) Close gconf-editor

Now Rhythmbox plays MP3s, no errors.

Very odd bug, very odd workaround. Who'd have thought that enabling visualizations (not even using them) would affect MP3 playback.

There is more information in the LaunchPad bug including debug files:

http://launchpadlibrarian.net/15149148/rhythmbox-log.txt
Comment 1 Jonathan Matthew 2008-09-20 07:05:16 UTC
Sounds like an xv/xorg driver bug.  Try disabling xv in gstreamer-properties - select 'x window system (no xv)' for the default video output.
Comment 2 Jonathan Matthew 2008-09-22 10:19:06 UTC
Output from 'GST_DEBUG=xvimagesink:5 rhythmbox' might also be helpful.
Comment 3 Tobias Mueller 2009-03-29 19:03:06 UTC
Ben, could you please provide the information Jonathan has for and reopen this issue then? Thanks in advance!
Comment 4 Steve Magoun 2009-04-24 02:10:41 UTC
I think this might be caused a bug in xvimagesink that causes a similar symptom with certain combinations of video card + movie resolution.

See http://bugzilla.gnome.org/show_bug.cgi?id=577346 for an explanation, patch, and output from GST_DEBUG=xvimagesink:5.
Comment 5 Charles Haynes 2009-08-22 08:53:46 UTC
Created attachment 141389 [details]
output from GST_DEBUG=xvimagesink:5 rhythmbox
Comment 6 Charles Haynes 2009-08-22 08:57:13 UTC
Created attachment 141390 [details]
output from lshw
Comment 7 Charles Haynes 2009-08-22 08:58:31 UTC
I'm having the same problem on a fit-pc2. I've attached debug output and lshw output.
Comment 8 Jonathan Matthew 2009-08-22 09:05:19 UTC
What version of rhythmbox are you using?  The code that I suspect was causing this was removed in 0.12.2.