Plasma Starts in TTY2 After Nvidia Driver Reinstallation & TTY1 stuck

Stagger_Lee · August 1, 2023, 3:56pm

There’s a related bug report opened just today:

SDDM 0.20 uses random TTY, breaks autostart programs needing X server

opened 07:34PM - 31 Jul 23 UTC

Since upgrading to SDDM 20.0, my X server no longer starts reliably on TTY1, ins…tead it seems to be fairly random, though it _usually_ opens on TTY2. In principle this shouldn't be a problem in itself, but unfortunately it has very problematic side-effects. I have a number of programs which I launch via KDE autostart options. Some of these need to open GUI windows (things like Firefox & Thunderbird, for example). Other users on Reddit and the Manjaro forum also report that cron jobs and/or systemd timers which should open GUI windows are failing. All failures are accompanied by the following messages: ``` Invalid MIT-MAGIC-COOKIE-1 key Cannot open display ":0.0" ``` [Edit]: the magic cookie message may be a red herring. But "Cannot open display" is the important message". Non-startup jobs can be fixed by issuing: `xhost +` Startup jobs _will_ work OK if I log out then log back in again, so it seems the problem is that somehow the change of TTY is causing an INITIAL problem opening the X display. I suspect other people's problem with cron/systemd jobs would also get fixed by that. I have downgraded SDDM to the 0.19 and this has solved my problems, which proves the new version to be responsible.

There are also users reporting this issue on the Manjaro forums (I don’t use Manjaro, but I visit their forums occasionally). For example: