Can't login with Gnome Xorg after upgrade from Fed33 to 35!

Strange behavior after upgrading from 33 to 35 by using Software GUI.
I can not login with Gnome Xorg. After entering of user name and password and ok it takes 1-2 seconds and login mask appears again. With standard Gnome (Wayland) i can login. But I need Xorg because I have many user apps installed which bases on X and will not run with Wayland.
To test I have set up a new user. With this fresh new user I can login with Gnome Xorg and Gnome (Wayland).

In log file I see the following error section which indicates that there is someting wrong with pipewire-pulse.
Any help is appreciated.

Karl …


20:13:24 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=fprintd comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
20:13:24 systemd: fprintd.service: Deactivated successfully.
20:13:24 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-hostnamed comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
20:13:24 systemd: systemd-hostnamed.service: Deactivated successfully.
20:13:24 kernel: BPF prog-id=0 op=UNLOAD
20:13:24 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-localed comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
20:13:24 systemd: systemd-localed.service: Deactivated successfully.
20:13:01 reporter-system: Process 19803 (pipewire-pulse) crashed in _nl_load_domain.cold()
20:12:56 systemd: user-1000.slice: Consumed 2h 7min 49.645s CPU time.
20:12:56 kernel: Dispatched 189 messages @ 34(±199)μs / message.
20:12:56 systemd: Stopped Create User’s Volatile Files and Directories.
20:12:56 kernel: disconnected from pipewire
20:12:56 systemd: Stopping Multimedia Service Session Manager…
20:12:56 kernel: stopped by signal: Beendet
20:12:56 systemd: pipewire-pulse.service: Consumed 2.062s CPU time.
20:12:56 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=user-runtime-dir@1000 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
20:12:56 kernel: BPF prog-id=0 op=UNLOAD
20:12:56 kernel: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-coredump@1-30516-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
20:12:56 systemd: pipewire-pulse.service: Main process exited, code=dumped, status=6/ABRT
20:12:56 systemd-coredum: Process 19803 (pipewire-pulse) of user 1000 dumped core.

Found module linux-vdso.so.1 with build-id: 6761b48f74742f0a29da87e0229205606b993486
Found module libavahi-client.so.3 with build-id: a74102919e50a8c29f9f6b7cb561d387a82761fa
Found module libavahi-common.so.3 with build-id: 07bf073b57a037f9bb8e64e12d460499ead55a7c
Found module libm.so.6 with build-id: cea55efc551e62cd8439d044aa9a765c445fb7bf
Found module libpipewire-module-protocol-pulse.so with build-id: a796a211fc2eaa2acd0e1d5750b648c3828deb52
Found module libpipewire-module-metadata.so with build-id: a851c88bb38d61c05ac7eecd825d891e315223fd
Found module libpipewire-module-adapter.so with build-id: e6e1a05539bd53ac5294794f9911efe1649f5151
Found module libpipewire-module-client-node.so with build-id: 0a7763db8222a2b7a5cd3a83d506c70ffb21d09f
Found module libpipewire-module-protocol-native.so with build-id: 4fecb545274fa2c46ac4d7d9dfcbb4069820492b
Found module libpipewire-module-rtkit.so with build-id: 478d7c7ebb28bbc5bf852e32f3b587c0eceee637
Found module libdbus-1.so.3 with build-id: 58e800f0865bde326c5c9ce510062d5b19902f67
Found module libspa-dbus.so with build-id: f32881e54181447e1a92fd96d260240f39dc59cd
Found module libgpg-error.so.0 with build-id: 081975d0a3416374b4883b2f1639fd3c9df42390
Found module libgcrypt.so.20 with build-id: 711d41580c5a8649a79a8430a985dac3e25b5ba2
Found module libcap.so.2 with build-id: 0214aa9cc6a8646eb9ec27ab7dda6a2219da6500
Found module liblz4.so.1 with build-id: fd02c4542a1ce1ad6c503b958447be1c37a4afee
Found module libzstd.so.1 with build-id: d578adb66721ada2286001a1316d3d6345b81218
Found module liblzma.so.5 with build-id: 7fec53ce7cba9489f130c99cfd3ace82e9dde0ee
Found module libsystemd.so.0 with build-id: e4996d7fd9705035bdd6072e68c9dc65647d7d1c
Found module libspa-journal.so with build-id: ab6320aff2eb3fbcfc48eed3bf6472f86a96c236
Found module libspa-support.so with build-id: b3c0f6ed22d66e9c24ff06f7b2eaa6ee04f60fd5
Found module ld-linux-x86-64.so.2 with build-id: b43118df1fdb4c0aff150b6f8f926bccdec2a7f0
Found module libgcc_s.so.1 with build-id: 88564abce789aa42536da1247a57ff6062d61dcb
Found module libc.so.6 with build-id: 644dac2c66a6e0b32674f0ec71e7431bd0c06a63
Found module libpipewire-0.3.so.0 with build-id: a3de7d27b646cc3493c48efab881db2041c7f7dd
Found module pipewire-pulse with build-id: 080140f6c806c95d85608bbc1ca1c44b60211e99
Stack trace of thread 19803:
#0 0x00007f80408c284c __pthread_kill_implementation (libc.so.6 + 0x8f84c)
#1 0x00007f80408756a6 raise (libc.so.6 + 0x426a6)
#2 0x00007f804085f7d3 abort (libc.so.6 + 0x2c7d3)
#3 0x00007f804085f6fb __assert_fail_base.cold (libc.so.6 + 0x2c6fb)
#4 0x00007f804086e396 __assert_fail (libc.so.6 + 0x3b396)
#5 0x00007f8040ab6207 pw_proxy_remove (libpipewire-0.3.so.0 + 0x79207)
#6 0x00007f8040a84ee2 pw_core_disconnect (libpipewire-0.3.so.0 + 0x47ee2)
#7 0x00007f8032dfde44 client_free (libpipewire-module-protocol-pulse.so + 0x15e44)
#8 0x00007f8032dfdff5 module_destroy.lto_priv.0 (libpipewire-module-protocol-pulse.so + 0x15ff5)
#9 0x00007f8040a9b5a0 pw_impl_module_destroy (libpipewire-0.3.so.0 + 0x5e5a0)
#10 0x00007f8040a7853d pw_context_destroy (libpipewire-0.3.so.0 + 0x3b53d)
#11 0x000055f70bbc15e5 main (pipewire-pulse + 0x15e5)
#12 0x00007f8040860560 __libc_start_call_main (libc.so.6 + 0x2d560)
#13 0x00007f804086060c __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d60c)
#14 0x000055f70bbc1755 _start (pipewire-pulse + 0x1755)

20:12:55 dbus-daemon: dbus-daemon[30166]: [session uid=42 pid=30166] Successfully activated service ‘org.gnome.Shell.Screencast’
20:12:55 gnome-shell: Registering session with GDM
20:12:55 xkbcomp: Errors from xkbcomp are not fatal to the X server
20:12:55 dbus-daemon: dbus-daemon[30166]: [session uid=42 pid=30166] Successfully activated service ‘org.gnome.ScreenSaver’

Open the session in wayland, open a terminal window, then run sudo dnf upgrade followed by sudo dnf distro-sync. That should make certain that everything is fully up to date and in sync with the repos.

The error seems to likely be that pipewire was not used in fedora 33 and your user had audio configured for pulseaudio. The new user automatically is configured to use pipewire. That means you may easily fix the issue by deleting the audio config files under your home directory then the next time you start an audio app they needed configs will be created for you.

I cannot tell you where the files are located, but they may be under ~/.config or somewhere under ~/ . You can look at the differences in those locations for your older user name and the new one you created to find out. Remember that a lot of apps create a dot file similar to .config in your home directory which can be seen by using ‘ls -a’ to show all files including the hidden ‘dot’ files.

Please check the change log to see which config files you have to remove.
Fedora 34 Change Set shows about the introduction of Pipewire to Fedora
and F35 shows the change to Wireplumber. You can follow the links in the wiki to get more info.

Releases/35/ChangeSet - Fedora Project Wiki
Releases/34/ChangeSet - Fedora Project Wiki

Hello @kkarsten62 ,
Welcome to ask.:fedora:.org!
You could try logging into the tty at that point instead of graphically and go from there, maybe start by disabling the multimedia session manager in systemd (so stop the unit) then start x to see if you get access. If it isn’t called you may not get the error and be able to continue. A journalctl -b (minus number of boots back) --priority=3 would help.

Many thanks for your help.

I have found the “trouble maker”.
There is a .profile file in the home folder. I have no glue where this file is coming from. I never created or touched them. The content seems to by a kind of a default system one. When I move it to .profile.sik then I can login with GNOME Xorg. In a new user home folder there is no .profile file also.
Content of the .profile is:

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
	. "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

Many thanks for your help.

I have found the “trouble maker”. There is a .profile file in $HOME folder. When moving it to .profile.sik then I can login with GNOME Xorg. I never created or touched this file. It seems to be a kind of system default file. In a new user $HOME folder created with Fedora 35 there is no .profile file also.
Content of .profile is:

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
	. "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

Interesting it wasn’t a .bash_profile since the default for Fedora Linux is bash. Are you using a different shell maybe? Possibly it placed the .profile file in your home, if so.

I remember seen this in other distributions.
It looks like an older way to set the users ~/bin alias ~.local/bin path variable.

In the actual bash version this is done in ~/.bashrc

I really have no idea where this .profile came from.

But I can reproduce a bit more. I have the following statement in my .bashrc file.
set 'bind bell-style none'

It’s turn off the beep / bell on linux terminal.

When commenting this out I can login with GNOME Xorg even with the .profile is in my home folder.