Bug 329244 - Cloning a dynamic playlist alters date values
Summary: Cloning a dynamic playlist alters date values
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Playlists/Dynamic Playlists (other bugs)
Version First Reported In: 2.8-git
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 2.9
Assignee: Amarok Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-26 11:08 UTC by robert marshall
Modified: 2023-01-02 05:28 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description robert marshall 2013-12-26 11:08:11 UTC
I have a dynamic playlist which displays as follows
Match All
   Match all sequentially
      the next track from the album
      else search for tracknumber: 1
  and not lastplay:<6m

when I clone it all the lines are the same except the last one which is now
and not lastplay:30/06/1970
I then tried creating another dynamic list to include just a 'not lastplay:<someTime' and that also cloned incorrectly.
I see that if I exit amarok and restart, then that playlist (which had 'not lastplay:<6m') is re-created incorrectly again with a exact date from 1970 (6 months from 1/1/1970 rather than 6 months from now).

The playlist in dynamic.xml looks as follows
    <playlist>
        <title> Test</title>
        <andBias>
            <ifElseBias>
                <albumPlayBias>
                    <follow>directlyFollow</follow>
                </albumPlayBias>
                <searchQueryBias>
                    <filter>tracknumber:1</filter>
                </searchQueryBias>
            </ifElseBias>
            <tagMatchBias invert="1">
                <field>last played</field>
                <numValue>15552000</numValue>
                <numValue2>1354103450</numValue2>
                <condition>equals</condition>
            </tagMatchBias>
        </andBias>
    </playlist>


Reproducible: Always



Expected Results:  
I'd expect dynamic lists to clone correctly and be recovered correctly on re-starting amarok
Comment 1 Georg Brunmayr 2014-02-26 06:28:46 UTC
I can confirm this issue in 2.8.0.
The date value is not calculated from today but 1/1/1970 when i use older or newer in the last played criteria. With every restart of Amarok the values have to be set to the right value manually to work. So the filter works, the issue has to be in the processing of the XML as it is loaded.
Comment 2 Andrew Crouthamel 2018-11-11 04:30:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-12 03:22:32 UTC
Changing back to REPORTED per request of Myriam (Amarok dev).
Comment 4 Justin Zobel 2022-12-03 09:01:37 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-18 05:14:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-02 05:28:37 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!