- Revert "plasmoid: Port to pragma ComponentBehavior: Bound"
This reverts commit 9ee0b23727.
- Revert "plasmoid: Flatten plugin controllers, menu and other non-graphical components"
This reverts commit d2ee2bfdd8.
- Revert "plasmoid: Basic code cleanup"
This reverts commit 90946829bf.
As discussed, re-enabling this for the next release
(cherry picked from commit a3f6816954)
15cb4327 Re-enabling bluetooth by default now https://bugs.kde.org/show_bug.cgi?id=482192 is fixed
Co-authored-by: Rob Emery <kde@mintsoft.net>
Context: https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/600#note_884500
When bluetooth doesn't exist on the machine at all, QTConnectivity
tries to communicate with Bluez via dbus and introduces a 30 odd second
pause. That's not necessarily a problem in concept, however this blocks
the main thread of KDEConnect, which also then blocks the main thread
of Plasma on logon and causes tremendous delays and very broken
behaviour.
For the life of me, I cannot find a way to do "is bluetooth ok" without
QTConnect kicking off the dbus call so I think the only option is to
thread off the startup of the providers so that pauses don't block
the whole process.
I've just tested this here and my logon with bluetooth missing went
from approx 35 seconds down to about 2.
Ready for input/feedback whenever people have time; in my testing at the moment it seems to completely break the behaviour of KDEConnect (i.e. things can't connect), I'm guessing this is something to do with the effect of wrapping everything in the QThread. I'll dig into that next and see if I can figure it out.
BUG: 481870
(cherry picked from commit bb146a76d0)
4beb8c65 Fixing hanging startup/logon when bluetooth is unavailable
Co-authored-by: Rob Emery <kde@mintsoft.net>
New OpenSSH versions don't ship them, causing an error:
Bad key types '+ssh-dss,ssh-rsa'
We will add compatibility with newer keys on the Android side soon, as
part of this year's GSOC project.
Flat is better than nested. Those non-graphical components don't need to
be buried deep inside visual hierarchy tree. For example, for me it was
confusing to find the device label item after Battery, Connectivity and
VirtualMonitor only to realize some time later that those were not
actual visual indicators.
