I recently updated to Nvidia driver 555.58.02
as I use Kdenlive and for some reason couldn’t create proxies using NVENC 264/265 (this fixed things (:).
Ever since the on-release update to plasma 6, I have been using X11 exclusively (with major issues like being forced to run both displays on the same frequency or facing a massive loss of performance and lags) because wayland froze / crashed my system a couple times and made things look really weird (e.g. the firefox task bar icon would turn into a ‘W’).
Yesterday, I tried changing my screen layout on my dual (identical) monitor setup from ‘extend to right’ to anything else, but nothing would happen.
In the past, usually the monitors would briefly turn off and when I got lucky, turn back on in the proper order (even this often didn’t work as it switched up my SET primary monitor, e.g. ‘extend to right’ would turn into ‘extend to left’). Now literally nothing happens.
This is true for both the system icon in the system tray as well as the shortcut Meta+P. No modes work, I am stuck having to use both monitors or gotta manually adjust everything in the display config.
When logging out, trying to switch to Wayland, this unfortunately doesn’t get fixed.
After multiple different solution attempts involving restarting or entirely shutting down the system, this still wouldn’t fix itself.
I made an apt, a pkcon and a full Discover / shop update, tried everything again to no avail.
I tried an apt install --reinstall kscreen, to no avail.
What am I missing?
And more importantly, how can I fix this?
555 seems to have some issues. Regress back to 550.
Switch to nouveau and reboot into it (use the software-properties-qt app), purge the nvidia subsystem (sudo apt-get --purge nvidia*), run apt-get clean and apt-get autoremove, reboot and reinstall the driver.
i just downgraded to 550.107.02, same issue when i use either wayland or x11 via logout screen switch.
on 555 i also got extremely frequent crashes (random crashes) since i made this post, often in the middle of me just clicking around. i hope at least those will be gone
In Ksettings try to turn off (disable) the non-primary monitor and reboot the system. After relogging in, try to enable it again. On occasion, there appears to be a 3rd “ghost” display associated with the ksettins display app. This might force it to go away.
Basically what I think is happening is the “virtual screen” (your desktop is actually virtual) that is created when you attach a second monitor is causing Ksettings to think there are 3 displays when there are only two.
It got itself really corrupted in X11 after doing a testing session in Wayland last night. Seems installing drivers in Wayland is a bad idea. It was the first time I did it. Everything seemed fine. Rebooted back into Wayland nicely after updating the driver from 550 to 555, did some tests (550 does not work well with Wine/Proton in Wayland). When I then went to compare the results in X11 it crashed the desktop hard, and the desktop, while partially usable was badly corrupted, even after reboots. What is weird is I has been using and testing 555 before with no issues.
Trying to purge it bricked the system so badly it took me until 2:30 this afternoon to figure out. For a while it was looking like I had bricked it so badly I might have to actually re-install Neon from scratch. I could not even get it to boot to the command line. I had to boot into Kubuntu to fix Neon.
The take away from this seems to be that certain drivers work OK with X but not Wayland, and other drivers work with Wayland but not X. And my computer DOES NOT like switching between X and Wayland.
this didnt fix it unfortunately. in fact, somehow both monitors were mirrored on login screen after disabling one monitor & restarting but the disabled monitor turned off right after login, the third/virtual “none” display still exists and the issue persists
but the disabled monitor turned off right after login, the third/virtual “none” display still exists and the issue persists