Failed login after upgrade to Leap 15.4

Hi there, forgive any typos as I’m using my phone to submit this. I run an upgrade from 15.3 to 15.4 on Wednesday and on booting up I run into an error “oh no something has gone wrong a problem has occurred and the system can’t recover. Please contact a system administrator”.
I have included output from inxi, 2 session loginctl, boot.msg & journalctl respectively on here. I can share more info as required.

https://susepaste.org/84409562

https://susepaste.org/33567214

https://susepaste.org/84435839

https://susepaste.org/42532496

https://susepaste.org/45991631

Maybe add some information on how you upgraded. “To upgrade” is a rather loose expression and it can be done in several ways.

I used this guide to run the upgrade https://gist.github.com/oleksis/8cb48edd682c8adf818da2d097ae2979

But, if that’s the case and, you can’t login, how did you manage to execute “inxi”, “loginctl” and, “journalctl”?

  • Looking at the output of “loginctl session-status «session number
    »” – you seem to have logged into the system via a VT – “tty1” …

And, the content of “/var/log/boot.msg” seems to be perfectly OK.
[HR][/HR]And, if I’m not mistaken, the systemd Journal entries indicate that, the openSUSE system is running the Oracle VirtualBox VM system …

  • There are some entries indicating the Kernel Module “vboxdrv
    ” …

And, there’s also an indication that, the User Desktop Environment is GNOME.
And, there’s an indication that, GNOME crashed –


Jul 29 10:52:53 openSUSELeap kernel: traps: gnome-shell[1876] trap int3 ip:7f3cc7337911 sp:7fffb4cb6200 error:0 in libglib-2.0.so.0.7000.4[7f3cc72dc000+131000]
Jul 29 10:52:54 openSUSELeap gnome-session[1868]: gnome-session-binary[1868]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Jul 29 10:52:54 openSUSELeap gnome-session-binary[1868]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5
Jul 29 10:52:54 openSUSELeap gnome-session-binary[1868]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jul 29 10:52:54 openSUSELeap /usr/lib/gdm/gdm-wayland-session[1867]: dbus-daemon[1867]: [session uid=460 pid=1867] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=460 pid=1868 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
Jul 29 10:52:54 openSUSELeap gdm-launch-environment][1831]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Jul 29 10:52:54 openSUSELeap gdm-launch-environment][1831]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul 29 10:52:54 openSUSELeap gdm[1821]: Gdm: GdmDisplay: Session never registered, failing

[HR][/HR]All of which indicates that, the Upgrade suffered more than a few errors.

  • Please review this openSUSE SDB article – <https://en.opensuse.org/SDB:System_upgrade&gt; and,
  • Please check the openSUSE Repositories you’re using and,
  • Please check the non-openSUSE Repositories you’re using and,
  • Please correct all errors found regarding the Repository URLs and then, execute “zypper refresh --force” and then,
  • Execute “zypper patch” and “zypper update” and then,
  • Reboot.
  • And then, if the GNOME DE still fails to start, use “yast2
    ” from a VT to sort out the installed package mess.

No idea who the bloke is – also, no idea if, he’s a SUSE employee.

  • Please use the openSUSE SDB – it’s been written by SUSE employees and, checked for correctness.

Please be aware that, openSUSE has some voluntary contributors but, the documentation is largely written by SUSE employees and, the system packages are SLE packages, maintained by SUSE staff members assigned to the openSUSE Project.

Yes I was logged in through runlevel 5

[HR][/HR]And, if I’m not mistaken, the systemd Journal entries indicate that, the openSUSE system is running the Oracle VirtualBox VM system …

  • There are some entries indicating the Kernel Module “vboxdrv
    ” … >

I have VirtualBox for Windows guest (work/LAN stuff). openSUSE is my host.

And, there’s also an indication that, the User Desktop Environment is GNOME.
And, there’s an indication that, GNOME crashed –

Jul 29 10:52:53 openSUSELeap kernel: traps: gnome-shell[1876] trap int3 ip:7f3cc7337911 sp:7fffb4cb6200 error:0 in libglib-2.0.so.0.7000.4[7f3cc72dc000+131000]
Jul 29 10:52:54 openSUSELeap gnome-session[1868]: gnome-session-binary[1868]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 5
Jul 29 10:52:54 openSUSELeap gnome-session-binary[1868]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 5
Jul 29 10:52:54 openSUSELeap gnome-session-binary[1868]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jul 29 10:52:54 openSUSELeap /usr/lib/gdm/gdm-wayland-session[1867]: dbus-daemon[1867]: [session uid=460 pid=1867] Activating service name=‘ca.desrt.dconf’ requested by ‘:1.2’ (uid=460 pid=1868 comm=“/usr/lib/gnome-session-binary --autostart /usr/sha”)
Jul 29 10:52:54 openSUSELeap gdm-launch-environment][1831]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Jul 29 10:52:54 openSUSELeap gdm-launch-environment][1831]: GLib-GObject: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed
Jul 29 10:52:54 openSUSELeap gdm[1821]: Gdm: GdmDisplay: Session never registered, failing

[HR][/HR]All of which indicates that, the Upgrade suffered more than a few errors.

  • Please review this openSUSE SDB article – <https://en.opensuse.org/SDB:System_upgrade&gt; and,
  • Please check the openSUSE Repositories you’re using and,
  • Please check the non-openSUSE Repositories you’re using and,
  • Please correct all errors found regarding the Repository URLs and then, execute “zypper refresh --force” and then,
  • Execute “zypper patch” and “zypper update” and then,
  • Reboot.
  • And then, if the GNOME DE still fails to start, use “yast2
    ” from a VT to sort out the installed package mess. >

“zypper patch” and a reboot appears to have fixed the problem. Sending this from my PC. Your help is much appreciated.

UNIX® System V Init is no longer used by openSUSE systems – it’s all systemd – despite the “systemd-sysvinit” and “sysvinit-tools” packages – which provide a wrapper to systemd to allow “SysV-style init” commands to be used.

  • Your system was at the “graphical.target
    ” with a crashed GUI. Which is, effectively, in practical terms, almost the same as the “multi-user.target”.

 # journalctl -b 0 --output=short-monotonic --no-hostname | grep -i 'reached target'
    1.106458] systemd[1]: Reached target Initrd /usr File System.
    1.106478] systemd[1]: Reached target Slice Units.
    1.106494] systemd[1]: Reached target Swaps.
    1.106503] systemd[1]: Reached target Timer Units.
    1.106774] systemd[1]: Reached target Socket Units.
    1.279504] systemd[1]: Reached target Path Units.
    3.675818] systemd[1]: Reached target Initrd Root Device.
    3.681005] systemd[1]: Reached target Preparation for Local File Systems.
    3.681053] systemd[1]: Reached target Local File Systems.
    3.687612] systemd[1]: Reached target System Initialization.
    3.687664] systemd[1]: Reached target Basic System.
    4.306078] systemd[1]: Reached target Preparation for Remote File Systems.
    4.306135] systemd[1]: Reached target Remote File Systems.
    4.410638] systemd[1]: Reached target Initrd Root File System.
    4.561107] systemd[1]: Reached target Initrd File Systems.
    4.561136] systemd[1]: Reached target Initrd Default Target.
    4.596943] systemd[1]: Reached target Switch Root.
    5.327342] systemd[1]: Reached target Slice Units.
    5.327374] systemd[1]: Reached target System Time Set.
    5.327413] systemd[1]: Reached target Local Verity Protected Volumes.
    5.331019] systemd[1]: Reached target RPC Port Mapper.
    5.342052] systemd[1]: Reached target Local Encrypted Volumes.
    5.383511] systemd[1]: Reached target Preparation for Local File Systems.
    5.673425] systemd[1]: Reached target Swaps.
    9.787129] systemd[1]: Reached target Local File Systems.
    9.954520] systemd[1]: Reached target NFS client services.
    9.954621] systemd[1]: Reached target Preparation for Remote File Systems.
   10.055571] systemd[1]: Reached target System Initialization.
   10.060759] systemd[1]: Reached target Path Units.
   10.064053] systemd[1]: Reached target Socket Units.
   10.064181] systemd[1]: Reached target Basic System.
   10.120214] systemd[1]: Reached target Host and Network Name Lookups.
   10.120383] systemd[1]: Reached target User and Group Name Lookups.
   10.169533] systemd[1]: Reached target Sound Card.
   10.705782] systemd[1]: Reached target Preparation for Network.
   21.544713] systemd[1]: Reached target Network.
   21.544839] systemd[1]: Reached target Network is Online.
   21.569558] systemd[1]: Reached target Remote File Systems.
   34.802333] systemd[1]: Reached target System Time Synchronized.
   34.807922] systemd[1]: Reached target Timer Units.
   35.185240] systemd[1]: Reached target Login Prompts.
   35.237145] systemd[1]: Reached target Multi-User System.
   35.698117] systemd[1]: Reached target Graphical Interface.
 #