Created attachment 12028 [details]
file ~/.config/radiotray-ng/bookmarks.json

I mean a comma is missing

Hello,

It affect also Cauldron version.

Please test radiotray-ng-0.2.5-1.1.mga7 in core/updates_testing.

You might need to remove old bookmarks file ~/.config/radiotray-ng/bookmarks.json first.

Hello,

I installed the testing package, but i had to rename ~/.config/radiotray-ng/ folder for radiotray-ng to regenerate the bookmarks.json.

So i suppose it will work on a fresh profile, but not on an already installed/launched one.

Hello
radiotray-ng-0.2.5-1.1.mga7 tested and works fine but it is necessary to delete the whole folder ~/.config/radiotray-ng before installing, not only bookmarks.json
Thanks

(In reply to Daniel BEZIVIN from comment #6)
> Hello
> radiotray-ng-0.2.5-1.1.mga7 tested and works fine but it is necessary to
> delete the whole folder ~/.config/radiotray-ng before installing, not only
> bookmarks.json
> Thanks

Based on this as I had never installed this before,

Suggested advisory:
========================
Updated radiotray-ng package fixes bugs

The updated package fixes bugs in bookmarks file.
Users are advised that they must delete ~./config/radiotray-ng folder before updating.

========================

Updated packages in core/updates_testing:
========================
radiotray-ng-0.2.5-1.1.mga7

from SRPM:
radiotray-ng-0.2.5-1.1.mga7.src.rpm

CC: (none) => ouaurelien

@David Hodgins,
Does this adv is satisfying? Does the fix seems OK?

CC: (none) => davidwhodgins

Not in my opinion. Most people never read advisories, especially before
installing updates.

I'm assuming it's safe to delete the directory ~./config/radiotray-ng after
installing, as long as radiotray-ng is not running.

I think the package should be modified to include a README.urpmi warning
users that old versions of that directory must be deleted with radiotray-ng
not running.

I can add README.update.urpmi if someone tells what to write to it.

(In reply to Jani Välimaa from comment #10)
> I can add README.update.urpmi if someone tells what to write to it.

Proposed README.update.urpmi

radiotray-ng package was updated.

Old version of files in that directory must be removed. We strongly advice you to make a backup of ~./config/radiotray-ng directory and remove it.
As user in a Terminal, please do:
"mv ~/.config/radiotray-ng/ ~/.config/radiotray-ng.old/"

Normally, according to our policies, we do not want to remove/rename/touch files in user directory, but sometimes, some config files can be problematic and make software to have some misbehaviour.

Ping?

Re ping. We should fix this.
@Packager can you take a look?

Pushed radiotray-ng-0.2.5-1.2.mga7 with README.update.urpmi to core/updates_testing.

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

MGA7-64 Plasma on Lenovo B50
First installed the current version, but that one was sort ot incomplete, since it  had no list of categories or stations.
Installed then the version of Comment 14, deleted the radiotray-ng folder from ~/.config, started radiotray-ng, and got the list of catergories and could pick one of the stations and listen.
Ok then.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => herman.viaene

Validating. Advisory in Comment 7

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0148.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED

MGA8-64 on different platforms
Install radiotray-ng-0.2.7-12.1 and run it for the first time:
$ radiotray-ng 
[2023-01-27 09:22:25.413503] [0x00007f1dfe6969c0] [error]   (config.cpp:45) - Failed to load: /home/tester8/.config/radiotray-ng/radiotray-ng.json : No such file or directory
terminate called after throwing an instance of 'boost::filesystem::filesystem_error'
  what():  boost::filesystem::copy_file: Invalid cross-device link: "/usr/share/radiotray-ng/bookmarks.json", "/home/tester8/.config/radiotray-ng/bookmarks.json"
Aborted (core dumped)
Subsequent tries result in radiotray running, but the menu just displays "About" - "Quit" and 3 greyed out options.
Tested on Plasma and MATE

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Herman,
As this bug was already resolved for mga7, pushed update, incl advisory
- please open a new bug for mga8 and close this one.

Also, have you tested on cauldron?
If valid for cauldron set the bug to cauldron and flag MGA8TOO

CC: (none) => fri

Even if Herman needs to open a new bug: can't repeat the issue. At first start (if  this app was never opened before), the config file gets created and the app starts in the systray with full functional menu. Below the (absolut normal and correct) output of first start of the app after installation.

MGA8 64bit Plasma

[rotz@rotz .config]$ radiotray-ng
[2023-01-27 14:45:58.317900] [0x00007f78300bd9c0] [error]   (config.cpp:45) - Failed to load: /home/rotz/.config/radiotray-ng/radiotray-ng.json : No such file or directory
[2023-01-27 14:45:58.330818] [0x00007f78300bd9c0] [debug]   (config.cpp:55) - saving: /home/rotz/.config/radiotray-ng/radiotray-ng.json

.

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED