removing reinstalling gnome desktop

Axios

I assume the command to remove gnome desktop is sudo eopkg rm gdm gnome-shell gnome-desktop-branding-fortitude

And to reinstall is sudo eopkg install gdm gnome-shell gnome-desktop-branding-fortitude
Tried just the install but didnt help still at oops screen after booting.
gives shared library error when starting gdm from terminal libreadline.so.6
journalctl shows after that error Unrecoverable failure in required component org.gnome.shell.desktop
then whole bunch of errors status 127.

brent

Axios sudo eopkg rm gdm gnome-shell gnome-desktop-branding-fortitude

Axios sudo eopkg install gdm gnome-shell gnome-desktop-branding-fortitude

I cut and paste both of these in the forum search and people had used these commands before (it sounds like).

when I lost my DM I remember also having to sudo systemctl start (or restart) XXXX.service. maybe two of them. With the XXX being gdm.service? or similar?
Saw a great webpage about systemctl and how to show all active or dead services. so at least you could rule that one out. or in.

Axios error Unrecoverable failure in required component org.gnome.shell.desktop
then whole bunch of errors status 127.

that I don't know about

brent

Axios Unrecoverable failure in required component org.gnome.shell.desktop

see a bunch of gnome desktop fails when I duck duck this phrase. Only one 127/gnome desktop thread, though: https://forums.opensuse.org/printthread.php?t=568669&pp=10&page=1

Skimming I see related to wayland, xorg, zypper(?) consistently

Staudey

Axios Tried just the install but didnt help still at oops screen after booting.

I'm not sure if we talked about this in another thread, but have you tried sudo eopkg it --reinstall mesalib. That particular package is known to sometimes cause the oops screen.

Edit: I would also suggest using the it --reinstall command for everything else you try, because if you first remove and then install packages, the remove can cause some other packages to get deleted (due to dependency) and the install afterwards of course won't re-install those auto-removed packages.

Axios

Staudey Had been working great left it on for days using it off on and and then programs started not opening so I rebooted and then the oops screen (On dell desktop.)
Dunno got image it before i get to carried away..
So just the it --reinstall should catch it?

Staudey

Axios So just the it --reinstall should catch it?

The sudo eopkg it --reinstall mesalib is a solution for one particular issue some people are experiencing, that manifests in an oops screen. I can't guarantee that it's what's happening in your case though. It won't hurt anyway (since it simply reinstalls the package)