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 341033 - Rhythmbox fails to play music on a USB-soundcard
Rhythmbox fails to play music on a USB-soundcard
Status: RESOLVED DUPLICATE of bug 341732
Product: rhythmbox
Classification: Other
Component: general
0.9.3
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-08 14:57 UTC by Sven Arvidsson
Modified: 2006-07-05 16:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
Debug output (71.53 KB, application/octet-stream)
2006-05-08 14:58 UTC, Sven Arvidsson
Details

Description Sven Arvidsson 2006-05-08 14:57:23 UTC
This bug was reported to the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=362764

Distribution: Debian testing/unstable
Package: rhythmbox
Severity: major
Version: GNOME2.14.0 0.9.3
Gnome-Distributor: Debian
Synopsis: Rhythmbox fails to play on a USB-soundcard
Bugzilla-Product: rhythmbox
Bugzilla-Component: playback
Bugzilla-Version: 0.9.3
Description:
Description of Problem:
When i try to play my music with Rhythmbox on my USB-soundcard, it
refuses to play any one of them. When i run with the --debug parameter,
the most interesting errormsg seems to be:
[0x812a8b0] [rb_shell_player_error] rb-shell-player.c:2213 (12:51:50):
playback error while playing: Could not get/set settings from/on
resource.
[0x812a8b0] [error_cb] rb-shell-player.c:2243 (12:51:50): exiting error
hander
[0x812a8b0] [rb_shell_player_error] rb-shell-player.c:2213 (12:51:50):
playback error while playing: Internal data flow error.


Steps to reproduce the problem:
1.  Have a usb-soundcard, and selecting it as default in .asoundrc
2.  Trying to play music(ogg,mp3)
3. ??? - not necessary.

Actual Results:
Nothing happens, rhythmbox tries the next song, and the next, and the
next.

Expected Results:
Music.

How often does this happen?
Always

Additional Information:
The card is:Bus 002 Device 002: ID 041e:3010 Creative Technology, Ltd
SoundBlaster MP3+
It uses the snd_usb_audio-module.
My system is :
Linux Arkadij 2.6.16-rc6 #2 Tue Mar 14 00:07:55 CET 2006 i686 GNU/Linux

XMMS, mplayer and Totem works as expected on the same card.
Rhythmbox worked previously, with Ubuntu 4.10 I think.
I have attached the output from rhythmbox --debug.
I hope that you are able to find the bug, because I would really enjoy
using something else than XMMS.

Kind regards,
Bjarte Aarmo Lund
Comment 1 Sven Arvidsson 2006-05-08 14:58:00 UTC
Created attachment 65028 [details]
Debug output
Comment 2 Alex Lancaster 2006-05-09 13:26:59 UTC
It could be a gstreamer problem.  What happens if you run:

gst-launch-0.10 playbin uri=file:///path/to/file"

If it fails on that, it's a gstreamer issue.
Comment 3 Sven Arvidsson 2006-06-24 10:47:17 UTC
The Debian bug report was updated with this information:

"Hello again, when i tried upstreams advice i got this error:

bjarte@Arkadij:~$ gst-launch-0.10 playbin uri=file:///musikk/Beastie\
Boys\ -\ intergalactic.mp3
Ställer in rörledningen till PAUSED...
Rörledningen utför PREROLL...
FEIL: fra element /playbin0/abin/audiosink/actual-sink: Kunne ikke
hente/sette innstillinger fra/på ressurs.
Tilleggsinformasjon for feilsøking:
gstalsasink.c(604): set_hwparams
(): /playbin0/abin/audiosink/actual-sink:
Rate doesn't match (requested 44100Hz, get 0Hz)
FEL: rörledningen vill inte utföra preroll.
Ställer in rörledningen till NULL...
FRIGÖR rörledning...


It seems to be gstreamer-specific then?  For mpd to work I had to
manually choose it's sampling-rate."
Comment 4 James "Doc" Livingston 2006-06-24 11:52:25 UTC
What version of gst-plugins-base do you have? I think this might be bug 341732, which was only fixed in 0.10.8.
Comment 5 Sven Arvidsson 2006-07-05 16:15:49 UTC
According to the original bug submitter, the upgrade to 0.10.8 fixed the problem.

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