[Testing Update] 2021-04-01 - Kernels, Gnome 40 Apps, Mesa 21.0.1, Kernels, Browsers

[flux]

hunspell-en_gb (2020.12.07-2) showing as orphan, but hunspell-en_GB (2020.12.07-1) didn’t - why?

[Th3Z0ne]

Ok, I updated again today and can not get into a GUI. I get only to that screen with the sad monitor.

Full journal of the boot: https://hknet.at/journal.txt

journal -b (lines with ERROR)

Apr 02 13:32:00 hk-01 gnome-session[1159]: gnome-session-binary[1159]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:00 hk-01 gnome-session-binary[1159]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:00 hk-01 gnome-session[1159]: gnome-session-binary[1159]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:00 hk-01 gnome-session-binary[1159]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:00 hk-01 gnome-session[1159]: gnome-session-binary[1159]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:00 hk-01 gnome-session-binary[1159]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:00 hk-01 /usr/lib/gdm-wayland-session[1158]: dbus-daemon[1158]: [session uid=120 pid=1158] Activating service name='org.gnome.ScreenSaver' requested by ':1.2' (uid=120 pid=1159 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
Apr 02 13:32:00 hk-01 /usr/lib/gdm-wayland-session[1169]: /usr/bin/gjs: symbol lookup error: /usr/lib/libgjs.so.0: undefined symbol: sysprof_clock

Apr 02 13:32:00 hk-01 org.gnome.Shell.desktop[1170]: /usr/bin/gnome-shell: symbol lookup error: /usr/lib/libgjs.so.0: undefined symbol: sysprof_clock

Apr 02 13:32:01 hk-01 gnome-session[1214]: gnome-session-binary[1214]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:01 hk-01 gnome-session-binary[1214]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:01 hk-01 gnome-session[1214]: gnome-session-binary[1214]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:01 hk-01 gnome-session-binary[1214]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:01 hk-01 gnome-session[1214]: gnome-session-binary[1214]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:01 hk-01 gnome-session-binary[1214]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 02 13:32:01 hk-01 /usr/lib/gdm-x-session[1213]: dbus-daemon[1213]: [session uid=120 pid=1213] Activating service name='org.gnome.ScreenSaver' requested by ':1.4' (uid=120 pid=1214 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
Apr 02 13:32:01 hk-01 /usr/lib/gdm-x-session[1476]: /usr/bin/gjs: symbol lookup error: /usr/lib/libgjs.so.0: undefined symbol: sysprof_clock

Apr 02 13:32:01 hk-01 org.gnome.Shell.desktop[1477]: /usr/bin/gnome-shell: symbol lookup error: /usr/lib/libgjs.so.0: undefined symbol: sysprof_clock
Apr 02 13:32:01 hk-01 gnome-session[1214]: gnome-session-binary[1214]: WARNING: App 'org.gnome.Shell.desktop' exited with code 127
Apr 02 13:32:01 hk-01 gnome-session-binary[1214]: WARNING: App 'org.gnome.Shell.desktop' exited with code 127
Apr 02 13:32:01 hk-01 org.gnome.Shell.desktop[1479]: /usr/bin/gnome-shell: symbol lookup error: /usr/lib/libgjs.so.0: undefined symbol: sysprof_clock

Apr 02 13:32:01 hk-01 gsd-sharing[1510]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Apr 02 13:32:01 hk-01 gsd-sharing[1510]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Apr 02 13:32:01 hk-01 gsd-sharing[1510]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 

I realy would need help as I can not update as long as I end up in an unusable system.

[michaldybczak]

@Th3Z0ne

I realy would need help as I can not update as long as I end up in an unusable system.

As usual, boot into tty and restore the last working backup or use chroot to do this. This is the basic first thing to do when a system or graphical session is not bootable. Of course, you can try to gather as much info on tty (if it’s available). Sometimes it turns out that one package is at fault, it gets updated and then the whole system update is working fine again.

[mfcmq]

Update went fine on 2 machines: KDE AMD/NVIDIA and i3 INTEL/NVIDIA HYBRID

[Termy]

all seems good here on KDE/AMD, thanks team!

[Th3Z0ne]

Ok, so now I am down to these packages:

baobab-40.0-1  evince-40.1-1  gedit-40.0-1  gnome-backgrounds-40rc-1
            gnome-bluetooth-3.34.5-1  gnome-calculator-40.0-1  gnome-characters-40.0-1
            gnome-clocks-40.0-1  gnome-desktop-1:40.0-1  gnome-disk-utility-40.0-1
            gnome-font-viewer-40.0-1  gnome-keyring-1:40.0-1
            gnome-online-accounts-3.39.92-1  gnome-screenshot-40.0-2
            gnome-system-monitor-40.0-2  gnome-terminal-3.40.0-1
            libnautilus-extension-40.0-1  mutter-3.38.4-2  nautilus-40.0-1

Everything else that came with this update I was able to perform without the system not giving me a GUI.

[Yochanan]

@flux

hunspell-en_gb (2020.12.07-2) showing as orphan, but hunspell-en_GB (2020.12.07-1) didn’t - why?

The packages were renamed:

upgpkg: hunspell-en 2020.12.07-2: Rebuild to rename packages.

[flux]

Thank you @Yochanan.

Should I then Mark as explicitly installed the new en_gb and en_us packages to reflect how the uppercase versions were, and to lose the orphan status of en_gb?

[Yochanan]

Yes, seems logical, eh?

[Th3Z0ne]

Hello, last info I am able to gather on my own regarding the fact that I end up with no working GUI after this Update is:

it’s mutter-3.38.4-2 package which is killing it. Updated everything but this and have a working system.

[Twifty]

Using the linux511 kernel with an AMD RX5700XT card is causing constant firefox tab crashes, and sometimes full browser crashes. Tried downgrading firefox to no avail, but using the linux510 kernel works fine. I’m guessing the amdgpu module is acting up again.

[hritwik]

try this solution, it worked for me.

Login screen not showing on startup

@huddo121 @spikerguy I found the fix for this, maybe you can look into this and if this works create a thread or announce in release post. A user had similar issue and posted on Arch forums and there i found answer. Although i have Intel iGPU and AMD dGPU, i faced this problem with all kernels (latest released 5.11) except 5.4. The issue is due to display drivers not being loaded before GDM and GDM requires these to display anything. So we have to use early KMS to load drivers during initramfs…

[hritwik]

you cat try this solution and report to devs if it works

Login screen not showing on startup

@huddo121 @spikerguy I found the fix for this, maybe you can look into this and if this works create a thread or announce in release post. A user had similar issue and posted on Arch forums and there i found answer. Although i have Intel iGPU and AMD dGPU, i faced this problem with all kernels (latest released 5.11) except 5.4. The issue is due to display drivers not being loaded before GDM and GDM requires these to display anything. So we have to use early KMS to load drivers during initramfs…

[anon88624618]

Thanks. I actually did this an another laptop and forgot that I didn’t on the one in question.

[Th3Z0ne]

I have and had early KMS enabled since first setup. (thus was on befor running into GDM chickened out)

cat /etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(intel_agp i915)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=(/crypto_keyfile.bin)

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
#HOOKS=(base udev autodetect modconf block keyboard keymap encrypt openswap resume filesystems fsck)
HOOKS=(base udev autodetect modconf block keyboard keymap encrypt resume filesystems fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

[gionno]

is there any problem with spectre-meltdown-checker since it is back to version 0.43?

[anon88624618]

I think we’re dealing with different roots of the issue. Maybe it would be best to open up a new thread, because there probably aren’t as many people stopping by here who might have a clue what’s wrong with your booting process.

EDIT: Did you try the latest unstable update with gnome-shell and gdm at version 40?

[Th3Z0ne]

@anon88624618

EDIT: Did you try the latest unstable update with gnome-shell and gdm at version 40?

Yes - switched to unstable and the result is the same grey - I cant continue - screen.
I also opened a new topic as suggested:

[Obsolete] GDM and thus gnome-shell fails to start unrecoverably

Hello, As the title “GDM and thus gnome-shell fails to start unrecoverably” suggests, since last testing branch update of “mutter” to mutter-3.38.4-2 my system wont make it to the GUI. I land at the graphical screen of death: [0EM60000000cXha] and I am told to contact the system maintainer The journal after booting into failed state shows following errors:

journal -b (lines with ERROR)

Apr 02 13:32:00 hk-01 gnome-session[1159]: gnome-session-binary[1159]: WARNING: Failed to upl…

Ps: right now I am downloading the dev image of gnome next to see if that boots, and than try and compare my and the image config…

[philm]

You have to download the regular gnome image from stable-staging branch and compare that. gnome-next is using unstable and Gnome 40 shell.

[philm]

I pushed mutter-3.38.4-2.1 with reenabling sysprof to see if that fixes issues with Gnome sessions.