Problems with xonox 1.0.1 in Ubuntu 22.04.4 LTS (Jammy Jellyfish)

[SaschaRei]

Problems with xonox 1.0.1 in Ubuntu 22.04.4 LTS (Jammy Jellyfish)

[SaschaRei]

Hello @x789,
thank you very much for your quick and friendly reply.

You exactly found the problem that I had: The above described key error occurs if you did a new clean xonox installation in a new system. If you start the Noxon Radio it tries to reconnect it to the last played station and contacts the xonox server with a empty station station list, which - of course - causes that error message.

Your information regarding the creation of the xonox.conf helped me to solve my problem. I've added manually with CURL one new station to the list and after this it worked perfectly. In next step I had to search the path of the xonox.conf, which was not detectable with the file search, because it was located as a result of the sudo issue in the protected location "admin:///root", while in the old VM it was stored in the users directory (although I just installed pip and xonox there also via sudo context and installed it in the new machine same way). After restoring the xonox.conf from the old VM in the discovered path of the new VM, all stations have been restored successfully. Now xonox works as perfect as before and there was also a further improvement: In the new xonox version now all five preset-buttons are working perfectly. It's like christmas. Thank you!

Even if I'm a bit ashamed of my request afterwards, I'm very, very happy that everything is now up and running. Thanks to Ubuntu's ESU updates, the current LTS version is now supported until 2032, so hopefully I won't have to ask any more questions until then. Nevertheless, I hope that Xonox will continue to be updated from time to time, if your time allows it. Many, many thanks for your support. I wish you a happy Easter and send my best regards and wishes
SaschaRei
:-)

[x789]

Hello @SaschaRei,
first of all, thank you for your kind words, for using xonox and for your patience.

If I understood correctly, you also upgraded xonox from 0.0.7.2 to 1.0.1 as part of your OS upgrade.
Normally a radio should not call the endpoint Search.asp without parameters. Probably the complete URL was not printed, so I have to guess a bit now.
I suspect that a radio wants to call a station that xonox does not recognize. This can happen if a radio wants to play the last played station automatically and the station list of xonox has changed in the meantime. The list of stations and their internally used IDs are managed by the server and not by the radios.

If you do not want to reuse your old xonox.conf:
The xonox.conf is only created when you add a station to the station list via the management API. Does the problem also exist if you take this approach?

In case you are using your old xonox.conf from 0.0.7.2:
What happens when you request the station list via your radio? Does the radio display a list? If a list is displayed and you select a station, does the error message appear in the xonox log?
Can you send me your xonox.conf? To protect your privacy, you are welcome to remove the names, descriptions and URLs of the stations. I am interested in the structure of the file. (0.0.7.2 and 1.0.1 should be compatible, but maybe I missed something).

Best wishes,
Till