System crash after login (black screen)

rbenitezd

After login in the system shows a white crash screen with a log out option, but after a couple of second the screen turns black but the cursor remains. I can access TTY and upgraded and checked for errors in packages but everything seems ok.

The logs captured are:
dmesg => dmesg

journalctl --boot=-1 => journalctl-1

journalctl --boot => journalctl

Is there a way to fix this? I see some crashes on gnome apps, maybe installing another WM can make the system usable?

WetGeek

rbenitezd After login in the system shows a white crash screen with a log out option

This could possibly be a driver issue, but it would still make sense to tell which DE you're using. Often that's needed in order to get much help.

rbenitezd

rbenitezd
I'm using budgie. Kernel 5.11.16-178 on a Dell optiplex 7050
running sudo eopkg check | grep -v OK throws no errors or corrupted files.
I ran the following commands:
sudo eopkg install -c desktop.budgie
and
sudo eopkg install -c desktop.gnome

because I saw some errors on the previous logs I posted with .gnome. in it so I thought maybe reinstalling the WM/DE could fix it and it did. The system is functional again.

Thanks for the replies, hope this can help anyone who encounters this issue.

Girtablulu

can you run sudo eopkg check | grep -v OK and see if you have any broken packages

WetGeek

Girtablulu

Doesn't the command need to grep for "Broken"? Looks like this will list a LOT of stuff that's OK.

Staudey

Girtablulu sudo eopkg check | grep -v OK

Somewhat off-topic: That's pretty neat, actually. Too bad we can't use it for the standard package fix command on the "General Troubleshooting" page because it will also print some other lines, not just the one with the package name. Should work with some additional modifications though

edit: Working but(t) ugly
sudo eopkg check | grep -v OK | awk '{print $4}' | tail --lines +2 | sed '/^$/d'

Will prettify it (after making myself familiar with awk again) and then probably do a PR for help-center-docs

Girtablulu

WetGeek run the command yourself and see what it puts out 😉 and I cannot use the word broken because it translates it into my language as an example

WetGeek

Girtablulu run the command yourself and see what it puts out

Having seen your answer, I imagine that the -v interts the search. I will try that. Thanks for putting up with me!

EDIT: Indeed. Just shows that nfs-utils is broken, but now displays the actual file in that package.
Checking integrity of nfs-utils Broken
Corrupted file: /run/nfs/state

That's the first time I'd ever seen it used that way.

WetGeek

WetGeek I imagine that the -v interts the search.

Yes, it lists lines that don't match the target. But it also lists the file that's broken within the package. I'd suspect it because I ran it in terminology, but it should be all bash anyway.

Still, since it provides more detail, I'm going to use Bea's version from here on.

WetGeek

WetGeek Still, since it provides more detail, I'm going to use Bea's version from here on.

Indeed ... I ran both versions in Konsole, and the -v one returns more information:

# eopkg check | grep -v OK
Checking all installed packages
Checking integrity of nfs-utils Broken
Corrupted file: /run/nfs/state
# eopkg check | grep 'Broken'
Checking integrity of nfs-utils Broken
#
I was pretty sure I'd never seen the offending file listed with the usual command.
Curiosity now satisfied.

elfprince

Staudey This is a nice example of using several Unix command line tools in a pipe. 😃

Staudey

rbenitezd I ran the following commands:
sudo eopkg install -c desktop.budgie
and
sudo eopkg install -c desktop.gnome

Wait, so you have both Budgie and the GNOME desktop installed? Might've been an issue with the display manager then (for example GNOME doesn't play nicely if you use slick-greeter, which is the default for Budgie).