login screen

English Install/Boot/Login
1

hi
I’m running Tumbleweed with Gnome,
after a “zypper dup” a week ago, wen I boot my system everything goes well until the login screen is shown, the screen in it self is like it was before but nothing works.
I do
crt+alt+f1, then login as user and then startx
the gnome session starts normally and everything works fine.

I’ve made all the updates after but the problem was not solved

It’s not a big problem just annoying, I searched in this forum but i find nothing
could anyone give me a suggestion ?

sorry for the bad English

thanks

2

Are you using gdm? https://en.wikipedia.org/wiki/GNOME_Display_Manager

less /etc/sysconfig/displaymanager
3

yes i am using GDM

4

Do you see any error messages in the journal?

journalctl -r

You could try installing ‘lightdm’ and see if it works.

5

This is due to a bug in Mesa

Hit Ctrl-Alt-F2 and login with username and password. Next do:


rm -rf ~/.cache
su -c 'rm -rf /var/lib/sddm/.cache'
su -c reboot
6

I don’t have sddm in my system, but i have tried those commands anyway, and it didn’t work

journalctl -r give me:

Feb 12 21:12:32 linux-w2ka.site su[6390]: pam_unix(su:session): session opened for user root by (uid=1000)Feb 12 21:12:32 linux-w2ka.site su[6390]: pam_systemd(su:session): Cannot create session: Already running in a session
Feb 12 21:12:32 linux-w2ka.site su[6390]: (to root) as on pts/0
Feb 12 21:12:32 linux-w2ka.site su[6390]: gkr-pam: couldn’t unlock the login keyring.
Feb 12 21:12:32 linux-w2ka.site su[6390]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyri
…
…
but I don´t if this is meaningful

7

I don’t have sddm in my system, but i have tried those commands anyway, and it didn’t work

journalctl -r give me:

Feb 12 21:12:32 linux-w2ka.site su[6390]: pam_unix(su:session): session opened for user root by (uid=1000)Feb 12 21:12:32 linux-w2ka.site su[6390]: pam_systemd(su:session): Cannot create session: Already running in a session
Feb 12 21:12:32 linux-w2ka.site su[6390]: (to root) as on pts/0
Feb 12 21:12:32 linux-w2ka.site su[6390]: gkr-pam: couldn’t unlock the login keyring.
Feb 12 21:12:32 linux-w2ka.site su[6390]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyri
…
…
but I don´t if this is meaningful

8

I suspect that you are describing Bug 1080015 Mouse unusable under Wayland

Maybe take a look at that bug report, and tell us if that is what you are seeing.

9

yes, you were right

if I use only the keyboard I can login from the login screen,
the mouse move the cursor but don’t click anything
strange because i don’t even use wayland

i will wait for solution to this bug

thankyou :wink:

10

You might like to add a comment to the bug report to indicate another user with that problem. Or you can just add yourself to the CC list, to get copies of email when the bug is updated.

Gnome defaults to Wayland, so you were using it. If you check comment #3 in the bug report, it indicates a small editing change you can make so that you use Xorg instead of Wayland. And then your system will work about the way it should.

11

thank you again
I will do it