TW 32 bit: Can't boot to GUI

English Install/Boot/Login
1

Oh no, something has gone wrong.
A problem has occured and the system can’t recover. Please contact a sysadmin.


journalctl -r
gnome-session-binary[1114]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly.
gnome-session-binary[1114]: Unrecoverable failure in required component org.gnome.Shell.desktop.
gnome-session[1114]: gnome-session-binary[1114]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
gnome-shell[1135]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
gnome-session-binary[1114]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
gnome-session[1114]: gnome-session-binary[1114]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
nscd[683]: 683 checking for monitored file `/passwd`: No such file or directory
nscd[683]: 683 checking for monitored file `/nsswitch`: No such file or directory

After systemd.unit=multi-user.target kernel boot option:


Failed to start Postfix Mail Transport Agent.

login:



journalctl -r
nscd[646]: 646 checking for monitored file `/passwd`: No such file or directory
nscd[646]: 646 checking for monitored file `/nsswitch`: No such file or directory
...
login: gkr-pam: unable to locate daemon control file
...
systemd: Failed to start Postfix Mail Transport Agent.
systemd: postfix.service: Failed with result 'exit-code'
...
systemd: Received SIGRTMIN+21 from PID 314 (plymouthd).
systemd: Received SIGRTMIN+21 from PID 314 (plymouthd).
systemd: postfix.service: Control process exited, code=exited, status=1/FAILURE
systemd: systemd-hostnamed.service: Deactivated successfully.
systemd: Failed to start Terminate Plymouth Boot Screen.
systemd: plymouth-quit.service: Failed with result 'timeout'.
systemd: plymouth-quit.service: start operation timed out. Terminating.

last shutdown (from GUI) before error has appeared:

journalctl -r
gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
systemd: /usr/lib/systemd/system-generators/systemd-rc-local-generator failed with exit status 127.
systemd: /usr/lib/systemd/system-generators/systemd-sysv-generator failed with exit status 127.
systemd: /usr/lib/systemd/system-generators/systemd-rc-local-generator failed with exit status 127.
systemd: /usr/lib/systemd/system-generators/systemd-sysv-generator failed with exit status 127.
systemd: /usr/lib/systemd/system-generators/systemd-rc-local-generator failed with exit status 127.
systemd: /usr/lib/systemd/system-generators/systemd-sysv-generator failed with exit status 127.

Is it please safe to try

zypper dup

?

2

Hi
Should always use zypper dup on Tumbleweed, what is your current snapshot version?


cat /etc/os-release | grep VERSION_ID
3

Hi, thank you.

20220329 is current snapshot version

4

Hi
Currently at 20220404, so you are currently six (6) snapshots behind… 0330, 0331, 0401, 0402, 0403 and 0404… best zypper dup, then see what happens.

5

There was some dependency problem so it was necessary to remove gdm but GUI starts.

Attempt to install gdm:

zypper in gdm
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides 'libmozjs-91.so.0' needed by the to be installed libgjs0-1.72.0-1.1.i586
 Solution 1: do not install gdm-42.0-2.1.i586
 Solution 2: break libgjs0-1.72.0-1.1.i586 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c):
6

Hi
AFAICT there are no issues with mozjs, gjs and gdm 32bit builds. Can you force a refesh and do another zypper dup as well as forcing the install of gdm?


zypper -vvv ref -f
zypper -vvv dup
zypper -vvv in -f gdm

Your release is at 20220406 now?

7

I happen to have Tumblweed 32-bit in a libvirt VM. So I attempted to install “gdm” and I get the same conflict message.

8

mozjs91 is blocked on 32 bit dues to missing dependencies.

9

Hi
Yes, very likely as the Gnome Maintainers made some tweaks for the fix to 32bit GDM.

@MakeTopSite try with the next snapshot 0407, it should be fixed.

10

Well thank you. Glad to see that TW 32 bit support may continue.

11

yes that snapshot has fixed the problem.