1. When I reinstalled with "sh autorun.sh", I got two terminals and the
first one said:

bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ sh autorun.sh
# Option “-x” is deprecated and might be removed in a later version of 
gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after 
it.
bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ 

The Second Terminal executed the install as expected, see also
attachment.

2. When I uninstalled Virtual box with "sh VBoxLinuxAdditions.run uninstall" 
the problem disappeared. The boot and login were normal.
But the problem reappeared after a reinstall "sh VBoxLinuxAdditions.run".

3. I have upgraded the system from Ubuntu 20.04. After a while I noticed
that DOSBOX and Conky did not run anymore with wayland, so I moved back
to xorg through the menu in the login screen. According to "the
Internet", it is a known issue with Conky and DOSDOX.

Maybe switching from wayland to xorg caused the problem, but that menu
disappeared from the login screen, so I cant move back to wayland.


** Attachment added: "vbox-issue"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+attachment/5574845/+files/vbox-issue

-- 
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

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     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to