| Summary: | KWin crashes in KWin::DrmPipeline::prepareAtomicPresentation on screen wake | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | kdebugs |
| Component: | generic-crash | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | filip.kendes1, henrik, kde-bugs, kde, kdedev, miso, nate, pramhof+kde, smichak.uv, strijbol.niko, xaver.hugl |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 6.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=500819 https://bugs.kde.org/show_bug.cgi?id=502156 |
||
| Latest Commit: | https://invent.kde.org/plasma/kwin/-/commit/7d5864caf3334ac9bd90dd1568680e05bcb20e6b | Version Fixed In: | |
| Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/99357/events/26e7313ecfcd4aceaaf85343e1815701/ | ||
|
Description
kdebugs
2025-02-13 21:30:38 UTC
*** Bug 500139 has been marked as a duplicate of this bug. *** *** Bug 500094 has been marked as a duplicate of this bug. *** A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/7205 Git commit 9dd70310eb016625313a0e81b6b49e98e64fff6a by Xaver Hugl. Committed on 24/02/2025 at 21:49. Pushed by zamundaaa into branch 'master'. backends/drm: reject output configurations that can't be powered at all Just disabling pipelines doesn't work, as the outputs are still enabled in that case and will try to present on the disabled pipeline, causing crashes. This fixes https://crash-reports.kde.org/share/issue/bbe74a0e4b494c929f8f52bca6a0953b M +3 -4 src/backends/drm/drm_gpu.cpp https://invent.kde.org/plasma/kwin/-/commit/9dd70310eb016625313a0e81b6b49e98e64fff6a Git commit 0d05df00b04d7913800bd7e10d3594a3fea8ecd2 by Xaver Hugl. Committed on 24/02/2025 at 21:49. Pushed by zamundaaa into branch 'master'. workspace: better deal with having more outputs than the GPU can drive Instead of just giving up, when generating a new output configuration we just disable outputs one by one. This *should* result in an output configuration that can actually be enabled, and it's up to the user to then change the set of enabled outputs to what they like to have. M +10 -4 src/backends/drm/drm_backend.cpp M +1 -1 src/backends/drm/drm_backend.h M +5 -1 src/backends/drm/drm_gpu.cpp M +1 -0 src/backends/drm/drm_pipeline.h M +2 -2 src/core/outputbackend.cpp M +1 -1 src/core/outputbackend.h M +6 -0 src/effect/globals.h M +6 -2 src/wayland/outputmanagement_v2.cpp M +62 -33 src/workspace.cpp M +1 -1 src/workspace.h https://invent.kde.org/plasma/kwin/-/commit/0d05df00b04d7913800bd7e10d3594a3fea8ecd2 Git commit 7d5864caf3334ac9bd90dd1568680e05bcb20e6b by Xaver Hugl. Committed on 25/02/2025 at 13:55. Pushed by zamundaaa into branch 'Plasma/6.3'. backends/drm: reject output configurations that can't be powered at all Just disabling pipelines doesn't work, as the outputs are still enabled in that case and will try to present on the disabled pipeline, causing crashes. This fixes https://crash-reports.kde.org/share/issue/bbe74a0e4b494c929f8f52bca6a0953b (cherry picked from commit 9dd70310eb016625313a0e81b6b49e98e64fff6a) M +3 -4 src/backends/drm/drm_gpu.cpp https://invent.kde.org/plasma/kwin/-/commit/7d5864caf3334ac9bd90dd1568680e05bcb20e6b Git commit a23949582f05c1db7c9bb3bf7fd0292b7120045d by Xaver Hugl. Committed on 25/02/2025 at 13:55. Pushed by zamundaaa into branch 'Plasma/6.3'. workspace: better deal with having more outputs than the GPU can drive Instead of just giving up, when generating a new output configuration we just disable outputs one by one. This *should* result in an output configuration that can actually be enabled, and it's up to the user to then change the set of enabled outputs to what they like to have. (cherry picked from commit 0d05df00b04d7913800bd7e10d3594a3fea8ecd2) M +10 -4 src/backends/drm/drm_backend.cpp M +1 -1 src/backends/drm/drm_backend.h M +5 -1 src/backends/drm/drm_gpu.cpp M +1 -0 src/backends/drm/drm_pipeline.h M +2 -2 src/core/outputbackend.cpp M +1 -1 src/core/outputbackend.h M +6 -0 src/effect/globals.h M +6 -2 src/wayland/outputmanagement_v2.cpp M +62 -33 src/workspace.cpp M +1 -1 src/workspace.h https://invent.kde.org/plasma/kwin/-/commit/a23949582f05c1db7c9bb3bf7fd0292b7120045d *** Bug 500942 has been marked as a duplicate of this bug. *** Looks like this issue is still reproducible Plasma 6.3.2 https://bugs.kde.org/show_bug.cgi?id=500942 (In reply to Filip from comment #9) > Looks like this issue is still reproducible Plasma 6.3.2 > > https://bugs.kde.org/show_bug.cgi?id=500942 For me (reporting in 500942), the issue even started with 6.3.2. It did not appear before the upgrade to 6.3.2 today (2 march 2025). I had run updates less than a week before that. (In reply to Henrik from comment #10) > (In reply to Filip from comment #9) > > Looks like this issue is still reproducible Plasma 6.3.2 > > > For me (reporting in 500942), the issue even started with 6.3.2. It did not > appear before the upgrade to 6.3.2 today (2 march 2025). > I had run updates less than a week before that. According to the version history shown at the link below, it seems that the previous version that worked was 6.3.0-3, so what worked in 6.3.0 broke when upgrading to 6.3.2-1. https:// packages. fedoraproject. org/pkgs/kwin/kwin/fedora-41-updates.html I have same problem on plasma 6.3.2 when connected DELL dock station to my XPS 9560 laptop. Using latest openSUSE Tumbleweed. Let's reopen this issue. Operating System: openSUSE Tumbleweed 20250301 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.4-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: Dell Inc. Product Name: XPS 15 9560 The regression is slightly different from the original bug report, and tracked in bug 500819. Let's leave this original issue as fixed Xaver, We just got a bug report from someone using 6.3.3 (Bug 502156) that looks like it has the same backtrace. What shall we do? And another one in bug 502268. Re-opening. *** Bug 502268 has been marked as a duplicate of this bug. *** *** Bug 502156 has been marked as a duplicate of this bug. *** |