You are not logged in.

#1 2017-01-04 14:23:45

piedro
Member
Registered: 2013-04-11
Posts: 218

[Solved] After I logout Gnome 3.22 I cannot login again...

Hello!

This is on fully up to date Arch with Gnome 3.22...

When I logout a Gnome session I cannot login again - journalctl shows me:

 arch gnome-keyring-pkcs11.desktop[1824]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 04 14:52:20 arch kernel: [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GE
Jan 04 14:52:20 arch kernel: [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GE
Jan 04 14:52:20 arch kernel: [drm:nvidia_drm_gem_import_nvkms_memory [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to import NVKMS memory to GE
Jan 04 14:52:20 arch gnome-shell[1834]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
Jan 04 14:52:20 arch gnome-shell[1834]: Unable to initialize Clutter.
Jan 04 14:52:20 arch gnome-session[1813]: gnome-session-binary[1813]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 04 14:52:20 arch gnome-session-binary[1813]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 04 14:52:20 arch gnome-session-binary[1813]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jan 04 14:52:20 arch gdm-password][1801]: pam_unix(gdm-password:session): session closed for user piedro
Jan 04 14:52:20 arch gdm[593]: GdmDisplay: display lasted 0,472714 seconds 

This also happens with any other user - I cannot login and logout and re-login.

I am completely lost here and do not know how to troubleshoot this...

What I tried:

- enabling Nvidia KMS and loading the modules as described in the Wiki - no change
- reinstalled gdm - no success (well I didn't really expect any change)

Could anyone help here?

On a side note: Can I switch off the gdm lock screen showing the clock after logging out a session - I'd really prefer to get the user list to choose from right away...?

thx, p.

Last edited by piedro (2017-02-07 11:29:58)

Offline

#2 2017-01-05 08:41:54

seth
Member
Registered: 2012-09-03
Posts: 49,991

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

This is probably only on wayland and nvidia-drm and does not happen when you use "gnome on xorg"?

Online

#3 2017-01-05 09:37:06

Ark987
Member
Registered: 2015-11-06
Posts: 3

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

I've noticed the same problem, what I did was from the GDM login screen I had to click the cog icon and select "GNOME on Xorg" then I could login and logout repeatedly. But I had to the same for all accounts in the computer.

Offline

#4 2017-01-05 09:41:44

bloff
Member
From: Poland
Registered: 2017-01-05
Posts: 1

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

That is gdm issue, after install nvidia drivers, can't anymore relogin. I change gdm to lightdm and now it works.

Offline

#5 2017-01-06 06:33:33

piedro
Member
Registered: 2013-04-11
Posts: 218

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

Thanks for your answers!

I used sddm before but then I could not use the "switch user" feature of gnome...

Can I switch users when using lightdm?

p.

Offline

#6 2017-01-06 08:57:48

seth
Member
Registered: 2012-09-03
Posts: 49,991

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

bloff is way off in his suggestion.
GDM will fail on nvidia because it or gnome likely still trying to use wayland which does not or not reliably work with the nvidia blob. Using lightdm kicks him to X11.

Ark987 confirms that it's likely a "gnome on wayland is f*** premature and should by no way be the default" issue, so try whether it works with gnome on X11.

Online

#7 2017-01-06 15:55:17

piedro
Member
Registered: 2013-04-11
Posts: 218

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

Thanks a lot!

The hint by Seth and Ark987 worked... if I set all logins on "Gnome on Xorg" it works again...
I am really confused, because I never realized this setting was there in the first place.

So Gnome uses Wayland as default? That seems a bit adventurous...
Also I checked a few weeks ago with "loginctl" and it showed me I've been using X11...

Strange thing is if I am doing a "loginctl" now I get:

c1   120 gdm    seat0  /dev/tty1
c2 1000 piedro  seat0 /dev/tty2
c3 1000 piedro  seat0 /dev/tty2

Why are there two session listed for my user? (I checked - both X11)

thx again, p.

Offline

#8 2017-02-07 08:39:25

Cxpher
Member
Registered: 2016-06-05
Posts: 13

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

[sean@mars ~]$ loginctl
   SESSION        UID USER             SEAT             TTY
        c3       1000 sean             seat0            /dev/tty2
        c2        120 gdm              seat0            /dev/tty1

2 sessions listed.
[sean@mars ~]$ loginctl show-session c3 -p Type
Type=x11

I can confirm this only happens with "GNOME on Wayland" selected. It will work fine with GNOME on X11. This is only if you have NVIDIA proprietary drivers installed.

The reason is because NVIDIA is not Wayland ready yet. However, because you have this installed, despite choosing the default Wayland option, you are still running on X11 due to lack of driver support for Wayland (NVIDIA).

As such, if user switching is needed via GDM, you might as well use GNOME on X11 since the NVIDIA driver does not support Wayland yet anyway. Then ensure that ForceFullCompositionPipeline is enabled via NVIDIA settings with your PowerMizer set to "Prefer Maximum Performance" and disable in game vsync options. This will ensure tearing dosen't occur in X11 generally while not hurting in game performance.

PowerMizer settings however, seem to reset on a reboot. As such, i use the bash script below and place it in /etc/profile.d/

[sean@mars profile.d]$ cat nvidia_powermizer.sh
#!/bin/bash
nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1 > /dev/null

This makes sure that my PowerMizer settings are set accordingly at every reboot.

It seems that choosing between GNOME on Wayland and GNOME on X11, despite defaulting to X11 due to NVIDIA driver, still seems to have certain differences which prevent gnome-session from handling the session properly upon a logout. Note that locking/unlocking the screen works fine. Just can't login back after you logout till either a reboot or switching to GNOME on X11 instead.

I've reported this as a bug on GNOME bugtracker but they likely can't do anything about it until NVIDIA properly supports Wayland.

PS : GNOME on Wayland isn't adventurous. I believe it's properly supported by nouveau which is what ships with the distributions by default. The NVIDIA proprietary driver is after all, a 3rd party driver. GNOME on Wayland is relatively stable by now and the latest Fedora also adopts it as default.

Any app that does not support Wayland will use XWayland to run (https://wayland.freedesktop.org/xserver.html). If the whole session however is not supported, despite choosing that option, the session will still run as type X11. However, as i mentioned earlier, choosing GNOME on X11 in such a case is better because there still seems to be differences which the gnome-session handler is unable to handle and you can't use GNOME on Wayland properly anyway.

Take note that if Red Hat's patches for supporting NVIDIA's EGLStreams are fully tested and ship with GNOME 3.24, this could potentially be automatically resolved with GNOME 3.24. But for 3.22, it's something we have to live with still --> http://www.phoronix.com/scan.php?page=n … -EGLStream

On a side note, GNOME settings could also see patches that will work fine with Redshift on Wayland ---> https://bugzilla.gnome.org/show_bug.cgi?id=742149

This means that both my pet peeves with Wayland atm, will be resolved in GNOME 3.24 hopefully. I can live without relogging in or use GNOME on X11 but Redshift is a pain atm. You can switch tty and back for it to work but it has other bugs that cause it to be difficult to use atm (only with ForceFullCompositionPipeline enabled then you need to switch tty for it to work on X11. On Wayland, Redshift does not work at all unless you use a patched gnome-settings package which will soon be default in GNOME 3.24 likely).

Last edited by Cxpher (2017-02-07 14:48:04)

Offline

#9 2017-02-07 11:29:08

piedro
Member
Registered: 2013-04-11
Posts: 218

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

Thank you very much for the detailed information and the long post (serious wiki quality)!

As for the moment I use gnome with Xorg and now I have a reason to really look forward to 3.24!

Thanks again, cxpher,
cheers, p.

Offline

#10 2017-02-07 14:48:19

Cxpher
Member
Registered: 2016-06-05
Posts: 13

Re: [Solved] After I logout Gnome 3.22 I cannot login again...

piedro wrote:

Thank you very much for the detailed information and the long post (serious wiki quality)!

As for the moment I use gnome with Xorg and now I have a reason to really look forward to 3.24!

Thanks again, cxpher,
cheers, p.

You're welcome.

Offline

Board footer

Powered by FluxBB