http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c1 --- Comment #1 from Guillaume GARDET --- /etc/sysconfig/displaymanager and /etc/gdm/custom.conf files are identical on x86_64 and aarch64. To make autologin work on aarch64, we must edit /etc/gdm/custom.conf and uncomment the following line which force the login screen to use Xorg: WaylandEnable=false -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c2 --- Comment #2 from Guillaume GARDET --- Created attachment 777999 --> http://bugzilla.opensuse.org/attachment.cgi?id=777999&action=edit journalctl log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c3 Oliver Kurz changed: What |Removed |Added ---------------------------------------------------------------------------- Blocker|--- |Yes CC| |okurz@suse.com --- Comment #3 from Oliver Kurz --- (In reply to Guillaume GARDET from comment #1)

/etc/sysconfig/displaymanager and /etc/gdm/custom.conf files are identical on x86_64 and aarch64.

To make autologin work on aarch64, we must edit /etc/gdm/custom.conf and uncomment the following line which force the login screen to use Xorg: WaylandEnable=false

I guess you could do that in the spec file of the package that owns this file, e.g. gdm, based on an arch-specific branch. Or require an additional fix-package which does this change? Have you checked for any upstream bugs describing this problem? Regarding the openQA test, as we have support for logging in users, e.g. see the use of the variable NOAUTOLOGIN, you might be able to detect the problem and workaround it in first_boot (or the helper function wait_boot) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c4 --- Comment #4 from Guillaume GARDET --- (In reply to Oliver Kurz from comment #3)

(In reply to Guillaume GARDET from comment #1)

...

/etc/sysconfig/displaymanager and /etc/gdm/custom.conf files are identical on x86_64 and aarch64.

To make autologin work on aarch64, we must edit /etc/gdm/custom.conf and uncomment the following line which force the login screen to use Xorg: WaylandEnable=false

I guess you could do that in the spec file of the package that owns this file, e.g. gdm, based on an arch-specific branch. Or require an additional fix-package which does this change? Have you checked for any upstream bugs describing this problem?

It is more a workaround than a fix. I did not find any upstream bug for this. Just an old openSUSE bug: https://bugzilla.suse.com/show_bug.cgi?id=1011356

Regarding the openQA test, as we have support for logging in users, e.g. see the use of the variable NOAUTOLOGIN, you might be able to detect the problem and workaround it in first_boot (or the helper function wait_boot)

Yes, I am testing an update of the first_boot test to record a soft failure for this bug, to be able to continue the tests. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c6 --- Comment #6 from Guillaume GARDET --- (In reply to Michal Srb from comment #5)

A sanity check: Does manual login work with WaylandEnable=true on AArch64?

With WaylandEnable=true on AArch64 I am able to login but loginctl still tell me that it is an X11 session.

It sounds strange that Wayland + AArch64 would somehow affect autologin. But it is fairly possible that it tries to do autologin, the session crashes and then it goes back to the login screen.

I noticed that login screen appears for 1 second, then a black screen for 1 second and the login screen appears again. It seems that login screen using Wayland is shown, crashes and the login screen using X11 is finally loaded. Is it possible? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c8 --- Comment #8 from Guillaume GARDET --- (In reply to Michal Srb from comment #7)

Please delete any ~/.xsession-errors* files in the home directory of the user that was supposed to be autologged-in, then reboot. When you get the login screen instead of the expected autologin, check if any such files were recreated. If yes, please attach them.

There is no such file. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c10 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mloviska@suse.com --- Comment #10 from Guillaume GARDET --- *** Bug 1102735 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c12 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #777999|0 |1 is obsolete| | --- Comment #12 from Guillaume GARDET --- Created attachment 779693 --> http://bugzilla.opensuse.org/attachment.cgi?id=779693&action=edit journalctl with virtio_gpu_dri.so installed The interesting part seems to be: gdm[1695]: gdm_session_handle_secret_info_query: assertion 'self->priv->user_verifier_interface != NULL' failed gdm-autologin][1723]: gkr-pam: couldn't get the password from user: Conversation error -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c14 --- Comment #14 from Guillaume GARDET --- I just tested ready to boot openSUSE-Tumbleweed-ARM-GNOME-raspberrypi3.aarch64-2018.08.13-Build.raw image on my Raspberry Pi 3 and when I enable autologin, it does work fine. On RPi3, loginctl states it uses X11. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[Build 20180722] openQA |GNOME autologin broken on |test fails to login in |aarch64 |first_boot, autologin | |broken on aarch64? | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c31 --- Comment #31 from Guillaume GARDET --- Anything to do to move forward? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c32 --- Comment #32 from Guillaume GARDET --- In the log there is: Failed to create backend: Could not find a primary drm kms device Whereas X uses a drm kms driver after Wayland failed. Is there any known incompatibilities with virtio-gpu-pci? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c34 --- Comment #34 from Guillaume GARDET --- (In reply to Guillaume GARDET from comment #33)

Maybe drm kms just load too late, as suggested here: https://nrhodes91.github.io/2018/11/25/archlinux-gnome-wayland-session/

I tried to force the load the drm/kms modules earlier and drm/kms is up after 3 seconds (vs 7 seconds previously), so way earlier before Wayland try to start. But it did not change anything. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c39 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #39 from Guillaume GARDET --- It is fixed in Tumbleweed 20190508. Snapshot 20190428 was still broken. I think there was an update regarding tty numbering in gnome wayland, but I cannot find it again. Maybe this is the update which fixed it? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1102563 http://bugzilla.opensuse.org/show_bug.cgi?id=1102563#c77 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |GNOME Version|Current |Leap 15.3 Product|openSUSE Tumbleweed |openSUSE Distribution Target Milestone|--- |Leap 15.3 --- Comment #77 from Guillaume GARDET --- Tumbleweed is fixed since a while, but Leap 15.3 is still affected. -- You are receiving this mail because: You are on the CC list for the bug.