Rhythmbox regularly stoped playing on gstreamer error: Rhythmbox-WARNING **: unable to stop playback: GStreamer encountered a general stream error.
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (also the maintainer of gstreamer
CC: (none) => dmorganec, fundawang, jani.valimaa, pterjan, shlomif
I would suggest that you report this problem upstream at bugzilla.gnome.org. We are shipping latest code now.
(In reply to comment #2) > I would suggest that you report this problem upstream at bugzilla.gnome.org. We > are shipping latest code now. @ Thierry I suppose you didn't find time to do that. You didn't give many details. Is your bug one of the following?: https://bugzilla.gnome.org/buglist.cgi?query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO;bug_status=RESOLVED;bug_status=VERIFIED;longdesc=%20GStreamer%20encountered%20a%20general%20stream%20error.;longdesc_type=allwordssubstr;product=GStreamer;op_sys=Linux (for some reason, putting the searchstring between "": "GStreamer encountered a general stream error" doesn't show all the bugs that have exactly this string)
Keywords: (none) => UPSTREAMCC: (none) => marja11Source RPM: rhythmbox-2.90.1-0.20111117.2.mga2 => rhythmbox-2.90.1-0.20111117.2.mga2, gstreamer
@ Thierry We have gstreamer0.10-0.10.36-1.mga2 now, is this bug still valid?
Summary: Rhythmbox regularly stoped playing on gstreamer error => Rhythmbox regularly stopped playing on gstreamer error
It still happens. But now w/o error message on the console. It usually stop at beginning of a new song after playing one. Suspending/relancing play by clicking twice on "play" do nothing. I've to move the time position to go on
(In reply to comment #5) > It still happens. But now w/o error message on the console. > It usually stop at beginning of a new song after playing one. > Suspending/relancing play by clicking twice on "play" do nothing. > I've to move the time position to go on I cannot reproduce this problem on x86-64 Mageia Linux 2/Cauldron on an Acer Laptop. I've played many mp3s from my collection using rhythmbox and everything was fine. Regards, -- Shlomi Fish
Is this related to bug 5195, i.e. is the file where it stops an ogg file?
CC: (none) => davidwhodgins
They're OGG too indeed
@ Thierry: Is this the correct version: gstreamer0.10-0.10.36-1.mga2.src.rpm ?
Summary: Rhythmbox regularly stopped playing on gstreamer error => Rhythmbox and amarok regularly stopped playing on gstreamer errorSource RPM: rhythmbox-2.90.1-0.20111117.2.mga2, gstreamer => gstreamer0.10-0.10.36-1.mga2.src.rpm, rhythmbox-2.90.1-0.20111117.2.mga2,
*** Bug 5195 has been marked as a duplicate of this bug. ***
CC: (none) => curtis_mageia
Summary: Rhythmbox and amarok regularly stopped playing on gstreamer error => Gstreamer error prevents playing OGG files in Rhythmbox and amarok
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Since Thierry has not been very responsive, and since I cannot reproduce this bug, I'm going to close it. Please reopen if you can reproduce again.
Keywords: NEEDINFO => (none)Status: NEW => RESOLVEDVersion: Cauldron => 2Resolution: (none) => INVALID
I switched to banshee b/c of that bug (& b/c rhytmbox is way slower that a couple years ago)
Hi Thierry, (In reply to comment #13) > I switched to banshee b/c of that bug (& b/c rhytmbox is way slower that a > couple years ago) but does the bug still exist? I cannot reproduce it here. Regards, -- Shlomi Fish.
Sorry for not following this bug very closely. I can still reproduce this bug with Amarok and Rhythmbox on Cauldron (updated June 4th). See Bug 5195 for my duplicate report
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Version: 2 => CauldronWhiteboard: (none) => MGA2TOO
I still cannot reproduce this bug. Are you people using PulseAudio by any chance? I'm using ALSA. Regards, -- Shlomi Fish
Yes, I'm using PulseAudio. I wondered if it's related. What's the best way to switch off Pulseaudio (without removing it) and use just ALSA?
just run draksound
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=267336
Created attachment 2523 [details] pulseaudio -vvvvv If I switch off PulseAudio, this bug does not occur. A pulseaudio debug session is attached. Here's what I did: - Started PA debug in a console with pulseaudio -vvvvv 3>&1 >&2 2>&3 3>&- | tee errs.txt (I already had an mp3 and an ogg queued up in Amarok) - Started playing the mp3. (then skipped ahead close to the end of the song) - At the end of the mp3, Amarok started playing the ogg (this was around line 2325 in the debug) - The track progression stopped in Amarok at 2 sec (this was around line 2450 in the debug) - The track started playing again showing in Amarok at 0:36 sec (Without the debug, it was coming on at around 4 min later) - Killed PA in the console.
Source RPM: gstreamer0.10-0.10.36-1.mga2.src.rpm, rhythmbox-2.90.1-0.20111117.2.mga2, => pulseaudio-2.0-4.mga3
CC: (none) => danielosmari
ha, for pulseaudio we do have a maintainer ;) Assigning to Colin :) @ Colin Although the bug seems to be in pulsaudio instead of in amarok, I'm not removing the upstream link nor the UPSTREAM keyword, I leave that to you to decide :-D
Assignee: bugsquad => mageia
Hmmm... I'm not so sure it's pulseaudio anymore. Change the backend to phonon-vlc => no problem with PA enabled The bug only occurs with phonon-gstreamer ]$ rpm -qa |grep phonon |sort lib64phonon4-4.6.0-1.mga2 lib64phononexperimental4-4.6.0-1.mga2 phonon-devel-4.6.0-1.mga2 phonon-gstreamer-4.6.1-2.mga3 phonon-gstreamer-debug-4.6.1-2.mga3 phonon-vlc-0.5.0-1.mga2 phonon-vlc-debug-0.5.0-1.mga2 phonon-xine-4.4.4-2.mga2
CC: jani.valimaa => (none)
This bug does not occur for me anymore in Rhythmbox, but it DOES still happen with Amarok (as reported in Bug 5195). I will reopen 5195.
As the comment refers to things working and carried on in another bug, I'll close this one.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED