[frameworks-plasma] [Bug 476172] Missing selection boxes in Plasma making a lot of UI elements unusable, especially by keyboard since plasma-framework5 5.111.0-1
https://bugs.kde.org/show_bug.cgi?id=476172 Hexagon changed: What|Removed |Added CC||k...@davidedmundson.co.uk, ||m...@ratijas.tk, ||notm...@gmail.com Version|unspecified |5.111.0 Component|general |tooltips Product|kde |frameworks-plasma Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476172] Missing selection boxes in Plasma making a lot of UI elements unusable, especially by keyboard since plasma-framework5 5.111.0-1
https://bugs.kde.org/show_bug.cgi?id=476172 --- Comment #1 from Hexagon --- After many restarts and up- and downgrades of the frameworks package and other packages, after I thought I had narrowed down the problem to the frameworks version, now suddenly the problem is gone even with the newest updates and Frameworks 5.111.0. I am currently not able to reproduce it anymore, which is not good as I wanted to document it further via screenshots and video. Maybe some kind of cache got cleared or something. But there was something there, it definitely made by computer very hard to use for a few days. :/ -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476172] New: Missing selection boxes in Plasma making a lot of UI elements unusable, especially by keyboard since plasma-framework5 5.111.0-1
https://bugs.kde.org/show_bug.cgi?id=476172 Bug ID: 476172 Summary: Missing selection boxes in Plasma making a lot of UI elements unusable, especially by keyboard since plasma-framework5 5.111.0-1 Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: apri...@posteo.net Target Milestone: --- The latest update of plasma-framework5 from version 5.110.0-1 to 5.111.0-1 on Archlinux creates major artifacts in the Plasma environment which makes it hard to use to unusable in some cases. It produces the following problems: - Globally every kind of selection marking behind objects is gone. f.e. selecting a file on the desktop, the current date in the panel, the selected element in the "start menu" and others. That makes navigating visually with the keyboard impossible. - The "task bar" is completely bugged. Open windows are shown as closed. Closed windows are shown as open. (having either the grey background or not). This makes window management very hard to impossible using the "Icons only task manager" It makes using Plasma as a whole extremely difficult and in some cases impossible to achieve certain tasks. This is why it should be considered critical. The problematic package was identified using system rollbacks. On Arch Linux the workaround to get a working system back is to downgrade the package plasma-framework5 to version 5.110.0-1. (the last working version, 5.111.0-1 does not work anymore: sudo pacman -U https://archive.archlinux.org/packages/p/plasma-framework5/plasma-framework5-5.110.0-1-x86_64.pkg.tar.zst The problem was probably introduced here: https://kde.org/announcements/frameworks/5/5.111.0/ STEPS TO REPRODUCE 1. Install plasma-frameworks 5.111.0-1 2. Relog into Plasma, but is not necessary on my PC. Directly after upgrading and downgrading the package the problem comes or goes away, depending on upgrading or downgrading. 3. Try selecting objects on the desktop, click on the clock in the "task bar", try to select a problem to launch from the "start menu" by keyboard. OBSERVED RESULT There is no blue selection box, making navigating or using UI elements / getting the current date from the calendar impossible EXPECTED RESULT In all described cases above there should be a blue selection box around Maybe it is something with the Intel iGPU. Would need testing from other people with an AMD or Nvidia GPU. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.8-arch1-1-surface (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7,7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: Microsoft Corporation Product Name: Surface Pro System Version: 1240D:0B:09F:5C:09P:38S:01E:0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 Hexagon changed: What|Removed |Added Version|5.27.2 |5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 --- Comment #5 from Hexagon --- Created attachment 162431 --> https://bugs.kde.org/attachment.cgi?id=162431=edit Video of the blurry cursor on xWayland windows compared to Wayland-native windows The problem is still present on Plasma 5.27.8. This video shows the problem more clearly than the previous screenshots. The bottom is the Wayland-native Plasma panel where the cursor is sharp. The top is Discord running in xWayland where the cursor is blurry / in low resolution. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] Glitching cursor and screen content in applications in full screen when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 --- Comment #5 from Hexagon --- New info of a chat with a KWin developer: The problem started after "Direct Scanout" was implemented in KDE Plasma 5.27 released on 2023-02-14. Workaround: One can disable the "Direct Scanout" using the environment variable "KWIN_DRM_NO_DIRECT_SCANOUT=1" in /etc/environment and relogging / restarting the computer. The problem should go away. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] Glitching cursor and screen content in applications in full screen when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 --- Comment #4 from Hexagon --- I just discovered, that it does not only occur in Firefox but other applications too and seems to be a general problem of KWin, therefore I changed the ticket title. It also happens on Signal. To reproduce it there send a video into a chat and start playback of it, enter fullscreen playback and move the mouse. You see the same glitches and mouse cursor size changes as in Firefox playing a YouTube video. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] Glitching cursor and screen content in applications in full screen when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 Hexagon changed: What|Removed |Added Summary|Glitching cursor and|Glitching cursor and screen |browser content when|content in applications in |Firefox is in full screen |full screen when using a |using a fractional scaling |fractional scaling factor |factor | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470497] New: Compositor-provided V-Sync is active on fullscreen applications even when turned off in the settings
https://bugs.kde.org/show_bug.cgi?id=470497 Bug ID: 470497 Summary: Compositor-provided V-Sync is active on fullscreen applications even when turned off in the settings Classification: Plasma Product: kwin Version: 5.27.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- Created attachment 159376 --> https://bugs.kde.org/attachment.cgi?id=159376=edit Compositor option to disable V-Sync in fullscreen applications KWin as a Wayland compositor provides V-Sync over all screen content to prevent tearing. As high performance graphics applications like video games often provide their own V-Sync implementation the compositor-provided V-Sync should be disabled to avoid two V-Sync operations in a row and to give the application the option to disable V-Sync alltogether to favor latency over image quality. To achieve this behavior KWin has a checkbox in the System Settings under "Display and Monitor -> Compositor" called "Reduce latency by allowing screen tearing artifacts in fullscreen applications", so basically "Disable compositor V-Sync in fullscreen applications". Unfortunately this checkbox does nothing, as Nate Graham looked up in the code. Therefore currently applications in KWin Wayland are not able to run without forced V-Sync, which they should be able to. STEPS TO REPRODUCE 1. Go to the system settings "Display and Monitor -> Compositor" and test with the activated and deactivated check box "Reduce latency by allowing screen tearing artifacts in fullscreen applications" 2. Open different fullscreen applications which do not have internal V-Sync like "glxgears -fullscreen" OBSERVED RESULT I can not get fullscreen applications to tear, suggesting that KWin forces V-Sync itself, even if it should not. EXPECTED RESULT The applications should tear and KWin should not apply V-Sync leaving them the option to figure it out themselves. SOFTWARE/OS VERSIONS Linux: 6.3.4-arch1-1 (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #45 from Hexagon --- I just noticed another behavior. When maximizing a Xwayland application and then closing and reopening it, it is not maximized anymore and has a 5 pixel border on the right. This happens f.e. with Spotify (Electron). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #34 from Hexagon --- Hmm. Weird. I have no idea why it is working on your machine. Some more info: I am using an AMD GPU. Connected via Display Port. Using the Mesa driver. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #32 from Hexagon --- Created attachment 159006 --> https://bugs.kde.org/attachment.cgi?id=159006=edit Spectacle scaling problem 800x600 at 150% I just took this picture. Spectacle version "spectacle 23.04.1-1" in the Arch repository. Left monitor with 800x600 at 150%. Right with 3840x2160 at 200%. As one can see the overlap of the screen differs with different resolutions and scaling factors. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #30 from Hexagon --- (In reply to Noah Davis from comment #28) > (In reply to Hexagon from comment #25) > > Thanks for the fix. Unfortunately the fix seems to not work for my monitor > > configuration. In my case the problem is still identical. > > - I am using spectacle 23.04.1-1 from the Archlinux repository. > > - My left monitor is 2560x1440px with a scaling factor of 150% > > - My center monitor is 3840x2160px with a scaling factor of 200% > > - The artifact can be seen on the center monitor as screenshotted in a > > duplicate bug report of me: https://bugs.kde.org/show_bug.cgi?id=468912 > > I can't test your exact configuration since one of my screens only goes up > to 1920x1080. Can you try setting the left screen to 1920x1080 at 150%? I > was unable to reproduce the bug using 1920x1080 at 150% and 3840x2160 at > 200%. Unfortunately Plasma does not let me set my monitor to 1920x1080. Although xrandr lists it as a supported option. On Windows I can set the monitor to 1920x1080. There seems to be a EDID problem. But I tried other combinations: - Middle monitor always 3840x2160 at 200% - Left monitor at 2560x1440 at 100% --> ok - Left monitor at 2560x1440 at 125% --> ok - Left monitor at 2560x1440 at 150%, 175% and 200% --> all of them problematic - Left monitor at 1280x720 at 100%, 125%, 150%, 175% and 200% --> all of them problematic - Left monitor at 800x600 at 100%, 125%, 150%, 175% and 200% --> all of them problematic - Left monitor at 640x480 at 100%, 125%, 150%, 175% and 200% --> all of them problematic So right now it seems almost all combinations are broken and only some are working. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 --- Comment #3 from Hexagon --- I just discovered that this does not only happen on YouTube, but every website triggering the "full screen" function of Firefox which is not the same as pressing F11. When using F11 the problem is not there. The fullscreen function of the browser can be called by JavaScript and Firefox presents a banner on the top on enabling stating "my.site.com is now full screen. Exit Full Screen (ESC)". It is probably this: docElm.mozRequestFullScreen(); https://hacks.mozilla.org/2012/01/using-the-fullscreen-api-in-web-browsers/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469763] Some GTK applications have a fuzzy mouse cursor with activated scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=469763 --- Comment #1 from Hexagon --- Created attachment 158948 --> https://bugs.kde.org/attachment.cgi?id=158948=edit Fuzzy mouse cursor demonstration I just added an image where I combined multiple screenshots to demonstrate the low resolution mouse cursor effect -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469763] New: Some GTK applications have a fuzzy mouse cursor with activated scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=469763 Bug ID: 469763 Summary: Some GTK applications have a fuzzy mouse cursor with activated scaling in Wayland Classification: Plasma Product: kwin Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- Some (can not say exactly the reason for it) applications (probably all GTK) have a fuzzy looking mouse cursor when using scaling on the system in Wayland. The programs are all running in native Wayland mode (verified with the KWin debug console). I noticed it on some flatpaks installed via Discover, but the problem also happens when I install them via the native package manager (pacman). STEPS TO REPRODUCE 1. Start a KWin Wayland session and activate scaling on the display (f.e. 200% or 150%) 2. Install one or multiple of problematic GTK programs (f.e. as flatpak): - Metadata Cleaner: https://flathub.org/apps/fr.romainvigier.MetadataCleaner - Paper: https://flathub.org/apps/io.posidon.Paper - Paper Clip: https://flathub.org/apps/io.github.diegoivan.pdf_metadata_editor Note: Some GTK apps do NOT have this problem like: https://flathub.org/apps/org.gnome.SimpleScan 3. Open the apps and hover with the cursor over them. OBSERVED RESULT The mouse cursor has fuzzy low resolution asymmetric edges EXPECTED RESULT The mouse cursor should look sharp SOFTWARE/OS VERSIONS Linux: 6.3.1-arch2-1 (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Hexagon changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #25 from Hexagon --- Thanks for the fix. Unfortunately the fix seems to not work for my monitor configuration. In my case the problem is still identical. - I am using spectacle 23.04.1-1 from the Archlinux repository. - My left monitor is 2560x1440px with a scaling factor of 150% - My center monitor is 3840x2160px with a scaling factor of 200% - The artifact can be seen on the center monitor as screenshotted in a duplicate bug report of me: https://bugs.kde.org/show_bug.cgi?id=468912 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 Hexagon changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469570] Visual artifact on the minimize and maximize buttons of the window of Firefox
https://bugs.kde.org/show_bug.cgi?id=469570 --- Comment #1 from Hexagon --- Created attachment 158825 --> https://bugs.kde.org/attachment.cgi?id=158825=edit A screenshot of the visual problem that the minimize and maximize buttons in firefox are cut off -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469570] New: Visual artifact on the minimize and maximize buttons of the window of Firefox
https://bugs.kde.org/show_bug.cgi?id=469570 Bug ID: 469570 Summary: Visual artifact on the minimize and maximize buttons of the window of Firefox Classification: Plasma Product: kwin Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- SUMMARY There is a visual artifact in the minimize and maximize buttons in Firefox. This was not present in Plasma 5.27.4. STEPS TO REPRODUCE 1. Open Firefox in Wayland mode in KDE Wayland session 2. Hover over the minimize, maximize or close buttons in the top right of the window OBSERVED RESULT The white circle around the symbols indicating that you are hovering over the button is cut off on the right side EXPECTED RESULT The circle should not be cut off SOFTWARE/OS VERSIONS Linux: 6.3.1-arch1-1 (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468912] Visual bug in the new Spectacle preview with multiple monitors and monitor scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=468912 --- Comment #3 from Hexagon --- (In reply to Noah Davis from comment #2) > Fixed in 23.04.1 > > *** This bug has been marked as a duplicate of bug 462860 *** Cool, thank you. I will test it again when 23.04.1 gets packaged for my distribution. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468912] Visual bug in the new Spectacle preview with multiple monitors and monitor scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=468912 --- Comment #1 from Hexagon --- Created attachment 158387 --> https://bugs.kde.org/attachment.cgi?id=158387=edit Visual artifacts with 200% scaling on the left monitor -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468912] New: Visual bug in the new Spectacle preview with multiple monitors and monitor scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=468912 Bug ID: 468912 Summary: Visual bug in the new Spectacle preview with multiple monitors and monitor scaling in Wayland Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: apri...@posteo.net CC: k...@david-redondo.de Target Milestone: --- Created attachment 158386 --> https://bugs.kde.org/attachment.cgi?id=158386=edit Visual artifacts with 150% scaling on the left monitor After the new UI update for Spectacle a new visual bug appeared in the preview, as can be seen in the attached screenshots. STEPS TO REPRODUCE 1. Open KDE Plasma in Wayland mode 2. Attach at least two monitors to your GPU. In the display settings set scaling of the left monitor to 150% and of the right monitor to 200%. This can depend on the resolutions. I think the right monitor must be "bigger" in the display settings preview to see this effect. 3. Open Spectacle and take a new screenshot with "rectangular region" OBSERVED RESULT The preview to select the rectangle shows a visual artifact. The right part of the right monitor gets duplicated to the left side of the right monitor, obstructing the view to the content behind. The area that gets duplicated depends on the scaling factor of the left monitor. The bigger the scaling factor of the left monitor the more gets duplicated on the right monitor. EXPECTED RESULT There are no visual artifacts. The preview shows the correct content. SOFTWARE/OS VERSIONS Linux: 6.2.12-arch1-1 (64-bit) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 Hexagon changed: What|Removed |Added Summary|XWayland apps have a|XWayland apps have a |slightly blurry mouse |slightly blurry mouse |cursor when using |cursor when using scaling |fractional scaling | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using fractional scaling
https://bugs.kde.org/show_bug.cgi?id=467061 Hexagon changed: What|Removed |Added CC||apri...@posteo.net Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Hexagon --- I can confirm this behavior. Additional information: I am using the default Plasma cursor theme (Breeze) In the display settings I am using: Legacy Applications (X11): Apply scaling themselves - It also happens when using an integer scaling factor f.e. 200% - The blurryness also applies to all other symbols of the mouse cursor theme like the hand symbol or the arrow symbol when resizing windows - In some xWayland applications one can see just a blurry version of the Breeze cursor; in other applications one can see a blurry version of the Adwaita cursor theme. So some xWayland applications seem to honor the cursor theme that was set in the Plasma settings and others default to the Adwaita cursor theme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #29 from Hexagon --- The problem exists now for over 6 months and it does not seem to have improved. Unfortunately I do not have enough insight to provide a fix myself. Could anyone involved in KWin please take a look at this problem? I think it influences the whole Plasma experience on Wayland as nearly anyone uses some kind of legacy application with xWayland and Hi-DPI monitors with scaling get more and more common. Who knows, maybe it is just a "off by one error" somewhere in the forwarding of the coordinates from the Xorg application to the Wayland wrapper window in KWin. Or the coordinates returned when the maximizeWindow() function is called returns wrong values, explaining why the border sometimes disappears until one maximizes the window again. Whatever it is, please try to find a solution. Thanks to all involved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] New: Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 Bug ID: 466749 Summary: Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor Classification: Plasma Product: kwin Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- SUMMARY Visual glitches in Firefox STEPS TO REPRODUCE 1. Using KDE Plasma (Wayland) set your monitor scaling factor to a fractional value like 150%, 195%, etc. 100% and 200% do not have this problem. 2. Open Firefox in Wayland mode with "MOZ_ENABLE_WAYLAND=1 firefox" and check if it is actually running in Wayland mode using "qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole" in the terminal. 3. Open a YouTube video in full screen an let it play. 4. Move the mouse cursor slowly. OBSERVED RESULT When moving the mouse cursor depending on which scaling value is chosen exactly and the monitor resolution one or both glitches occur: 1) The mouse cursor flickers, jumps or changes in size (from it's 100% scale size to f.e. 150% and back and forth) 2) The whole window jitters left and right by a few pixels. Maybe this is related to https://bugs.kde.org/show_bug.cgi?id=459373 where full screen applications leave pixel gaps. EXPECTED RESULT When moving the mouse cursor it should stay consistently in size and the browser content should not wiggle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 Hexagon changed: What|Removed |Added Summary|Maximized XWayland apps |Maximized XWayland apps |leave some pixels on the|leave pixel gaps when using |right border with |a fractional scaling factor |fractional scale factor | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave some pixels on the right border with fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #25 from Hexagon --- Hi guys. I would highly recommend to add this issue to the "15 minute bug initiative" https://tinyurl.com/plasma-15-minute-bugs. I am using Plasma (Wayland) with these pixel bugs now for several months and it is not fixed at all, contrary to some comments here. Only on some configurations of monitor placement, resolutions and (important!) scaling the border disappears. But one should not have to worry to set the scaling smaller or bigger than wanted, just to prevent this ugly visual problem, which makes Plasma look buggy from the very first minute of usage where you configure your screens. Also it is a major selling point of Wayland, that now scaling works correctly, important for newer Hi-DPI monitors. This would contradict, at least for KDE Plasma. Unfortunately I am not a C++ developer myself to provide a fix myself, but I can provide testing data. Here are my findings: - I am testing with the program glxgears which provides a black background and runs in Xwayland. Then I set my desktop background to full white. That way one can see the pixel rows better. - I am using a triple monitor setup with (from left to right): A: 2560x1440@150%, B: 3840x2160@200%, C: 2560x1440@150% - I am using the newest release plasma-wayland-session 5.27.1-1 on Arch - By chaning the scaling of the monitors A, B and C I can produce three different states on all of them: 1) No borders at all (perfect) 2) Vertical pixel row on the right spanning up even to the header bar of the window with the size of 1 pixel 3) Number 2 + Horizontal pixel row on the bottom with the size of 1 or 2 pixels Thanks for your work in this. I hope we can get a real fix soon to make the pixel border a thing of the past, regardless of monitor placement, resolutions and scaling settings. If you need more information don't hesitate to ask. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466041] Data must be copied twice before being pasted on Wayland when history size is set to 1 entry
https://bugs.kde.org/show_bug.cgi?id=466041 Hexagon changed: What|Removed |Added CC||apri...@posteo.net --- Comment #2 from Hexagon --- I can reproduce it on Arch as well. The problem also existed on Plasma 5.26 already. Operating System: Arch Linux KDE Plasma Version: 5.27.0-1 KDE Frameworks Version: 5.103.0-1 Qt Version: 5.15.8+kde+r181-1 Kernel Version: 6.1.12.arch1-1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463958] Recurring stutter of the whole desktop
https://bugs.kde.org/show_bug.cgi?id=463958 --- Comment #22 from Hexagon --- After four days of testing and looking for the stutter I can confirm, that it has not occurred on my machine again. Either the UEFI update or disabling the fTPM functionality of my mainboard has indeed solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463958] Recurring stutter of the whole desktop
https://bugs.kde.org/show_bug.cgi?id=463958 --- Comment #20 from Hexagon --- (In reply to Tom Englund from comment #18) > if i didnt miss something but seems you all are on ryzens. i would check if > your fTPM/TPM is enabled in bios. unsure when exactly this landed > https://github.com/torvalds/linux/commit/ > b006c439d58db625318bf2207feabf847510a8a6 but it introduces the > https://www.amd.com/en/support/kb/faq/pa-410 which windows 11 users hit when > it began requiring people to enable TPM. i myself hit it aswell. affects > pretty much entire ryzen lineup. some vendors have bios updates to mitigate > this. most dont. they are working on some workaround for this tho > https://bugzilla.kernel.org/show_bug.cgi?id=216989 , i myself dont use the > tpm for anything and simply disabled it in bios. Thanks Tom for the information. I checked my mainboard's (MSI MPG-B550-GAMING-PLUS) website and there was an UEFI update that I executed. I disabled the fTPM functionality of my mainboard as well. I will tell, if it does occur again. Maybe it is really just the known "fTPM stutter problem" that AMD processors face and has nothing to do with KDE and was introduced with the Linux kernel 6.1. Thanks for the tip :) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 463958] Recurring stutter of the whole desktop
https://bugs.kde.org/show_bug.cgi?id=463958 --- Comment #15 from Hexagon --- Hi. The problem is still present with the newest Plasma version and I think it is pretty severe and should have greater attention as it has breaking effects for a lot of use cases on the whole desktop. The recurring stutter is unacceptable for any form of media consumption, creation and even video calls, etc. What information is needed to start fixing this problem? I am more than happy to provide any information needed to get my stutter free desktop experience back. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 463958] Recurring stutter of the whole desktop
https://bugs.kde.org/show_bug.cgi?id=463958 Hexagon changed: What|Removed |Added Summary|weird stuttering effect |Recurring stutter of the ||whole desktop -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 463958] weird stuttering effect
https://bugs.kde.org/show_bug.cgi?id=463958 --- Comment #8 from Hexagon --- Edgars, what did you do exactly to downgrade to KDE 5.26.4? I have not tried to downgrade as I don't know which components have to be downgraded, as the KDE environment consists of about 20 packages on Arch. Which ones did you downgrade? Just plasma-wayland-session? Maybe by selectively downgrading each package at a time we could narrow down the problem to a specific KDE component. Furthermore: Does this only happen on Wayland or on X11 too? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 463958] weird stuttering effect
https://bugs.kde.org/show_bug.cgi?id=463958 Hexagon changed: What|Removed |Added CC||apri...@posteo.net --- Comment #4 from Hexagon --- I can confirm this problem. My setup: - Using Arch Linux (Kernel linux 6.1.4.arch1-1) - Using KDE Plasma (Wayland): plasma-wayland-session 5.26.5-1 - Processor: AMD 5900X, GPU: AMD Radeon 6900XT, MESA drivers My findings: - The problem is new. 3 weeks old max I think. - The problem is hard to reproduce. It randomly occours sometimes every 30 minutes, sometimes 2 hours without a stutter. The stutter is very short (about 800ms). During this stutter the complete desktop hangs including the mouse cursor, audio (pipewire), playing video or anything else you have open. I have encountered it dragging Wayland applications like Dolphin over the screen, playing a fullscreen YouTube video with Firefox (Wayland), playing Minecraft (Xwayland), playing games through Steam like CS:GO (linux native), playing games through WINE like The Witcher 3, listening to music with Elisa and more. It is very annoying and makes consuming multimedia content (especially with sound) extremely frustrating, wondering when it will hang the next time. It feels like there is a buffer of some sort running full. (just speculation) If you need further information, don't hesitate to ask. I hope the problem can be found soon :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized xwayland apps leave some pixels on the right border
https://bugs.kde.org/show_bug.cgi?id=459373 Hexagon changed: What|Removed |Added CC||apri...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451300] Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working
https://bugs.kde.org/show_bug.cgi?id=451300 --- Comment #12 from Hexagon --- (In reply to Zamundaaa from comment #11) > FreeSync isn't supported by NVidia either Okay. It seems like people who value the highest visual fidelity (especially the whole Gaming on Linux group of people) are then dependent on NVIDIA adding support for Gsync and Freesync on Wayland in their proprietary driver. As I am new to the world of issues and reporting: If you know could you please point me to the right direction where I can address this issue to NVIDIA? I think especially for the development of Gaming on Linux it is extremely important to have Variable Refresh Rate with Gsync and FreeSync working on Wayland using NVIDIA as Xorg doesn't provide a way to use it with more than one monitor attached. But as most gamers have at least a second monitor for communication this renders VRR unusable in Linux, being a major disadvantage for all gamers which try to move from Windows. Where is the right place to tell NVIDIA the importance of this and maybe to build pressure from the community to urge them to implement VRR on Wayland? Thanks for your help in advance. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451300] Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working
https://bugs.kde.org/show_bug.cgi?id=451300 --- Comment #10 from Hexagon --- (In reply to Zamundaaa from comment #9) > NVidia doesn't support GSync on Wayland yet. It'll work once they do Ah okay. Thanks for the reply. I understand your statement as: 1) "Real" Gsync with a hardware module in the monitor is currently not supported by the NVIDIA driver using Wayland. How is it about: 2) Freesync (Also called Gsync Compatible) Monitors with NVIDIA driver and Wayland? Unfortunately I don't have a Freesync Monitor to test this. Do Freesync monitors work already or does neither 1) and 2) work currently with Wayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451300] Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working
https://bugs.kde.org/show_bug.cgi?id=451300 --- Comment #7 from Hexagon --- It seems like the Arch packages already have set this link: lrwxrwxrwx 1 root root 32 Feb 15 02:05 nvidia-drm_gbm.so -> ../libnvidia-allocator.so.510.54 Unfortunately it doesn't work yet. Just to be clear: Do you have a working KDE Plasma Wayland session with a hardware Gsync monitor with Gsync working? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451300] Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working
https://bugs.kde.org/show_bug.cgi?id=451300 --- Comment #4 from Hexagon --- I found this: https://zamundaaa.github.io/wayland/2021/12/14/about-gaming-on-wayland.html As of version 5.23 kwin_wayland supports rendering multiple screens at different refresh rates dynamic adjustment to the current rendering load, to minimize latency Adaptive Sync / FreeSync / (once NVidia supports it on Wayland) GSync direct scanout with fullscreen apps Here someone says that kwin_wayland will support GSync as soon as NVIDIA supports it on Wayland. My question: Is Gsync not working on KDE Wayland due to KDE or to the NVIDIA driver? I would like to know if it is just a bug or maybe not implemented yet on KDE or NVIDIA side. Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451300] Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working
https://bugs.kde.org/show_bug.cgi?id=451300 --- Comment #3 from Hexagon --- Hi Victor, unfortunately I didn't quite get what you mean. You pasted steps of actions for the Sway compositor and said that it fixes some bug where "MESA failed to load nvidia-drm". I don't know how this is related to the problem I described. Could you please explain further what you mean? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451300] New: Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working
https://bugs.kde.org/show_bug.cgi?id=451300 Bug ID: 451300 Summary: Plasma Wayland Session: Hardware GSYNC with NVIDIA GPU not working Product: kwin Version: 5.24.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- SUMMARY Using a Plasma Wayland session, a NVIDIA GPU (RTX 2080) and a GSYNC monitor (which has a GSYNC hardware module, not FreeSync/VESA-VRR) GSYNC does not work. In my test with the monitor "ASUS PG279Q" the indication LED on the monitor should display red to indicate the monitor recognises a GSYNC signal. Instead it displays a white LED, indicating GSYNC is not active. In Plasma X11 my monitor LED shows GSYNC as enabled and it is working. STEPS TO REPRODUCE 1. Start a Plasma Wayland session with an NVIDIA GPU and a GSYNC monitor with a GSYNC hardware module 2. Observe if the monitor shows via the status LED, FPS counter or other measure that it is working in GSYNC mode OBSERVED RESULT GSYNC does not work EXPECTED RESULT GSYNC should work SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 NVIDIA proprietary driver: 510.54-5 -- You are receiving this mail because: You are watching all bug changes.
