[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 296255] New: Loading stream multiple times fails
From:       Amos Kariuki <amoskahiga () gmail ! com>
Date:       2012-03-18 9:15:50
Message-ID: bug-296255-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=296255

            Bug ID: 296255
          Severity: normal
           Version: 2.5.0
          Priority: NOR
          Assignee: amarok-bugs-dist@kde.org
           Summary: Loading stream multiple times fails
    Classification: Unclassified
                OS: Linux
          Reporter: amoskahiga@gmail.com
          Hardware: openSUSE RPMs
            Status: UNCONFIRMED
         Component: Streams
           Product: amarok

User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20100101
Firefox/10.0.2
Build Identifier: 

If a playlist has two or more streams, restarting (stopping and playing) an
actively playing stream will cause it to fail to play in all subsequent times.

Reproducible: Always

Steps to Reproduce:
1. (Optionally) Clear the current Playlist.
2. Add two media streams using the "Playlist -> Add Stream..." menu option.
Here are two sample NPR URLs you can use:
 - http://live.scpr.org:80
 - http://kqed-ice.streamguys.org:80/kqedradio-go-e1
2. Start playing the first media stream.
3. Stop and restart the actively playing (first) media stream.
Actual Results:  
The stream will fail to play in all subsequent attempts.
The second stream can however be started, stopped and restarted.

Expected Results:  
The media stream should play when it's restarted in all subsequent attempts.

From some debugging it seems that the EngineController::m_media object's
"state" is getting into an unexpected value/state (loading, stopped, or
playing) than is expected.

I was unable to figure out exactly what was going on but could alleviate the
problem a little using the attached temporary workaround patch -- it gets the
media stream load on the second try. The patch probably breaks other stuff, but
you can use it to see where I was poking around which hopefully is close to the
problem area.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]