[kwin] [Bug 487308] [wish] gamma and brightness ruled by ambient light
https://bugs.kde.org/show_bug.cgi?id=487308 Zamundaaa changed: What|Removed |Added Status|REOPENED|CONFIRMED CC||xaver.h...@gmail.com --- Comment #3 from Zamundaaa --- Adjusting the backlight brightness and whitepoint of the screen is something I plan to implement with sensors meant for that purpose (like on the Framework laptops, the Steam Deck and most phones); once that's done, we could try doing it with the camera as well. > Only one app can use the camera at a time, so this would block the camera for > all other apps with more legitimate use cases for it. Pipewire is fixing that problem afaik, so it shouldn't be a problem, at least not in the long term. I agree that the privacy light thing is an issue though, so this would have to be opt-in, at least on laptops. Power usage might also be an issue, we'll just have to test it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456569] External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569 Zamundaaa changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #18 from Zamundaaa --- I wonder if this might be similar to bug 487208. Do you have adaptive sync enabled, and if so, does disabling it change anything? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487208] Full screen apps dim/turn off the screen when invoked under Wayland
https://bugs.kde.org/show_bug.cgi?id=487208 Zamundaaa changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #9 from Zamundaaa --- Great, then you have a workaround and the cause of the problem. Please make a bug report about this at https://gitlab.freedesktop.org/drm/i915/kernel/-/issues; hopefully they can fix this or at least blacklist the screen for VRR support -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487409] LG monitor hotplug on DPMS power on causes several applications to resize their windows
https://bugs.kde.org/show_bug.cgi?id=487409 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||xaver.h...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Zamundaaa --- Are the misbehaving windows tiled in any way before the screens turn off? There's a whole bunch of fixes related to that + hotplugs in 6.0.5 > Desktop should make an attempt to absorb the DRM event and seed a new DRM > surface handle to the compositor. Delaying drm events by multiple seconds is not an option, and wouldn't reliably fix this either. No, the compositor needs to handle hotplug events properly, and KWin does have a bunch of code in place to do so. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478137] Desktop grid is not available as an option for screen edges/corners
https://bugs.kde.org/show_bug.cgi?id=478137 Zamundaaa changed: What|Removed |Added CC||0x73757...@gmail.com --- Comment #11 from Zamundaaa --- *** Bug 486999 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486999] In KDE Plasma 6.x, the grid view is not displayed when touching the screen edge with the mouse. This feature worked in version 5.x.
https://bugs.kde.org/show_bug.cgi?id=486999 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||xaver.h...@gmail.com --- Comment #2 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 478137 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483008] Turning off external monitor causes kwin crash
https://bugs.kde.org/show_bug.cgi?id=483008 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In|6.0.3 |6.1.0 Status|ASSIGNED|RESOLVED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/84412b22df |ma/kwin/-/commit/b232e80319 |01c5b00074e486cad3a432b04c9 |0a408ec22bb94bfa0f4ef0cbba8 |53d |eed --- Comment #29 from Zamundaaa --- Git commit b232e803190a408ec22bb94bfa0f4ef0cbba8eed by Xaver Hugl. Committed on 22/05/2024 at 20:33. Pushed by zamundaaa into branch 'master'. backends/drm: don't update outputs from within DrmGpu DrmBackend::updateOutputs may delete DrmGpu objects, so calling it from within a DrmGpu method can cause problems FIXED-IN: 6.1.0 M +4-1src/backends/drm/drm_backend.cpp M +0-2src/backends/drm/drm_gpu.cpp https://invent.kde.org/plasma/kwin/-/commit/b232e803190a408ec22bb94bfa0f4ef0cbba8eed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484037] Primary display loses its resolution configuration when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=484037 --- Comment #11 from Zamundaaa --- *** Bug 486504 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 Zamundaaa changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #18 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 484037 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484037] Primary display loses its resolution configuration when resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=484037 --- Comment #9 from Zamundaaa --- The resolution was 1080p in this case, but the mode list looks okay. The EDID hash also hasn't changed... my best guess would be that at some point, the driver exposes the display with lower resolution modes only, so KWin falls back to that as well, and it doesn't restore the actually intended mode later when it gets the correct modelist. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485458] Display configuration resets after waking up laptop from suspend
https://bugs.kde.org/show_bug.cgi?id=485458 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Zamundaaa --- Does this also happen if you disable the KScreen2 background service in system settings? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483437] Support per-setup display scales
https://bugs.kde.org/show_bug.cgi?id=483437 Zamundaaa changed: What|Removed |Added Component|compositing |multi-screen Severity|normal |wishlist Summary|Save displays' properties |Support per-setup display |for only this specific |scales |display arrangement missing | |in Plasma 6 | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485403] Enabling HDR freezes system
https://bugs.kde.org/show_bug.cgi?id=485403 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #11 from Zamundaaa --- hmm, the drm log is cut off in the exact same spot as the last one. That suggests to me something is going very wrong in the kernel. Please report this to NVidia, they might be able to do more about this -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend on Xorg
https://bugs.kde.org/show_bug.cgi?id=417157 Zamundaaa changed: What|Removed |Added Summary|colord-kde's functionality |colord-kde's functionality |only works to a very|only works to a very |limited extend |limited extend on Xorg --- Comment #20 from Zamundaaa --- (In reply to David REVOY from comment #17) > @Zamundaa: In all the case, it was related to Plasma 5.x and X11 Okay, then let's keep this open. > A similar > feature doesn't exist ( possibility to Profile and Calibrate from the System > Settings) in the current Wayland panel to apply color profile. Afaik, the > new system can only apply an existing profile to a device. Display settings will have a way to profile the displays, once argyllcms doesn't rely on X11 gamma ramps anymore and can produce correct profiles on Wayland - or we have an alternative. (In reply to Odin Vex from comment #18) > REVOY is correct as far as I've been able to tell. When I first upgraded to > KDE 6 I couldn't get Color Management to even work as it did (with Wayland, > it worked on my system for some reason). Instead I -accidentally- found > color profile assignment in the Display Configuration settings. Colord support for displays will not be revived for kwin_wayland, as its way of operating is inherently incompatible with the per-surface color management system in Wayland and it causes apps to produce wrong colors. > Color Management is where any/all of that should be, just like every other > system. > This way we can calibrate/assign profiles to any/all devices, not just > displays. I'm not sure who moved it and why but it makes no sense whatsoever > to put the option on the Display Configuration and only for displays. For now, the colord settings page will stay in place for non-display devices, but I don't think keeping it that way makes a lot of sense in the long term. People don't configure the abstract "color management" concept, they configure a display, or a printer, or a scanner, and the color management settings for them should be in the settings pages for those devices. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482918] Tiled windows no longer get XDG_TOPLEVEL_STATE_TILED_* states set as expected
https://bugs.kde.org/show_bug.cgi?id=482918 Zamundaaa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||6.1 --- Comment #4 from Zamundaaa --- The relevant commit was 6.0-only, and we haven't introduced a similar workaround in master, so this issue should be gone in 6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481017] CS2 leaves taskbar manager on top of a game when alt tabbing.
https://bugs.kde.org/show_bug.cgi?id=481017 Zamundaaa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #6 from Zamundaaa --- In https://github.com/ValveSoftware/csgo-osx-linux/issues/3274, others report it happening with other DEs, so this is a bug in the game or in SDL. You can use a window rule for a more persistent workaround -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483221] On Wayland, Screen Flickering with KDE Plasma 6 on AMD Radeon 780M
https://bugs.kde.org/show_bug.cgi?id=483221 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #16 from Zamundaaa --- Sorry, I kinda missed the email about this. The last thing to do here is to get the output of drm_info without any environment variables set / when you can trigger the glitches, and also again with KWIN_DRM_USE_MODIFIERS=0 set. With that, the source of the problem is narrowed down a lot, and we can make a driver bug report about this -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 417157] colord-kde's functionality only works to a very limited extend
https://bugs.kde.org/show_bug.cgi?id=417157 --- Comment #16 from Zamundaaa --- I think it would be good to clarify what this bug report is about. Is it about colord not working on Xorg, or it not working on Wayland? If it's the latter, that is fixed by KWin no longer having colord integration and instead supporting ICC profiles directly, and this bug report should be closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Zamundaaa changed: What|Removed |Added CC||k...@hexchain.org --- Comment #18 from Zamundaaa --- *** Bug 464674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464674] Wallpaper size changes after toggling external display while session is locked or any windows are open
https://bugs.kde.org/show_bug.cgi?id=464674 Zamundaaa changed: What|Removed |Added Resolution|--- |DUPLICATE CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED --- Comment #4 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 468159 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483008] Turning off external monitor causes kwin crash
https://bugs.kde.org/show_bug.cgi?id=483008 Zamundaaa changed: What|Removed |Added Target Milestone|1.0 |--- Component|general |wayland-generic Product|plasmashell |kwin Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486869] Do not invoke two-modifiers keyboard shortcuts (like Alt+Shift) when used as part of other key combinations
https://bugs.kde.org/show_bug.cgi?id=486869 --- Comment #6 from Zamundaaa --- (In reply to zkdebugsk from comment #5) > BTW, I still think that KWin should take over the custom keyboard switching > shortcuts handling and support what Windows can. > > If I prepare a PR doing that, suppose it has an elegant implementation, will > such PR be accepted, or this is a too radical change? If it's possible to handle it ourselves and disable the thing in libxkbcommon, I think that would be a reasonable path forward -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486460] Random black screen with GL_INVALID_OPERATION
https://bugs.kde.org/show_bug.cgi?id=486460 --- Comment #4 from Zamundaaa --- Does your KWin build have https://invent.kde.org/plasma/kwin/-/commit/8c3332f6195dcf213c481c28ddbff680f20a20a9 in it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456997] black screen when watching video in fulscreen using webcord and vivaldi
https://bugs.kde.org/show_bug.cgi?id=456997 Zamundaaa changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #10 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 456569 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456569] External monitor goes black when video player is fullscreen
https://bugs.kde.org/show_bug.cgi?id=456569 --- Comment #17 from Zamundaaa --- *** Bug 456997 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480885] High CPU usage for window under cursor \ plasma shell (if over desktop) and kwin_wayland when moving mouse cursor
https://bugs.kde.org/show_bug.cgi?id=480885 Zamundaaa changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #15 from Zamundaaa --- Sorry, I don't know how to do it on Neon either; it "just works" on Fedora and Arch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487208] Full screen apps dim/turn off the screen when invoked under Wayland
https://bugs.kde.org/show_bug.cgi?id=487208 --- Comment #6 from Zamundaaa --- Okay, the difference I see is that VRR gets enabled in fullscreen. Does this still happen if you disable adaptive sync in the display settings? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #16 from Zamundaaa --- You can set a mode with kscreen-doctor with > kscreen-doctor output.1.mode.0 (0 is the number of the mode in the list you want) or > kscreen-doctor output.1.mode.3840x2160@60 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486391] QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391 Zamundaaa changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/0f41239515 ||99cfdc99b53cde6911990158151 ||293 --- Comment #6 from Zamundaaa --- Git commit 0f4123951599cfdc99b53cde6911990158151293 by Xaver Hugl. Committed on 21/05/2024 at 22:26. Pushed by zamundaaa into branch 'master'. waylandserver: set render backend for linuxdrmsyncobj directly The code would previously never set the render backend, causing the use of explicit sync to fail M +0-4src/platformsupport/scenes/opengl/abstract_egl_backend.cpp M +4-0src/wayland_server.cpp https://invent.kde.org/plasma/kwin/-/commit/0f4123951599cfdc99b53cde6911990158151293 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479492] On Wayland, plasmashell exits with large(ish) number of windows
https://bugs.kde.org/show_bug.cgi?id=479492 --- Comment #12 from Zamundaaa --- Git commit 3465ecac1685256b0862d5c4478756d2b5ca1c4f by Xaver Hugl. Committed on 21/05/2024 at 15:48. Pushed by zamundaaa into branch 'master'. wayland: implement plasma window management v17 This fixes plasmashell crashing because of the stacking order string exceeding the size of a Wayland message M +35 -3src/wayland/plasmawindowmanagement.cpp https://invent.kde.org/plasma/kwin/-/commit/3465ecac1685256b0862d5c4478756d2b5ca1c4f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 Zamundaaa changed: What|Removed |Added CC||odzi...@gmail.com --- Comment #17 from Zamundaaa --- *** Bug 487324 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487324] Loss of tiled window placement upon monitor standby
https://bugs.kde.org/show_bug.cgi?id=487324 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 461886 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479492] On Wayland, plasmashell exits with large(ish) number of windows
https://bugs.kde.org/show_bug.cgi?id=479492 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwayland/-/commit/b2bf7b ||e7a7a23960da08cccabaf907494 ||84a9f19 --- Comment #11 from Zamundaaa --- Git commit b2bf7be7a7a23960da08cccabaf90749484a9f19 by Xaver Hugl. Committed on 21/05/2024 at 15:49. Pushed by zamundaaa into branch 'master'. client: update plasma-window-management to v17 M +57 -2src/client/plasmawindowmanagement.cpp M +1-1src/client/registry.cpp https://invent.kde.org/plasma/kwayland/-/commit/b2bf7be7a7a23960da08cccabaf90749484a9f19 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479492] On Wayland, plasmashell exits with large(ish) number of windows
https://bugs.kde.org/show_bug.cgi?id=479492 --- Comment #10 from Zamundaaa --- Git commit c4015a2085149ae58ca9f269641f28d175e6497e by Xaver Hugl. Committed on 21/05/2024 at 15:43. Pushed by zamundaaa into branch 'master'. update to plasma window management v17 M +1-1src/windowsystem/windowsystem.cpp https://invent.kde.org/plasma/kwayland-integration/-/commit/c4015a2085149ae58ca9f269641f28d175e6497e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479492] On Wayland, plasmashell exits with large(ish) number of windows
https://bugs.kde.org/show_bug.cgi?id=479492 --- Comment #9 from Zamundaaa --- Git commit a77b52206eab268ce778c981175dac689505a5b0 by Xaver Hugl. Committed on 21/05/2024 at 15:38. Pushed by zamundaaa into branch 'master'. plasma-window-management: add a stacking order object Instead of sending the stacking order as a single string, which can cause the client to crash, send it as a series of events with a done at the end M +36 -4src/protocols/plasma-window-management.xml https://invent.kde.org/libraries/plasma-wayland-protocols/-/commit/a77b52206eab268ce778c981175dac689505a5b0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487294] casted cursor moves even when not moved over window
https://bugs.kde.org/show_bug.cgi?id=487294 Zamundaaa changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||xaver.h...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 Zamundaaa changed: What|Removed |Added CC||rhav...@rhavenn.net --- Comment #16 from Zamundaaa --- *** Bug 487284 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487284] multi-monitor sleep on-wake the windows size and positioning is all over
https://bugs.kde.org/show_bug.cgi?id=487284 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 461886 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486585] Physical monitor size reported as 790x0 mm on Wayland
https://bugs.kde.org/show_bug.cgi?id=486585 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/7bf40c3501 ||d85af921f95d7398cd52840db83 ||9f2 Status|ASSIGNED|RESOLVED --- Comment #5 from Zamundaaa --- Git commit 7bf40c3501d85af921f95d7398cd52840db839f2 by Xaver Hugl, on behalf of Jakub Piecuch. Committed on 21/05/2024 at 11:22. Pushed by zamundaaa into branch 'master'. utils/edid: use detailed timings to compute physical screen size An EDID can contain zero or more detailed timing definitions, which can contain more precise physical dimensions of the screen (in millimeters, as opposed to centimeters). The Xorg server has similar logic for determining the physical screen size from the EDID: pick the first sane size from the detailed timing definitions, and fall back to the screen size given in the "Basic Display Parameters & Features" section. M +30 -2src/utils/edid.cpp https://invent.kde.org/plasma/kwin/-/commit/7bf40c3501d85af921f95d7398cd52840db839f2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483801] Night Color wrong temperature when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=483801 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/9fef6380d4 |ma/kwin/-/commit/1c7d007165 |d4de7d20408861db8708505bec8 |e81b52bcd0b0c9fae3a68053cc0 |de0 |eb8 --- Comment #3 from Zamundaaa --- Git commit 1c7d007165e81b52bcd0b0c9fae3a68053cc0eb8 by Xaver Hugl. Committed on 21/05/2024 at 04:09. Pushed by zamundaaa into branch 'Plasma/6.0'. backends/drm: adapt the color factors to the target colorspace Otherwise the effect of night color is much bigger in larger colorspaces. This is mostly a workaround, but the better solution (adapting the color temperature of the colorspace instead) will have to wait for 6.1 FIXED-IN: 6.0.5 (cherry picked from commit 9fef6380d4d4de7d20408861db8708505bec8de0) M +7-4src/backends/drm/drm_egl_layer_surface.cpp M +1-0src/backends/drm/drm_egl_layer_surface.h https://invent.kde.org/plasma/kwin/-/commit/1c7d007165e81b52bcd0b0c9fae3a68053cc0eb8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487037] kwin software cursor fallback locks up entire screen under certain conditions
https://bugs.kde.org/show_bug.cgi?id=487037 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/bbf4f46b28 ||0efb24c34df23253f20b195c1f3 ||47c --- Comment #2 from Zamundaaa --- Git commit bbf4f46b280efb24c34df23253f20b195c1f347c by Xaver Hugl. Committed on 20/05/2024 at 11:14. Pushed by zamundaaa into branch 'master'. compositor_wayland: properly handle moving the cursor plane failing On test failure, the plane has to be disabled or future atomic tests fail M +24 -10 src/compositor_wayland.cpp https://invent.kde.org/plasma/kwin/-/commit/bbf4f46b280efb24c34df23253f20b195c1f347c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487082] Not all screens update on window re-paints when using Zoom effect on Wayland
https://bugs.kde.org/show_bug.cgi?id=487082 Zamundaaa changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||xaver.h...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487208] Full screen apps dim/turn off the screen when invoked under Wayland
https://bugs.kde.org/show_bug.cgi?id=487208 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||xaver.h...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Zamundaaa --- Please attach the output of drm_info before, and while the screen is off -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Zamundaaa changed: What|Removed |Added CC||kdebugs.81do7@haxing.ninja --- Comment #37 from Zamundaaa --- *** Bug 487168 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487168] KWin 1.5x UI Scaling + 2256x1504 results in garbage pixels at the bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=487168 Zamundaaa changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||xaver.h...@gmail.com --- Comment #3 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 482987 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486869] Do not invoke two-modifiers keyboard shortcuts (like Alt+Shift) when used as part of other key combinations
https://bugs.kde.org/show_bug.cgi?id=486869 Zamundaaa changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Zamundaaa --- The shortcut you linked is Qt::META | Qt::ALT | Qt::Key_K by default, not ctrl+shift -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483801] Night Color wrong temperature when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=483801 Zamundaaa changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/9fef6380d4 ||d4de7d20408861db8708505bec8 ||de0 Version Fixed In||6.0.5 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Zamundaaa --- Git commit 9fef6380d4d4de7d20408861db8708505bec8de0 by Xaver Hugl. Committed on 14/05/2024 at 12:47. Pushed by zamundaaa into branch 'master'. backends/drm: adapt the color factors to the target colorspace Otherwise the effect of night color is much bigger in larger colorspaces. This is mostly a workaround, but the better solution (adapting the color temperature of the colorspace instead) will have to wait for 6.1 FIXED-IN: 6.0.5 M +7-4src/backends/drm/drm_egl_layer_surface.cpp M +1-0src/backends/drm/drm_egl_layer_surface.h https://invent.kde.org/plasma/kwin/-/commit/9fef6380d4d4de7d20408861db8708505bec8de0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476805] Make the brightness slider affect the brightness of SDR content when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=476805 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/9d76 ||ee3831a4b05580e2928e396f3c7 ||4e61d6d5a --- Comment #2 from Zamundaaa --- Git commit 9d76ee3831a4b05580e2928e396f3c74e61d6d5a by Xaver Hugl. Committed on 14/05/2024 at 08:10. Pushed by zamundaaa into branch 'master'. daemon/controller: add support for KWin brightness control This works with HDR for now, and can be extended to take care of other methods of brightness control later on as well M +1-0daemon/CMakeLists.txt A +130 -0daemon/controllers/kwinbrightness.cpp [License: LGPL(v2.0+)] A +57 -0daemon/controllers/kwinbrightness.h [License: LGPL(v2.0+)] M +2-0daemon/controllers/screenbrightnesscontroller.cpp https://invent.kde.org/plasma/powerdevil/-/commit/9d76ee3831a4b05580e2928e396f3c74e61d6d5a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/dcda15e5e3 |ma/kwin/-/commit/6f22435096 |1899e92e9895ffc908e92b47d3a |1453b286b4865798a624f3560bd |b9d |e01 --- Comment #36 from Zamundaaa --- Git commit 6f224350961453b286b4865798a624f3560bde01 by Xaver Hugl. Committed on 13/05/2024 at 08:28. Pushed by zamundaaa into branch 'Plasma/6.0'. core/renderlayer: don't implicitly truncate width and height of the geometry Otherwise, repaint regions will be limited to a pixel less than it should be in some cases FIXED-IN: 6.0.5 (cherry picked from commit dcda15e5e31899e92e9895ffc908e92b47d3ab9d) M +1-1src/core/renderlayer.cpp https://invent.kde.org/plasma/kwin/-/commit/6f224350961453b286b4865798a624f3560bde01 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/dcda15e5e3 ||1899e92e9895ffc908e92b47d3a ||b9d Status|ASSIGNED|RESOLVED Version Fixed In||6.0.5 --- Comment #35 from Zamundaaa --- Git commit dcda15e5e31899e92e9895ffc908e92b47d3ab9d by Xaver Hugl. Committed on 13/05/2024 at 08:07. Pushed by zamundaaa into branch 'master'. core/renderlayer: don't implicitly truncate width and height of the geometry Otherwise, repaint regions will be limited to a pixel less than it should be in some cases FIXED-IN: 6.0.5 M +1-1src/core/renderlayer.cpp https://invent.kde.org/plasma/kwin/-/commit/dcda15e5e31899e92e9895ffc908e92b47d3ab9d -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480171] With 225% scale on a 4k screen, right-side-tiled windows and full-screen video/image content are not fully adjacent to right screen edge
https://bugs.kde.org/show_bug.cgi?id=480171 --- Comment #29 from Zamundaaa --- Yes, fractional-scale-v2 should fix this, but we don't have a Qt implementation yet to actually test it in practice -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486849] Regression: Grid Overview not available as corner action
https://bugs.kde.org/show_bug.cgi?id=486849 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 478137 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478137] Desktop grid is not available as an option for screen edges/corners
https://bugs.kde.org/show_bug.cgi?id=478137 Zamundaaa changed: What|Removed |Added CC||k...@fuchsnet.ch --- Comment #10 from Zamundaaa --- *** Bug 486849 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486869] Do not invoke two-modifiers keyboard shortcuts (like Alt+Shift) when used as part of other key combinations
https://bugs.kde.org/show_bug.cgi?id=486869 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- KWin doesn't do layout switching shortcuts, that's done in libxkbcommon - and this is a very old bug in it . See https://github.com/xkbcommon/libxkbcommon/issues/420 for more details -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486831] workspace.currentDesktop doesn't work under wayland
https://bugs.kde.org/show_bug.cgi?id=486831 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #2 from Zamundaaa --- > An integer representing the current virtual desktop should be returned The API returns a VirtualDesktop object, not an integer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486585] Physical monitor size reported as 790x0 mm on Wayland
https://bugs.kde.org/show_bug.cgi?id=486585 Zamundaaa changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Zamundaaa --- Adding the same workaround to KWin sounds reasonable -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468807] Monitors not going to sleep on SDDM login screen when SDDM in native Wayland mode with KWin as its compositor
https://bugs.kde.org/show_bug.cgi?id=468807 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 484015 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484015] SDDM Wayland does not go into monitor powersave timeout with no user logged in
https://bugs.kde.org/show_bug.cgi?id=484015 Zamundaaa changed: What|Removed |Added CC||u...@compsci.cas.vanderbilt ||.edu --- Comment #7 from Zamundaaa --- *** Bug 468807 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480026] Screen turning off in one of various ways (idle power off, esc on lock screen, Turn Off Screen shortcut invoked over D-Bus) shuts screen off very temporarily
https://bugs.kde.org/show_bug.cgi?id=480026 Zamundaaa changed: What|Removed |Added CC||now...@gmail.com --- Comment #15 from Zamundaaa --- *** Bug 379474 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379474] KWin wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 Zamundaaa changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #21 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 480026 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Zamundaaa changed: What|Removed |Added CC||art.petrosyan...@gmail.com --- Comment #31 from Zamundaaa --- *** Bug 484804 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484804] Screen Bug
https://bugs.kde.org/show_bug.cgi?id=484804 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Zamundaaa --- *** This bug has been marked as a duplicate of bug 482987 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD
https://bugs.kde.org/show_bug.cgi?id=470106 --- Comment #5 from Zamundaaa --- Git commit 2f7649edc535c68e1906c2dd3b14152e0ed9f0b9 by Xaver Hugl. Committed on 08/05/2024 at 21:41. Pushed by zamundaaa into branch 'master'. applets/brightness: fix max brightness change notification The wrong signal name was used, which meant the maximum brightness value of the slider and the actual maximum powerdevil uses could get out of sync M +1-1applets/brightness/plugin/screenbrightnesscontrol.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/2f7649edc535c68e1906c2dd3b14152e0ed9f0b9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486723] Spam in journald ~ "kwin_wayland_drm: Signed range property value out of bounds."
https://bugs.kde.org/show_bug.cgi?id=486723 --- Comment #4 from Zamundaaa --- Are you sure you're not still running the old version? IN_FENCE_FD has a max of INT32_MAX, not -1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486599] Request for a use-native-DPI setting
https://bugs.kde.org/show_bug.cgi?id=486599 Zamundaaa changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||xaver.h...@gmail.com --- Comment #5 from Zamundaaa --- Sorry, but if you want to have content be shown at specific (physical or otherwise) sizes, you need to request that feature from apps, otherwise you will never have any guarantees - no matter if system wide scaling is involved or not. > Providing no attempt is made to defeat the use of QT_FONT_DPI, could it at > least be acceptable that it remains a documented solution that can be > employed in such cases? We can't ensure that workarounds keep working, as it comes at the cost of the intended system working. If it turns out that many people are causing bugs on their PC by having the environment variable set, we might override it in Plasma at some point. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463549] Plasma with PRIME Render Offload wakes up my NVIDIA card when launching a KDE app on integrated GPU
https://bugs.kde.org/show_bug.cgi?id=463549 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Zamundaaa --- Afaict this is caused by something (DrKonqi or plasma-integration maybe?) creating an OpenGL context on startup, and the NVidia driver not handling that well - https://github.com/NVIDIA/egl-wayland/issues/89. That seems to be fixed in driver 550, so this issue should be gone as well -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486735] System completely locking down "randomly?" when using an eGPU
https://bugs.kde.org/show_bug.cgi?id=486735 Zamundaaa changed: What|Removed |Added Resolution|--- |UPSTREAM CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Zamundaaa --- > Some (maybe useful) logs captured via sudo journalctl -b-1 | tail -n50 after > a crash Unfortunately afaict there's nothing that would even hint towards a crash in there. > NO input is taken (not even the REISUB method works) > even SSH doesn't connect In that case, it's some sort of kernel bug. As it only happens with the eGPU connected, https://gitlab.freedesktop.org/drm/amd/-/issues is likely the best place to find answers -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 486602] Monitor position incorrect
https://bugs.kde.org/show_bug.cgi?id=486602 --- Comment #4 from Zamundaaa --- Git commit 716578aac559ffc0866cd857d8a39f197cbf3be4 by Xaver Hugl. Committed on 06/05/2024 at 17:31. Pushed by zamundaaa into branch 'master'. kcm: remember position of disabled screens even after the KCM was closed At least on Wayland, the position is remembered regardless of the enablement status, so there's no reason not to remember is M +3-1kcm/output_model.h https://invent.kde.org/plasma/kscreen/-/commit/716578aac559ffc0866cd857d8a39f197cbf3be4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486723] Spam in journald ~ "kwin_wayland_drm: Signed range property value out of bounds."
https://bugs.kde.org/show_bug.cgi?id=486723 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED CC||xaver.h...@gmail.com Resolution|--- |FIXED --- Comment #1 from Zamundaaa --- This was already fixed, you need to update to https://invent.kde.org/plasma/kwin/-/commit/24807dfa50f0583a8cd509465ff706c48a9719a8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #13 from Zamundaaa --- hmm, those outputs looks all correct - kscreen-doctor knows it's in the small mode, and it's sent to other wayland clients correctly as well. If you set the correct mode with kscreen-doctor, does that work at least? If not, can you set a different resolution first and then the correct one? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486621] Support overscan on Intel
https://bugs.kde.org/show_bug.cgi?id=486621 --- Comment #5 from Zamundaaa --- I checked which properties were supported on Intel, and it seems I misremembered. There are properties for overscan that KWin could still support, but those are for VC4, and the Intel driver doesn't support them. So it'll have to be implemented in software for Intel as well... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #9 from Zamundaaa --- (In reply to Michael Butash from comment #4) > Is it DP output to DP input, or some mode conversion to HDMI? > > I have this happen almost clockwork after a suspend awaken, reboot, even > just a glitch of the power to the dock or something, and seems to come > largely from having to use DP on dock to HDMI on TV conversion. Often I'll > see the display after reset come up instead of my Samsung TV's I use to > display as generic "NVidia 640x480", and is usually all xrandr sees as well, > indicating like the conversion chip in the cable/adapter glitches and EDID > data doesn't resolve correctly on the host. I often have to end up > unplugging physically and resetting the DP end of the cable/adapter to fix > it. That's a NVidia driver bug, the proprietary driver has some issues with reading the EDID sometimes. You can report it at https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 (In reply to Kalzi from comment #8) > I have attached three txt files that have the output of drm_info for before, > during and after Okay, so the driver reports the correct mode list, and KWin has actually set the 640x480 mode. Can you also attach the output of > kscreen-doctor -o and > wayland-info while the output is wrongly in that 640x480 mode? What I suspect is happening is that the driver temporarily reports 640x480 as the only supported mode at some point after the display goes to standby, and KWin doesn't automatically switch back to the correct mode (which shouldn't be very complicated to fix). If the display settings doesn't let you set the right mode though, there might be more going on -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486621] Support overscan on Intel
https://bugs.kde.org/show_bug.cgi?id=486621 Zamundaaa changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Zamundaaa --- Judging by https://drmdb.emersion.fr/snapshots/b4bf7bec5647, NVidia doesn't support any of the drm properties that could be used for overscan. We can support it regardless by applying it in software (and by using drm plane scaling) but it'll take a bit more time to do that. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456853] Monitor arrangement is not remembered when turning off one monitor via software
https://bugs.kde.org/show_bug.cgi?id=456853 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Zamundaaa --- The application that modifies output settings is responsible for correctly restoring it too. There's nothing KScreen can do about it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486621] Support overscan on Intel
https://bugs.kde.org/show_bug.cgi?id=486621 --- Comment #2 from Zamundaaa --- Intel uses different drm properties for overscan than AMD and Nouveau, and KWin currently doesn't support them. Shouldn't be hard to change that though -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486621] Support overscan on Intel
https://bugs.kde.org/show_bug.cgi?id=486621 Zamundaaa changed: What|Removed |Added Summary|Kscreen-doctor: Setting |Support overscan on Intel |overscan doesn't work | Product|KScreen |kwin Component|kscreen-doctor |platform-drm Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485837] x conf file being changed without confirmation
https://bugs.kde.org/show_bug.cgi?id=485837 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- KScreen doesn't edit any Xorg config files, it just issues xrandr commands. The config file changes you see are done by something else -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 483662] KScreen on Wayland unable to set HDMI audio mode to "force-dvi"
https://bugs.kde.org/show_bug.cgi?id=483662 Zamundaaa changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 482888] kscreen-doctor always saves settings for next sessions
https://bugs.kde.org/show_bug.cgi?id=482888 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Zamundaaa --- All output config changes are persistent by design, sorry. If you want to have a quick way of turning on and off the second screen, try the OSD (Meta+P) or bind the relevant kscreen-doctor commands to do it to keyboard shortcuts of your own -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 486602] Monitor position incorrect
https://bugs.kde.org/show_bug.cgi?id=486602 Zamundaaa changed: What|Removed |Added Product|kwin|KScreen Component|multi-screen|common Assignee|kwin-bugs-n...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486602] Monitor position incorrect
https://bugs.kde.org/show_bug.cgi?id=486602 --- Comment #2 from Zamundaaa --- No, this is internal to the KScreen GUI. It already has logic to remember this position, but it seems to be a bit buggy -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Zamundaaa --- Please attach the output of drm_info before, and after triggering the issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/4e01d2c8b7 |ma/kwin/-/commit/e5313626b7 |a0edf49c1b49fbaf7cbc3663592 |de7ca036ef4d273febc214a6146 |da4 |6ef --- Comment #93 from Zamundaaa --- Git commit e5313626b7de7ca036ef4d273febc214a61466ef by Xaver Hugl, on behalf of Vyacheslav Mayorov. Committed on 03/05/2024 at 17:22. Pushed by zamundaaa into branch 'Plasma/6.0'. workspace: fix syncing the stacking order with Xorg Deleted windows have frameId zero, which makes Xorg stack other windows below the bottom-most window instead of the correct one. To avoid that, filter out deleted windows in Workspace::propagateWindows. (cherry picked from commit 4e01d2c8b7a0edf49c1b49fbaf7cbc3663592da4) M +2-2src/layers.cpp https://invent.kde.org/plasma/kwin/-/commit/e5313626b7de7ca036ef4d273febc214a61466ef -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/14c08422ca |ma/kwin/-/commit/b3880f6bce |32e6b5d6cca9b1ae1a472f68de9 |9844f641e12020e4ec7e290e38a |da6 |014 --- Comment #15 from Zamundaaa --- Git commit b3880f6bce9844f641e12020e4ec7e290e38a014 by Xaver Hugl. Committed on 03/05/2024 at 16:59. Pushed by zamundaaa into branch 'Plasma/6.0'. placementtracker: fix quick tiled windows not being restored correctly There were two problems: 1. Workspace interacted with the tile mode of windows before inhibiting the placement tracker, so the wrong window state was stored in the placement tracker 2. Window::setQuickTileMode is unintuitive and has some undesired side effects, meant to handle quick tiling with keyboard shortcuts and by dragging the window with a mouse specifically. This commit just works around that by un-setting the tile mode first M +62 -0autotests/integration/outputchanges_test.cpp M +4-0src/placementtracker.cpp M +5-4src/workspace.cpp https://invent.kde.org/plasma/kwin/-/commit/b3880f6bce9844f641e12020e4ec7e290e38a014 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461886] Waking screen causes application windows to disappear
https://bugs.kde.org/show_bug.cgi?id=461886 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/14c08422ca ||32e6b5d6cca9b1ae1a472f68de9 ||da6 Resolution|--- |FIXED --- Comment #14 from Zamundaaa --- Git commit 14c08422ca32e6b5d6cca9b1ae1a472f68de9da6 by Xaver Hugl. Committed on 03/05/2024 at 13:58. Pushed by zamundaaa into branch 'master'. placementtracker: fix quick tiled windows not being restored correctly There were two problems: 1. Workspace interacted with the tile mode of windows before inhibiting the placement tracker, so the wrong window state was stored in the placement tracker 2. Window::setQuickTileMode is unintuitive and has some undesired side effects, meant to handle quick tiling with keyboard shortcuts and by dragging the window with a mouse specifically. This commit just works around that by un-setting the tile mode first M +64 -0autotests/integration/outputchanges_test.cpp M +4-0src/placementtracker.cpp M +5-4src/workspace.cpp https://invent.kde.org/plasma/kwin/-/commit/14c08422ca32e6b5d6cca9b1ae1a472f68de9da6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 Zamundaaa changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #27 from Zamundaaa --- KScreen being stopped preventing this isn't too surprising, as it can trigger output changes and that seems to be what's using so much CPU, but > or call it manually with --replace then the CPU load does no longer exceed > normal levels very much is. I don't really have an explanation for that one -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #90 from Zamundaaa --- Great investigation! Please make a merge request and we'll get that backported for 6.0.5 > But im unsure about Wayland... Does it exist on Wayland? I don't think the X11 stacking order should affect input event routing on Wayland, but with X11 there's often surprises. Only way to know for sure is for someone to test the patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486149] Option to set FreeSync (VRR) mode has disappeared
https://bugs.kde.org/show_bug.cgi?id=486149 --- Comment #14 from Zamundaaa --- > But the driver probably shouldn't be reporting a lack of VRR support in the > first place right? Maybe, we'd have to confirm my theory first. Would you be willing to patch KWin to get that information? > Also, if I set it to "Automatic" on a boot where the option appears, would > that still apply to a boot where the option isn't present (considering that > the driver does in fact still support it)? No, if KWin thinks adaptive sync isn't supported, it won't try to use it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476037] external monitor disabled temporarily upon DPMS on, resulting in misposition of vertically maximized windows
https://bugs.kde.org/show_bug.cgi?id=476037 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/df9f8f8346 |ma/kwin/-/commit/a32456618a |b5b7645578e37365dabb1a7b02c |da23cbb860f75a0a41b4dbe8187 |a5a |f4c --- Comment #8 from Zamundaaa --- Git commit a32456618ada23cbb860f75a0a41b4dbe8187f4c by Xaver Hugl. Committed on 03/05/2024 at 13:55. Pushed by zamundaaa into branch 'Plasma/6.0'. fix vertically maximized windows sometimes being moved out of the screen ...and add a test for it M +86 -0autotests/integration/outputchanges_test.cpp M +1-1src/window.cpp https://invent.kde.org/plasma/kwin/-/commit/a32456618ada23cbb860f75a0a41b4dbe8187f4c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476037] external monitor disabled temporarily upon DPMS on, resulting in misposition of vertically maximized windows
https://bugs.kde.org/show_bug.cgi?id=476037 --- Comment #7 from Zamundaaa --- Git commit 5049dd233750001ccdad875ac668b7c6c89570fe by Xaver Hugl. Committed on 03/05/2024 at 13:55. Pushed by zamundaaa into branch 'Plasma/6.0'. placementtracker: fix vertically maximized windows being misplaced ...and extend the autotest to cover that situation. M +23 -13 autotests/integration/outputchanges_test.cpp M +1-11 src/placementtracker.cpp https://invent.kde.org/plasma/kwin/-/commit/5049dd233750001ccdad875ac668b7c6c89570fe -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486478] Quick Tiled windows no longer act maximised
https://bugs.kde.org/show_bug.cgi?id=486478 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Zamundaaa --- This is because we're working around a GTK bug in 6.0, which made it impossible to resize tiled GTK windows. It should work as expected again in 6.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476037] external monitor disabled temporarily upon DPMS on, resulting in misposition of vertically maximized windows
https://bugs.kde.org/show_bug.cgi?id=476037 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/df9f8f8346 ||b5b7645578e37365dabb1a7b02c ||a5a --- Comment #6 from Zamundaaa --- Git commit df9f8f8346b5b7645578e37365dabb1a7b02ca5a by Xaver Hugl. Committed on 03/05/2024 at 13:45. Pushed by zamundaaa into branch 'master'. fix vertically maximized windows sometimes being moved out of the screen ...and add a test for it M +86 -0autotests/integration/outputchanges_test.cpp M +1-1src/window.cpp https://invent.kde.org/plasma/kwin/-/commit/df9f8f8346b5b7645578e37365dabb1a7b02ca5a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476037] external monitor disabled temporarily upon DPMS on, resulting in misposition of vertically maximized windows
https://bugs.kde.org/show_bug.cgi?id=476037 --- Comment #5 from Zamundaaa --- Git commit fb28d75ad8efd8b58ef572e2163b8082fc9095c9 by Xaver Hugl. Committed on 03/05/2024 at 13:45. Pushed by zamundaaa into branch 'master'. placementtracker: fix vertically maximized windows being misplaced ...and extend the autotest to cover that situation. M +23 -13 autotests/integration/outputchanges_test.cpp M +1-11 src/placementtracker.cpp https://invent.kde.org/plasma/kwin/-/commit/fb28d75ad8efd8b58ef572e2163b8082fc9095c9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486460] Random black screen with GL_INVALID_OPERATION
https://bugs.kde.org/show_bug.cgi?id=486460 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Zamundaaa --- > If I click anywhere in the screen it will come back and everything is fine > again That's pretty weird. Does it ever happen while you have something continuously updating on the screen? Like glxgears maybe? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486460] Random black screen with GL_INVALID_OPERATION
https://bugs.kde.org/show_bug.cgi?id=486460 Zamundaaa changed: What|Removed |Added Summary|Periodic crash in |Random black screen with |kwin_wayland|GL_INVALID_OPERATION CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485425] Running Steam causes KWin's CPU usage to always increase and breaks always-on VRR on desktop
https://bugs.kde.org/show_bug.cgi?id=485425 --- Comment #2 from Zamundaaa --- I can see VRR "breaking" when Steam is open, because it's almost constantly updating its window at the full refresh rate, but it works again once I close it or focus a different window that updates with at least 30Hz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486471] "Track Mouse" doesn't track tablet cursor movements
https://bugs.kde.org/show_bug.cgi?id=486471 Zamundaaa changed: What|Removed |Added Severity|normal |wishlist CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- Tablet inputs don't move the mouse cursor, they move the tablet cursor, which is a separate thing. Changing "track mouse" to "track cursor" isn't an unreasonable request though -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486461] Wayland: window focus is per-dialog, not per-application
https://bugs.kde.org/show_bug.cgi?id=486461 Zamundaaa changed: What|Removed |Added Ever confirmed|0 |1 CC||xaver.h...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #85 from Zamundaaa --- (In reply to Oded Arbel from comment #84) > Firefox upstream just applied a "workaround" (their definition) to fix this > issue by updating the input region. Afaiu GTK is doing something wrong, so that seems fine. > A. do we know that the issue with input region being set incorrectly by the > window (and or not updated on resize) isn't what the IntelliJ issue is about? I'm relatively sure that's not possible; Xwayland doesn't set any input regions (yet), so it always covers the whole window for X11 apps on Wayland. > B. IIUC, shaping the input region is related to non-rectangular windows, > i.e. windows with transparent parts where the surface will not receive > events on those transparent areas - isn't the Firefox issue flies in the > face of Wayland security assurances? If windows can decide not to receive > events on areas they paint (and let them "fall through" to the next window) > it sounds like they can also grab events on areas that they don't paint by > shaping their input region to be larger than the painted region - this seems > problematic to me. Apps don't get input events outside of the input region. There's no grabbing input events on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482222] When using a touchscreen, using multi-finger touch gestures causes the desktop to misbehave
https://bugs.kde.org/show_bug.cgi?id=48 Zamundaaa changed: What|Removed |Added CC||aleix...@kde.org --- Comment #6 from Zamundaaa --- *** Bug 486221 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
