[Solved] GNOME 3.34 crash on Wayland

IrvineHimself · 2019-09-20 12:12:32

I have similar problem and can confirm that it is not the kernel, but rather something to do with gnome.

Here is the relevant update from my pacman log

[2019-09-20 08:33] [PACMAN] Running 'pacman -Syu'
[2019-09-20 08:33] [PACMAN] synchronizing package lists
[2019-09-20 08:33] [PACMAN] starting full system upgrade
[2019-09-20 08:38] [ALPM] transaction started
[2019-09-20 08:38] [ALPM] upgraded libelf (0.176-1 -> 0.177-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-desktop (1:3.32.2-1 -> 1:3.34.0-1)
[2019-09-20 08:38] [ALPM] upgraded cheese (3.32.1-2 -> 3.34.0-2)
[2019-09-20 08:38] [ALPM] upgraded gjs (2:1.56.2-1 -> 2:1.58.0-1)
[2019-09-20 08:38] [ALPM] upgraded libgweather (3.32.2-1 -> 3.33.92+11+g13ce5dd-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-clocks (3.32.0-2 -> 3.34.0-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-settings-daemon (3.32.1-1 -> 3.34.0-1)
[2019-09-20 08:38] [ALPM] upgraded libgnomekbd (3.26.1-1 -> 3.26.1+2+g8d02ebd-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-control-center (3.32.2-1 -> 3.34.0.1+10+g0f8e3f332-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-session (3.32.0-1 -> 3.34.0-1)
[2019-09-20 08:38] [ALPM] upgraded libgdm (3.32.0+2+g820f90f5-2 -> 3.34.0-2)
[2019-09-20 08:38] [ALPM] upgraded mutter (3.32.2+43+gb7f158811-1 -> 3.34.0+6+gab7af2d0c-1)
[2019-09-20 08:38] [ALPM] installed gnome-autoar (0.2.4-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-shell (1:3.32.2+11+g1c6abf378-1 -> 1:3.34.0+94+g3d86e6e79-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-shell-extensions (3.32.1-1 -> 3.34.0-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-terminal (3.32.2-1 -> 3.34.0-1)
[2019-09-20 08:38] [ALPM] upgraded gnome-tweaks (3.32.0-1 -> 3.33.90+27+ge26f21d-1)
[2019-09-20 08:38] [ALPM] upgraded intel-ucode (20190618-1 -> 20190918-1)
[2019-09-20 08:38] [ALPM] upgraded linux (5.2.14.arch2-1 -> 5.3.arch1-1)
[2019-09-20 08:38] [ALPM] upgraded openresolv (3.9.1-1 -> 3.9.2-1)
[2019-09-20 08:38] [ALPM] transaction completed
[2019-09-20 08:38] [ALPM] running '30-systemd-udev-reload.hook'...
[2019-09-20 08:38] [ALPM] running '30-systemd-update.hook'...
[2019-09-20 08:38] [ALPM] running '60-linux.hook'...
[2019-09-20 08:38] [ALPM] running '90-linux.hook'...
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Starting build: 5.3.0-arch1-1-ARCH
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Image generation successful
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Starting build: 5.3.0-arch1-1-ARCH
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2019-09-20 08:38] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2019-09-20 08:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2019-09-20 08:39] [ALPM-SCRIPTLET] ==> Image generation successful
[2019-09-20 08:39] [ALPM] running 'glib-compile-schemas.hook'...
[2019-09-20 08:39] [ALPM] running 'gtk-update-icon-cache.hook'...
[2019-09-20 08:39] [ALPM] running 'update-desktop-database.hook'...

And here is my temporary downgrade to get my system working:

pacman -U /var/cache/pacman/pkg/mutter-3.32.2+43+gb7f158811-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-desktop-1:3.32.2-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/cheese-3.32.1-2-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-control-center-3.32.2-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-clocks-3.32.0-2-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-settings-daemon-3.32.1-1-x86_64.pkg.tar.xz var/cache/pacman/pkg/gnome-session-3.32.0-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-shell-1:3.32.2+11+g1c6abf378-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-shell-extensions-3.32.1-1-any.pkg.tar.xz  /var/cache/pacman/pkg/libgdm-3.32.0+2+g820f90f5-2-x86_64.pkg.tar.xz /var/cache/pacman/pkg/libgnomekbd-3.26.1-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-terminal-3.32.2-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/gnome-tweaks-3.32.0-1-any.pkg.tar.xz /var/cache/pacman/pkg/libgweather-3.32.2-1-x86_64.pkg.tar.xz

Note: I am running a wayland environment, and do not use a display manager. The initial symptom was an "apparent" freeze at logon. After unfreezing the logon, I added most of the *3.32 series of peripheral packages because they were incompatible with the *3.34 series.

When I get a chance, (this afternoon?), I will go through my logs and the above downgrades to see if I can identify the specific package which causes the problem.

Irvine

Last edited by IrvineHimself (2019-09-22 09:03:02)

IrvineHimself · 2019-09-20 12:43:52

V1del wrote:

I..... because if we are starting to source xinitrc.d chances are high we want an X11 session.

Just to point out, I personally don't launch an x11 session, and don't have an .xintrc.

For reference, my wayland session is launched by my .bash_profile

#
# ~/.bash_profile
#

[[ -f ~/.bashrc ]] && . ~/.bashrc

# Everything below was added by me :)

if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]] && [[ $XDG_SESSION_TYPE = tty ]]; then
  # Launch my text based throbber
  EtcIssueThrobber &
fi

if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]] && [[ $XDG_SESSION_TYPE = tty ]]; then
  # Launch gnome-shell (see https://wiki.archlinux.org/index.php/GNOME#Wayland_sessions)
  # Redirected stndout and stnderror so as not to interfere with throbber
  # QT_QPA_PLATFORM=wayland XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session > /dev/null 2>&1
  # according to V1del, Dbus is already started, see https://bbs.archlinux.org/viewtopic.php?id=247321 #6 and #22
  QT_QPA_PLATFORM=wayland XDG_SESSION_TYPE=wayland gnome-session > /dev/null 2>&1
fi

# Import environment into systemd/user. (In wayland, setting the correct environmental variables for
# systemd/user is not quite as transparent as it was under the xorg-server.)
# see https://wiki.archlinux.org/index.php/Systemd/User#Environment_variables
systemctl --user import-environment

Edit:
Also here is my .pam_environment

### I believe this is functionally equivalent to /etc/environment

# For a general discussion of environment variables
# see https://wiki.archlinux.org/index.php/.pam_environment#Per_user

### Needed to integrate nano with mc: Also solves the minor irritation
# of Thunar opening multiple instances of Geany
export EDITOR=nano

### Set FjSymlinks in path
# see https://wiki.archlinux.org/index.php/.pam_environment#Per_user
PATH=/usr/local/bin/FjSymlinks

### Fix large Vlc icons
# see https://forum.videolan.org/viewtopic.php?t=144265
QT_AUTO_SCREEN_SCALE_FACTOR=0

### Use qtc5t tool
QT_QPA_PLATFORMTHEME=qt5ct

### More fully enable Wayland
# see https://wiki.archlinux.org/index.php/Wayland#GUI_libraries
CLUTTER_BACKEND=wayland
SDL_VIDEODRIVER=wayland

## Enable Firefox Wayland
# see https://aur.archlinux.org/packages/fedora-firefox-wayland-bin/#comment-688161
MOZ_ENABLE_WAYLAND=1

Last edited by IrvineHimself (2019-09-20 12:47:47)

V1del · 2019-09-20 12:47:27

You evidently have another issue and might want your own thread for it... Post a journal from a fully updated system otherwise ths won't go far.

Splitting from https://bbs.archlinux.org/viewtopic.php?id=249302

Last edited by V1del (2019-09-20 12:49:42)

IrvineHimself · 2019-09-20 14:07:26

Sorry, incoorect boot

Last edited by IrvineHimself (2019-09-20 14:09:20)

IrvineHimself · 2019-09-20 14:18:38

Here is the correct boot http://ix.io/1W1k

seth · 2019-09-20 14:49:28

Sep 20 14:23:32 mine gnome-shell[907]: Failed to create backend: Could not get session ID: Session '1' is not a graphical session (type: 'tty')
Sep 20 14:23:32 mine systemd[853]: gnome-shell-wayland.service: Failed with result 'protocol'.
Sep 20 14:23:32 mine systemd[853]: Failed to start GNOME Shell on Wayland.
Sep 20 14:23:32 mine systemd[853]: Dependency failed for GNOME Shell on Wayland.
Sep 20 14:23:32 mine systemd[853]: Dependency failed for GNOME Wayland Session.
Sep 20 14:23:32 mine systemd[853]: Dependency failed for GNOME Wayland Session (session: gnome).

There're two GPUs and this looks like some autologin.
How do you start gnome exactly?

Also try early KMS and haveged (there're some posts of ppl. randomly failing to start X11 because the drm device can't be taken)

IrvineHimself · 2019-09-21 09:46:07

seth wrote:

.... There're two GPUs ....

I have a Nividia GPU using the nouveau driver and the built in Intel GPU.

seth wrote:

.... and this looks like some autologin.
How do you start gnome exactly? ....

I start Gnome from my .bash_profile, (above,) with

QT_QPA_PLATFORM=wayland XDG_SESSION_TYPE=wayland gnome-session > /dev/null 2>&1

seth wrote:

.... Also try early KMS ....

As per Wiki, I added MODULES=(i915 nouveau) to /etc/mkinitcpio.conf and rebuilt my initramfs with mkinitcpio -p linux-hardened.

This didn't appear to make any difference.

seth wrote:

.... and haveged (there're some posts of ppl. randomly failing to start X11 because the drm device can't be taken)

I am sorry, I am not sure what you mean by this.... Looking through the KMS wiki article, I noticed a section on Forcing modes and EDID, which seems relevant(?)

For reference: At the moment, I am using the Gnome settings manager to set the display.

Irvine

seth · 2019-09-21 13:46:01

https://wiki.archlinux.org/index.php/Haveged

Since wayland (afaik) doesn't support optimus setups for now, I'd suggest to only use i915 and rather blacklist nouveau.

IrvineHimself · 2019-09-21 15:31:34

Thanks for the link, (and your patience.) Before installing haveged, I had been playing DVDs on vlc and available entropy was in the region of 3800. After installing the package and Immediately following a reboot, (first starting Firefox etc,) available entropy was 3063.

After removing nouveau from MODULES=(i915 ) in /etc/mkinitcpio.conf, I created the file /etc/modprobe.d/BlacklistNouveau.conf with the following:

 blacklist nouveau

It didn't help.

Searching the forum to make sure I had correctly blacklisted nouveau, I found this post which suggested that I need to blacklist the following:

blacklist nouveau
blacklist rivafb
blacklist nvidiafb
blacklist rivatv
blacklist nv
blacklist uvcvideo

Editing my blacklist file to reflect this made absolutely no difference. This was not really surprising, since running mkinitcpio -M shows most of these modules are not being detected anyway:

=$ mkinitcpio -M
==> Modules autodetected
ac
acpi_cpufreq
aesni_intel
ahci
atkbd
battery
coretemp
crc32c_intel
crc32_pclmul
crct10dif_pclmul
evdev
ext4
fjes
ghash_clmulni_intel
hid_generic
i2c_i801
i8042
i915
input_leds
intel_cstate
intel_powerclamp
intel_rapl
intel_rapl_perf
intel_uncore
intel_wmi_thunderbolt
intel_xhci_usb_role_switch
iTCO_wdt
iwlwifi
joydev
kvm_intel
mac_hid
mei_hdcp
mei_me
mousedev
nouveau
pcc_cpufreq
pcspkr
psmouse
r8169
rtsx_pci
rtsx_pci_ms
rtsx_pci_sdmmc
sd_mod
serio_raw
snd_hda_codec_conexant
snd_hda_codec_hdmi
snd_hda_intel
snd_soc_skl
sr_mod
toshiba_acpi
toshiba_bluetooth
tpm_crb
tpm_tis
uas
usbhid
usb_storage
uvcvideo
wmi
wmi_bmof
x86_pkg_temp_thermal
xhci_pci
=$

Irvine

Last edited by IrvineHimself (2019-09-21 15:33:29)

seth · 2019-09-21 19:48:44

Meh.

Can you start gnome from a multi-user.target session (ie. w/o the autolaunch in the bashrc)?
https://wiki.archlinux.org/index.php/Sy … _boot_into

Also, just a hunch, try the "dbus-run-session gnome-session" variant and also drop whatever "EtcIssueThrobber" is.
nb. that this variant currently has an "exec" statement, so "systemctl --user import-environment" won't be reached!

wart83 · 2019-09-22 07:52:33

I have two graphics cards: intel and nvidia
For nvidia I use the proprietary drivers and gdm to start the session.
It seem that with the last update the problem of starting gnome session with wayland has been solved.

cat /var/log/pacman.log | grep 2019-09-22

[2019-09-22 09:18] [PACMAN] Running 'pacman -Syu'
[2019-09-22 09:18] [PACMAN] synchronizing package lists
[2019-09-22 09:18] [PACMAN] starting full system upgrade
[2019-09-22 09:18] [ALPM] transaction started
[2019-09-22 09:18] [ALPM] upgraded brasero (3.12.2+62+gbd1a4d5b-1 -> 3.12.2+65+gb14df0a8-1)
[2019-09-22 09:18] [ALPM] upgraded glm (0.9.9.6-1 -> 0.9.9.6-2)
[2019-09-22 09:18] [ALPM] upgraded mutter (3.34.0+6+gab7af2d0c-1 -> 3.34.0+30+gb5775e3d8-1)
[2019-09-22 09:18] [ALPM] upgraded gnome-shell (1:3.34.0+94+g3d86e6e79-1 -> 1:3.34.0+148+g506b75fc7-1)
[2019-09-22 09:18] [ALPM] upgraded openssh (8.0p1-2 -> 8.0p1-3)
[2019-09-22 09:18] [ALPM] transaction completed
[2019-09-22 09:18] [ALPM] running '30-systemd-daemon-reload.hook'...
[2019-09-22 09:18] [ALPM] running '30-systemd-tmpfiles.hook'...
[2019-09-22 09:18] [ALPM] running '30-systemd-update.hook'...
[2019-09-22 09:18] [ALPM] running 'glib-compile-schemas.hook'...
[2019-09-22 09:18] [ALPM] running 'gtk-update-icon-cache.hook'...
[2019-09-22 09:18] [ALPM] running 'update-desktop-database.hook'...
[2019-09-22 09:18] [ALPM] running 'update-mime-database.hook'...

cat /etc/mkinitcpio.conf

# 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=()

# 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 filesystems keyboard 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_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

cat /etc/modprobe.d/blacklist-nouveau.conf

blacklist nouveau
options nouveau modeset=0

lsmod | grep nvidia

nvidia_drm             57344  0
nvidia_modeset       1126400  1 nvidia_drm
nvidia              19558400  25 nvidia_modeset
drm_kms_helper        212992  2 nvidia_drm,i915
drm                   516096  7 drm_kms_helper,nvidia_drm,i915
ipmi_msghandler        65536  2 ipmi_devintf,nvidia

cat /etc/gdm/custom.conf

# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

IrvineHimself · 2019-09-22 09:02:24

seth wrote:

... just a hunch, try the "dbus-run-session gnome-session" variant ....

Brilliant, this solved the problem. Thank you.

For reference: After successfully logging on using dbus-run-session gnome-session, (and double checking that it wasn't a fluke,) I removed my Nouveau blacklist, (along with i915 from the modules array,) uninstalled haveged, and was still able to launch the updated Gnome shell.

wart83 wrote:

.... It seem that with the last update the problem of starting gnome session with wayland has been solved....

I still need to launch gnome with

QT_QPA_PLATFORM=wayland XDG_SESSION_TYPE=waylanddbus-run-session gnome-session

As oppose to the previous

QT_QPA_PLATFORM=wayland XDG_SESSION_TYPE=wayland gnome-session

EtcIssueThrobber and GDM: The last time I checked, GDM required xorg-server as a dependency, and, since I am trying to minimise xorg dependencies, GDM is out.

EtcIssueThrobber is my version of a primitive display manger that can, potentially, allow me to choose between a plain console and/or multiple desktop environments. When launching Gnome with the dbus-run-session gnome-session variant, it works as before and does not cause any problems.

Thanks for all your help

Irvine

Edit: Confused Wayland and Gnome

Last edited by IrvineHimself (2019-09-22 09:10:15)

ikswokor · 2019-09-22 11:32:31

hello guys,

i have a similiar issue - after boot i automatic login to gnome wayland session, and after few seconds (sometimes minutes) I get kicked to the login screen. Here's full log file http://ix.io/1Wng

wrz 22 09:52:15 delliks systemd[2060]: Started GNOME Session Manager (session: gnome).
wrz 22 09:52:15 delliks systemd[2060]: Reached target GNOME Session Manager is ready.
wrz 22 09:52:15 delliks systemd[2060]: Starting GNOME Shell on Wayland...
wrz 22 09:52:15 delliks gnome-shell[7345]: Failed to create backend: Could not take control: GDBus.Error:System.Error.EBUSY: Device or resource busy
wrz 22 09:52:15 delliks systemd[2060]: gnome-shell-wayland.service: Failed with result 'protocol'.
wrz 22 09:52:15 delliks systemd[2060]: Failed to start GNOME Shell on Wayland.
wrz 22 09:52:15 delliks systemd[2060]: Dependency failed for GNOME Shell on Wayland.
wrz 22 09:52:15 delliks systemd[2060]: Dependency failed for GNOME Wayland Session.
wrz 22 09:52:15 delliks systemd[2060]: Dependency failed for GNOME Wayland Session (session: gnome).
wrz 22 09:52:15 delliks systemd[2060]: gnome-session-wayland@gnome.target: Job gnome-session-wayland@gnome.target/start failed with result 'dependency'.
wrz 22 09:52:15 delliks systemd[2060]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'.
wrz 22 09:52:15 delliks systemd[2060]: gnome-session-wayland.target: Triggering OnFailure= dependencies.
wrz 22 09:52:15 delliks systemd[2060]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'.
wrz 22 09:52:15 delliks systemd[2060]: gnome-shell-wayland.service: Triggering OnFailure= dependencies.
wrz 22 09:52:15 delliks systemd[2060]: Requested transaction contradicts existing jobs: Transaction for gnome-shell-disable-extensions.service/start is destructive (gnome-session-stable.tim>
wrz 22 09:52:15 delliks systemd[2060]: gnome-shell-wayland.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-shell-disable-extensions.service/start is destructive (>
wrz 22 09:52:15 delliks systemd[2060]: gnome-session-stable.timer: Succeeded.
wrz 22 09:52:15 delliks systemd[2060]: Stopped GNOME Session is not yet stable (running for <2 minutes).
wrz 22 09:52:15 delliks systemd[2060]: Stopped target GNOME Session Manager is ready.
wrz 22 09:52:15 delliks systemd[2060]: Stopping GNOME Session Manager (session: gnome)...

seth · 2019-09-22 13:24:05

@Irvine, since you fork EtcIssueThrobber and it runs under the same conditions as your gnome shell, there's potential for a collision ultimately causing this issue. I'd try w/o it and w/o dbus-run-session to not fix one oddity with another.

@ikswokor, no you don't - this entirely different. I suspect some 3rd party extensions failing, so remove all of them. I doubt please open a new thread or report your post for a split.

IrvineHimself · 2019-09-22 14:36:40

seth wrote:

@Irvine, since you fork EtcIssueThrobber and it runs under the same conditions as your gnome shell, there's potential for a collision ultimately causing this issue. I'd try w/o it and w/o dbus-run-session to not fix one oddity with another.

After confirming the problem, removing EtcIssueThrobber and logging on "w/o it and w/o dbus-run-session" was one of the first things I checked. Additionally, I checked with and without dbus-run-session for all the variations of blacklists, early kms, entropy and EtcIssueThrobber, and the problem appears only when dbus-run-session is missing.

Grepping ps -aux only shows the grep command.

=$ ps -aux | grep "EtcIssueThrobber"
stupidme    1944  0.0  0.0   6268  2340 pts/0    S+   14:56   0:00 grep --color=auto EtcIssueThrobber
=$

So the fork seems to exit cleanly. However, I value your advice and, now that you have raised my awareness, I am very conscious of the potential pitfalls. Looking at what I am trying to achieve with "EtcIssueThrobber", the fork was actually a hangover from an early iteration and is no longer necessary for it to work. As a result, I will remove the fork and let my .bash_profile run sequentially.

Thank you for taking the time to point that out.

Irvine

Arch Linux

#1 2019-09-20 12:12:32

[Solved] GNOME 3.34 crash on Wayland

#2 2019-09-20 12:43:52

Re: [Solved] GNOME 3.34 crash on Wayland

#3 2019-09-20 12:47:27

Re: [Solved] GNOME 3.34 crash on Wayland

#4 2019-09-20 14:07:26

Re: [Solved] GNOME 3.34 crash on Wayland

#5 2019-09-20 14:18:38

Re: [Solved] GNOME 3.34 crash on Wayland

#6 2019-09-20 14:49:28

Re: [Solved] GNOME 3.34 crash on Wayland

#7 2019-09-21 09:46:07

Re: [Solved] GNOME 3.34 crash on Wayland

#8 2019-09-21 13:46:01

Re: [Solved] GNOME 3.34 crash on Wayland

#9 2019-09-21 15:31:34

Re: [Solved] GNOME 3.34 crash on Wayland

#10 2019-09-21 19:48:44

Re: [Solved] GNOME 3.34 crash on Wayland

#11 2019-09-22 07:52:33

Re: [Solved] GNOME 3.34 crash on Wayland

#12 2019-09-22 09:02:24

Re: [Solved] GNOME 3.34 crash on Wayland

#13 2019-09-22 11:32:31

Re: [Solved] GNOME 3.34 crash on Wayland

#14 2019-09-22 13:24:05

Re: [Solved] GNOME 3.34 crash on Wayland

#15 2019-09-22 14:36:40

Re: [Solved] GNOME 3.34 crash on Wayland

Board footer