You are not logged in.
Today, after the (long awaited) upgrade from Gnome 3.22.x to 3.24.1, gdm crashes and it's impossible to start any gnome-session (whether on Xorg or wayland).
I've also tried to start gnome-session from a xterm, under a xdm-session, but the the outcome is the same.
From the journal log it looks like a problem with gtk3 and/or glib2.
systemd-coredump[536]: Process 534 (gnome-session-f) of user 120 dumped core.
Stack trace of thread 534:
#0 0x00007f51bc5fbde9 n/a (libgtk-3.so.0)
#1 0x00007f51bc497a88 n/a (libgtk-3.so.0)
#2 0x00007f51bc4acb84 n/a (libgtk-3.so.0)
#3 0x00007f51bc498dbc n/a (libgtk-3.so.0)
#4 0x00007f51bc4acaac n/a (libgtk-3.so.0)
#5 0x00007f51bc4acb05 n/a (libgtk-3.so.0)
#6 0x00007f51bc499722 n/a (libgtk-3.so.0)
#7 0x00007f51bbe0431f g_type_create_instance (libgobject-2.0.so.0)
#8 0x00007f51bbde61fb n/a (libgobject-2.0.so.0)
#9 0x00007f51bbde7c0d g_object_newv (libgobject-2.0.so.0)
#10 0x00007f51bbde83c4 g_object_new (libgobject-2.0.so.0)
#11 0x00007f51bc4b4fea n/a (libgtk-3.so.0)
#12 0x00007f51bc692f87 n/a (libgtk-3.so.0)
#13 0x00007f51bbe0431f g_type_create_instance (libgobject-2.0.so.0)
#14 0x00007f51bbde61fb n/a (libgobject-2.0.so.0)
#15 0x00007f51bbde7c0d g_object_newv (libgobject-2.0.so.0)
#16 0x00007f51bbde83c4 g_object_new (libgobject-2.0.so.0)
#17 0x0000000000401db3 n/a (gnome-session-failed)
#18 0x00007f51bb739511 __libc_start_main (libc.so.6)
#19 0x00000000004021ba n/a (gnome-session-failed)
Last edited by joe_silver (2017-04-24 22:00:31)
Offline
A reinstallation of the set GNOME and gdm solved my issue.
pacaur -s GNOME gdm
Offline
Yes, it worked! Thanks!
Offline
I am having the same problem
Tried re-installing gdm and the important packages from GNOME. Still wont work
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
I also tried re-installing gdm and GNOME. Still having the same problem.
Thanks,
Greg
Offline
I didn't use the pacaur command suggested by Fenisu.
I tried instead
cd /var/cache/pacman/pkg
find . -name \*xz -exec sudo pacman --noconfirm -U \{\} \;
And then rebooted. Of course it is essential that all the downloaded packages are still there.
In particular you might try to re-install gnome-settings-daemon, which has been giving headaches to many users since the upgrade.
Offline
Having a similar problem and updating all gnome package (especially gdm and gnome-settings-daemon) didn't work on two systems.
Big difference is, that Xorg works, but I'm unable (gnome-session-f dumping core, stacktrace leading to libgtk-3.so.0) to login to Wayland from GDM.
Offline
Yes same issue now resolve for me. I try different thing but at the end the problem was simple : partial upgrade !!!
In fact i had to force the upgrade to gnome 3.24 with pacman -Syudd because i was stuck with an aur package (gstreamer0.10-good) depending on libsoup-gnome (now libsoup). So some dependency was left unresolve. I note this because i install downgrade from aur with yaourt to downgrade mutter (i was searching the problem) and yaourt give me a list of unresolve dependency. I resolve each dependency and the problem was solve.
This was silly from me : never copy past a command line you don t fully understand !!! Maybe it's your case so look after missing package
Offline
partial upgrade !!!
Thanks for sharing, but this isn't the problem here. Still investigating.
Last edited by Henry78 (2017-04-26 10:53:47)
Offline
For the recored: I tried to login with a newly created user and this works. I have to dig into this.
Offline
For the recored: I tried to login with a newly created user and this works. I have to dig into this.
I am not even getting to the login screen. I just get some weird screen flickering (for about 5 times) in which I will see the mouse cursor for half a second.
Then I am just presented with a few lines of the kernel log (tlp loaded, xyz loaded.... loaded).
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
I also get this exact same coredump, logging in just pops me back into gdm.. the fix reported here does not work for me.
Offline
epicarch: This happens only for Wayland Sessions? Because I'm able to start Xorg-Sessions but Wayland Session dumpes a core.
Offline
I had the same problem, in my case it was caused by gnome-settings-daemon-redshift, which prevented updates of other packages. I had to uninstal it and install gdm and gnome-settings-daemon again (see https://bbs.archlinux.org/viewtopic.php?id=225499). That solved the problem.
Offline
I am not using wayland, just normal old xorg. reinstalling gnome-settings-daemon and gdm did not work.
Offline
Since GNOME 3.24 was rolled out I am also not able to launch the Wayland-based GNOME session anymore from GDM.
I appear to be hit by this systemd-related bug and cannot run a Wayland-based GNOME session from a system terminal either. The Xorg-based GNOME sesson still works, though.
For the record, because it might be relevant in this context, I am not using anything NVIDIA on this system.
For those where reinstalling gnome-settings-daemon and gdm did not solve the issue, could you
Disable GDM (# systemctl disable gdm.service)
Reboot
Log in as your user on the system command line
Start a Wayland GNOME session from there ($ XDG_SESSION_TYPE=wayland dbus-run-session gnome-session)
and see if that gets you a GNOME session?
Offline
I'm able to start a Wayland session from command line (though I didn't disable gdm), but I'm also able to login to a Wayland session from gdm using a fresh user account.
I still don't know how to find why my user triggered a core dump.
Offline
Henry78 wrote:For the recored: I tried to login with a newly created user and this works. I have to dig into this.
I am not even getting to the login screen. I just get some weird screen flickering (for about 5 times) in which I will see the mouse cursor for half a second.
Then I am just presented with a few lines of the kernel log (tlp loaded, xyz loaded.... loaded).
None of the posted methods fixed it for me :
Here is a journalctl -xe after boot:
Setup 1: Thinkpad T14s G3, 14" FHD - R7 6850U - 32GB RAM - 2TB Solidigm P44 Pro NVME
Setup 2: Thinkpad X1E G1, 15.6" FHD - i7-8850H - 32GB RAM - NVIDIA GTX 1050Ti - 2x 1TB Samsung 970 Pro NVME
Accessories: Filco Majestouch TKL MX-Brown Mini Otaku, Benq XL2420T (144Hz), Lo(w)gitech G400, Puretrak Talent, Sennheiser HD800S + Meier Daccord FF + Meier Classic FF
Offline
I'm able to start a Wayland session from command line (though I didn't disable gdm), but I'm also able to login to a Wayland session from gdm using a fresh user account.
I still don't know how to find why my user triggered a core dump.
This is a strong hint that the problem lies in your personal settings (though I can't figure out where and why).
Offline
I am also experiencing this issue. GDM refuses to start, showing only a blinking cursor. However mine seems to run on infinitely.
Disabling GDM and running a wayland session as suggested above didn't work. I got org.freedesktop.systemd1 failed to start.
Dmesg indicates that the gnome session is failing due to a segfault in libgtk-3.
Here's the weird bit though. It only seems to fail when using two external monitors via my docking station. I can boot normally with my laptop undocked (x220). But docked with two monitors attached fails. Docked with one monitor attached results in a session with the monitors in extended configuration but the cursor in mirrored configuration and otherwise non responsive.
Offline
This is a strong hint that the problem lies in your personal settings (though I can't figure out where and why).
Yes it is, and I finally managed to locate the root-cause (on one of the two misbehaving computers): I removed
~/.config/gnome-session
, which only contained the empty folder
~/.config/gnome-session/saved-session/
.
With the the (empty) folders in place, gnome-sessions fails with a core dump, can't imagine why....
Mai 02 09:14:54 nb00270 systemd-coredump[13013]: Process 12920 (nextcloud) of user 1000 dumped core.
Stack trace of thread 12920:
#0 0x00007fd58cb16a10 raise (libc.so.6)
#1 0x00007fd58cb1813a abort (libc.so.6)
#2 0x00007fd58d9f5e21 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so
#3 0x00007fd5811f432e _ZN14QXcbConnectionC2EP19QXcbNativeInterfacebj
#4 0x00007fd5811f753e _ZN15QXcbIntegrationC1ERK11QStringListRiPPc (l
#5 0x00007fd5814b730d n/a (libqxcb.so)
#6 0x00007fd58e4ad9fd _ZN27QPlatformIntegrationFactory6createERK7QSt
#7 0x00007fd58e4bbe0b _ZN22QGuiApplicationPrivate25createPlatformInt
#8 0x00007fd58e4bc90d _ZN22QGuiApplicationPrivate21createEventDispat
#9 0x00007fd58dbf0c0f _ZN23QCoreApplicationPrivate4initEv (libQt5Cor
#10 0x00007fd58e4be32f _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.
#11 0x00007fd58ec5c089 _ZN19QApplicationPrivate4initEv (libQt5Widgets
#12 0x000000000056192a _ZN11SharedTools19QtSingleApplicationC2ERK7QSt
#13 0x000000000048dbdc _ZN3OCC11ApplicationC1ERiPPc (nextcloud)
#14 0x0000000000474f18 main (nextcloud)
#15 0x00007fd58cb03511 __libc_start_main (libc.so.6)
#16 0x000000000047555a _start (nextcloud)
Offline
Had the same problem and deleting .config/gnome-sessions , which contained only the empty folder saved-session too, solved it. Thx Henry78 for sharing your solution!
Offline
"Funny" thing: After Logging out and restarting my machine, I get the same behaviour as before. Apparently ~/.config/gnome-session was created again (this time with some files) and i have again to remove it, to be able to login from GDM.
This is how the folder looks like after logout/restart:
find .config/gnome-session
.config/gnome-session/
.config/gnome-session/saved-session
.config/gnome-session/saved-session/org.gnome.Shell.desktop
.config/gnome-session/saved-session/10980988e578aca766149370945131040600000132880074.desktop
Offline
It stays interesting. I had some situations where I had to remove .config/gnome-session again to be able to login from GDM. The new finding is, that the removal of org.gnome.Shell.desktop was sufficient to get a working login to Wayland from GDM.
Contents of org.gnome.Shell.desktop:
[Desktop Entry]
Name=gnome-shell
Comment=Client 106bfc779c7475c74a149341590625953900000008840000 which was automatically saved
Icon=system-run
Type=Application
StartupNotify=true
X-GNOME-Autostart-startup-id=106bfc779c7475c74a149341590625953900000008840000
Exec=gnome-shell --sm-client-id 106bfc779c7475c74a149341590625953900000008840000
X-GNOME-Autostart-discard-exec=rm -f /home/henry/.config/mutter/sessions/106bfc779c7475c74a149341590625953900000008840000.ms
Maybe the last line ("rm -f ...") helps me to find the real problem. But I'm really out of my waters here.
Offline
That line is weird.
My ~/.config/gnome-session/saved-session is empty, and both saved-session and its parent directory gnome-session are dated "Apr 19, 2015", which is when I installed gnome for the first time, I think.
Did you check the same file in /usr/share/applications ?
Offline