Re: First round of feedback from Fedora 40 KDE Plasma 6 (Wayland-only) discussion
On Mon, Sep 18, 2023 at 8:42 AM David Edmundson wrote: > > On Mon, Sep 18, 2023 at 5:45 AM Neal Gompa wrote: > me of them, I've got ideas, others less so. > > > > The first thing that came up was that KiCad seems to need help and has > > had a bad experience interfacing with some folks over resolving their > > issues moving into a Wayland world. > > Given I'm quoted, I said we shouldn't rush clients to not be on Xwayland. > These are just Kicad's known issues, it'll be longer to fix all the > issues that come up after they're ported. > That's what Xwayland is for, and we've put a lot of effort into it. > They seem to be under the impression that KiCad can't run effectively under XWayland either and refuse to support it because of that. I'm quite fine with convincing them to be comfortable with XWayland too. -- 真実はいつも一つ！/ Always, there's only one truth!
Re: First round of feedback from Fedora 40 KDE Plasma 6 (Wayland-only) discussion
On Mon, Sep 18, 2023 at 5:45 AM Neal Gompa wrote: me of them, I've got ideas, others less so. > > The first thing that came up was that KiCad seems to need help and has > had a bad experience interfacing with some folks over resolving their > issues moving into a Wayland world. Given I'm quoted, I said we shouldn't rush clients to not be on Xwayland. These are just Kicad's known issues, it'll be longer to fix all the issues that come up after they're ported. That's what Xwayland is for, and we've put a lot of effort into it. David
First round of feedback from Fedora 40 KDE Plasma 6 (Wayland-only) discussion
Hey all, So unless you've been living under a rock for the past week, you might have noticed a bunch of buzz about Fedora KDE proposing to drop the X11 session with Plasma 6[1]. Those of you who were at Akademy last year[2] or this year[3] knew that this was coming. For the rest of you... 🤭 Over the past few days, I've gotten a deluge of use-cases and needs that would be useful to sort through and figure out actions to move forward on. Some of them, I've got ideas, others less so. The first thing that came up was that KiCad seems to need help and has had a bad experience interfacing with some folks over resolving their issues moving into a Wayland world. * https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/6KLDR4WM7PMJ7VJTP4LH2HA4RAMCR6UJ/ * https://groups.google.com/a/kicad.org/g/devlist/c/-glHquy0b20/m/nSBa_ntOAAAJ I don't have any particular suggestions here, though David Edmundson mentioned in the Fedora KDE Matrix room the idea of creating a new protocol to support their particular need of positioning and plumbing it through to Qt so that wxQt can use it. Also, some dedicated outreach might be a good idea to get them to be more amenable to the Wayland world. Session restore has come up a few times. It actually came up during the initial discussion within the SIG too, and has come up again during the proposal discussion in Fedora. * https://pagure.io/fedora-kde/SIG/issue/347#comment-856399 * https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/D76KHIPEPS6N7N3QHX6KBVDQ4RF5NVYO/ GNOME designed a protocol for their use, can we reuse this as an initial way to solve this problem? What's stopping us from doing something here? Barrier/Input-Leap has come up as well. Seamless keyboard and mouse handoff across computers is in demand. * https://discussion.fedoraproject.org/t/89794/6 * https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/12 The necessary portal frontends have landed in xdg-desktop-portal and so we're just missing the requisite backend in xdg-desktop-portal-kde. Something that was a little surprising to find out is that kwin's support for the number pad seems to be in less than ideal condition. * https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/5VHB34MWX5UTJE3CLOINE6OBREQIX4RY/ This doesn't seem huge to fix, but I don't know a lot about key maps... A rather dominating part of the discussion has been color management (or the current lack thereof). * https://discussion.fedoraproject.org/t/89794/12 * https://discuss.kde.org/t/fedora-kde-40-plans-to-completely-drop-x11/5047 * https://invent.kde.org/plasma/kwin/-/issues/11 This one seems to have been dragging on upstream in wayland-protocols for years now. Could we consider shipping the draft as a kde namespaced protocol (similar to what the Chrome OS folks did for aura-shell) and migrating to the finalized version later? (As a sidebar, I'm extremely disappointed in how poorly wayland-protocols governance is going right now. I count seven wayland-protocols proposed by folks I know are from KDE that are in varying states of being stuck, with all but three 6+ months old and in varying levels of decay. This is seriously hampering the development of Plasma Wayland from my point of view. And it's not just protocols from KDE that benefit KDE. Even ones from GNOME developers that we want are in similar ruts.) The lack of functioning support for host-guest clipboard copy-paste in Plasma Wayland with SPICE was also brought up as a problem. Not just for regular virtualization use, but also because it hampers testing workflows. * https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/AERH56JOMVKMNJA6MDKCFFC7DKGIRV53/ * https://bugzilla.redhat.com/show_bug.cgi?id=2016563 * https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/26 I am not sure what should be done here, but it clearly kind of sucks to have this problem. It's not currently on our list of Plasma Wayland "Showstoppers", maybe it should be listed there? Semi-related but not necessarily in the land of KDE, I got feedback on the Fediverse about the lack of a method for pre-authorizing applications to access portals means that certain classes of applications are functionally impossible to use in a Wayland environment. The example I was given was Veyon, which allows teachers to control school computer labs and monitor them while they're in use. This is a much more interesting variation of the automatic headless remote integration case for IT support systems software. * https://mastodon.tedomum.net/@lebout2canap/111074670912414830 * https://github.com/flatpak/xdg-desktop-portal/issues/1105 This is probably a solution that needs to be handled at the xdg-desktop-portal level, but I wanted to highlight it here for everyone. So you might think that with this list that it's all bad news, but it's not! The good news is that most of these were already captured
Monday meeting notes for 18/09/2023
Nico * I spent some time cleaning up runtime warnings in plasmashell * Which exposed some minor issues * Reworked kstart help page: https://invent.kde.org/plasma/kde-cli-tools/-/merge_requests/87 * Fixed a small regression in systemsettings: https://invent.kde.org/plasma/systemsettings/-/merge_requests/254 * Fixed various Qt 6.6 build issues in kde stuff * Some cleanups for thumbnail code * And some powerdevil cleanup * In terms of more interesting stuff: * Made a patch to use the new QML module stuff for KCMs: https://invent.kde.org/frameworks/kcmutils/-/merge_requests/171 * Which allows us to benefit from the qmlcachegen compiler etc * And it's surprisingly self-contained * We also should think about doing something like that for applets, at least first-party ones * That's it from me Arjen * main thing I've been doing is work on replacing basiclistitem in kirigami * I think the kirigami side is now pretty much done * there's an open mr for plasma-workspace that has some regressions, nothing too major though * https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2948 Kai Uwe Wrote a post about what I did in Plasma 6 in August: https://blog.broulik.de/2023/09/on-the-road-to-plasma-6-vol-%e2%85%b2/ :-) I was looking into using a “soft hyphen” in places to allow for dynamic word wrapping of certain long works in German. It seems to render fine (App result breaks in Kickoff grid view, shows in a single line with no hyphen in KRunner) but KRunner needs to be adjusted to ignore those characters during matching, otherwise it wouldn’t find them anymore. Still unsure if we can somehow enable dynamic wordwrapping, with a Kirigami component or something based on this LaTeX word hyphenation database? Plasma: Fixed add to panel / add to desktop not working in Kickoff Currently fixing “Add to favorites” not working in Kickoff Also found that Kickoff doesn’t reload the menu, it creates it only once per delegate, so “add to favorites” doesn’t update live in the menu… Hack around KFontViewer not working on Wayland, please review: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3290 Strip null bytes from FileChooser portal, in line with what we had to do in Solid, please review https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/226 Kirigami: Did a bunch of fixes for Mnemonics, please review: Trigger update when toggling mnemonic, so QStyle repaints, https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/296 Rework event filter: https://invent.kde.org/frameworks/kirigami/-/merge_requests/1255 Currently every single MnemonicAttached installs an event filter on the QWindow Fix mnemonics not working on buttons, https://invent.kde.org/frameworks/kirigami/-/merge_requests/1256 Toggle control in FormLayout on mnemonic activation, like QFormLayout does: https://invent.kde.org/frameworks/kirigami/-/merge_requests/1254 Vlad * I have been working on making resizing windows on wayland less glitchy * qtwidgets: if you run qt dev, then dolphin, kate and any other application that uses qwidgets should look perfect if it's resized * qtquick: it's more challenging but it's fixable https://bugreports.qt.io/browse/QTBUG-116982. The good thing is that it is a problem common to other platforms too so there's motivation to fix it * As is, wayland is glitcher than x11 * but hopefully with my changes in dev, they are going to be on par Natalie fixed manual inhibition state not synchronized across battery applets: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3294 started digging into patching logind to emit lid close property change signal so we can move forward with https://invent.kde.org/plasma/powerdevil/-/issues/22 revived discussion on energy saving KCM redesign: https://invent.kde.org/plasma/powerdevil/-/issues/10 looked into some suspension related bug reports -- Marco Martin
