Error after boot end up at login screen

Hi from a Windows install as I am unable to get into my usual Opensuse Tumbelweed install. Did a DUP in the week but seem to remember thinking I’d wait until after Easter to do another. This morning on boot I’m getting dumped back to login screen after sceen kind of flashed and went black. Tired X11 from there instead of Wayland, but got same error. Ttied previous Kernel but had same result. Tried recvoery mode but that seemed to stall at a sound line for no apprent reason. I see there are a few post on here about lack of graphic environments so not sure if this is related to this?

Tried the termimal opption from boot to see if I could sudo Zypper dup from there but that doesn;t seem to work either. Any help or advice on how to recvoer from this without doing a fresh reinstall? Sorry can’t share much as I can’t get into the Opensuse system beyond the login screen.

How did you enter the terminal? By adding 3 to the kernel command line to enable network? What exactly did not work?

I did it via selecting c I think it was, which is one of the options in the Grub Boot screen. Is there a better way to do it from the login screen?

As described here:

Given the recovery mode, could you try “Ctlr D” at the point where it is stalled to reach the display manager?

I got the recovery mode to work this time. Tried the system ctl command which ended up showing about 3000+ lines which didn’t seem to help apart from maybe flaggin some stuff it didn’t like with Alsa audio, Bluetooth & HP Cups printing etc. Managed to get into a terminal from there and tried a Zypper DUP from there & was offered big upgrade from 20250414 to 18 which I guess is the dates. This seemed to start & was offered the dreaded Nvidia T&c’s to accept which I said Y to after which it seemed to hang. Tried again saying n to that & eventually got told all repos seemed to be unavailable. Tried Zypper refresh for this but no luck.
So maybe I need to try the suggestion to get the network up from hui above to get this to work perhaps? So I’ll go and try that now.

Thank you for taking the time to suggest that help with networking etc. This did enbable me to upgrade from to 2025o418 & the latest kernel 6.14.2-1. Unfortunately this did not solve my issue. If I’m quick I’m able to unlock a keyring which enables an application that requires the internet to start and log in. My system then crashes and gives me the following screen which I’m then stuck on as it is frozen and I can’t click the login button, although the cursor moves around. I’m using the same hardware on Windoze for this message. SO it seems like some issue with Gnome / the graphical interface that others are having problems with


maybe?

@jjis you need to disable all your GNOME shell extensions and see if that helps.

Hi Malcom, I haven’t tried that as I haven’t been able to get into a desktop today. One of the few recent changes there was to activate the status indicators, so I had wondered if that could be interfering with it as I have a few daemon tyoe things that kick in at start up too.
Is there a way to tturn extensions off in the edit mode via the GRUB as per the network thing from hui? In the meantime I’ll try recovery mode again I guess?

@jjis log in to a tty (ctrl+alt+F1)as your user, run gsettings set org.gnome.shell disable-user-extensions true then switch to root user and run systemctl isolate multi-user.target then run systemctl isolate graphical.target && exit and log in and test.

1 Like

Happy Easter to you Malcom from an Opensuse system having followed the above instructions as it came straight up having done that. So are those persistent changes or will it revert to having extensions and maybe the same problem on a reboot?
I guess I could try removing / disabling that status indicator if not, as it seemed to work fine before I made that change.

@jjis maybe it wasn’t patched correctly? If you open up the Extensions tool and disable that one and enable any others you have one at a time and test. As in enable one, logout/login if all ok, then the next etc.

Yes, when they are disabled, it’s persistent.

OK thanks understood. I’ll try that that. On checking & turning extensions back on II noticed there was an error message against Quick settings Tweaks. So maybe it was that? So I’ve disabled that & the status icons & will see how that goes. Thanks again and to others who spared the time to help today. Have a great day y’all.

1 Like

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