Comment 26 for bug 2031198

Revision history for this message
Bruce Goodwin (bgoodwin) wrote : Re: Boots to black after upgrade to 22.04, Cannot use other TTY interfaces either (ctrl+alt+f2, etc)

The apport updates above were dumped on boot after removing all nvidia packages (`apt remove --purge '*nvidia*'` and `apt autoremove`) thus attempting to use the nouveau driver. The laptop booted directly to a black screen with the backlight on, and I immediately ssh-ed in and collected logs with `apport-collect`

Then i wanted to see if I'm actually able to login in this state, but the user X session is merely invisible with the procedrue:

1: Check for the login screen's session:
```
publius@voldemort:~$ loginctl list-sessions
SESSION UID USER SEAT TTY
      2 1000 publius pts/0
     c1 128 gdm seat0 tty1

2 sessions listed.
publius@voldemort:~$ loginctl show-session c1
Id=c1
User=128
Name=gdm
Timestamp=Thu 2023-08-17 18:17:43 EDT
TimestampMonotonic=14305206
VTNr=1
Seat=seat0
TTY=tty1
Remote=no
Service=gdm-launch-environment
Scope=session-c1.scope
Leader=1083
Audit=4294967295
Type=wayland
Class=greeter
Active=yes
State=active
IdleHint=yes
IdleSinceHint=1692310965050340
IdleSinceHintMonotonic=316001633
LockedHint=no
```

2: Attempted the "pretend there's a login screen that i just can't see" workaround (Comment#5).

3: Then look to see if the sessions have changed
```
publius@voldemort:~$ loginctl list-sessions
SESSION UID USER SEAT TTY
      2 1000 publius pts/0
      4 1000 publius seat0 tty2

2 sessions listed.
publius@voldemort:~$ loginctl show-session 4
Id=4
User=1000
Name=publius
Timestamp=Thu 2023-08-17 18:24:30 EDT
TimestampMonotonic=421274657
VTNr=2
Seat=seat0
TTY=tty2
Remote=no
Service=gdm-password
Scope=session-4.scope
Leader=1800
Audit=4
Type=wayland
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
LockedHint=no
```

So it looks like yes,
* There is an invisible login screen present
* I can log in at that screen
* the login screen's wayland session (owner `gdm`) is replaced with the user's (owner `publius`) wayland session.
* And neither session can put graphics on the monitor - In the complete absense of nvidia packages/drivers/kernel modules.