Dear Maintainer,

After logging in via the gdm3 graphical greeter, the ‘Oh no, something went
wrong …’ splash screen is shown for a few seconds.  Then, in most cases the
normal session appears.  (On rare occasions the login screen is shown again and
I have to log in again.)  Apparently, gnome-shell dies.

journalctl -b /usr/bin/gnome-session is not too helpful for me (Note the change
in the pid.):

Jun 28 10:56:47 snowdrop gnome-session[1106]: Entering running state
Jun 28 10:56:47 snowdrop gnome-session[1106]: openConnection: connect: No such file or directory
Jun 28 10:56:47 snowdrop gnome-session[1106]: cannot connect to brltty at :0
Jun 28 10:56:49 snowdrop gnome-session[1106]: Gjs-Message: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory)
Jun 28 10:56:54 snowdrop gnome-session[1106]: gnome-session[1106]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 28 10:56:54 snowdrop gnome-session[1106]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 28 10:56:54 snowdrop gnome-session[1106]: (gnome-settings-daemon:1127): GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon: The connection is closed
Jun 28 10:56:54 snowdrop gnome-session[1106]: (gnome-settings-daemon:1127): GLib-GIO-WARNING **: Invalid id 4 passed to g_bus_unown_name()
Jun 28 10:56:55 snowdrop gnome-session[1481]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Jun 28 10:56:55 snowdrop gnome-session[1481]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Jun 28 10:56:55 snowdrop gnome-session[1481]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Jun 28 10:56:55 snowdrop gnome-session[1481]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Jun 28 10:56:55 snowdrop gnome-session[1481]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jun 28 10:56:56 snowdrop gnome-session[1481]: Gjs-Message: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory)
Jun 28 10:56:56 snowdrop x-session-manager[1481]: Entering running state

This problem occurs on three different computers.  What they have in common are
similar graphics cards:

#1:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)

#2:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

#3:
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)


If you need more information, please let me know.

Regards,

Marcel

I suffer from the same problem (gdm3/3.14.1-8). Today I updated to the
current version in sid (gdm3/3.14.2-1) but no change.

$ lspci |egrep VGA
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U
Integrated Graphics (rev 09)

For now I switched to "slim".

Regards, rck

I just want to confirm that I have the same problem.
I don't know what types of logs etc. I should include.

Marek

I'm experiencing the same issue in strectch.

gdm3 version: 3.14.1-8

$ lspci | egrep VGA
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
Integrated Graphics Controller (rev 0b)