Summary: | Wayland Session: Plasma crashes in QSGBatchRenderer::QMatrix4x4_Accessor::is2DSafe() when moving widgets to second screen | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | aTosser <atosser> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | akselmo, doucxldh, kde, kdedev, nate, postix, vladkosh1 |
Priority: | NOR | Keywords: | drkonqi, multiscreen |
Version: | 5.27.10 | ||
Target Milestone: | 1.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=449981 https://bugs.kde.org/show_bug.cgi?id=410964 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
aTosser
2023-12-25 19:09:43 UTC
Can't reproduce on Plasma 6. Does this happen if the secondary monitor is not rotated? Possibly a driver issue too. I had held out hope that this issue had resolved itself. It seems this bug wanted to be my Valentine. Same triggers, 5.27.10-r1/5.115.0 Mesa 24.0.0 for this issue. I will be updating to 24.0.1 in the next few hours and will continue looking into the source of this problem. Linux 6.7.4 So far it seems rather widget agnostic however I tend to only use the various usage monitor widgets on the desktop itself. I am not really able to "test" for the rotation question asked due to the intermittence. I believe mesa has been on the same version for this period so the driver being an issue is possible. For further clarification: I can move windows and widgets around the screens and the crash will only happen once the mouse cursor reaches the border between the displays. I do not know if the window snap edge interaction is causing issue or if there is something waylandy about the windows no longer being on the same... canvas? Sometimes I can move a widget and it will just be happy and then a few seconds later move that same widget and trigger the crash. In other circumstances I can wiggle the mouse back and forth beyond the border and it will be fine for more than a dozen crossings. The only thing consistent in the experience is I never have the opportunity to release the mouse button and after kwin has recovered the widget is gone, somehow removed. I was able to reproduce on first try with the following steps. Create an "Individual Core Usage" widget to the screen. Set to color grid. (Columns were changed to 8 for my system) Set widget to hide background. Move widget from screen 2 (right) to screen 1 (left) (crash) The consistency is hiding the widget background. This setting is the culprit. I also tested with display rotation 0 with the same results. *** Bug 482979 has been marked as a duplicate of this bug. *** Created attachment 170132 [details]
New crash information added by DrKonqi
plasmashell (5.24.7) using Qt 5.15.3
- What I was doing when the application crashed:
moving widgets (cpu load/network load/RAM load) to second screen
- Custom settings of the application:
nothing
-- Backtrace (Reduced):
#4 0x000076c285fb722e in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5 0x000076c285fbcb25 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6 0x000076c285fbd352 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7 0x000076c285fa4924 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8 0x000076c285fa4df3 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
The backtrace looks very similar to bug 446874, which has been resolved since this bug was opened. Are you still able to reproduce this on an up to date system?https://bugs.kde.org/show_bug.cgi?id=479001# ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |