PlasmaTube seems to show nothing due to invalid server, while AudioTube returns some search results but without any songs list to play
I use audiotube, and it works well. Can you provide more info : is it installed as flatpak, snap, package of which distro ?
1 Like
I use manjaro too. Is it from the repo of manjaro ? I suppose yes . I had problems with the flatpak version. Maybe try re-installing .
Why the hell would I use a Flatpak or a Snap on Manjaro ? I’m using Unstable branch which pulls packages directly from Arch stable repos, the app is available there as native, and reinstalling it does nothing, the app is simply broken, I even encountered a crash the moment I clicked on play button.
I said that because it was only available as flatpak before.
In my side the music is playing but at launch it is complaining about the version of python-ytmusicapi:
Running with untested version of ytmusicapi 1.2.1. If you experience errors, please report them to your distribution.qrc:/MinimizedPlayerControls.qml:142:9: Unable to assign null to QQuickAnchorLine
But it runs. (version from the repo)
I downgraded python-ytmusicapi package from 1.2.1 to 1.1.0 according to this warning message shown on terminal : The currently tested and supported version is 1.1.0
But nothing works, and the app still crashes when I click on play button.
Run from terminal shows
futuresql: Running "select * from playlists"
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
qrc:/components/DoubleActionButton.qml:131:9: Unable to assign [undefined] to int
KeyError: 'content'
At:
/usr/lib/python3.11/site-packages/ytmusicapi/navigation.py(81): nav
/usr/lib/python3.11/site-packages/ytmusicapi/mixins/watch.py(138): get_watch_playlist
zsh: segmentation fault (core dumped) audiotube
I think PlasmaTube is down because Google shut down the default Individous instance it was using.
Audiotube has some quirks but it should work overall. Please report the bug at bugs.kde.org. It might be a Manjaro packaging issue as well, the devs will figure out in the bugreport.
2 Likes
Yes this is the reason, the default instance is borked but it should work if you use another instance. That reminds me that we should switch the instance (or if someone is interested, it’s a great first merge request!)
Ideally it would prompt you on first start-up to select an instance from a list, or possibly choose one based on some criteria (like if it even works).
1 Like