[frameworks-kio] [Bug 446557] New: File Properties symlink entry not respected
https://bugs.kde.org/show_bug.cgi?id=446557 Bug ID: 446557 Summary: File Properties symlink entry not respected Product: frameworks-kio Version: 5.88.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Properties dialog Assignee: kio-bugs-n...@kde.org Reporter: verme...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When entering a new relative destination for a symlink in the file properties window, it will either not set the symlink or change it to an absolute path. STEPS TO REPRODUCE 1. Right-click a symlink -> Properties 2. In "Points to" change it from an absolute path to a relative path (in this use-case the destination is the same, the path needed is just relative) 3. Hit OK OBSERVED RESULT Dialog closes with path unchanged EXPECTED RESULT Dialog should close with the path changed to exactly what is in the "Points to" field. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: KDE Neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION The properties dialog closes without any acknowledgement that the exact user input was not respected. If there are any validity checks being performed, or it's checking to see if the path is the "same" in some way, it should not modify user input without warning. In the event that the path is malformed at most a warning dialog should spawn stating that an invalid link was entered (with a CONTINUE/CANCEL option) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397628] New: Plasma Wayland wallpaper incorrectly scaled on start
https://bugs.kde.org/show_bug.cgi?id=397628 Bug ID: 397628 Summary: Plasma Wayland wallpaper incorrectly scaled on start Product: plasmashell Version: 5.13.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: verme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 114500 --> https://bugs.kde.org/attachment.cgi?id=114500&action=edit the incorrect scale (left) and expected result (right) When Plasmashell starts on a Wayland Session with 2x scaling enabled, the wallpaper is over-scaled. This can be temporarily corrected in a session by killing Plasmashell and restarting it (killall plasmashell && plasmashell). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397628] Plasma Wayland wallpaper incorrectly scaled on start
https://bugs.kde.org/show_bug.cgi?id=397628 --- Comment #1 from Ken Vermette --- Created attachment 114502 --> https://bugs.kde.org/attachment.cgi?id=114502&action=edit When going from 2x scale to 1x scale the wallpaper will also become undersized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397631] New: Full-screen applications (e.g. games) are incorrectly scaled in Wayland
https://bugs.kde.org/show_bug.cgi?id=397631 Bug ID: 397631 Summary: Full-screen applications (e.g. games) are incorrectly scaled in Wayland Product: kwin Version: 5.13.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 114503 --> https://bugs.kde.org/attachment.cgi?id=114503&action=edit Left is incorrect scale, right is expected result. When launching a fullscreen (xwayland?) application on a 2x scaled Wayland session, the application will render at native resolution then be upscaled, making only a corner of the application visible. This is most apparent in games, applications such as Firefox or VLC are not affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397632] New: Analogue clock hands rendered with inconsistent sizes
https://bugs.kde.org/show_bug.cgi?id=397632 Bug ID: 397632 Summary: Analogue clock hands rendered with inconsistent sizes Product: plasmashell Version: 5.13.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Analogue Clock Assignee: bhus...@gmail.com Reporter: verme...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 114504 --> https://bugs.kde.org/attachment.cgi?id=114504&action=edit Clock on the desktop vs clock in Date & Time. (Using "Aether Dark" theme in these shots) The Analogue clock hands are rendered at inconsistent sizes. They vary slightly with size (blocking "pixel perfect" results") and desktop scaling. The most apparent is when viewing the date-and-time settings. Aside from a general fix, how hand scaling works is unclear so I'd also like to request a new "hint-alternate-hand-placement" hint be added for future development. This hint would have the following behavioral changes from the current system: - The hands will not be magically scaled, the scale of the hands will match the scale of the clock. - The hands will rotate according to the center-point of the bounding box, not the position of the object. - The hands may be an arbitrary size. The hand could, possibly, be larger than the clock face. In some situations it also means parts of the hand might even be clipped. It is up to the theme author to avoid this. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376293] Security page is inaccessible
https://bugs.kde.org/show_bug.cgi?id=376293 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||verme...@gmail.com --- Comment #1 from Ken Vermette --- The security page can be found via the following path: Home -> Get Involved -> (link under "Security and Bug Reporting") -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376296] Kde.org has two diferent donation pages
https://bugs.kde.org/show_bug.cgi?id=376296 Ken Vermette changed: What|Removed |Added CC||verme...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Ken Vermette --- There's an issue where it will forcefully redirect the donate page to the old page, even if the new page is present under the donate header - which is how we had it. We need to figure out where the rule is which forcefully redirects away from the new pages, and then this will be fixed. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376302] kde.org/products abuses KDevelop icon for "Development Tools", better use "applications-development" icon
https://bugs.kde.org/show_bug.cgi?id=376302 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ken Vermette --- SVN commit 1482420 by kvermette: M develop.png WebSVN link: http://websvn.kde.org/?view=rev&revision=1482420 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376298] Kde.org front-page removed spam trap email
https://bugs.kde.org/show_bug.cgi?id=376298 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ken Vermette --- SVN commit 1482423 by kvermette: M +19 -0 footer.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1482423 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376294] Kde.org has two incompatible cookie warnings
https://bugs.kde.org/show_bug.cgi?id=376294 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ken Vermette --- SVN commit 1482425 by kvermette: M +2 -2 header.js WebSVN link: http://websvn.kde.org/?view=rev&revision=1482425 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376288] "Wiki To Learn" in the footer should be "WikiToLearn"
https://bugs.kde.org/show_bug.cgi?id=376288 Ken Vermette changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ken Vermette --- SVN commit 1482426 by kvermette: M +1 -1 footer.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1482426 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376297] Donations tracking field in front-page is broken
https://bugs.kde.org/show_bug.cgi?id=376297 Ken Vermette changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ken Vermette --- SVN commit 1482427 by kvermette: M +1 -1 footer.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1482427 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376364] community.kde.org should be linked from kde.org/get-involved, section "Wikis"
https://bugs.kde.org/show_bug.cgi?id=376364 Ken Vermette changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ken Vermette --- SVN commit 1482461 by kvermette: Added the community wiki link; though I edited the description provided a bit as we'd have some redundant wording. Also updated to an https link in the footer; I previously linked to an outdated page which didn't accept https, when I switched to docs.qt.io I didn't switch back to https. FInally, though not in this bug, I added techbase to the list of wikis to complete the trifecta; even though techbase is already listed under "develop", I think it helps that people know they can "get involved" with that wiki as well, not implying it's developers-only in some way. M +1 -1 aether/footer.php M +12 -2 get-involved.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1482461 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376291] New kde.org adds tracking by 3rd-party, googleapis.com
https://bugs.kde.org/show_bug.cgi?id=376291 Ken Vermette changed: What|Removed |Added CC||verme...@gmail.com --- Comment #1 from Ken Vermette --- Google doesn't use Google fonts as a tracking mechanism, at least, not in the way that any website doesn't do by nature with basic traffic logging. See: https://developers.google.com/fonts/faq#what_does_using_the_google_fonts_api_mean_for_the_privacy_of_my_users Google doesn't have cookies for web fonts, uses heavy caching (meaning only the first hit a day for a font - from anywhere - may be logged), and other things. The only metrics Google states they collect from web fonts is "which fonts are popular", and "which websites use fonts", but neither of them are user-specific. Additionally, browsers properly implementing https should not provide referral information *at all* to included resources - not even the domain referring. Noto is made by Google, and Google updates the web fonts regularly. I don't know how often the font is adjusted or added to, but it was a consideration. Serving the font ourselves will cost us a little extra load without the caching (nothing anyone will ever notice, but still - it can add up if we aren't careful), and the font may periodically fall out-of-date. All that being said, while I personally don't consider the use of Google Fonts as a breach of privacy or introduction of tracking, I understand the concern. KDE also prides itself on privacy, and even the *opportunity* to gleam some small amount of information from our service could be considered an issue. Even the perception of tracking may be enough in some cases. If someone really paranoid disables third-party resources to ensure no tracking can happen, the downsides will be marginal; either an existing noto on their machine will be used, or it will fall back to a similar looking sans font. I'm neutral on moving the font resources to our server, but knowing that fonts are not a viable form of tracking to Google nor one that they claim to try using, I'd like to ask if this is still considered an issue; if it is, I'll go ahead and do the switch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397632] Analogue clock hands rendered with inconsistent sizes
https://bugs.kde.org/show_bug.cgi?id=397632 --- Comment #2 from Ken Vermette --- (In reply to Nate Graham from comment #1) > Whoa, I don't think that's what the clock is supposed to look like. Why is > it a donut? Is this some artifact of your theme? That's how it's meant to look. In the sample attachment the widget on the desktop is rendered correctly, but the image in the Date & Time module is broken with the radically undersized hands. Fixing the hands would resolve the bug; but outside of that the extra points added are simply to allow for more creative and predictable analog clock design. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385778] Physics breaks down between the Wayland window decoration and XCB contents
https://bugs.kde.org/show_bug.cgi?id=385778 Ken Vermette changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Ken Vermette --- In recent versions it has stopped displaying the odd behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397632] Analogue clock hands rendered with inconsistent sizes
https://bugs.kde.org/show_bug.cgi?id=397632 --- Comment #4 from Ken Vermette --- (In reply to Nate Graham from comment #3) > (In reply to Ken Vermette from comment #2) > > (In reply to Nate Graham from comment #1) > > > Whoa, I don't think that's what the clock is supposed to look like. Why is > > > it a donut? Is this some artifact of your theme? > > > > That's how it's meant to look. > Like a donut, with a giant hole cut out of the middle? That's not what mine > looks like... Are you using the Aether Dark theme? -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376297] Donations tracking field in front-page is broken
https://bugs.kde.org/show_bug.cgi?id=376297 Ken Vermette changed: What|Removed |Added CC||verme...@gmail.com --- Comment #3 from Ken Vermette --- This patch was accidentally reverted, it has since been reinstated. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376297] Donations tracking field in front-page is broken
https://bugs.kde.org/show_bug.cgi?id=376297 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376297] Donations tracking field in front-page is broken
https://bugs.kde.org/show_bug.cgi?id=376297 Ken Vermette changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Ken Vermette --- SVN commit 1482523 by kvermette: M +1 -1 footer.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1482523 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376288] "Wiki To Learn" in the footer should be "WikiToLearn"
https://bugs.kde.org/show_bug.cgi?id=376288 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Ken Vermette --- SVN commit 1482525 by kvermette: M +1 -1 footer.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1482525 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376291] New kde.org adds tracking by 3rd-party, googleapis.com
https://bugs.kde.org/show_bug.cgi?id=376291 Ken Vermette changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Ken Vermette --- Alrighty, all that sounds reasonable. I'll put this on my Tuesday to-dos after I sleep off the jet-lag. ;) -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 376291] New kde.org adds tracking by 3rd-party, googleapis.com
https://bugs.kde.org/show_bug.cgi?id=376291 Ken Vermette changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Ken Vermette --- SVN commit 1483072 by kvermette: Added Noto and Noto Bold to be hosted on-site. Modified header code to check if Capacity functions are being included, if they cannot, it will not break the system. This should make testing easier. M +2 -1 aether/header.php A css/Noto-Sans-700 (directory) A css/Noto-Sans-700/LICENSE.txt AMcss/Noto-Sans-700/Noto-Sans-700.eot A css/Noto-Sans-700/Noto-Sans-700.svg AMcss/Noto-Sans-700/Noto-Sans-700.ttf AMcss/Noto-Sans-700/Noto-Sans-700.woff AMcss/Noto-Sans-700/Noto-Sans-700.woff2 A css/Noto-Sans-regular (directory) A css/Noto-Sans-regular/LICENSE.txt AMcss/Noto-Sans-regular/Noto-Sans-regular.eot A css/Noto-Sans-regular/Noto-Sans-regular.svg AMcss/Noto-Sans-regular/Noto-Sans-regular.ttf AMcss/Noto-Sans-regular/Noto-Sans-regular.woff AMcss/Noto-Sans-regular/Noto-Sans-regular.woff2 M +27 -1 css/aetherCore.css WebSVN link: http://websvn.kde.org/?view=rev&revision=1483072 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385778] New: Physics breaks down between the Wayland window decoration and XCB contents
https://bugs.kde.org/show_bug.cgi?id=385778 Bug ID: 385778 Summary: Physics breaks down between the Wayland window decoration and XCB contents Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Conveniently marked by the thin blue strip separating window contents and the title decoration is a realm where logic, physics, and good sense break down. This area only applies to windows with XCB-based applications running in a Wayland session, not native Wayland applications. In practice it's a bit taller than the blue strip, but the blue strip is a good marker for where the issues are. It may take a few attempts to replicate the issues; - Clicking this area will sometimes pass the cursor through to the contents below. If the contents are another window, it will bring that window into the forefront. - On trackpads clicking this area will sometimes instead cause the cursor to switch into resizing mode. Dragging at this point will begin resizing the window from one of the top corners. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385782] New: Right-clicking tray icons (network, battery) will spawn multiple mis-placed context menus
https://bugs.kde.org/show_bug.cgi?id=385782 Bug ID: 385782 Summary: Right-clicking tray icons (network, battery) will spawn multiple mis-placed context menus Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 108362 --> https://bugs.kde.org/attachment.cgi?id=108362&action=edit Showing multiple menus being spawned by repeatedly clicking on tray items. Some tray icons will open a single context menu placed towards the top-left of the screen. Others will spawn multiple context menus (placed similarly) Replicate by right-clicking on tray icons in a Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385784] New: Plasma shell does not close context menus for panel widgets in Wayland
https://bugs.kde.org/show_bug.cgi?id=385784 Bug ID: 385784 Summary: Plasma shell does not close context menus for panel widgets in Wayland Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 108363 --> https://bugs.kde.org/attachment.cgi?id=108363&action=edit Screenshot of task manager items with mutple context menus. Opening context menus for Plasma shell panel items will not close the menu while interacting with Plasma panel elements. You can also open multiple context menus this way (unrelated to the tray item bug) and continue interacting with panels and panel widgets without dismissing the menus. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385786] New: Context sub-menus for some applications show up at the top-left of the screen when there is not enough room on the right side of the screen
https://bugs.kde.org/show_bug.cgi?id=385786 Bug ID: 385786 Summary: Context sub-menus for some applications show up at the top-left of the screen when there is not enough room on the right side of the screen Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 108364 --> https://bugs.kde.org/attachment.cgi?id=108364&action=edit Screenshot of the bug Replicate by opening dolphin, and right-clicking on the display area towards the right side of the screen. The sub-menu will show up on the top right. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385787] New: When minimizing windows, the mouse cursor will be ignored into moved
https://bugs.kde.org/show_bug.cgi?id=385787 Bug ID: 385787 Summary: When minimizing windows, the mouse cursor will be ignored into moved Product: kwin Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- This mainly affects when you are minimizing multiple windows at once. You must move the mouse slightly after each minimization in order to press the next minify button. To replicate this issue; 1. Open and maximize multiple windows. 2. Click the minimize button 3. You will see the the decoration does not 'see' the mouse, there is no hover effect on the next minimize button. Without moving the mouse, click the newly exposed minimize button. 4. Nothing happens. 5. Move the mouse slightly 6. The mouse will be 'seen' and the click will be accepted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378356] New: Mouse cursors have abnormally dark pixels around edges
https://bugs.kde.org/show_bug.cgi?id=378356 Bug ID: 378356 Summary: Mouse cursors have abnormally dark pixels around edges Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- Created attachment 104844 --> https://bugs.kde.org/attachment.cgi?id=104844&action=edit Samples as seen by placing the cursor next to the preview in systemsettings. Most visible when viewing "Breeze" cursors on a white or light background. Pixels which are white (or light) which are semitransparent will appear darkened. When taking screenshots, if on an X11 system, the cursor will appear 'as it should' in the screenshot. If on a Wayland system the cursor will faithfully show the issue in the screenshot. This was tested on an X11 machine running Nvidia Prop drivers, and a Wayland Intel machine. I have seen it on others. This bug has been present for years, it is not new; it is only because my Wayland session took an accurate screenshot that I'm able to report this. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper
https://bugs.kde.org/show_bug.cgi?id=361778 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Ken Vermette --- For Plasma 5.10 and beyond I've added 1900x1200 wallpapers to the build/sizing script. For the SVG stuff I think I'll defer that until later, as if we switch to SVG at some point, it limits what we can do in the future... And it's off-topic anyway. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper
https://bugs.kde.org/show_bug.cgi?id=361778 --- Comment #6 from Ken Vermette --- Shoot, just replied to the wrong bug. Either way, 4k wallpapers are included now anyways. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 375825] Please include 1920x1200 size wallpaper
https://bugs.kde.org/show_bug.cgi?id=375825 Ken Vermette changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ken Vermette --- For Plasma 5.10 and beyond I've added 1900x1200 wallpapers to the build/sizing script. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378356] Mouse cursors have abnormally dark pixels around edges
https://bugs.kde.org/show_bug.cgi?id=378356 --- Comment #2 from Ken Vermette --- I've reported this bug upstream. If they recommend a solution or request more information I'll relay what they say here. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 378820] Icons without white border in breeze-cursor theme
https://bugs.kde.org/show_bug.cgi?id=378820 Ken Vermette changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED CC||verme...@gmail.com --- Comment #2 from Ken Vermette --- Sadly this is a bug in DRI, I've already filed a report (I've neglected my own upstream bug report, but I'll get back on it). What's happening is the light border it does have is being rendered much darker than it should be. If you don't mind, please hit up the report in this link and add your own system info: https://bugs.freedesktop.org/show_bug.cgi?id=100534 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 497991] New: Severe lag when KWin disables compositing
https://bugs.kde.org/show_bug.cgi?id=497991 Bug ID: 497991 Summary: Severe lag when KWin disables compositing Classification: Plasma Product: kwin Version: 6.2.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com Target Milestone: --- SUMMARY When an application goes full-screen on KWin-Wayland it becomes unusable due to lag when KWin disables compositing. Using the "Show Compositing" effect to display when compositing is active shows this is the issue. STEPS TO REPRODUCE 1. Enable "Show Compositing" effect (optional) 2. Open any full-screen application (Video players, games) 3. Put the application into a full-screen state, if not already in full-screen. OBSERVED RESULT Extreme frame-rate drops, stuttering mouse. "Feels" within the range of 12fps. EXPECTED RESULT Smooth video playback, or smooth gameplay under low load. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 6.2 KDE Plasma Version: 6.2.4 (also present in at least 6.2.3) KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION - The "Show FPS" effect forces compositing to be enabled, so it cannot be used to benchmark. It does prove that it's not otherwise a performance issue. - For quick testing, shaking the mouse momentarily enables compositing. You can shake the mouse to instantly see full-screen applications run smoothly. - Some applications, like Firefox, do not disable compositing in full-screen mode. Applications exhibiting this effect include Haruna (Video player), Factorio (Game), Oxygen not Included (Game). - Using Intel Arc Graphics WORKAROUNDS: - Using a brew of KWin rules, games can be forced to run full-screen in a composited environment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 497991] Severe lag when KWin disables compositing
https://bugs.kde.org/show_bug.cgi?id=497991 --- Comment #2 from Ken Vermette --- Here is a video of the issue as described: https://youtu.be/KkPrFrWLmaI Specifically during the Factorio segments you can see the game visibly speed up and slow down depending on the state of 'compositing' (as reported by the plugin); I shake the mouse several times during the video to force compositing during gameplay. When 'compositing' is off, the mouse is also incredibly sluggish and stuttery. Big buck bunny is a bit harder to see the issue with, but it's in the video as well. It's likely an issue when Kwin kicks into direct scanout, but that's a lamens' best guess. If there's a method to disable direct scanout, I'm willing to give it a shot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 498339] New: Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 Bug ID: 498339 Summary: Media Keys Not Working Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: verme...@gmail.com CC: fanzhuyi...@gmail.com Target Milestone: --- SUMMARY Various keys including brightness, volume, media play/pause, screenshot, etc do not work. STEPS TO REPRODUCE 1. Press media key (e.g. volume up) OBSERVED RESULT Nothing happens. EXPECTED RESULT Corresponding action happens (e.g. volume up) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION - Running "sudo libinput debug-events" shows that the various keys are being detected (KEY_VOLUMEUP, KEY_VOLUMEDOWN, KEY_BRIGHTNESSUP, etc) - Manually starting or re-starting gives no errors. - Nothing is showing --- Checking systemctl gives this: systemctl --user status plasma-kglobalaccel.service ○ plasma-kglobalaccel.service - KDE Global Shortcuts Server Loaded: loaded (/usr/lib/systemd/user/plasma-kglobalaccel.service; static) Active: inactive (dead) since Mon 2025-01-06 19:43:36 EST; 20min ago Process: 1585 ExecStart=/usr/lib/x86_64-linux-gnu/libexec/kglobalacceld (code=exited, status=0/SUCCESS) Main PID: 1585 (code=exited, status=0/SUCCESS) CPU: 29ms --- Here be the process: ps aux | grep kglobalaccel kver7402 0.0 0.0 9280 2176 pts/1S+ 20:08 0:00 grep --color=auto kglobalaccel --- Checking journalctl gives nothing interesting: journalctl --user -u plasma-kglobalaccel.service Nov 15 01:45:26 kver-glasstower systemd[59198]: Stopping plasma-kglobalaccel.service - KDE Global Shortcuts Server... Nov 15 01:45:26 kver-glasstower systemd[59198]: Stopped plasma-kglobalaccel.service - KDE Global Shortcuts Server. (etc) --- Here's what the deps list looks like: systemctl --user list-dependencies plasma-kglobalaccel.service plasma-kglobalaccel.service ● ├─background.slice ● ├─dbus.socket ○ ├─kde-nomodeset.service ● └─basic.target ● ├─paths.target ● ├─sockets.target ● │ ├─dbus.socket ● │ ├─dirmngr.socket ● │ ├─drkonqi-coredump-launcher.socket ● │ ├─gpg-agent-browser.socket ● │ ├─gpg-agent-extra.socket ● │ ├─gpg-agent-ssh.socket ● │ ├─gpg-agent.socket ● │ ├─keyboxd.socket ● │ ├─pipewire-pulse.socket ● │ ├─pipewire.socket ● │ ├─pk-debconf-helper.socket ● │ ├─snapd.session-agent.socket ● │ └─speech-dispatcher.socket ● └─timers.target ○ ├─drkonqi-coredump-cleanup.timer ○ ├─drkonqi-sentry-postman.timer ● └─launchpadlib-cache-clean.timer -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 498339] Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 --- Comment #2 from Ken Vermette --- (In reply to fanzhuyifan from comment #1) > Thank you for your bug report! > > Is this on X11 or wayland? The plasma-kglobalaccel service only runs > standalone on X11, on wayland this is run inside kwin. Nono - thank _you_ for taking a looksee! This is on Wayland; if there's any tests or anything that you need, just let me know! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 498339] Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 --- Comment #4 from Ken Vermette --- (In reply to fanzhuyifan from comment #3) > Could you attach the content of the file `~/.config/kglobalshortcutsrc`? > > If possible, would you be able to check if the error is reproducible on x11? > Thanks! Here's the contents of the file... I'll test on X11 probably tomorrow, I've got to run for the moment. [ActivityManager] _k_friendly_name=Activity Manager switch-to-activity-50e65e51-d1ce-48c5-9e72-769045c8b77e=none,none,Switch to activity "Default" [KDE Keyboard Layout Switcher] Switch to Last-Used Keyboard Layout=Meta+Alt+L,Meta+Alt+L,Switch to Last-Used Keyboard Layout Switch to Next Keyboard Layout=Meta+Alt+K,Meta+Alt+K,Switch to Next Keyboard Layout _k_friendly_name=Keyboard Layout Switcher [kaccess] Toggle Screen Reader On and Off=Meta+Alt+S,Meta+Alt+S,Toggle Screen Reader On and Off _k_friendly_name=Accessibility [kcm_touchpad] Disable Touchpad=Touchpad Off,Touchpad Off,Disable Touchpad Enable Touchpad=Touchpad On,Touchpad On,Enable Touchpad Toggle Touchpad=Touchpad Toggle\tMeta+Ctrl+Zenkaku Hankaku,Touchpad Toggle\tMeta+Ctrl+Zenkaku Hankaku,Toggle Touchpad _k_friendly_name=Touchpad [kmix] _k_friendly_name=Audio Volume decrease_microphone_volume=Microphone Volume Down,Microphone Volume Down,Decrease Microphone Volume decrease_volume=Volume Down,Volume Down,Decrease Volume decrease_volume_small=Shift+Volume Down,Shift+Volume Down,Decrease Volume by 1% increase_microphone_volume=Microphone Volume Up,Microphone Volume Up,Increase Microphone Volume increase_volume=Volume Up,Volume Up,Increase Volume increase_volume_small=Shift+Volume Up,Shift+Volume Up,Increase Volume by 1% mic_mute=Microphone Mute\tMeta+Volume Mute,Microphone Mute\tMeta+Volume Mute,Mute Microphone mute=Volume Mute,Volume Mute,Mute [ksmserver] Halt Without Confirmation=none,,Shut Down Without Confirmation Lock Session=Meta+L\tScreensaver,Meta+L\tScreensaver,Lock Session Log Out=Ctrl+Alt+Del,Ctrl+Alt+Del,Show Logout Screen Log Out Without Confirmation=none,,Log Out Without Confirmation LogOut=none,,Log Out Reboot=none,,Reboot Reboot Without Confirmation=none,,Reboot Without Confirmation Shut Down=none,,Shut Down _k_friendly_name=Session Management [kwin] Activate Window Demanding Attention=Meta+Ctrl+A,Meta+Ctrl+A,Activate Window Demanding Attention Cycle Overview=none,none,Cycle through Overview and Grid View Cycle Overview Opposite=none,none,Cycle through Grid View and Overview Decrease Opacity=none,,Decrease Opacity of Active Window by 5% Edit Tiles=Meta+T,Meta+T,Toggle Tiles Editor Expose=Ctrl+F9,Ctrl+F9,Toggle Present Windows (Current desktop) ExposeAll=Ctrl+F10\tLaunch (C),Ctrl+F10\tLaunch (C),Toggle Present Windows (All desktops) ExposeClass=Ctrl+F7,Ctrl+F7,Toggle Present Windows (Window class) ExposeClassCurrentDesktop=none,none,Toggle Present Windows (Window class on current desktop) Grid View=Meta+G,Meta+G,Toggle Grid View Increase Opacity=none,,Increase Opacity of Active Window by 5% Kill Window=Meta+Ctrl+Esc,Meta+Ctrl+Esc,Kill Window Move Tablet to Next Output=none,none,Move the tablet to the next output MoveMouseToCenter=Meta+F6,Meta+F6,Move Mouse to Center MoveMouseToFocus=Meta+F5,Meta+F5,Move Mouse to Focus MoveZoomDown=none,none,Move Zoomed Area Downwards MoveZoomLeft=none,none,Move Zoomed Area to Left MoveZoomRight=none,none,Move Zoomed Area to Right MoveZoomUp=none,none,Move Zoomed Area Upwards Overview=Meta+W,Meta+W,Toggle Overview Setup Window Shortcut=none,,Setup Window Shortcut Show Desktop=Meta+D,Meta+D,Peek at Desktop Suspend Compositing=Alt+Shift+F12,Alt+Shift+F12,Suspend Compositing Switch One Desktop Down=Meta+Ctrl+Down,Meta+Ctrl+Down,Switch One Desktop Down Switch One Desktop Up=Meta+Ctrl+Up,Meta+Ctrl+Up,Switch One Desktop Up Switch One Desktop to the Left=Meta+Ctrl+Left,Meta+Ctrl+Left,Switch One Desktop to the Left Switch One Desktop to the Right=Meta+Ctrl+Right,Meta+Ctrl+Right,Switch One Desktop to the Right Switch Window Down=Meta+Alt+Down,Meta+Alt+Down,Switch to Window Below Switch Window Left=Meta+Alt+Left,Meta+Alt+Left,Switch to Window to the Left Switch Window Right=Meta+Alt+Right,Meta+Alt+Right,Switch to Window to the Right Switch Window Up=Meta+Alt+Up,Meta+Alt+Up,Switch to Window Above Switch to Desktop 1=Ctrl+F1,Ctrl+F1,Switch to Desktop 1 Switch to Desktop 10=none,,Switch to Desktop 10 Switch to Desktop 11=none,,Switch to Desktop 11 Switch to Desktop 12=none,,Switch to Desktop 12 Switch to Desktop 13=none,,Switch to Desktop 13 Switch to Desktop 14=none,,Switch to Desktop 14 Switch to Desktop 15=none,,Switch to Desktop 15 Switch to Desktop 16=none,,Switch to Desktop 16 Switch to Desktop 17=none,,Switch to Desktop 17 Switch to Desktop 18=none,,Switch to Desktop 18 Switch to Desktop 19=none,,Switch to Desktop 19 Switch to Desktop 2=Ctrl+F2,Ctrl+F2,Switch to Desktop 2 Switch to Desktop 20=none,,Switch to Desktop 20 Switch to Desktop 3=Ctrl+F3,Ctrl+F3,Switch to Desktop
[frameworks-kglobalaccel] [Bug 498339] Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 --- Comment #6 from Ken Vermette --- (In reply to fanzhuyifan from comment #5) > The contents of your `~/.config/kglobalshortcutsrc` look correct -- the > shortcuts for volume control are correctly set. > > In krunner, if you search for "kwin debug console" and launch it, and go to > the input events tab, and press the media keys (volume up, volume down), > what do you see in the Qt::Key code field? Are the key presses correctly > resolved to Key_VolumeUp and Key_VolumeDown? I's not even receiving those key codes at all; it's receiving other keystrokes and mouse movement, but no media keys. Trying it our on X11, the media keys do work as normal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 498339] Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 --- Comment #7 from Ken Vermette --- (In reply to Ken Vermette from comment #6) > (In reply to fanzhuyifan from comment #5) > > The contents of your `~/.config/kglobalshortcutsrc` look correct -- the > > shortcuts for volume control are correctly set. > > > > In krunner, if you search for "kwin debug console" and launch it, and go to > > the input events tab, and press the media keys (volume up, volume down), > > what do you see in the Qt::Key code field? Are the key presses correctly > > resolved to Key_VolumeUp and Key_VolumeDown? > > I's not even receiving those key codes at all; it's receiving other > keystrokes and mouse movement, but no media keys. > > Trying it our on X11, the media keys do work as normal. Oh, as a follow up, I should mention that at one point the media keys did work on Wayland on a previous installation on this machine (My previous installation was long in the tooth); This is an issue on a fresh install, so it may be something with a new version of Plasma, Qt, or something with an older bundled configuration. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 498339] Media Keys Not Working
https://bugs.kde.org/show_bug.cgi?id=498339 --- Comment #9 from Ken Vermette --- (In reply to fanzhuyifan from comment #8) > What is the output of `xmodmap -pke | grep -i volume`? If nothing is > outputted you need to add your media keys to the keymap. I get... xmodmap -pke | grep -i volume keycode 122 = XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume keycode 123 = XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume (Thanks again, btw) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 497991] Severe lag when KWin disables compositing
https://bugs.kde.org/show_bug.cgi?id=497991 --- Comment #5 from Ken Vermette --- (In reply to Zamundaaa from comment #4) > (In reply to Ken Vermette from comment #2) > > It's likely an issue when Kwin kicks into direct scanout, but that's a > > lamens' best guess. If there's a method to disable direct scanout, I'm > > willing to give it a shot. > There's > https://invent.kde.org/plasma/kwin/-/wikis/Environment- > Variables#kwin_drm_no_direct_scanout for that Okay, addd That works like a charm! So it seems scanout and Intel Arc don't play too nicely. I personally am happy, but I'll check into this ticket later and do any troubleshooting steps in case you want to use me as your guinea pig. :) For any Googlers, run the command "kate /etc/environment" (might create a new file) and add the line: KWIN_DRM_NO_DIRECT_SCANOUT=1 Then save & restart. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502587] New: Plasma Animations causing Full-Screen Repaints
https://bugs.kde.org/show_bug.cgi?id=502587 Bug ID: 502587 Summary: Plasma Animations causing Full-Screen Repaints Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: verme...@gmail.com Target Milestone: 1.0 SUMMARY Various plasma animations such as progress bars, timeout indicators, or notification paging transitions cause full-screen repaints. Overall Plasma Shell is very eager to cause full-screen repaints. Can cause micro-stutters and slowdowns, especially for long-running animations. I'd guess it would probably hit battery life on mobile devices, too. STEPS TO REPRODUCE 1. Enable the Kwin painting effect 2a. Begin a large file transfer (or some other event to trigger an ongoing progress animation) 2b. Open the "Hidden Icons" area of the system tray and move your mouse over various buttons 2c. Trigger any transitions, including opening any popup-based widget (menus, tray items, etc) OBSERVED RESULT The entire screen repaints EXPECTED RESULT Repainting should be limited to just the progress bar, or the popup surface SOFTWARE/OS VERSIONS KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Intel Arc Graphics Wayland ADDITIONAL INFORMATION Likely several smaller problems. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364607] New: In Wayland session when Breeze decoration set to "no borders", you cannot resize from frameless edges/corners
https://bugs.kde.org/show_bug.cgi?id=364607 Bug ID: 364607 Summary: In Wayland session when Breeze decoration set to "no borders", you cannot resize from frameless edges/corners Product: kwin Version: 5.6.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: verme...@gmail.com When using Wayland session I set the Breeze decoration to "no borders", so only the title-bar remained. After doing so I could not resize the windows from the left, bottom, or right edges, or either of the bottom corners. I am able to resize from the top edge, and the top corners. Reproducible: Always Steps to Reproduce: 1. Set Breeze decoration to "No Borders" 2. Attempt to resize from the left, bottom, or right edges, or either bottom corner. Actual Results: Cannot resize window from any "frameless" edge or corner. Expected Results: Resize the window via an "invisible" frame. (Possible additional bug report?) the resize handle in the bottom-right corner is not present. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356280] Option to disable panel transparency
https://bugs.kde.org/show_bug.cgi?id=356280 Ken Vermette changed: What|Removed |Added CC||verme...@gmail.com --- Comment #2 from Ken Vermette --- Additionally, disabling compositing will remove several distractions, including animations, as well as removing transparency. One thing we could do is add an intensity option slider to the Kwin "Background Contrast" effect; with the extreme intensity effectively drowning out the background completely, only picking up a small amount of colour. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper
https://bugs.kde.org/show_bug.cgi?id=361778 --- Comment #1 from Ken Vermette --- For reference we offer resolutions up to 3200x2000 right now. 4K has a resolution of 3840x2160 being the consumer standard. There are some people out there starting to float 8K (7680x4320 !!!) as a thing and while it sounds ludicrous now, there was a time when 4K was crazy. But we also have to remember some people have multiple monitors and may want to span their wallpapers across multiple 4K monitors anyway. Really, I'd like a solution where we can reasonably bundle 8K wallpapers as well to be future-proofed. The main problem I think we're facing (and the push-back we'll see) is filesize. Right now we're using PNG format images, and depending on complexity the wallpapers have run filesizes between 10-30MB. A 4K wallpaper runs about ~3MB on its own (for skylight), a pretty big hit... But encoded in JPG at 98% quality we halve it to 1.4MB, where I think 8K would become feasible too. Even then, we can encode these ultra-high-def images at slightly lower qualities as pixel-level compression artifacts becomes less visible on these screens. There were issues with JPG and configuration hardcoding stuff, and because of how we release software, we may need to wait a release or two for 4K/8K wallpapers if we wait for JPG. I'll light some fires under people or try to get some patches in to begin correcting this. Right now the way we distribute wallpapers will cause size complaints if we include them as we do now; we need to fix that first, I think. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper
https://bugs.kde.org/show_bug.cgi?id=361778 --- Comment #3 from Ken Vermette --- (In reply to Aleix Pol from comment #2) > Couldn't we distribute the wallpaper in SVG? If we can do it, I'm all in for using SVG straight from the tap; it was something I brought up before during the Plasma Sprint, but I didn't get an enthused reaction. Performance concerns were cited. Maybe we could have the system check for a named scalable file if the screen is larger than the largest provided PNG wallpaper. If you're using a lower end computer then the PNG graphics might be faster, but if you're running the kind of screen with 4K resolutions it's less of a concern - you probably have the horsepower to render/cache the image anyway. If we do this, we can probably drop the higher resolution wallpapers as well and save some space. My one question would be how this might affect the splash or locks screens; could they also use SVG images? -- You are receiving this mail because: You are watching all bug changes.
