Hi everyone,
I am happy to announce the immediate availability of Amarok 3.0 “Castaway”!
This is the first stable Qt5/KDE Frameworks 5 based version of Amarok, and first stable release since 2018, when the final Qt4 based version 2.9.0 was released.
Not Haiku ready (or I’m not up for the job) just can’t get the center screen to show up or connect to the/a (?) database. But again could just be me, build is OK and playback works fine on local and remote files (including podcasts).
Looking at your screenshot posted on #kde, seems like the context view components have not been loaded successfully. If you start the program with amarok --debug, do you get any messages telling about context applet qml files not being found? (E.g. on my system, the context view qml data is in /usr/lib64/qml/org/kde/amarok/)
~> amarok --debug
**********************************************************************************************
** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
** amarok --debug **
**********************************************************************************************
Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server")
kf.kirigami: Failed to find a Kirigami platform plugin
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Context dock/ContextDock) Negative sizes (400,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (0,-1) are not possible
kf.windowsystem: Could not find any platform plugin
QSystemTrayIcon::setVisible: No Icon set
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
kf.kio.workers.http: Can't communicate with kded_kcookiejar!
kf.kio.workers.http: Can't communicate with kded_kcookiejar!
"applications.menu" not found in ()
kf.service.sycoca: Service type not found: "application/x-webarchive"
kf.service.sycoca: Service type not found: "application/x-khtml-adaptor"
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible
Calling appendChild() on a null node does nothing.
Screenshot from the package and the installed files:
Ok, the debug mode doesn’t seem to work as intended there, as there’s the warning about not being in debug mode first and no debug output after. Does e.g. amarok --help give a list of commandline options? (If not, something’s not working with parsing of commandline arguments; if yes, something’s just not right with setting the debug flag) kf.kirigami: Failed to find a Kirigami platform plugin also sounds like something that possibly could be relevant
~> amarok --help
Usage: amarok [options]
The audio player by KDE
Options:
-h, --help Displays help on commandline options.
--help-all Displays help including Qt specific options.
-v, --version Displays version information.
--author Show author information.
...
I think build mode shouldn’t affect whether --debug provides verbose debug output (could be wrong though); seems more like the command line argument fails to get through to amarok and that’s why debug output is not activated. I’m not familiar with Haiku internals at all, but looking at package contents, sounds plausible that the context applet qml files are not found (debug output might be able to tell more about where the program tries to search them from)
That’s interesting. I can’t right away come up with any good idea why enabling debug mode would fail to work, but I’ll have a look at related code some time later and see if I could spot something that could be platform dependant.
Yes, it’s true that work should continue with Qt6 porting soon.
However, it would not have made sense not to release a Qt5/KF5 version first, as the porting work was pretty much done and anything that improves Qt5 experience is likely to help with Qt6, too. As 3.0 uses only single functionalities that are deprecated in Qt 5.15, the steps to Qt6 shouldn’t be that hard.
I’ve merged the update for Flathub so it should be available soon (once it’s built & published, so around tomorrow).
Right now it’s in Beta so if folks are interested, testing it and reporting success / failure would be great and then we could move it to the stable remote and it would be more visible on Flathub website: Move out of Beta · Issue #5 · flathub/org.kde.amarok · GitHub
Amarok was always the best media player, I think when it went to v2 it lost some of its original magic. Hopefully you can bring it back and give it a nice refresh. Thanks for doing this!
You know what else would be cool? Use this as a front end to replace the ugly front end of linux media server - an otherwise really good server that just has an ugly front end. It’s got all the pieces to make are really awesome client server setup and give it a great head start.
