Plasma Starts in TTY2 After Nvidia Driver Reinstallation & TTY1 stuck

Unfortunate_Spaceman · August 1, 2023, 1:00pm

So a couple of weeks ago, I encountered an issue with the Nvidia drivers. After some investigation, I realized it’s related to this Github issue. It seems to be a more general problem, and I found out that I’m not the only one experiencing it. Anyway, while I was tinkering with the Nvidia driver and nvidia-inst, I managed to mess up my system. I switched to tty2 and reinstalled the original Nvidia driver that was causing problems. In the end, everything seemed to work fine, except for the flickering issue but i left that alone .

But, today when I tried to switch to tty2, nothing happened. Upon investigation, it turns out that after reinstalling the driver, the system started using plasma in tty2.

14:33:07 up 3:59, 3 users, load average: 1,86, 1,73, 1,92
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
user tty2 10:34 3:48m 9:41 0.08s /usr/bin/startplasma-x11

When I switch to tty1, it appears to be stuck on ‘Started Network Manager Script Dispatcher Service.’:

I’ve spent all morning trying to troubleshoot this and I’m at my wits end, any help would be greatly appreciated.

journalctl does not provide anything particularly useful

journalctl -xe
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: OpenGL version:                         3.1
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: GLSL version:                           1.40
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: X server version:                       1.21.1
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: Linux kernel version:                   6.4.6
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: Requires strict binding:                no
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: GLSL shaders:                           yes
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: Texture NPOT support:                   yes
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: Virtual Machine:                        no
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: BlurConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: ZoomConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: WindowViewConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: SlidingPopupsConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: SlideConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: OverviewConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: KscreenConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 kwin_x11[1000]: DesktopGridConfig::instance called after the first use - ignoring
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x561c424dbc20) QQmlContext(0x561c438912a0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.n>
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x561c424dbc20) QQmlContext(0x561c438912a0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.n>
aug 01 14:09:54 user-ms7a68 wireplumber[1142]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner
aug 01 14:09:54 user-ms7a68 plasmashell[3341]: Crash Annotation GraphicsCriticalError: |[0][GFX1-]: GFX: RenderThread detected a device reset in PostUpdate (t=11861.6) |[1][GFX1-]: Failed to make rende>
aug 01 14:09:54 user-ms7a68 plasmashell[3341]: Crash Annotation GraphicsCriticalError: |[0][GFX1-]: GFX: RenderThread detected a device reset in PostUpdate (t=11861.6) |[1][GFX1-]: Failed to make rende>
aug 01 14:09:54 user-ms7a68 kcminit[73881]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
aug 01 14:09:54 user-ms7a68 kcminit[73881]: Initializing  "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
aug 01 14:09:54 user-ms7a68 kcminit[73881]: kcm_touchpad: Using X11 backend
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "auto_null"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "auto_null.monitor"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:09:54 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:54 user-ms7a68 plasmashell[1065]: org.kde.plasma.pulseaudio: No object for name "alsa_input.usb-Kingston_HyperX_Virtual_Surround_Sound_00000000-00.3.analog-stereo"
aug 01 14:09:58 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:09:58 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:42 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:42 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:50 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:50 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:53 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:53 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:53 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:10:53 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:00 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:00 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:03 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:03 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:05 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:05 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:14 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:14 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:42 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:42 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:55 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:11:55 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:12:14 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:12:14 user-ms7a68 rtkit-daemon[1026]: Supervising 12 threads of 7 processes of 1 users.
aug 01 14:12:15 user-ms7a68 dbus-daemon[722]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.1130' (uid=0 pid=74465 com>
aug 01 14:12:15 user-ms7a68 dbus-daemon[722]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
aug 01 14:12:17 user-ms7a68 sudo[74465]:   user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/journalctl -xe
aug 01 14:12:17 user-ms7a68 sudo[74465]: pam_unix(sudo:session): session opened for user root(uid=0) by user(uid=1000)

*Edit
as i wrote this post i started searching for broken tty’s and i managed to get into TTY1 but it also restarted every tty as tty2 also restarted and now without the GUI and unfortunately I could not start plasma shell in TTY1

systemctl restart getty@tty1.service

ricklinux · August 1, 2023, 1:38pm

Try resetting your nvidia driver to nouveau open source and see if it will boot to the desktop.

nvidia-inst -n

Reboot and see if it reaches the desktop. Then check drivers with

inxi -Ga

Stagger_Lee · August 1, 2023, 2:56pm

EDIT - oops, this was an older bug report - I meant to post a new one, see my later post (#8) - give me a break, I hadn’t had my coffee yet .

SDDM starting on TTY2 instead of TTY1 is a known issue (I am affected by this, too, and I am using integrated Intel graphics):

github.com/sddm/sddm

Xorg is not started on first free tty (tty1)

opened 08:42PM - 21 Apr 21 UTC

GoTeamAnt

Xorg is started on tty2: ``` $ ps ax | grep Xorg 600 tty2 Ssl+ 4:25… /usr/lib/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /var/run/sddm/{5a3bbd6d-1d5e-4fbf-8438-e5c609fac15f} -noreset -displayfd 17 ``` I am running sddm 0.19.0 on Archlinux which has a patch for allocating vts. [https://github.com/sddm/sddm/commit/f0b6dec6.patch](https://github.com/sddm/sddm/commit/f0b6dec6.patch) tty1 is free: ``` $ sudo fuser /dev/tty1 $ sudo fuser /dev/tty2 /dev/tty2: 600 ``` Expected: Xorg should be started at tty1.

You can use the chvt command to get back into your graphical session:

chvt 2

Unfortunate_Spaceman · August 1, 2023, 2:56pm

I was not able to boot with the nouveau driver just as last time when i was troubleshooting the flickering.
I reinstalled again the proprietary one.

I found out when I restart the TTY2 which im currently in, then it drops me into TTY1 with plasma shell and it works fine, I just need to find out what changes upon restarting it or what makes it broken in the first place. Also when i restart TTY1 both 1 and 2 break

systemctl restart getty@tty2.service

Unfortunate_Spaceman · August 1, 2023, 3:04pm

Thanks will look into it.

Is your TTY1 “broken” as well as in the above picture I posted?

Stagger_Lee · August 1, 2023, 3:09pm

Yes, it looks like that if I remove the quiet option from my grub.

Unfortunate_Spaceman · August 1, 2023, 3:37pm

Another thing, it might relate but not sure at this point.

When booting it shows the normal “Welcome to Endeavour OS” it looks like as if it’s booting but at this point (see picture bellow) shows another “Welcome to Endeavour OS” and proceeds to normally boot

At this point I’m very much inclined to reinstalling the entire OS but then again nothing seems to be broken except TTY1 and I’ve been running with this installation for the past 3+ years

Stagger_Lee · August 1, 2023, 3:56pm

There’s a related bug report opened just today:

github.com/sddm/sddm

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

opened 07:34PM - 31 Jul 23 UTC

beermad

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:

Unfortunate_Spaceman · August 1, 2023, 3:56pm

Unbelievable
Thank you @Stagger_Lee
I read through the sddm github repo, from what i can tell 0.20 is pretty shit, i have downgraded to 0.19 and suddenly it solved my TTY issue

17:51:48 up 0 min, 2 users, load average: 3,09, 0,85, 0,29
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
user tty1 17:51 38.00s 1.95s 0.08s /usr/bin/startplasma-x11
user pts/0 17:51 2.00s 0.00s ? w

ricklinux · August 1, 2023, 4:32pm

Is this just an X11 issue with SDDM because i am running an Nvidia GTX 1060 on KDE with Wayland and i don’t have any issue?

Edit:
Nor do i have an issue on X11 i don’t think or is it related to the actual Nvidia card?

Stagger_Lee · August 1, 2023, 4:35pm

I don’t use Wayland, so I don’t know and I don’t really care.

However, note that the bug report specifically references X server.

I also don’t use Nvidia yet I have the issue.

It’s not a big deal. If I drop to a TTY, I can get back to the graphical session on TTY2 by using the chvt command. So I haven’t been following this closely.

ricklinux · August 1, 2023, 4:40pm

I was just wondering because i also have it running on amdgpu with Wayland on KDE and i don’t seem to have any issue either. I never thought i would ever run Wayland but so far I’m happier with it than previously.
Thanks.

system · August 3, 2023, 4:40pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.