Rhythmbox failed to create output image buffer 60x60

Bug #236201 reported by elgilicious
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Rhythmbox
Unknown
Medium
gst-plugins-base0.10 (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

OS: Linux Mint Elyssa RC2
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
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: rhythmbox
Uname: Linux 2.6.24-16-generic i686

Tags: apport-bug
Revision history for this message
elgilicious (elginearl-deactivatedaccount) wrote :
Revision history for this message
Jonathan Ernst (jonathan.ernst) wrote :

I have another user with the same problem :

"failed to create output image buffer of 60x50 pixels"

Changed in rhythmbox:
status: New → Confirmed
Revision history for this message
Jonathan Ernst (jonathan.ernst) wrote :

See also http://ubuntuforums.org/showthread.php?t=803889

And my user also has an HP UMPC.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
 We have instructions on debugging some types of problems. http://wiki.ubuntu.com/DebuggingProcedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Adam Niedling (krychek) wrote :

I just encountered this bug. Rhythmbox says: "Failed to create output image buffer of 60x60 pixels" when I try to play an mp3.
Totem can play mp3s and youtube also works.

Changed in rhythmbox:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

May someone experiencing the bug get a rhythmbox debug log? just run rhythmbox from the command line as: rhythmbox --debug &> rhythmbox-log.txt and attach that file to the report, thanks.

Changed in rhythmbox:
status: New → Incomplete
Revision history for this message
Adam Niedling (krychek) wrote :

Here it is. Some messages are not in English thou.. I hope it's helpful.

Changed in rhythmbox:
status: Incomplete → New
Revision history for this message
Keith (kjackson7-93) wrote :

I am experiencing the same problem. Rhythmbox was working fine until I followed the instructions at http://wiki.ubuntu.com/LaptopTestingTeam/HP2133 for upgrading the video driver. Also when I load rhythmbox and click on visualization and play a song it works. As soon as I click on "browse" the song stops playing.

Attached is a copy of the log.

Revision history for this message
Sebastien Bacher (seb128) wrote :

seems to be a video driver dependent issue

Revision history for this message
benmhall (ubuntu-linuxgruven) wrote :

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.

Revision history for this message
Adam Niedling (krychek) wrote :

Benmhall's workaround works. Thx.
I realized I started having this issue since I installed the via driver from linux.via.com.tw . The driver isn't exactly for my hardware but other than this I had no problems.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could anybody having the issue report it directly to bugzilla.gnome.org?

Changed in rhythmbox:
status: New → Incomplete
Revision history for this message
Seba78 (teo78) wrote :

This is the solution, Congratulations. Sebastian Ramírez from Uruguay, South America.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

no response, closing the report, feel free to re open it if you manage to reproduce the bug with hardy or intrepid and sent the report upstrema, thanks.

Changed in rhythmbox:
status: Incomplete → Invalid
Revision history for this message
benmhall (ubuntu-linuxgruven) wrote :

Since nothing has been fixed here, this bug shouldn't be closed.

The problem still exists between the Via driver and Rhythmbox. Sure, the problem may well be with the Via driver, but surely Rhythmbox shouldn't crash when playing MP3 audio (not even using visualizations) because of a bug in the video driver. Moreover, the crash in no way indicates a problem with a video driver or the player. At the very least, a better error message would be in order, no?

The bug has been confirmed by multiple people with Hardy and derivative distributions.

Changed in rhythmbox:
status: Invalid → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has not been closed because it's fixed but because somebody having the issue needs to send it to bugzilla.gnome.org,

Changed in rhythmbox:
status: Confirmed → Incomplete
Revision history for this message
benmhall (ubuntu-linuxgruven) wrote :

Just to be clear, what you would like is for someone to send the text files that have been included in this bug report to a related bug report in bugzilla.gnome.org. Is this correct?

(If so, I must say that it would seem easier for end-users who have been affected and have figured out a workaround to just let this artificially close than it would to take the action that you require. )

Reading and following this bug report, I had no idea that action at bugzilla.gnome.org was needed by one of us. Where would this be indicated so that I may better understand Ubuntu's bug tracking system for other issues?

Cheers,

Ben

Revision history for this message
Sebastien Bacher (seb128) wrote :

ubuntu is not writting rhythmbox and just distributing it, the people who write the software use bugzilla.gnome.org and not launchpad. The ubuntu bug triage team usually send the issues ubuntu users are having there, but in case where the bug requires a specific configuration to be trigger it's better than somebody who has the issue and can do testing send the bug

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Nobody seems interested in sending this to upstream as per Sebastien said someone able to reproduce this should send it upstream, if you do it please re open the bug and tell us the bug number, closing the report for now, thanks in advance.

Changed in rhythmbox:
status: Incomplete → Invalid
Revision history for this message
benmhall (ubuntu-linuxgruven) wrote :

Filed bug in the Gnome Bugzilla database:

http://bugzilla.gnome.org/show_bug.cgi?id=552796

Changed in rhythmbox:
status: Invalid → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for sending the bug to GNOME

Changed in rhythmbox:
status: Confirmed → Triaged
Changed in rhythmbox:
status: Unknown → New
Changed in rhythmbox:
status: New → Incomplete
Changed in rhythmbox:
status: Incomplete → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

could somebody reply to the questions on the upstream bug

Changed in rhythmbox (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Steve Magoun (smagoun) wrote :

I think this is caused by an xvimagesink bug. Explanation and patch here: http://bugzilla.gnome.org/show_bug.cgi?id=577346

(I updated gnome bug 552796 with this info too)

Changed in rhythmbox:
status: Invalid → Unknown
affects: rhythmbox (Ubuntu) → gst-plugins-base0.10 (Ubuntu)
Changed in gst-plugins-base0.10 (Ubuntu):
status: Incomplete → Triaged
Changed in rhythmbox:
status: Unknown → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

what videocard and driver do you use? upstream seems to think that's a driver issue

Changed in gst-plugins-base0.10 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gst-plugins-base0.10 (Ubuntu):
status: Incomplete → Invalid
Changed in rhythmbox:
importance: Unknown → Medium
status: Invalid → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.