Mageia 9, x86_64, clean install, fully up to date.

I updated a few file names of my play list in Amarok as it didn't like
non ASCII characters (foreign accented characters) in the file names.
When I press the save playlist button, it does nothing.

The last playlist that saved successfully (in Amarok database) was 13th
March 2024, so assume some update has screwed it. In particular, there
as a large KDE update recently.

Can anyone check if they also have this problem.

I have run Amarok from the command line, and pressing the save playlist
button does absolutely nothing, so nothing is echoed to the command line.

If you export the playlist to disk, it does save to disk .. but "Save
Playlist to 'Amarok Database'" OR "Save Playlist to 'Playlists Files On
Disk" does nothing.

Leaving the playlist and creating a brand new database and saving the
list to it, also did not get the playlist save button working, although
the now new database was 100% "clean" (no stats or anything).

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: - (2:250/1@fidonet)

On 2024-03-26 06:10, Ar wrote:

Mageia 9, x86_64, clean install, fully up to date.

I updated a few file names of my play list in Amarok as it didn't like
non ASCII characters (foreign accented characters) in the file names.
When I press the save playlist button, it does nothing.

The last playlist that saved successfully (in Amarok database) was 13th March 2024, so assume some update has screwed it. In particular, there
as a large KDE update recently.

Can anyone check if they also have this problem.

I have run Amarok from the command line, and pressing the save playlist button does absolutely nothing, so nothing is echoed to the command line.

If you export the playlist to disk, it does save to disk .. but "Save Playlist to 'Amarok Database'" OR "Save Playlist to 'Playlists Files On Disk" does nothing.

Leaving the playlist and creating a brand new database and saving the
list to it, also did not get the playlist save button working, although
the now new database was 100% "clean" (no stats or anything).

I'm not an Amarok user, but I did just try the "save playlist" button,
and as you said it did absolutely nothing. I had a very short playlist
set up with five titles, then cleared it, tried the save button twice,
then used the "undo last action" button once - which promptly restored
my playlist, indicating pressing "save" wasn't seen as an "action."

Yes, Amarok was part of the large update of KDE applications a few days
ago. It was tested for very basic functions, like launching without
crashing, creating a playlist, playing from it, but apparently no one
thought to check "save playlist."

Please file a new bug at https://bugs.mageia.org/ to get a developer to
look into it. If you do not have a Mageia identity, you will need to
create one at https://identity.mageia.org/

I could do file the bug, but not being an Amarok user of any experience
it's difficult for me to accurately explain the issue, or to be able to confirm when it is fixed.

TJ

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 27/03/2024 19:32, TJ wrote:

I'm not an Amarok user, but I did just try the "save playlist" button,
and as you said it did absolutely nothing. I had a very short playlist
set up with five titles, then cleared it, tried the save button twice,
then used the "undo last action" button once - which promptly restored
my playlist, indicating pressing "save" wasn't seen as an "action."

Yes, Amarok was part of the large update of KDE applications a few days
ago. It was tested for very basic functions, like launching without crashing, creating a playlist, playing from it, but apparently no one thought to check "save playlist."

Thanks for confirming the bug in that it's not just me with the problem.

Please file a new bug at https://bugs.mageia.org/ to get a developer to
look into it. If you do not have a Mageia identity, you will need to
create one at https://identity.mageia.org/

I could do file the bug, but not being an Amarok user of any experience
it's difficult for me to accurately explain the issue, or to be able to confirm when it is fixed.

I will report the bug, I used to be an unofficial tester, but that was
when I had a spare machine to play on with a real full install not a VM.

For what it's worth, I also found another bug with the trash icon on the desktop and in Dolphin file manager. If you clear it of files to delete,
the icon does not show it's cleared, and if you click to see the
contents of the trash, they are still there, even though sometimes the
file size has increased meaning it was deleted. Close and restart
Dolphin and the trash icon shows cleared, and the contents of trash are
also cleared from display.

Thanks for your help TJ.

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: - (2:250/1@fidonet)

On 2024-03-27 20:34, Ar wrote:

I will report the bug, I used to be an unofficial tester, but that was
when I had a spare machine to play on with a real full install not a VM.

If it's been some time since you logged in (years), you may find that
your old login isn't accepted. A few years back, we all had to change
our passwords because of a security issue. Use "forgotten password?" at https://identity.mageia.org/ to do that.

VM tests are valid on a lot of things, too. I use them frequently. We'd welcome you back...

For what it's worth, I also found another bug with the trash icon on the desktop and in Dolphin file manager. If you clear it of files to delete,
the icon does not show it's cleared, and if you click to see the
contents of the trash, they are still there, even though sometimes the
file size has increased meaning it was deleted. Close and restart
Dolphin and the trash icon shows cleared, and the contents of trash are
also cleared from display.

Report that, as well, but in a separate bug. It may be an upstream bug
that The Friendly Folks at KDE will have to fix, but then again, maybe not.

Thanks for your help TJ.

No thanks needed. It's why I'm here.

TJ

--- MBSE BBS v1.0.8.6 (Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)