Black screen after login GNOME

Walnut

I had my laptop freeze up and after a hard reboot I have a black screen now after login.
I am able to log into TTY and have tried the following.
sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
This reinstalled linux-firmware and noto-sans-ttf
I have also run
sudo usysconf run -f
sudo eopkg rdb
sudo eopkg up
System is up to date with no packages to upgrade.

After restarting the issue is still persisting.
Laptop is Core i7-5500U
Kernel: 5.14.15-203.current
Intel HD Graphics 5500 driver i915
GNOME desktop environment
I'm lost on where to go from here, any assistance would be greatly appreciated.

algent

Walnut Is this a fresh install, or you did the update and then you had black screen after login.

Walnut

algent Not a fresh install, been running without fault for 24 months. Was streaming a netflix show when video froze and it became unresponsive, after restart everything looked normal and it loaded up to login screen, after entering password screen stays black. Laptop was normally updated weekly but I almost never power it down or restart it, once maybe twice a year.

algent

Walnut If last updated isn't working for you, I guess you have to try to rollback before this update. Maybe it is a problem with latest kernel.

Walnut

algent I'll give that a try

Walnut

algent Rolling back with sudo eopkg history -t 237 has not worked, took it back to Oct 25th but problem still there.

pomon

Did you connect any monitor/TV while streaming?

Walnut

pomon No monitor / TV used.

algent

Walnut I don't know what this problem could be. Another thing worth trying is to boot from a flashed USB drive with Solus or whatever linux in it too see if boots or not.

Walnut

algent Solus Budgie USB has booted straight up with fully working DE. Netflix streaming without issue.

Walnut

pomon gnome -session throws no arguments but does nothing
walnut@walnut ~ $ gnome-session
walnut@walnut ~ $

walnut@walnut ~ $ systemctl status gdm
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2021-11-04 09:01:06 AEDT; 22h ago
Main PID: 3322 (gdm)
Tasks: 7 (limit: 9369)
Memory: 4.8M
CPU: 109ms
CGroup: /system.slice/gdm.service
├─ 679 /usr/sbin/gdm
└─1671 /usr/bin/gnome-keyring-daemon --daemonize --login

Using sudo adds the following:
Nov 04 09:01:06 walnut systemd[1]: Starting GNOME Display Manager...
Nov 04 09:01:06 walnut systemd[1]: Started GNOME Display Manager.
Nov 04 09:01:15 walnut gdm-password][3587]: gkr-pam: unable to locate daemon control file
Nov 04 09:01:15 walnut gdm-password][3587]: gkr-pam: stashed password to try later in open session
Nov 04 09:01:15 walnut gdm-password][3587]: pam_unix(gdm-password:session): session opened for user walnut by (uid=0)
Nov 04 09:01:15 walnut gdm-password][3587]: gkr-pam: unable to locate daemon control file
Nov 04 09:01:15 walnut gdm-password][3587]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

Checking against my gnome desktop with eopkg li | grep gnome the following are missing from the laptop.

libgnome - This is the non-gui part of the library formerly known as gnome-libs.
libgnomecanvas2 - The libgnomecanvas package contains the GNOME canvas library.
libgnomeui - User Interface library for GNOME

I have installed them restarted and still no DE.

I thnk it might be time to back up the home folder and give budgie a try, after all, who wants to use gnome these days 🙂
Thank you pomon algent brent for trying to work through this with me.

algent

Walnut That is good news, it means no hardware issues. Are you sure when you rolled back the updates you did use old kernel to boot?

Walnut

algent I spammed space on startup and selected the earlier of the entries. 5.14.14-202.current
ixni in TTY shows that's what is loaded. It behaves the same as 5.14.15-203.current

pomon

Try typing gnome-shell into the TTY before logging in. Show cat .xinitrc

Walnut

pomon gnome-shell returns: Failed to configure: Unsupported session type.
cat .xinitrc returns: No such file or directory.

pomon

Sorry. gnome-session and You log in to TTY as root. So cat /home/USER/.xinitrc. Your nickname for USER

Walnut

pomon gnome-sessions returns:
root@walnut /home/walnut # gnome-sessions
bash: gnome-sessions: command not found

cat .xinitrc as root returns:
root@walnut /home/walnut # cat /home/recovery/.xinitrc
cat: /home/walnut/.xinitrc: No such file or directory

pomon

Log in to TTy as user. Enter gnome-session, not gnome-sessions. Give the result of ls -lAh | grep -v '^ d'. You propably don't have an .xinitrc file, so you need to create it in your home directory with the content:

#! /bin/bash

exec gnome-session

Walnut

pomon Sorry about entering gnome-sessions I'll try my best to pay greater attention to what I'm doing.
.xinitrc did not exist, it has now been created and reports
walnut@walnut ~ $ cat .xinitrc
#! /bin/bash

exec gnome-session

Still no DE after restarting.

pomon

Hmm. I'm running out of ideas. Show: systemctl status gdm and eopkg li | grep gnome. Someone with Gnome can check if something is missing.
Well, what happens when you enter gnome-session on your TTY account

brent

pomon I agree display manager maybe and command would be sudo systemctl status gdm.service I believe. could it be an nvidia thing as well?