I don't use a wayland session. Also on the first login screen the xorg
session has been selected in the menu. I understand vmwgfx is the
VMware Linux graphics driver also used by Virtualbox for exposing
3D/OpenGL/3D hardware acceleration to guest virtual machines. Switching
off 3D acceleration did not help.
Remains the fact that the problem only shows up in Ubuntu 22.04 and not
in Ubuntu 22.04; Ubuntu Mate 22.04 nor in any 20.04 version or in
Fedora 36 Beta also with Gnome 42.
Curious, do you have any cooperation with the VBox maintainers?
On Wed, 2022-04-06 at 02:35 +, Daniel van Vugt wrote:
> BertN45: The only error that stands out to me in your log is that the
> vmwgfx kernel driver keeps logging:
>
> kernel: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open
> channel.
>
> If that's the problem then it's a bug in the kernel (where the vmwgfx
> driver lives) and/or the hypervisor.
>
> Otherwise the log shows that the Wayland session starts successfully
> and
> tries to register itself with GDM. And 30 seconds later, GDM starts a
> Xorg session.
>
> ** Tags added: vmwgfx
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966786
Title:
login screen shown twice with VirtualBox Guest Additions
Status in gdm3 package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
The login screen is shown twice and I have to supply the password
twice. The system works normally afterwards. When I select auto-login
in the settings still one login screen is shown.
gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static)
Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited,
status=0/SUCCESS)
Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
Memory: 5.0M
CPU: 125ms
CGroup: /system.slice/gdm.service
└─1915 /usr/sbin/gdm3
mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]:
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125)
by (uid=0)
mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate
daemon control file
mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password
to try later in open session
mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]:
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by
(uid=0)
mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam:
gnome-keyring-daemon started properly and unlocked keyring
mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was
already dead.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 28 11:48:17 2022
InstallationDate: Installed on 2020-01-25 (793 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: gdm3
UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp