Bug 506491 - Asahi Linux: Plane operation would have crashed DCP. Screen locker is broken.
Summary: Asahi Linux: Plane operation would have crashed DCP. Screen locker is broken.
Status: RESOLVED DUPLICATE of bug 506316
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.4.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-02 14:08 UTC by Trung Nguyen
Modified: 2025-07-02 20:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Trung Nguyen 2025-07-02 14:08:29 UTC
SUMMARY
On Fedora Linux Asahi Remix 42, the compositor does an illegal request for DCP. The result is (not limited to) the screen locker is broken, requiring dropping into TTY and doing `loginctl unlock-session`.

STEPS TO REPRODUCE
1.  Login to your user account
2.  Wait for the screen to autolock
3.  Observe

OBSERVED RESULT
The screen locker is broken. A message from DCP driver is printed:

```
[  369.437762] apple-drm soc:display-subsystem: Plane operation would have crashed DCP! Rejected!
                                DCP requires 32x32 of every plane to be within screen space.
                                Your compositor asked to overlay [2355x1571, 2403x1600] on 2560x1600.
                                This is not supported, and your compositor should have
                                switched to software compositing when this operation failed.
                                You should not have noticed this at all. If your screen
                                froze/hitched, or your compositor crashed, please report
                                this to the your compositor's developers. We will not
                                throw this error again until you next reboot.
```
Note that the message is sometimes printed by stuffs thats not the screen locker, though it reliably affects the screenlocker.

EXPECTED RESULT
The screen locker works normally.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux Asahi Remix 42
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.14.8-400.asahi.fc42.aarch64+16k (64-bit)
Graphics Platform: Wayland
Processors: 4 × Apple Avalanche (M2), 4 × Apple Blizzard (M2)
Memory: 23.0 GiB of usable RAM
Graphics Processor 1: Apple M2
Graphics Processor 2: llvmpipe
Product Name: Apple MacBook Air (13-inch, M2, 2022)
U-Boot Version: 2025.04

ADDITIONAL INFORMATION

Other samples from journalctl:
```
Jul 01 12:43:36 trung-macbookair kernel: apple-drm soc:display-subsystem: Plane operation would have crashed DCP! Rejected!
                                                                 DCP requires 32x32 of every plane to be within screen space.
                                                                 Your compositor asked to overlay [322x1572, 370x1600] on 2560x1600.
                                                                 This is not supported, and your compositor should have
                                                                 switched to software compositing when this operation failed.
                                                                 You should not have noticed this at all. If your screen
                                                                 froze/hitched, or your compositor crashed, please report
                                                                 this to the your compositor's developers. We will not
                                                                 throw this error again until you next reboot.
Jul 01 12:43:37 hostname systemd[1089]: Started app-org.mozilla.firefox@46fbaed5d9d347e4af37561d593666ee.service - Firefox - Web Browser.
```
Comment 1 Nicolas Fella 2025-07-02 20:20:35 UTC
The message is completely unrelated to the screen locker not working

*** This bug has been marked as a duplicate of bug 506316 ***