Lots of KDE folks are winding down for well-deserved end-of-year breaks, but that didn't stop a bunch of people from landing some awesome changes anyway! This will be a short one, and I may skip next week as many of us are going to be focusing on family time. But in the meantime, check out what we have here:
What about showing touchscreen devices some love?
Next year, lots of windows 10 devices will be left unsupported!
I got myself a surface pro and installed KDE on it, but:
Virtual keyboard support is very bad(Maliit config tool at least?!?)
Cannot change long click behaviour ( emulate right click as an option maybe?)
And many more when KDE could outshine Gnome with minimal effort.
As far of the desktop goes, KDE already exceeds everything else out there, good job devs.
I really really can’t wait for being able to let go of every-single-day having to manually update the system!
This way I can just do whatever I have to do, while it will download the updates and be sure that at shutdown my system will update it self without any interaction needed!!!
Great work!!!
I wish all a holy and peaceful Christmas!
Thanks for all you do, devs. Happy holidays and new year. Get some rest and family time!
Virtual keyboard support is very bad(Maliit config tool at least?!?)
There are plans to eventually drop Maliit and move to qvk. This is one of the KDE Goals - We Care About Your Input tasks.
I appreciate all that the KDE Devs do, truly, have a great holiday and Christmas!
Hi,
open-link(-symbolic) , if i am right an Emblem, right-bottom at the Mimetype-icon,
therefor should it also moved in emblems folder by side of emblem-link-symbolic
because also in the Lagenci?s? OS’s from past is the Icon of link and this, open-link, the same, right bottom at the “File” and should also used as the same, because both be “link’s” … and Standart is normally … the emblem “symbolic-link”
But more important is, moving the icon open-link(-symbolic) into emblems, because, this is, what it is, a Emblem. (and in my opinion, a double-moubble of a icons do we need not (makes only a moreworks of it… 
)
then recreate the Icon from the Chains to the icon like the open-link it is, because the american factory have exactly this as symbolic-link…
(imo)
best regards
Blacky
@sitter thanks a lot for that Firefox Plasma integration bridge!
Hopefully someone else will find time to build on that and create a similar bridge for other browser and snaps.
It annoyed me at no end when Canonical decided to move browsers into snaps so that could have some high profile entries in their store.
And not caring a bit about the massively broken user experience.
Thankfully KDE Neon packages Firefox native so its users were better shielded but I still have a broken Chromium to contend with.
With the hard bits done I can now hope for its Plasma integration returning at some point as well
Hello Nate,
Plasma 6 is really coming along well. Thanks for all of the great work all of you do!
I believe I’ve found a bug though and before I go make a useless bug report, it needs to be tested by a couple of people.
When I make a windowed widget in my tray there is no way to configure it. There is no configure menu when you right click the tray icon, and no menu when you right click the widget once you pop it up. Hot keys do not work either (Alt+D, S).
The configuration menu works fine on desktop widgets, just not with windowed widgets, whether they are in the tray or floating on the desktop. They quit working on the first Plasma 6 upgrade from Plasma 5 to Plasma 6 on Tumbleweed.
I was running TW for months then upgraded to P6. I built a computer for a friend and his also was upgraded from P5 to P6 on TW. I don’t know if it’s leftover files from P5, a KDE bug, and of course it could be a QT bug. It could be a Tumbleweed bug only, but I would think that’s the least likely cause.
I have deleted all of the RC files and restarted Plasma and much more since the P6 upgrade. I assumed it was a problem with leftover files or a small bug the developers would find. Since they haven’t found it, I’m thinking maybe it’s just our upgraded machines or maybe all upgraded machines. I’ve spent countless hours looking for missing packages and files and looking at leftover P5 files etc.
Can you configure the widget when you run this?
I tried a lot of widgets too. I can’t configure any of them.
plasmawindowed --statusnotifier org.kde.plasma.systemmonitor.net
Analog clock doesn’t work either.
plasmawindowed --statusnotifier org.kde.plasma.analogclock
I can reproduce the issue. However I’m not sure this was ever tested, as plasmawindowed is really intended for developer use. Feel free to open a bug report about it. Thanks!