Bug 569166 - audacious does not start playing when opening new directories
Summary: audacious does not start playing when opening new directories
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: audacious
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Michael Schwendt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-28 14:45 UTC by Till Maas
Modified: 2010-02-28 16:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-28 16:00:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Till Maas 2010-02-28 14:45:05 UTC
Description of problem:

When I open a directory with audacious using the button marked with an eject symbol, audacious does not start playing. If I open files, it does. In 2.1 it
started playing in both cases.

Version-Release number of selected component (if applicable):
audacious-2.2-10.fc12

How reproducible:
always

Steps to Reproduce:
1. open a directory
  
Actual results:
files are loaded, audacious does not play

Expected results:
audacious starts playing


Additional info:
I reported this in a update comment. Since Upstream just commited a fix for this in their SCM, I want to make you aware of this.

Patch is here, but it does not cleanly apply to Fedora's version:
http://hg.atheme.org/audacious/audacious/rev/dd859d5643ab
The first problem where it does not match is afaics this:
    1.53 -            playlist_insert_folder (playlist, -1, list->data);
    1.54 +            playlist_insert_folder_v2 (playlist, -1, list->data, opening);

Upstream bug (does not contain additional info):
http://jira.atheme.org/browse/AUD-144

Comment 1 Michael Schwendt 2010-02-28 16:00:44 UTC
I'm aware of AUD-144 already as I'm one of those who has monitored that ticket.

The issue is not important enough for me to spend time on trying to backport the changes. And I don't have any plans either for Audacious 2.3. Roll-out of 2.1 and 2.2 has been too bumpy.

Comment 2 Till Maas 2010-02-28 16:35:38 UTC
(In reply to comment #1)
> I'm aware of AUD-144 already as I'm one of those who has monitored that ticket.
> 
> The issue is not important enough for me to spend time on trying to backport
> the changes. And I don't have any plans either for Audacious 2.3. Roll-out of
> 2.1 and 2.2 has been too bumpy.    

Do you know how long it will probably take until 2.3 will be released? I guess it won't happen for F13, will it? Do you know, whether I have to rebuild all plugins I use if I want to update to the SCM release?

Comment 3 Michael Schwendt 2010-02-28 16:57:36 UTC
Last time I had a look, one plugin API version had changed once more.

F13 will not ship with 2.3. Too much has changed since 2.2.


Note You need to log in before you can comment on or make changes to this bug.