[kwin] [Bug 485034] New: Feature requests for Custom Tiling
https://bugs.kde.org/show_bug.cgi?id=485034 Bug ID: 485034 Summary: Feature requests for Custom Tiling Classification: Plasma Product: kwin Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: tony...@gmail.com CC: notm...@gmail.com Target Milestone: --- So, all of this actually was a not so laid down "monologue" in Niccolò Veggero's Telegram group. I am just reporting it here so that we all can discuss it. As a tiling scripts user, I feel as though the Tiling API is incomplete and this is painfully evident when, pre-Tiling API, Bismuth would work really well but, post-Tiling API, Polonium (which uses the Tiling API) is very much limited. In which ways, you ask? The first enormous issue is that windows have to be shift-dragged to snap to tiles. This is okay if we're looking at tiles like they are implemented in PowerToys and it does overlap largely with that scope, but it isn't how tiling window managers really work. In a tiling environment windows should be able to be just dragged to other tiles, and the layout should be able to accomodate for the change (sure, this is up to the script that is providing the actual tiling engine implementation, but still it cannot do this now and so it pains a lot of people.) Talking about shift-dragging, we should be able to shift-drag floating windows even if we only have one big tile. Currently KWin won't allow shift-dragging anywhere if you only have one window tiled in one tile, but Polonium exploits the shift-drag functionality to split that tile into two and place the other window besides the already placed one. Lastly, there should be a way for tiling scripts to be able to provide clear highlighted insertion points for windows (which would require one less hack - that is, what I described above.) This could be done by repurposing desktop corner snapping, or by providing edge-snapping inside tiles. And still, I feel as though this would only scrape the surface. KWin's Tiling API is a big promise, but far from complete; yet, I hope script developers and KDE contributors can collaborate towards a common goal here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 --- Comment #3 from Naomi Calabretta --- That commit is to be either reverted or looked upon because it makes two assumptions: 1. All Plasma users have a session which is managed by Systemd or similar (user service supervision) which of course can start some services to reach a target, for example the graphical target, at which point KWin starts; 2. PipeWire will never ever be restarted. If that was the case, the error would probably surface again, even on supervised sessions. This is what I can conclude from a raw look at the code; though it should not be hard to check if initialization has failed and at least attempt it again at some other point in time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 --- Comment #1 from Naomi Calabretta --- Breakage is supposed to start from this commit here: https://invent.kde.org/plasma/kwin/-/commit/37d2a7914329c65361eedfd995f25bd6867b68bc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] New: Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Bug ID: 483137 Summary: Screencast plugin fails if PipeWire is started after KWin Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tony...@gmail.com Target Milestone: --- SUMMARY On Artix Linux we use XDG Autostart to start services - such as PipeWire. There has been a change between 5.27.10 and 6.0.1 that now makes KWin not reinitialize the screencast plugin in the rare case it won't find the /run/user/1000/pipewire-0 socket. This causes all sorts of breakages- from Spectacle and OBS not being able to screen record to chat apps not being able to screen share, plus task thumbnails in plasmashell will be missing. STEPS TO REPRODUCE 1. Start Plasma on Artix Linux or any Linux distribution which starts Plasma before PipeWire 2. Observe logs (I used PIPEWIRE_DEBUG=4 as an env variable) 3. Observe screencast plugin being bugged out OBSERVED RESULT Screencast doesn't work with "Failed to connect PipeWire context" as an error. EXPECTED RESULT Screencast works anyway. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Not applicable -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482928] New: Font rendering is weird on scaled displays
https://bugs.kde.org/show_bug.cgi?id=482928 Bug ID: 482928 Summary: Font rendering is weird on scaled displays Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tony...@gmail.com Target Milestone: --- Created attachment 166742 --> https://bugs.kde.org/attachment.cgi?id=166742=edit Screenshot of font rendering SUMMARY System settings (and also the shell) render fonts wonkily, specifically on a scaled screen (mine is a 4k screen set at 150%). STEPS TO REPRODUCE 1. Open System Settings with a font where this is easily noticeable. I used Urbanist, SF Pro Display and Segoe UI. 2. Observe the font rendering OBSERVED RESULT Misaligned characters EXPECTED RESULT Smooth rendering SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Not applicable -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #22 from Naomi Calabretta --- > Please open separate issues for anything that isn't strictly "missing > features on the configuration module". It is a separate issue, but it also is a missing feature of the configuration module. I see no "map to all available outputs" option in kcm_tablet, and I see no other way of bypassing it for certain input devices. I am only bringing this here in the hopes a switch / checkbox / something that accounts for that issue can be made as a feature in kcm_tablet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457556] New: Honor high resolution scrollwheels
https://bugs.kde.org/show_bug.cgi?id=457556 Bug ID: 457556 Summary: Honor high resolution scrollwheels Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tony...@gmail.com Target Milestone: --- SUMMARY Wayland 1.21 introduced high-res scroll events to wl_pointer[1]. It would be nice to have KWin updated so that applications get the smooth scrolling treatment (as it is with Plasma on X11 -- so it's feature parity, really). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix Linux rolling/KDE Plasma 5.25.4 (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION [1]: https://lists.freedesktop.org/archives/wayland-devel/2022-June/042268.html -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 Naomi Calabretta changed: What|Removed |Added CC||tony...@gmail.com --- Comment #20 from Naomi Calabretta --- Just a heads up for this issue which affects tablet configuration and it is nerve wracking: https://bugs.kde.org/show_bug.cgi?id=450874 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450874] Plasma Wayland remaps virtual tablet input
https://bugs.kde.org/show_bug.cgi?id=450874 Naomi Calabretta changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450874] Plasma Wayland remaps virtual tablet input
https://bugs.kde.org/show_bug.cgi?id=450874 --- Comment #4 from Naomi Calabretta --- (In reply to David Edmundson from comment #3) > What's the user-facing impact of this? As I said, some users use third party programs to get their tablets working. When they do so, it's up to this program to map the handedness, orientation and input/output area of the tablet. Right now, this cannot properly function because `kcm_tablet` also provides handedness and orientation settings; but the most important user-facing impact of this is being unable to map the output to a certain display area, such as a window, a window region, or a region between two displays (if for some reason there's someone with this kinda use case). `kcm_tablet` doesn't support any of those use cases, and third party software like OpenTabletDriver usually factor in all the monitors' position, orientation and size to calculate display areas, X11-style, and therefore the input will be spit out in absolute coordinates relative to the total graphical real estate available to the user. When KWin maps this "absolute input" to be relative to just a display, things break and the user (me) gets really confused. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450874] Plasma Wayland remaps virtual tablet input
https://bugs.kde.org/show_bug.cgi?id=450874 --- Comment #2 from Naomi Calabretta --- (In reply to David Edmundson from comment #1) > I don't follow what you mean by " KWin maps virtual tablet input as if it > were a real tablet" As far as I know, the program I use has to use `uinput` to pass input events the way I want them to be to programs. Since `uinput` creates virtual input devices from the userspace, KWin seems to not be currently able to distinguish between them and real input devices. That was my point. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450874] New: Plasma Wayland remaps virtual tablet input
https://bugs.kde.org/show_bug.cgi?id=450874 Bug ID: 450874 Summary: Plasma Wayland remaps virtual tablet input Product: kwin Version: 5.24.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tony...@gmail.com Target Milestone: --- SUMMARY I am a pen display owner, and with the release of Plasma 5.24 I am looking to switch from x11 to Wayland. During my tests I encountered problems with the userspace tablet driver I am using, which is OpenTabletDriver. I outlined them in detail in the project's GitHub issue tracker[1], believing it was a matter of "just adding support for Plasma Wayland" (and I suggested a couple of ways to do so), but turned out the developers felt it wasn't really their problem, since other Wayland implementations work well and they didn't feel the need to make a special use case just for Plasma. Now, this could be the end of the story, but it really outlines a problem: KWin maps virtual tablet input as if it were a real tablet, therefore causing mapping problems for end users. I don't know if the second problem is a bug to be reported on KDE bugzilla or just a shortcoming, but either way this is breaking my use case and for the time being I cannot really switch to Wayland; and I feel like other people who draw with the help of userspace drivers can also be held back by such thing. I think there should be at least a setting in `kcm_tablet` that disables all internal mapping and "just accepts the input"; that, or a DBus call that the userspace driver can make, or (better) both things. STEPS TO REPRODUCE 1. Use OpenTabletDriver as an userspace tablet driver / configuration solution 2. Try to actually use the tablet under the Wayland session 3. Notice that the output is not what you expected OBSERVED RESULT KWin maps the virtual tablet input as if it was a real tablet plugged in and using a kernel driver. EXPECTED RESULT KWin won't map input coming from a virtual input device by default. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Artix Linux, 5.24.2 (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION [1]: https://github.com/OpenTabletDriver/OpenTabletDriver/issues/2083 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 --- Comment #2 from Naomi Calabretta --- Created attachment 125702 --> https://bugs.kde.org/attachment.cgi?id=125702=edit New crash information added by DrKonqi kdeconnectd (1.4.0) using Qt 5.13.2 - What I was doing when the application crashed: Well, you know clicking on the blue pointer stuff on the Android app? Yeah that's it. -- Backtrace (Reduced): #6 QScopedPointer >::operator-> (this=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 [...] #9 QObject::setProperty (this=0x0, name=0x7f587d145f82 "xPos", value=...) at kernel/qobject.cpp:3918 #10 0x7f587d1453f1 in PresenterPlugin::receivePacket(NetworkPacket const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_presenter.so #11 0x7f58ac1b44d0 in Device::privateReceivedPacket(NetworkPacket const&) () from /usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1 #12 0x7f58a99b191f in QtPrivate::QSlotObjectBase::call (a=0x7fff33ff9e70, r=0x558867f1d1a0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 Naomi Calabretta changed: What|Removed |Added CC||tony...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404234] plasmoid previews not working
https://bugs.kde.org/show_bug.cgi?id=404234 Naomi Calabretta changed: What|Removed |Added CC||m...@arytonex.pw --- Comment #9 from Naomi Calabretta --- This is happening to me also on KDE neon User Edition 5.15; updated today via APT from 5.14.5. -- You are receiving this mail because: You are watching all bug changes.
