Bug 70485 - Files are not played automatic, while noatun is already running
Summary: Files are not played automatic, while noatun is already running
Status: RESOLVED FIXED
Alias: None
Product: noatun
Classification: Unmaintained
Component: split (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Charles Samuels
URL:
Keywords:
: 77151 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-12-15 09:54 UTC by jsvrp.gw
Modified: 2004-06-12 22:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jsvrp.gw 2003-12-15 09:54:00 UTC 
Version:            (using KDE KDE 3.1.94)
Installed from:    SuSE RPMs
OS:          Linux

Using kde 3.2 beta 2.

When you start an audiofile (e.g. from Konqueror) and Noatun is not started, Noatun will start and play the file right away. This is normal. 

But, when you start an audiofile when Noatun is already running, the player stops and you have to click manually play, to play the selected audiofile. Also when noatun is started, but not playing, you have the same problem.

This sounds like a bug and is already present from as long I started using noatun (from kde 3.1).
I can not find any setting to avoid this.

Cheers,

Jeroen
Comment 1 Stefan Gehn 2004-06-05 10:49:29 UTC 
Does this still happen with latest noatun? It doesn't happen here.
Comment 2 uli9999 2004-06-06 12:55:04 UTC 
When I click on a MP3 file in Konqueror, it starts immediately.

However, when I click on a M3U playlist while Noatun is already active, then Noatun stops and I must click "play" manually. (This does not depend on whether Noatun was playing or stopped before.) I think this should be considered as a bug.

I have the option "Automatically play first file" enabled.
Comment 3 Stefan Gehn 2004-06-06 20:29:15 UTC 
Fixed in CVS, splitplaylist was at fault.
Comment 4 Stefan Gehn 2004-06-12 22:58:20 UTC 
*** Bug 77151 has been marked as a duplicate of this bug. ***