Bug 462725 - [NVIDIA, X11] When external monitor is plugged in at boot and have different frame rate icons and fronts are missing Plasma
Summary: [NVIDIA, X11] When external monitor is plugged in at boot and have different ...
Status: RESOLVED FIXED
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.25.90
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 464892 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-12-06 21:00 UTC by shinjii
Modified: 2023-03-10 10:26 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.27.2


Attachments
Screen of desktop (2.10 MB, image/png)
2022-12-06 21:00 UTC, shinjii
Details
HDMI Connected before login (2.15 MB, video/mp4)
2023-01-05 11:14 UTC, shinjii
Details
HDMI DISCONNECTED before login (3.13 MB, video/mp4)
2023-01-05 11:15 UTC, shinjii
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shinjii 2022-12-06 21:00:53 UTC
Created attachment 154376 [details]
Screen of desktop

STEPS TO REPRODUCE
1. Just upgraded from Fedora 36 to Fedora 37

OBSERVED RESULT
KDE on X11 is damaged... i can't use it anymore... it looks like on the screen - no icons, no fonts in settings/programs etc, can't use mouse right button, green bar at the bottom without icons etc.
BUT Kde on Wayland is working fine... except broken screen refresh rate (on X11 refresh rate working fine!!!... lol) - I wrote about this bug here https://bugs.kde.org/show_bug.cgi?id=462551

EXPECTED RESULT
Should everything working like before upgrade :D 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 37
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Comment 1 Nate Graham 2022-12-07 20:24:06 UTC
What GPU hardware are you using?

Do icons show up in Dolphin? Can you right-click in Dolphin?
Comment 2 shinjii 2022-12-08 19:51:55 UTC
(In reply to Nate Graham from comment #1)
> What GPU hardware are you using?
> 
> Do icons show up in Dolphin? Can you right-click in Dolphin?

1. Nvidia GTX 1660Ti (notebook) with nvidia drivers 520.56.06
2. Hmmm... weird but when I was writing this subject there wasn't icons anywhere... on dolphin, on system settings etc. but now I checked and there was icons and I can right-click in Dolphin.
But still menu is without icons, can't see "logout menu", desktop without icons, when right-click on desktop there isn't menu and just it select all desktop (like when you left-click and move mouse), green bottom bar etc.
Comment 3 Nate Graham 2022-12-09 01:14:11 UTC
Did you happen to upgrade your NVIDIA drivers during the process? If you revert to an older version of the drivers, does the problem go away?
Comment 4 shinjii 2022-12-09 09:44:47 UTC
(In reply to Nate Graham from comment #3)
> Did you happen to upgrade your NVIDIA drivers during the process? If you
> revert to an older version of the drivers, does the problem go away?

I guess it could be updated but I don't know man :D there was ~3000 packages upgraded because it was move from F36 to F37.... I don't know what version was before upgrade to F37, 99% it was also 520.xx.xx
Comment 5 shinjii 2022-12-12 12:36:18 UTC
Alright I found it!!
It's broken if I have a second screen connected before logging into KDE, if it's disconnected KDE loads normally then I can connect a second screen and everything works.... but it's very annoying because you have to remember about it disconnect/connect second screen before logging into KDE.
Comment 6 Nate Graham 2022-12-14 22:26:20 UTC
This definitely seems like an NVIDIA issue. Please report this issue to the NVIDIA folks, either by sending an email to linux-bugs@nvidia.com or making a post at https://forums.developer.nvidia.com/c/gpu-graphics/linux/

It would be helpful to the NVIDIA developers if you could run nvidia-bug-report.sh and attach the resulting file in your report. Thanks!
Comment 7 shinjii 2022-12-15 14:03:51 UTC
(In reply to Nate Graham from comment #6)
> This definitely seems like an NVIDIA issue. Please report this issue to the
> NVIDIA folks, either by sending an email to linux-bugs@nvidia.com or making
> a post at https://forums.developer.nvidia.com/c/gpu-graphics/linux/
> 
> It would be helpful to the NVIDIA developers if you could run
> nvidia-bug-report.sh and attach the resulting file in your report. Thanks!

No it's not that.
I uninstalled nvidia official drivers and since 2-3 days have just Nouveau... situation from https://bugs.kde.org/show_bug.cgi?id=462551 is now working good... but X11 still is damaged while second screen connected.
In Fedora 36 was everything fine....
Comment 8 Nate Graham 2022-12-15 19:08:49 UTC
Can you clarify which exact things are still broken for you, on which screen, in which apps?
Comment 9 shinjii 2022-12-15 20:50:40 UTC
(In reply to Nate Graham from comment #8)
> Can you clarify which exact things are still broken for you, on which
> screen, in which apps?

It looks like on screen from my first comment (on main screen, not second).
1. When I try right-click on desktop it select all desktop and everything dissappear
2. When I try to click on "start menu" (there where it should be, on screen as you can see there's nothing) there's no fonts, just icons
3. I can't see any system icons on bottom bar
etc.

But like I said in previous comments - suddenly Dolphin works fine lol.
Comment 10 Nate Graham 2022-12-23 21:53:18 UTC
Any chance I could ask you to take a screen recording that shows these things happening?
Comment 11 shinjii 2023-01-02 11:52:38 UTC
(In reply to Nate Graham from comment #10)
> Any chance I could ask you to take a screen recording that shows these
> things happening?

I changed laptop few days ago but with the same disk and system (from earlier laptop) - I'm waiting now for display port -> usb-c cabel and I'll let you know if this still exists! 
Because now I have again Nvidia drivers but newer card - Nvidia RTX 3060, maybe something's different, will see...
Comment 12 shinjii 2023-01-02 14:53:07 UTC
(In reply to Nate Graham from comment #10)
> Any chance I could ask you to take a screen recording that shows these
> things happening?

Ok I recored video, where send it to you? It's over 400mb....
Comment 13 Nate Graham 2023-01-02 20:49:21 UTC
You'll need to compress it using a more efficient video codec. Reducing the resolution would help too. If it still doesn't fit in the 4Mb size limit, you could upload it using Dropbox or a file sharing site.
Comment 14 shinjii 2023-01-05 11:14:12 UTC
(In reply to Nate Graham from comment #13)
> You'll need to compress it using a more efficient video codec. Reducing the
> resolution would help too. If it still doesn't fit in the 4Mb size limit,
> you could upload it using Dropbox or a file sharing site.

Ok I attached 2 videos.
1. Is when HDMI/Display-port is connected BEFORE login to KDE (X11)
2. Is when HDMI/display-port is diconnected BEFORE LOGIN but I connected it successfully after login and everything is working fine.

To be clear:
Now it's SECOND NOTEBOOK but with the same disk and system (from this first notebook), earlier (when I started this bug) it was intel i7-10750h and Intel GPU + Nvidia GTX 1660Ti, now it's AMD Ryzen 7 6800H with AMD GPU + Nvidia RTX 3060.
Earlier I had official drivers from nvidia, but then I uninstalled them and it didn't work even on noveau, now I have again nvida official drivers and it's still not working... 
Now when I was recording videos settings are:
Nvidia Drivers: 525.60.11
Server version number: 11.0
Server vendor version: 1.20.14 (12014000)
KDE: 5.26.4
Kernel: 6.1.3 ROG Edition (from asus-linux.org, on earlier notebook it was just from Fedora 37 6.0.x)
Comment 15 shinjii 2023-01-05 11:14:47 UTC
Created attachment 155054 [details]
HDMI Connected before login
Comment 16 shinjii 2023-01-05 11:15:17 UTC
Created attachment 155055 [details]
HDMI DISCONNECTED before login
Comment 17 Nate Graham 2023-01-05 17:32:35 UTC
Thanks. Super weird.
Comment 18 Dmitrii Chermnykh 2023-01-05 18:22:24 UTC
The problem probably has something to do with PRIME or Reverse PRIME which is not really stable on NVIDIA. 

Do you use the NVIDIA driver from the repositories or the package provided by NVIDIA on their website? 
The one from NVIDIA might not be compatible with the distribution and cause some problems.
For Hybrid GPUs distros typically enable `nvidia-drm.modeset=1` which used to be turned of by default for the drivers, I don't know if they decided to turn it on. 

There are also two possibilities for AMD driver: `amdgpu` X11 driver and `modesetting` driver which is the universal one that relies on the kernel driver. From my experience, `modesetting` seems to have less problems with hybrid GPUs (I'm using Ryzen 5700H + Nvidia 3050 Ti Mobile)

I think I had something similar on older laptop but I've managed to fix it with reinstalling drivers and resetting X11 configs, but I don't remember which graphical artifacts I've encountered
Comment 19 shinjii 2023-01-05 18:34:55 UTC
(In reply to Dmitrii Chermnykh from comment #18)
> The problem probably has something to do with PRIME or Reverse PRIME which
> is not really stable on NVIDIA. 
> 
> Do you use the NVIDIA driver from the repositories or the package provided
> by NVIDIA on their website? 
> The one from NVIDIA might not be compatible with the distribution and cause
> some problems.
> For Hybrid GPUs distros typically enable `nvidia-drm.modeset=1` which used
> to be turned of by default for the drivers, I don't know if they decided to
> turn it on. 
> 
> There are also two possibilities for AMD driver: `amdgpu` X11 driver and
> `modesetting` driver which is the universal one that relies on the kernel
> driver. From my experience, `modesetting` seems to have less problems with
> hybrid GPUs (I'm using Ryzen 5700H + Nvidia 3050 Ti Mobile)
> 
> I think I had something similar on older laptop but I've managed to fix it
> with reinstalling drivers and resetting X11 configs, but I don't remember
> which graphical artifacts I've encountered

Hi,
But it started happening after upgrade Fedora 36 to 37...it was working earlier....  and weird is that it works when HDMI is disconnected BEFORE login, after login when I connect it it's working - isn't it weird? :D
I'm using nvidia drivers from repository.
That option nvidia-drm.modeset=1 i have also =1 :P 
I reinstalled today many drivers and nothing helped... how to reset X11 config? but if I good remember I don't have much in .config file.
Comment 20 Dmitrii Chermnykh 2023-01-05 19:15:47 UTC
(In reply to shinjii from comment #19)
> (In reply to Dmitrii Chermnykh from comment #18)
> > The problem probably has something to do with PRIME or Reverse PRIME which
> > is not really stable on NVIDIA. 
> > 
> > Do you use the NVIDIA driver from the repositories or the package provided
> > by NVIDIA on their website? 
> > The one from NVIDIA might not be compatible with the distribution and cause
> > some problems.
> > For Hybrid GPUs distros typically enable `nvidia-drm.modeset=1` which used
> > to be turned of by default for the drivers, I don't know if they decided to
> > turn it on. 
> > 
> > There are also two possibilities for AMD driver: `amdgpu` X11 driver and
> > `modesetting` driver which is the universal one that relies on the kernel
> > driver. From my experience, `modesetting` seems to have less problems with
> > hybrid GPUs (I'm using Ryzen 5700H + Nvidia 3050 Ti Mobile)
> > 
> > I think I had something similar on older laptop but I've managed to fix it
> > with reinstalling drivers and resetting X11 configs, but I don't remember
> > which graphical artifacts I've encountered
> 
> Hi,
> But it started happening after upgrade Fedora 36 to 37...it was working
> earlier....  and weird is that it works when HDMI is disconnected BEFORE
> login, after login when I connect it it's working - isn't it weird? :D
> I'm using nvidia drivers from repository.
> That option nvidia-drm.modeset=1 i have also =1 :P 
> I reinstalled today many drivers and nothing helped... how to reset X11
> config? but if I good remember I don't have much in .config file.

The X11 user configuration is located in `/etc/X11/xorg.conf` and `/etc/X11/xorg.conf.d` 
If you're using the distribution default configuration the `/etc/X11/xorg.conf` is probably empty and the `/etc/X11/xorg.conf.d` should probably contain only locale configuration 
Distribution defaults are typically located in `/usr/share/X11/xorg.conf.d/` folder
For archlinux when I encounter some weird bugs on NVIDIA, I usually switch to amd-only or nvidia-only mode (with optimus manager) to check if the issues reappear. I don't know if there is an alternative to optimus-manager for fedora. 

Does the problem only occurs with kde apps or in some other apps as well (e.g. in chromium or some games)?
Comment 21 shinjii 2023-01-05 19:22:04 UTC
(In reply to Dmitrii Chermnykh from comment #20)
> (In reply to shinjii from comment #19)
> > (In reply to Dmitrii Chermnykh from comment #18)
> > > The problem probably has something to do with PRIME or Reverse PRIME which
> > > is not really stable on NVIDIA. 
> > > 
> > > Do you use the NVIDIA driver from the repositories or the package provided
> > > by NVIDIA on their website? 
> > > The one from NVIDIA might not be compatible with the distribution and cause
> > > some problems.
> > > For Hybrid GPUs distros typically enable `nvidia-drm.modeset=1` which used
> > > to be turned of by default for the drivers, I don't know if they decided to
> > > turn it on. 
> > > 
> > > There are also two possibilities for AMD driver: `amdgpu` X11 driver and
> > > `modesetting` driver which is the universal one that relies on the kernel
> > > driver. From my experience, `modesetting` seems to have less problems with
> > > hybrid GPUs (I'm using Ryzen 5700H + Nvidia 3050 Ti Mobile)
> > > 
> > > I think I had something similar on older laptop but I've managed to fix it
> > > with reinstalling drivers and resetting X11 configs, but I don't remember
> > > which graphical artifacts I've encountered
> > 
> > Hi,
> > But it started happening after upgrade Fedora 36 to 37...it was working
> > earlier....  and weird is that it works when HDMI is disconnected BEFORE
> > login, after login when I connect it it's working - isn't it weird? :D
> > I'm using nvidia drivers from repository.
> > That option nvidia-drm.modeset=1 i have also =1 :P 
> > I reinstalled today many drivers and nothing helped... how to reset X11
> > config? but if I good remember I don't have much in .config file.
> 
> The X11 user configuration is located in `/etc/X11/xorg.conf` and
> `/etc/X11/xorg.conf.d` 
> If you're using the distribution default configuration the
> `/etc/X11/xorg.conf` is probably empty and the `/etc/X11/xorg.conf.d` should
> probably contain only locale configuration 
> Distribution defaults are typically located in `/usr/share/X11/xorg.conf.d/`
> folder
> For archlinux when I encounter some weird bugs on NVIDIA, I usually switch
> to amd-only or nvidia-only mode (with optimus manager) to check if the
> issues reappear. I don't know if there is an alternative to optimus-manager
> for fedora. 
> 
> Does the problem only occurs with kde apps or in some other apps as well
> (e.g. in chromium or some games)?

I have "optimus manager" here and... changed it from Hybrid to Integrated card (AMD) and then HDMI and displayport didn't work lol so I guess hybrid mode is fine... 
The most important thing is that happening only on X11... on Wayland it's working fine :P 
What about apps? hmmm.... I don't know, maybe they are working because as you can see on my videos in attachments that dolphin is working fine, simple screen recorder also.... it looks like just broken desktop with icons and bottom bar...
Comment 22 Dmitrii Chermnykh 2023-01-06 12:11:05 UTC
(In reply to shinjii from comment #21)

> I have "optimus manager" here and... changed it from Hybrid to Integrated
> card (AMD) and then HDMI and displayport didn't work lol so I guess hybrid
> mode is fine... 

Could you check if the problem appears "nvidia only" mode (the mode when the apps are rendered by nvidia and the integrated screen just draws the image from nvidia's framebuffer)? 

> The most important thing is that happening only on X11... on Wayland it's
> working fine :P 

Seems like it's X11 driver problem, not the kernel drivers and probably not a plasma bug

Are you using `modesetting` or `amdgpu` driver for x11? 

Do you have nouveau installed together with the nvidia driver?
Comment 23 shinjii 2023-01-06 17:52:30 UTC
(In reply to Dmitrii Chermnykh from comment #22)
> (In reply to shinjii from comment #21)
> 
> > I have "optimus manager" here and... changed it from Hybrid to Integrated
> > card (AMD) and then HDMI and displayport didn't work lol so I guess hybrid
> > mode is fine... 
> 
> Could you check if the problem appears "nvidia only" mode (the mode when the
> apps are rendered by nvidia and the integrated screen just draws the image
> from nvidia's framebuffer)? 
> 
> > The most important thing is that happening only on X11... on Wayland it's
> > working fine :P 
> 
> Seems like it's X11 driver problem, not the kernel drivers and probably not
> a plasma bug
> 
> Are you using `modesetting` or `amdgpu` driver for x11? 
> 
> Do you have nouveau installed together with the nvidia driver?

I'll check mode only Nvidia someday, but not today.
I don't know what I'm using in X11 how to check it (amdgpu/modesetting) ? Remember that I had earlier intel not amd so I guess it's not about amdgpu :D 
I have that package nouveau:
xorg-x11-drv-nouveau.x86_64 - 1:1.0.17-4.fc37
Comment 24 josh 2023-01-12 14:00:02 UTC
I haven't tried rebooting with my external monitor disconnected yet, but I'm having the same problem after upgrading to F37.  It only happens when running an X11 session - I don't have the problem when running a Wayland session, but I also cannot get the external monitor to be recognized either (NVIDIA -> HDMI).  My Google searches turned up a suggestion that the solution was to downgrade kscreen and libkscreen to 5.25, but that's not an option in F37.  But maybe that gives a hint about where to look?  I'll try rebooting without the monitor connected and see if that fixes things temporarily, but it's not really a good long-term solution.
Comment 25 josh 2023-01-12 14:07:08 UTC
OK, I rebooted without the monitor connected, then connected it before I logged in and the icons were still missing.  I logged out and disconnected the monitor, then logged in without the monitor connected and the icons were back.  Connecting the monitor worked fine and I still have my icons, so it's something about having the monitor connected when starting the KDE session that's making things break.
Comment 26 shinjii 2023-01-12 15:23:04 UTC
(In reply to josh from comment #25)
> OK, I rebooted without the monitor connected, then connected it before I
> logged in and the icons were still missing.  I logged out and disconnected
> the monitor, then logged in without the monitor connected and the icons were
> back.  Connecting the monitor worked fine and I still have my icons, so it's
> something about having the monitor connected when starting the KDE session
> that's making things break.

uffff....finally someone with exactly the same problem like me :P
Comment 27 shinjii 2023-01-13 10:11:07 UTC
But today I checked it again (after some updates of Plasma etc.) and I have new chapter :D
When second screen connected before login - again everything like on my earlier videos.... but... when I logout and disconnect hdmi, after login and reconnecting hdmi there's no signal lol 
Ofcourse on Wayland there is signal.
Comment 28 Aspidov Sergei 2023-02-01 19:19:59 UTC
I encountered this error as early as last year in November 2022~
This error was on Manjaro Linux Stable  \  Arch Linux 
This error appears only on laptops with nvidia + intel graphics in Plasma x11 sesion any actual kernel 

I Use:
video-hybrid-intel-nvidia-prime 
nvidia-utils 525.60.11-2
kscreen and libkscreen to 5.25.1<=
KDE Plasma 5.26.4
KDE FW 5.101.0
QT 5.15.7
Kernel 5.15.85-1 Manjaro
X11

Same trouble
https://forum.manjaro.org/t/panel-icons-disappears-after-hovering/132997/4
https://forum.manjaro.org/t/all-desktop-and-menu-icons-missing/125832
https://forum.manjaro.org/t/icons-missing-wrong-fonts-unresponsive-plasma-after-update/127958
https://forum.manjaro.org/t/system-hangs-out-freezes-on-external-monitor-after-last-update/129926/20
https://bbs.archlinux.org/viewtopic.php?id=280535

Temporary solution: 
1. Disconnect the external monitor which is connected via type C or set the same refresh rate main and external monitor
2. Downgrade kscreen and libkscreen to 5.25.5<= and ignore updatre
3. When your log on in plasma, try to upload new desktop wallper, after refresh all to be normal ( after logout, need do it again )
4. Install optimums manager and use only intel or nvidia driver.

5. Not all situation - GRUB_CMDLINE_LINUX_DEFAULT dd this parameter ibt=off
Comment 29 Aspidov Sergei 2023-02-02 08:58:28 UTC
This problem only occurs on 
1. Laptop
2. On which an external display is connected
3. In KDE only x11 
4. With intel + nvidia hybrid GPU\driver installed 
5. kscreen and libkscreen =>5.25.90
6. Primary and secondary monitor refresh rates do not match. 

Fix way:
1. Go to system settings \display and monitor \ set same Refresh rate to all monitor
2. Downgrade kscreen and libkscreen to 5.25.5<= and ignore update
3. install optimus-manager and switch gpu to nvidia \ intel only
4. When your log on in plasma, try to upload new desktop wallper, after refresh all to be normal ( after logout, need do it again ) YES  WHY!!!!
Comment 30 stasadev 2023-02-17 14:46:23 UTC
I also have the same problem. Today I tried to do a git bisect for kscreen and libkscreen and luckily found the culprit.

This is a libkscreen commit https://invent.kde.org/plasma/libkscreen/-/commit/18b8f22c0f31c05d067f8231bce54153808fed6f which first appeared in v5.25.90.

I reverted this commit, and tested the changes in v5.26.5 and v5.27.0. The external monitor works as expected.
Comment 31 Nate Graham 2023-02-17 19:00:33 UTC
Nice find! I wonder if that also caused Bug 460341.
Comment 32 stasadev 2023-02-17 20:47:12 UTC
(In reply to Nate Graham from comment #31)
> Nice find! I wonder if that also caused Bug 460341.

It can actually be related.

I don't have that problem on my laptop (my screen is connected via HDMI), but I have another PC with two monitors (HDMI + DisplayPort) where the monitor connected via DP is lost from time to time.

I don't have a problem with wakeup (since I don't use it), but I found something consistent (checked it a few times to make sure):

1. boot Plasma v5.26.5 with DP disabled, then enable DP => no image, I need to enable the monitor in System Settings.
2. boot Plasma v5.26.5 (+ patch rollback) with DP disabled, then enable DP => the monitor works.
Comment 33 Bug Janitor Service 2023-02-25 02:38:12 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/libkscreen/-/merge_requests/107
Comment 34 ratijas 2023-02-25 16:22:08 UTC
Git commit 1d237c29655c7e3fb15fb9b71e5f167bd207593f by ivan tkachenko.
Committed on 25/02/2023 at 15:15.
Pushed by ratijas into branch 'master'.

Revert "fix(randr): screen is dirty when switching display modes"

This reverts commit 18b8f22c0f31c05d067f8231bce54153808fed6f.

It has caused a regression on NVIDIA, that makes all screens go black
and only the cursor remains.
FIXED-IN: 5.27.2

M  +26   -21   backends/xrandr/xrandrconfig.cpp

https://invent.kde.org/plasma/libkscreen/commit/1d237c29655c7e3fb15fb9b71e5f167bd207593f
Comment 35 ratijas 2023-02-25 16:23:23 UTC
Git commit b274575c23a7cccb1482da4e680826f2b9823e71 by ivan tkachenko.
Committed on 25/02/2023 at 16:23.
Pushed by ratijas into branch 'Plasma/5.27'.

Revert "fix(randr): screen is dirty when switching display modes"

This reverts commit 18b8f22c0f31c05d067f8231bce54153808fed6f.

It has caused a regression on NVIDIA, that makes all screens go black
and only the cursor remains.
FIXED-IN: 5.27.2
(cherry picked from commit 1d237c29655c7e3fb15fb9b71e5f167bd207593f)

M  +26   -21   backends/xrandr/xrandrconfig.cpp

https://invent.kde.org/plasma/libkscreen/commit/b274575c23a7cccb1482da4e680826f2b9823e71
Comment 36 shinjii 2023-02-27 14:22:09 UTC
(In reply to ratijas from comment #35)
> Git commit b274575c23a7cccb1482da4e680826f2b9823e71 by ivan tkachenko.
> Committed on 25/02/2023 at 16:23.
> Pushed by ratijas into branch 'Plasma/5.27'.
> 
> Revert "fix(randr): screen is dirty when switching display modes"
> 
> This reverts commit 18b8f22c0f31c05d067f8231bce54153808fed6f.
> 
> It has caused a regression on NVIDIA, that makes all screens go black
> and only the cursor remains.
> FIXED-IN: 5.27.2
> (cherry picked from commit 1d237c29655c7e3fb15fb9b71e5f167bd207593f)
> 
> M  +26   -21   backends/xrandr/xrandrconfig.cpp
> 
> https://invent.kde.org/plasma/libkscreen/commit/
> b274575c23a7cccb1482da4e680826f2b9823e71

So it's not working on 5.27.1 ? Because I can now log-in to X11 and icons etc. are fine but screen is now flickering like old 90s/00s monitors lol
Comment 37 Nate Graham 2023-02-27 14:24:17 UTC
The fix is in 5.27.2.
Comment 38 shinjii 2023-02-27 14:25:53 UTC
(In reply to Nate Graham from comment #37)
> The fix is in 5.27.2.

Ok, we'll see after fedora will upgrade repository:)
Comment 39 Kenny Hui 2023-03-04 09:56:28 UTC
*** Bug 464892 has been marked as a duplicate of this bug. ***
Comment 40 shinjii 2023-03-10 10:26:08 UTC
I can confirm it's now working! :)