Summary: | Plasma 5.26 completely breaks my multi-monitor setup | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Stefan Radermacher <kde> |
Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hajit.00, mrmazda, nicolas.fella |
Priority: | NOR | ||
Version: | 5.26.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Stefan Radermacher
2022-10-16 07:50:39 UTC
Additional info: I've tried this with a separate, new user account, the effects are the same. Similar situation here. Primary 2K monitor via DP, and FHD monitor via HDMI. After updating to Plasma 5.26 2K monitor is disabled. Enabling it in Display Configuration does nothing. I can enable it only in NVidia-Settings. and it works until I power off monitor, after power on it again disabled. *** This bug has been marked as a duplicate of bug 450068 *** I'm not sure that this is really a duplicate of bug 450068. That bug already occurs in Plasma 5.24, but my problem is new with 5.26, previously this catastrophic failure did not occur. It really doesn't matter whether this is dup'd to bug 450068 or bug 385135 or some other "multi-screen support" bug. The fix for 450068 when it arrives will be fixing multiple bugs that were made worse, or were unhelped by, or were new in, 5.26. In the mean time, disable automatic KScreen2 startup and manage displays with xrandr/arandr as best suits your own setup, if X automagic display management doesn't work well enough on its own without KScreen2 interference. (In reply to Felix Miata from comment #5) > It really doesn't matter whether this is dup'd to bug 450068 or bug 385135 > or some other "multi-screen support" bug. The fix for 450068 when it arrives > will be fixing multiple bugs that were made worse, or were unhelped by, or > were new in, 5.26. In the mean time, disable automatic KScreen2 startup and > manage displays with xrandr/arandr as best suits your own setup, if X > automagic display management doesn't work well enough on its own without > KScreen2 interference. How would I best “disable automatic KScreen2 startup”? > (In reply to Felix Miata from comment #5)
> How would I best “disable automatic KScreen2 startup”?
Never mind, I found it.
|