[plasmashell] [Bug 478838] Plasmashell sometimes crashes in QPlatformWindow::hasPendingUpdateRequest() after or during screen being turned off
https://bugs.kde.org/show_bug.cgi?id=478838 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477941] Plasma crashes in ShellCorona::createWaitingPanels() after connecting the external display
https://bugs.kde.org/show_bug.cgi?id=477941 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478700] kwin_wayland + NVIDIA modesetting - Atomic commits failed (and crash)
https://bugs.kde.org/show_bug.cgi?id=478700 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 Matthias Dahl changed: What|Removed |Added Version Fixed In|5.27.6 |5.27.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 Matthias Dahl changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #47 from Matthias Dahl --- @Sebi: You're very welcome. And btw, I know exactly how you feel... been in the same situation quite a few times myself. :-) Thanks to David Edmundson, the fix has now been merged to the stable branch (5.27) and will be part of the next stable release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #45 from Matthias Dahl --- I'm very sorry but the fix has not been applied to the stable 5.27 branch yet, only master. (Plasma 6). I will ping the appropriate people right away. Sorry I haven't been paying closer attention to this lately. :-( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #40 from Matthias Dahl --- Thanks for looking into this-- very much appreciated! :-) Here you go: https://invent.kde.org/plasma/kwin/-/merge_requests/4080 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #38 from Matthias Dahl --- I posted a (lengthy) comment on the 3236 merge request with my findings and suggestion, but after being ignored, I felt somewhat stupid/embarrassed, so I deleted it. The code itself was only a few lines that I never posted because it was just a PoC on my end. I wanted to get a discussion going if this would be a possible solution and where the best place would be, to extend the damage event and how, so I could have come up with a proper implementation that could have been merged eventually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #36 from Matthias Dahl --- With the limited man power KWin has and this being a rather nasty problem (and not a priority), I wouldn't hold my breath for this to get fixed any time soon, I am afraid. I spent a few weeks trying to fix it, deep diving in kwin internals but at the end, I came to the conclusion that there is (imho) no way to make it work with all the floating point numbers and rounding. You have damage events in logical coordinates that are just one pixel in height... after scaling both coordinates and size, they have to perfectly fit where the damage is in device coordinates or you will end up with graphical glitches. That is extremely hard, if not impossible, to do right all the time. I shared my findings and tried to suggest a possible solution I called "fuzzy repaint". Basically you add a few pixel in each direction to the damage event to account for possible floating point/rounding errors. Even a very basic PoC on my end, fixed all glitches and worked fine. It would have required my work and thought to make it safe and sound, but it was better than what we have now and did not require a full repaint or anything else expensive. Unfortunately I was ignored (which is absolutely fine!), so I called it a day and moved on to different shores... :-( It's a pity really. On the surface, with KDE and KWin, you get pretty much everything you wished for with their handling of Wayland/Xwayland, scaling and HiDPI, but it has also has to work properly which is where it falls short. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468715] High CPU usage w/ kwin_wayland while in VT (text console)
https://bugs.kde.org/show_bug.cgi?id=468715 --- Comment #3 from Matthias Dahl --- My hunch was incorrect. Since I am running dbus-broker, I was expecting this to be the culprit. But after monitoring and debugging, everything is just fine and Session::activeChanged is also emitted. But nothing is wired up to actually use that signal to pause kwin. It does some udev monitoring for the drm device and for the pause and resume device from the Session but that's it. Session::activeChanged is used for the input devices, though. Could it be possible that the open source Mesa stack for example does a pause/resume device (which incidentally pauses kwin) and the proprietary nvidia driver does not thus exposing the fact that Session::activeChanged is not actually evaluated (and kwin not paused consuming high cpu)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468715] High CPU usage w/ kwin_wayland while in VT (text console)
https://bugs.kde.org/show_bug.cgi?id=468715 --- Comment #2 from Matthias Dahl --- Thanks for the info. That was very helpful and I do have a hunch now what could be the cause. I will further debug this next week and report back with my findings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468715] New: High CPU usage w/ kwin_wayland while in VT (text console)
https://bugs.kde.org/show_bug.cgi?id=468715 Bug ID: 468715 Summary: High CPU usage w/ kwin_wayland while in VT (text console) Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ua_bugz_...@binary-island.eu Target Milestone: --- Created attachment 158230 --> https://bugs.kde.org/attachment.cgi?id=158230&action=edit a "perf record -g -T -P --running-time" for the kwin_wayland process w/ high cpu usage SUMMARY While I was working to fix a different kwin bug for the past several weeks, I came across this very annoying and consistent (as-in: happens almost 100% of time time) behavior: Switching to the VT (text console) while running kwin_wayland, will result in kwin_wayland eating betweet 40%-50% CPU until I switch back. STEPS TO REPRODUCE 1. Start kwin_wayland (as part of the plasma desktop) 2. Move the mouse around 3. Switch to the VT (text console) OBSERVED RESULT High CPU usage of kwin_wayland EXPECTED RESULT kwin_wayland should be idle SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.27.4 Qt Version: 5.15.9 Qt compile version: 5.15.9 XCB compile version: 1.15 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12301001 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Noto Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 0 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 99 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: allowTearing: true Screen Edges desktopSwitching: true desktopSwitchingMovingClients: true cursorPushBackDistance: 1x1 timeThreshold: 300 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mouse: yes Number of Screens: 1 Screen 0: - Name: HDMI-A-1 Enabled: 1 Geometry: 0,0,2560x1440 Scale: 1.5 Refresh Rate: 6 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1080/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 530.41.03 OpenGL
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #26 from Matthias Dahl --- Since my bug 466643 was marked a duplicate of this one, I will comment here. Though I am not entirely sure if this bug is the same bug I am experiencing. Here are some observations from my side: 1. I am seeing flickering blue lines (full and partial) between the items of menus. For example, if you right-click on the desktop, move your mouse around on the opening menu (also around the desktop itself), those flickering blue lines will be between the menu items. The flickering stops immediately when the mouse movement stops. Also, while using konsole and Midnight Commander, moving the "selection bar" up and down over files, will leave line artifacts as well. 2. This is with any scale fractional scale, integer scales are fine. 3. Desktop effects seemingly have no effect on this. I also don't have blur or background contrast active. 4. This happen with Breeze (Dark/Light) and Adwaita (Dark/Light) for example but disappears completely with Fusion which, otoh, seems somewhat slow/sluggish as a downside. 5. I tried https://invent.kde.org/plasma/kwin/-/merge_requests/3236 but it made no noticeable difference in my case (currently running with it). 6. I have seen this for quite some time now, probably since Nvidia introduced their GBM support. 7. I am running the latest git qt-5 branches for everything kde (Plasma, kwin, etc.) except normal applications. 8. Java applications using FlatLaf are apparently also completely fine. KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.27.2 Qt Version: 5.15.8 Qt compile version: 5.15.8 XCB compile version: 1.15 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12201008 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Breeze Plugin recommends border size: None onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 36 Options === focusPolicy: 0 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 99 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: allowTearing: true Screen Edges desktopSwitching: true desktopSwitchingMovingClients: true cursorPushBackDistance: 1x1 timeThreshold: 300 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mouse: yes Number of Screens: 1 Screen 0: - Name: HDMI-A-1 Enabled: 1 Geometry: 0,0,2560x1440 Scale: 1.5 Refresh Rate: 6 Adaptive Sync: incapable Compositing ===
[kwin] [Bug 466643] flickering blue line with scaling > 100%
https://bugs.kde.org/show_bug.cgi?id=466643 --- Comment #1 from Matthias Dahl --- 1. Just tested w/ Nvidia drivers 530.30.02, nothing has changed at all. 2. When moving the mouse around the whole desktop while the menu is open with the blue lines, they will flicker with the movement of the mouse. If one stops moving the mouse, the flickering stops. 3. Desktop effects seemingly have no effect on this matter whatsoever. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466643] New: flickering blue line with scaling > 100%
https://bugs.kde.org/show_bug.cgi?id=466643 Bug ID: 466643 Summary: flickering blue line with scaling > 100% Classification: Plasma Product: kwin Version: 5.26.90 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ua_bugz_...@binary-island.eu Target Milestone: --- SUMMARY In a Plasma/Wayland session, with scaling set to anything above 100%, a flickering blue line is seen on menus between the items while moving through the items with the mouse. Also when using Midnight Commander in konsole, moving the bar around over different items, will leave line artifacts as well. This happens with Breeze and Adwaita for example, but not with the Fusion style which, otoh, seems rather sluggish and slow. STEPS TO REPRODUCE 1. Set scaling to anything above 100% (e.g. 150%) 2. Right click on the Plasma desktop 3. Move the mouse up and down in the menu the opened OBSERVED RESULT Flickering blue (full or partial) blue lines between the menu items. EXPECTED RESULT No flickering blue lines. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Nvidia driver: 525.89.02 egl-gbm: 1.1.0 egl-wayland: 1.1.11-r1 Everything is compiled from yesterday's Qt-5 based git kde branches. This specific problem has been around for ages w/ the Nvidia driver at least. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 454671] krunner hangs after ALT-F2 and typing in the first letter - must be killed afterwards (wayland / nvidia)
https://bugs.kde.org/show_bug.cgi?id=454671 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u --- Comment #4 from Matthias Dahl --- I can confirm, this is still a problem with KDE's git master from today on an up2date Gentoo ~amd64 system w/ Qt 5.15.5, nvidia 515.57 and egl-wayland 1.1.10-r1. This has been a problem for ages, long before GBM support was introduced by nvidia. krunner works perfectly fine in a X11 session. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] Notifications cause system lag
https://bugs.kde.org/show_bug.cgi?id=414785 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433907] plasmashell works slow when displaying textual list of grouped tasks for big group
https://bugs.kde.org/show_bug.cgi?id=433907 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422801] Screen Edges for Virtual Desktop Switching are not working
https://bugs.kde.org/show_bug.cgi?id=422801 Matthias Dahl changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422801] Screen Edges for Virtual Desktop Switching are not working
https://bugs.kde.org/show_bug.cgi?id=422801 --- Comment #1 from Matthias Dahl --- Commit bc2df9f84be7ff12ab7e67ee7931eae1f5aeacce (which references bug #422816), also fixes this bug. Thanks! :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422801] New: Screen Edges for Virtual Desktop Switching are not working
https://bugs.kde.org/show_bug.cgi?id=422801 Bug ID: 422801 Summary: Screen Edges for Virtual Desktop Switching are not working Product: kwin Version: 5.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ua_bugz_...@binary-island.eu Target Milestone: --- SUMMARY Since upgrading to 5.19.0, virtual desktops cannot be switched via screen edges, at least not reliably. I have a setup with 8 virtual desktops (2 rows, 4 each). When I move the mouse cursor to a corner, the desktop is switched to its neighbour. But not when I move to an edge. If a window is present and I move the mouse cursor to the top edge, the desktop is switched, but this does not work on the other edges (a panel is on the bottom edge). STEPS TO REPRODUCE 1. Configure a 4x2 virtual desktop layout. 2. Set "Switch desktop on edge" to "Always Enabled" 3. Set a "Activation delay" and "Reactivation delay" of 300ms 4. Move your mouse cursor to any desktop edge while the desktop is empty with just your panel showing OBSERVED RESULT Nothing happens. EXPECTED RESULT The virtual desktop should be switched according to the triggered edge. SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: Gentoo ~amd64 w/ official kde and qt overlay (available in About System) KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 386665] Drop dependency on pulseaudio-gconf
https://bugs.kde.org/show_bug.cgi?id=386665 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343184] KWin misdetects trimple-buffering (at least on login)
https://bugs.kde.org/show_bug.cgi?id=343184 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380219] New: plasmashell crashes on startup w/ Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=380219 Bug ID: 380219 Summary: plasmashell crashes on startup w/ Qt 5.9 Product: plasmashell Version: 5.9.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ua_bugz_...@binary-island.eu Target Milestone: 1.0 Created attachment 105720 --> https://bugs.kde.org/attachment.cgi?id=105720&action=edit crash backtrace Starting with Qt 5.9 (current git head), plasmashell crashes on startup. I tested with KDE Frameworks 5.34 and git master as well as Plasma 5.9.5, 5.9.95 and git master. The crash is always the same. So far, every other KDE application runs just fine (including KWin), it is just Plasma that is acting up. My system is Gentoo x86_64 (~amd64) w/ gcc 6.3.0, nvidia drivers 381.22 (GTX 1080), glibc 2.24, Xorg 1.19.3, Mesa 17.1.0 and Qt 5.9 (git head). I have attached a complete backtrace of the crash which is 100% reproducible. I am pretty much at my wit's end right now since I tried to track this down myself but this hasn't lead my anywhere thus far. :-( Please let me know if there is anything, anything at all, which I can do to help fix and/or locate this bug. Thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #22 from Matthias Dahl --- (In reply to Dmitry Belyakin from comment #21) > Could it be related to libinput? The problem is with Qt -- and it has been located (= the commit that caused it and why it is happening). I have provided a patch as a stepping-stone (so to speak) to a final solution but thus far, I got no reaction at all on the Qt bug tracker. Personally, I use my patch without any problems but it is _definitely_ not a final solution. I am planning on revisiting this issue once I have some more free time on my hands -- and if it hasn't been fixed meanwhile. It is really a pity that this hasn't been addressed yet and remains an open issue, even though the cause has been located and a first patch was provided. :-( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368164] Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail
https://bugs.kde.org/show_bug.cgi?id=368164 --- Comment #5 from Matthias Dahl --- Interesting, I found one more way to easily trigger the restart w/ and w/o the contrast effect enabled: Slide the KWin window a bit under the panel and start browsing through the msgs, and the effects will restart over and over again. This also happens if you make the window maximized, I guess due to the shadow effect or whatnot. If you move the window out of the way of the panel, things are fine -- as long as the contrast effect is not active. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #15 from Matthias Dahl --- (In reply to akm from comment #14) > can also confirm this on Thumbleweed, took me a while to find this bug > report, just glad its not only me getting irritated by it :) Thanks for reporting back here. It would be awesome if you could hop over to the Qt bug, give that qml minimal working example a try I posted there and report your findings as well as some system stats there as well. You can try the mwe by simply opening it with "qmlscene". Thanks so much in advance... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368164] Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail
https://bugs.kde.org/show_bug.cgi?id=368164 --- Comment #4 from Matthias Dahl --- > So there is some GL error which is then sent to us. Wouldn't it be beneficial to track down what is causing that error in the first place? I have seen this both with my old system (Fermi) and my new one (Pascal) across several driver major versions. Also, it seems like this desktop effect is a common offender and causing trouble, judging from what I was able to read up on it. Besides all that, I bet there is something terrible wrong here. Going from msg to msg shouldn't flicker the desktop panel, nor should it cause to restart the desktop effects eventually. To me, it seems a bit like there is timing involved somewhere. While I was using the akonadiconsole and did a restart of akonadi, akonakiconsole was obviously "busy"/"sluggish" while I moved the window to another desktop... and the desktop effects were restarted. Again, with the effect naturally on. I mean, I have no problem turning it off... and I see no advantage of having it on. But others will as well run into this problem -- and it is an annoying bug. And not everyone will have the time and patience to track it down or will report it here. It is, imho, bad press for KDE when in its default configuration, such a bug exists. Just my two cents, and I absolutely mean no disrespect here. Just trying to draw a wider picture... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368164] Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail
https://bugs.kde.org/show_bug.cgi?id=368164 --- Comment #2 from Matthias Dahl --- Unfortunately, kwin_x11 reports nothing except for the system info when it restarts. The one thing that does get logged though (and I just noticed this now) is: kernel: NVRM: Xid (PCI::01:00): 31, Ch 0020, engmask 0101, intr 1000 It is hard to say if this happens immediately before the rest or after. It is at least logged after the rest is noticeable on the screen. It makes no difference btw, if OpenGL 3.1 or 2.0 is used. Except for that, there is only the usual "Desktop effects were restarted due to a graphics reset" and that it was requested. Here the support info: https://paste.kde.org/pdp5kzzws Once the desktop effects restarted, the output is different though: -glPreferBufferSwap: 0 +glPreferBufferSwap: 99 Meaning, VSYNC is off and one has to manually enable it again. Is there anything else I can do? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368164] New: Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail
https://bugs.kde.org/show_bug.cgi?id=368164 Bug ID: 368164 Summary: Background contrast effect causes panel flickering and composition restarts while browsing through mails in KMail Product: kwin Version: 5.7.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: ua_bugz_...@binary-island.eu While browsing through mails in KMail, the composition is being restarted every few seconds and with each mail jump, the panel flickers. This took me quite a while to figure out, since it is not so obvious (@Thomas Lübking: you gonna like this one): It is the background contrast effect. As soon as it is off, everything behaves just fine. This bug has been around a bit since I haven't used KMail for who knows long and just am about to switch back. I remember I saw this exact behavior the last time I tried KMail (which was already on Qt5 back then, but unfortunately I don't know when that was). Reproducible: Always Steps to Reproduce: 1. Make sure composition as well as background contrast effect is on 2. Open KMail in a folder with quite a few mails 3. Browse through those mails with n and p in a pace that still shows the individual mails Actual Results: With each mail shown, the panel will flicker. After a few mails, the composition will restart with the typical msg that something requested that action and the inherent screen side-effects. Expected Results: No flickering. No composition restarts. KDE Applications 16.08, Frameworks 5.25.0, Plasma 5.7.4, NVIDIA Drivers 370.23 (GTX 1080) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #13 from Matthias Dahl --- A quick grep revealed that apart from KWIN, a few other places still use ScrollView and would need adaptation as well to set the Flickable's pixelAligned=true to avoid the corruption. All things said though, this should not cause such a severe corruption after all. I have tried all morning long to debug what is going on in Qt but right now all I got is a head that is about to lift off from my shoulders. I hope the Qt devs do consider the bug report and won't leave it to rot. By the way, could someone set this to confirmed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #11 from Matthias Dahl --- Like expected, this issue can be seen in other places as well. Pretty much everywhere where something inherited from Flickable is issued, like the Widgets browser (via "Add widgets..."). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #10 from Matthias Dahl --- Created attachment 100867 --> https://bugs.kde.org/attachment.cgi?id=100867&action=edit severe corruption in kickoff Here another example screenshot where the corruption was more severe... which is actually also the typical case. The corruption in the unscrollable area below (Computer, Leave, ...) won't be fixed by scrolling or re-opening the menu. Only "restarting" kickoff will fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #9 from Matthias Dahl --- Since this also belongs here, I am copying and pasting from the Qt bug report where I just added the following: Ok, here what I have been able to debug: Everything that uses something inherited from Flickable (like ListView) will expose the issue. Scrolling will result in fractional positions for the content which will cause (severe) font corruption. Since Flickable defaults pixelAligned to false since its inception, those fractional positions are not rounded. Switching pixelAligned to true, fixes the corruption entirely, like expected. Most instances in KDE leave pixelAligned at its default, thus the widespread problem. As far as I know, subpixel positioning is currently only supported on Mac OS X. Questions remains, how are those fractional positions handled on other platforms – especially Linux? It seems like something is going terribly wrong and corrupting the glyph cache. Either way, I don't think fractional positions should result in a corrupted type face whatsoever... or any kind of corruption. Is there anything else I can do to further debug this and be of any help? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #8 from Matthias Dahl --- Like expected, a minimal Qt example was asked for in the Qt bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #7 from Matthias Dahl --- Meanwhile I have also tested this with a fresh OpenSuSE Tumbleweed Live iso in a virtual machine and the issue is also 100% reproducible there as well. I have also taken the liberty to report this upstream: https://bugreports.qt.io/browse/QTBUG-55638 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #6 from Matthias Dahl --- I forgot to mention: I also tested this with Qt's 5.6 git branch as of today -- the corruption is absolutely the same, even though a lot of font and scrolling related fixes went in after 5.6.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #5 from Matthias Dahl --- Created attachment 100847 --> https://bugs.kde.org/attachment.cgi?id=100847&action=edit font corruption after one wheel unit in application launcher -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #4 from Matthias Dahl --- Created attachment 100846 --> https://bugs.kde.org/attachment.cgi?id=100846&action=edit font corruption after one wheel unit in kcm desktop effects -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 --- Comment #3 from Matthias Dahl --- I can confirm this issue as well. It has been long-standing, unfortunately. I will attach two more screenshots which show it rather prominently -- one from the application launcher and one from the desktop effects kcm. My experience is that this can only be triggered when scrolled via mouse wheel and that way it is 100% reproducible and happens all the time. For example: 1) Open the desktop effects kcm. 2) Scroll the list of effects one wheel unit down --> Font corruption happens If you scroll another wheel unit, everything looks fine again. Another wheel unit, and the font is garbled again. And so forth. I have tried to narrow this down but so far have failed. If there is anything I can do at all to help track this bug down, please let me know. I am seeing this on a fresh Gentoo x86_64 system w/ frameworks 5.25.0, plasma 5.7.4, Qt 5.6.1 and freetype 2.6.5. Xorg uses nvidia driver 370.23. KWIN Compositor is using OpenGL 3.1. But neither of those latter ones make any difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358472] plasma widgets: fonts get corrupted on scrolling vertically
https://bugs.kde.org/show_bug.cgi?id=358472 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 367892] During folder synchronisation Akonadi blocks out other operations like deleting or viewing mails
https://bugs.kde.org/show_bug.cgi?id=367892 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 360171] orphaned and hanging kf5/plasma-processes after session end
https://bugs.kde.org/show_bug.cgi?id=360171 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u --- Comment #1 from Matthias Dahl --- I am seeing the same thing here -- the list of dangling processes varies but kded5 usually stays around and needs to be killed with SIGKILL. And also, yes, systemd hangs for the specified timeout value during shutdown/reboot until it successfully kills those processes which is very unfortunate. :-( Those dangling processes are an old issue (see bug 359651 for example) which I have noticed ever since I switched to KDE 5 (which was quite some time ago). But that some of them can only be killed and thus delay the shutdown, that is definitely new. This is seen with Qt 5.6 (w/ the qtdbus fix for the spy stuff), KDE Frameworks 5.20.0 and Plasma 5.6 on an uptodate Gentoo ~amd64 system. If there is anything more I can do to help diagnose this further, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356516] moving from one to another virtual desktop can skip a virtual desktop inbetween
https://bugs.kde.org/show_bug.cgi?id=356516 --- Comment #4 from Matthias Dahl --- (In reply to Thomas Lübking from comment #3) > - Do you have (autohiding or other) panels on either edge? Yes -- and even more interestingly, it is on the right side. ;-) Never actually suspected that one at all. Removing the panel does indeed make the problem go away. The panel is not full size and configured so that windows can go above it. And no auto hide or anything like it. It's used as an quick launcher of sorts, with icons for all my apps I use daily. > - What happens if you lower activation to 0. No change. > - Is this by moving windows or by pure pointer activation - and is the other > variant affected as well? Pure pointer activation is used here. But I just tried the by moving windows variant, and that one is _not_ affected and works just fine (w/ the panel on the right side naturally). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356516] moving from one to another virtual desktop can skip a virtual desktop inbetween
https://bugs.kde.org/show_bug.cgi?id=356516 --- Comment #2 from Matthias Dahl --- Sure: Activation delay is 150ms Reactivation delay is 350ms Playing with those had not effect either (already tried that) -- and apart from that, those exact settings work fine with KWin < 5.5. :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356516] New: moving from one to another virtual desktop can skip a virtual desktop inbetween
https://bugs.kde.org/show_bug.cgi?id=356516 Bug ID: 356516 Summary: moving from one to another virtual desktop can skip a virtual desktop inbetween Product: kwin Version: 5.5.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ua_bugz_...@binary-island.eu Hello... I updated to Plasma 5.5.0 and immediately started running into the following problem that I seem to have narrowed down to KWin (since downgrading it alone to 5.4.3 makes this particular bug go away) : I have 8 virtual desktops, arranged in a 2x4 manner. When moving from one virtual desktop to another by going over the right edge of the screen, there is a 50:50 chance that it will switch one desktop further and skip the actual correct desktop. This does not happen when going from right to left, only from left to right. It seems like the mouse cursor is not always properly reset to the proper side and thus causes a another jump... but I am not sure on this one. Like I said, downgrading KWin to 5.4.3 does fix at least this problem but causes new ones in other areas, so it is not really even a workaround. ;-) If there is anything I can do to help further diagnose this, please let me know. Reproducible: Always Steps to Reproduce: 1. Create several virtual desktops (e.g. 2x4) 2. Switch between them several times by moving the mouse cursor over the right edge of the screen Actual Results: Sometimes the correct desktop is skipped and there screen jumps one desktop too far. Expected Results: Switch to the correct desktop. -- You are receiving this mail because: You are watching all bug changes.
