You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Fedora Kionite, the qdbus binary for Qt6 is located at /usr/bin/qdbus-qt6. I went to the Arch Linux package search and found that the exact same version of qt6-qttools (6.8.0-1) has its binary located at /usr/bin/qdbus6. So I guess for Arch Linux users, nothing is wrong. Fedora Kionite users will be forced to use the advanced settings to manually change the command from qdbus6 [...] to qdbus-qt6 [...] though. I was wondering if there is maybe a way to test these two different paths with a Plasma widget (e.g. testing which qdbus6 and which qdbus-qt6 to see which one returns a valid path).
It's honestly not a big deal now that I know why I'm forced to use the advanced settings (I can just change it and forget about it). But for new users that just installed the widget, it would at least be helpful to know why it doesn't work out-of-the-box on some systems. Maybe at least make a note about it in the README.md and the KDE Store page about possibly needing to change qdbus6 to qdbus-qt6 in the advanced settings.
The text was updated successfully, but these errors were encountered:
On Fedora Kionite, the qdbus binary for Qt6 is located at
/usr/bin/qdbus-qt6
. I went to the Arch Linux package search and found that the exact same version of qt6-qttools (6.8.0-1) has its binary located at/usr/bin/qdbus6
. So I guess for Arch Linux users, nothing is wrong. Fedora Kionite users will be forced to use the advanced settings to manually change the command fromqdbus6 [...]
toqdbus-qt6 [...]
though. I was wondering if there is maybe a way to test these two different paths with a Plasma widget (e.g. testingwhich qdbus6
andwhich qdbus-qt6
to see which one returns a valid path).It's honestly not a big deal now that I know why I'm forced to use the advanced settings (I can just change it and forget about it). But for new users that just installed the widget, it would at least be helpful to know why it doesn't work out-of-the-box on some systems. Maybe at least make a note about it in the README.md and the KDE Store page about possibly needing to change
qdbus6
toqdbus-qt6
in the advanced settings.The text was updated successfully, but these errors were encountered: