I use Audacious + plugins for years. It was built as GTK variant. I upgraded my whole desktop (KDE Plasma based) and now default Audacious flavour is QT based. It is OK and everything works except keyboard shortcuts to control player. GTK flavour of the audacious-plugins contains plugin "hotkey" but QT flavour should have "qthotkey" (includd in the source archive). I reverted back to GTK based Audacious just for this reason but it seems ood to have GTK Audacious on QT based KDE. Can we have qthotkey enabled for QT flavour?
Hi, Thanks for the report. I need to take a look. Maybe the qt hotkey plugin was only "forgotten" in the port, maybe it was disabled for some technical reason. I'll report back here once I've discovered what the situation is.
Looks like that plugin was disabled due to a missing dependency. I also noticed some other missing dependencies in the audacious ports. So I'm fixing it all, I'll commit an update to the port shortly fixing all these issues and adding this plugin. I'll also enable, as an option, the QT OpenGL spectrum analyzer plugin.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=b02e706ba7e9acf0a1834f4cc64c82dc74793ebc commit b02e706ba7e9acf0a1834f4cc64c82dc74793ebc Author: Guido Falsi <madpilot@FreeBSD.org> AuthorDate: 2022-06-11 13:33:44 +0000 Commit: Guido Falsi <madpilot@FreeBSD.org> CommitDate: 2022-06-11 13:33:44 +0000 multimedia/audacious-plugins: Add missing dependencies, enable missing plugins - Add some missing dependencies - Adding these dependencies enables building the qthotkey plugin [1] - Added dependencies also allow building the qtaudio plugin - Add OPENGL option to the qt flavor too, and add requirements to allow building the gl-spectrum-qt visualization plugin PR: 264605 [1] multimedia/audacious-plugins/Makefile | 18 ++++++++++++------ multimedia/audacious-plugins/pkg-plist | 3 +++ 2 files changed, 15 insertions(+), 6 deletions(-)
(In reply to Guido Falsi from comment #2) Thank you for your quick action. I will test it once the package is rebuilt in a pkg repository!
(In reply to Miroslav Lachman from comment #4) Have you checked everything now works as expected?
PLugin added to port, no feedback from submitter.
(In reply to Guido Falsi from comment #6) I am sorry for my late reply. I am very busy with my personal life. I already tested Audacious QT with audacious-plugins. It still does not work as GTK version. With GTK version I can use global keyboard shortcuts (System Settings / Shortcuts / Custom Shortcuts) where I have definitions to send single characters to application selected by Window title: .* - Audacious$ This does not work with Audacious QT. I tried to change Window title, I tried Window class but Audacious QT never received the character (Z, X, C, V, B for prev, play, pause, stop, next) With qthotkey I must disable these global Custom Shortcuts and setup shortcuts in configuration of this plugin. It works fine, I just don't understand why GTK version works with global shortcuts and QT doesn't. If anybody want to test I should note that I am using Winamp Classic Interface (XMMS skin) in GTK and QT too - if that matters. The next difference between GTK and QT version of Audacious is this: I use KDE Plasma as my desktop and have it configured to start applications which were running on the end of the last session (Firefox, Thunderbird, DoubleCommander etc.) I have Audacious always running and playing. With GTK version Plasma starts Audacious as any other application on startup. But with QT version Audacious is never starter automatically, I must start it manually. I don't know why GTK version is running better in QT based KDE Plasma than "native" QT Audacious. I don't know if it is problem of the port (I guess not) or with upstream.
(In reply to Miroslav Lachman from comment #7) Hi, It's difficult for me to reply to the specific points because your usage of audacious is completely different from mine. I never used KDE (I have no idea how session management works there) and never autostarted audacious, never used the winamp classic interface (I personally hated that in the 90s already, but that's just me), never used the hotkeys plugin (did not even know that existed since you reported this issue). Testing this would require time for me (also because I don't have a VM ready right now for such testing, but that could be fixed relatively fast). I can only give general suggestions. For the global vs local hotkeys, maybe that's just how qt works, actually the hotkey and qthotkey plugins are two completely different source bases, so there could be significant differences. Looking at the source code does not help me since I don't know the API details of QT and GTK well enough to extrapolate more information there. In relation to the autostart configuration, I don't know how QT handles session autostart, but have you tried completely wiping out audacious from your autostart configuration and reconfiguring it from scratch?
(In reply to Guido Falsi from comment #8) The autostart I mean "saved KDE Plasma session". I don't have any settings what application should start on startup it is handled automatically by KDE - it starts all application which were running at the session shutdown. In my case it is usually Firefox, Thunderbird, SciTE, Konsole, Audacious, Double Commander. If i close SciTE manually before shutdown it will not be started next time I start KDE. But Audacious in QT flavor is not started. Audacious in GTK flavor is handled well as any other application running on the session shutdown. I understand that you have a completely different environment, so I don't even want you to waste your time.
(In reply to Miroslav Lachman from comment #9) Maybe I came out more rude than I meant. I thought kde had some way to tweak the session startup. Have you checked for errors in your log files? First place to look into is .xsession-errors
I don't have .xsession-errors. But I checked KDE session files (.config/ksmserverrc and .config/session/kwin_saved at previous logout_) and the audacious is not listed in any of them. It seems like KDE Plasma cannot recognize running Audacious QT (but works fine with GTK) then it is not saved in session and not restarted on next boot.
Strange you have no .xsession-errors, BTW how are you starting Xorg? via startxx or using a display manager? I admit I have no idea what is causing this behaviour, but hat could be a relevant information. I'm not even sure if software needs to provide something for session support that is maybe missing from the QT version. This could be an issue with audacious or KDE session management. I thing you should file a detailed report with the audacious folks, and CC me, maybe their feedback can shed some light. I only maintain the port, I have never really looked at the source code more than what was needed to make it compile, so I don't know the internals. If you also want to ask about the qhotkey plugin I'd suggest you do that in a separate issue, since these are two separate concerns.
I have KDE started from SDDM. I do not use console login to start X manually. Thank you for your time and advice, I will report this issue to Audacious folks when time permits. Maybe I will have some spare time in September. I have a wild guess that my original problem (global shortcuts not working) is related to this session problem. It seems in both cases KDE does not see Audacious as Xorg application running that's why KDE cannot send characters to Audacious and cannot save it to session for the next startup. But the whole Xorg is kind of magic to me, I am mainly FreeBSD headless servers guy.