| Summary: | display configuration not working after update | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | bugs.kde.org |
| Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | nate, plasma-bugs-null, xaver.hugl |
| Priority: | NOR | Keywords: | multiscreen |
| Version First Reported In: | 6.1.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
drm_info console output
kscreen-doctor strace Output of `journalctl --user-unit plasma-kwin_wayland.service --boot 0` Output of: `kscreen-doctor -o` wayland-info |
||
|
Description
bugs.kde.org
2024-08-11 00:06:56 UTC
Workaround: For now I worked around that issue by unbinding the ast driver from the pcie device of the virtual monitor. `echo 0000:42:00.0 > /sys/module/ast/drivers/pci:ast/unbind` If that worked, it sounds like a kernel regression. I recommend contacting your distro or Kernel folks directly. Hi, I think there is a misunderstanding. The workaround is to remove the 2nd monitor entirely. I don't see how that would indicate a kernel module/driver issue. The devices themselves are working. At most I think this is a display server (Wayland) issue. Could you elaborate why you think this is a kernel regression by change? I'm sure others will ask the same question and I'm currently a bit confused by your assessment of the situation. Please attach the output of "kscreen-doctor -o" and drm_info 🐛🧹 ⚠️ 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! Created attachment 173146 [details]
drm_info console output
Hi,
I've tried running `kscreen-doctor -o` now multiple times over the past few days, however it appears that it just gets stuck. It doesn't output anything and never completes/returns.
I however attached at least the drm_info output for now. Please advice on how to proceed with the (also) not working kscreen-doctor.
Created attachment 173147 [details]
kscreen-doctor strace
I attached the full strace output of kscreen-doctor too. For some reason it gets stuck in an endless loop of:
```
poll([{fd=4, events=POLLIN}], 1, -1) = 1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 8) = 8
```
hmm, the drm_info output shows the virtual display being enabled as well. kscreen-doctor not working is weird... but might explain why the display settings GUI doesn't work properly either.
Maybe there's something in KWin's log, could you attach that too?
> journalctl --user-unit plasma-kwin_wayland --boot 0
ideally after trying to change some display settings
Created attachment 173292 [details]
Output of `journalctl --user-unit plasma-kwin_wayland.service --boot 0`
Created attachment 173293 [details]
Output of: `kscreen-doctor -o`
Wait a sec, `--user-unit`? So I was supposed to run the former commands as user too? Up until now I tried running kscreen-doctor as root 🤦 Tried it just now again as normal user and it worked. It only gets stuck in the endless loop when ran as root. The kscreen-doctor output is now attached together with the requested journalctl output. Sorry for that.
Yes, pretty much nothing in your session runs as root. Even with Xorg, running X11 utilities as root is only harmful. > Output of: `kscreen-doctor -o` There's definitely some inconsistent state here: kscreen-doctor says the display is off too. In the logs I see > Sep 03 23:51:14 PC-001 kwin_wayland[3797]: kwin_wayland_drm: drmPrimeFDToHandle() failed > Sep 03 23:51:14 PC-001 kwin_wayland[3797]: kwin_wayland_drm: Failed to create framebuffer: Input/output error (which is a really severe kernel driver bug, please report it!), which could explain some misbehavior - but the code keeps the display off in this case, and never turns it on, so I'm not sure what's going on yet. Please also attach the output of wayland-info, I'd like to compare it to what kscreen says as well. Created attachment 173564 [details]
wayland-info
Attaching wayland-info.
🐛🧹 ⚠️ 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! |