gdm issueshttps://gitlab.gnome.org/GNOME/gdm/-/issues2023-03-12T17:23:51Zhttps://gitlab.gnome.org/GNOME/gdm/-/issues/837For unknown reason not appears dropdown menu with list of sessions when I pre...2023-03-12T17:23:51ZMikhail GavrilovFor unknown reason not appears dropdown menu with list of sessions when I press to gear button.Description of problem:
For unknown reason not appears dropdown menu with list of sessions when I press to gear button. And gdm every time starting last selected session. I have two desktop PC one loads always Wayland session because las...Description of problem:
For unknown reason not appears dropdown menu with list of sessions when I press to gear button. And gdm every time starting last selected session. I have two desktop PC one loads always Wayland session because last was Wayland session and other loads X11 session because last was X11 session.
- I don't have nvidia gpu
```
❯ lspci -nn | grep VGA
0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0)
❯ glxinfo | grep Vendor
amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!
Vendor: AMD (0x1002)
```
- desktop session files are present in system
```
❯ ls -la /usr/share/xsessions
total 32
drwxr-xr-x. 1 root root 156 Mar 8 18:02 .
drwxr-xr-x. 1 root root 5100 Mar 9 01:51 ..
-rw-r--r--. 1 root root 8139 Feb 14 05:00 gnome-classic.desktop
-rw-r--r--. 1 root root 7617 Feb 14 05:00 gnome-classic-xorg.desktop
-rw-r--r--. 1 root root 7830 Mar 6 05:00 gnome.desktop
-rw-r--r--. 1 root root 7915 Mar 6 05:00 gnome-xorg.desktop
```
```
❯ systemctl status gdm
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Thu 2023-03-09 02:09:50 +05; 1min 21s ago
Main PID: 1448 (gdm)
Tasks: 4 (limit: 76760)
Memory: 5.9M
CPU: 279ms
CGroup: /system.slice/gdm.service
└─1448 /usr/sbin/gdm
Mar 09 02:09:50 secondary-ws systemd[1]: Starting gdm.service - GNOME Display Manager...
Mar 09 02:09:50 secondary-ws systemd[1]: Started gdm.service - GNOME Display Manager.
Mar 09 02:09:54 secondary-ws gdm[1448]: Gdm: GdmDisplay: Session never registered, failing
Mar 09 02:09:54 secondary-ws gdm[1448]: Gdm: GdmDisplay: Session never registered, failing
Mar 09 02:10:09 secondary-ws gdm-password][2258]: gkr-pam: unable to locate daemon control file
Mar 09 02:10:09 secondary-ws gdm-password][2258]: gkr-pam: stashed password to try later in open session
Mar 09 02:10:36 secondary-ws gdm[1448]: Gdm: Child process -1761 was already dead.
```
Version-Release number of selected component (if applicable):
```
# rpm -q gdm
gdm-43.0-7.fc39.x86_64
```
Demonstration:
![IMG_1500](/uploads/6588e0031bc499c52b185718de1991c9/IMG_1500.mp4)https://gitlab.gnome.org/GNOME/gdm/-/issues/591screen content left visible on lock in virtualbox2023-04-16T01:07:54ZLyndon Brownscreen content left visible on lock in virtualboxAfter the Gnome 3.36 update in Debian Sid, I've noticed that in a VirtualBox environment when the screen lock times out the screen content remains visible until you return and create some activity, at which point the screen content is th...After the Gnome 3.36 update in Debian Sid, I've noticed that in a VirtualBox environment when the screen lock times out the screen content remains visible until you return and create some activity, at which point the screen content is then immediately replaced with the lockscreen, i.e. it knows it should be locked but the actual lock screen is not shown until user activity occurs.
Host is also Debian Sid. VirtualBox version on host is 6.1.6-dsfg-2. VirtualBox guest version in VM is the same version.
The timeout length in the host happens to be significantly longer than that of the VM.
Before submitting this I made sure to check everything was up to date in both the host and the VM and rebooted the VM; I had the VM up with no applications running, and with the VM in a maximised (non-fullscreen) window. I timed things with a stopwatch, leaving the VM window in focus and did not touch the computer. After the lockscreen timeout of the VM passed with no lockscreen appearing, I continued waiting for the additional minutes until reaching the host lockscreen timeout, whereby the host started dimming the screen in activating its lockscreen. I then moved the cursor to cancel that which also caused an update of the in focus VM, triggering its screen content to be replaced with the lockscreen.https://gitlab.gnome.org/GNOME/gdm/-/issues/471After you switch to another session in GDM and try to login typing a wrong pa...2019-03-19T07:50:25ZStrangiatoAfter you switch to another session in GDM and try to login typing a wrong password, session selected in "gear menu" is revertedgdm 3.30.3 on Arch Linux
1. do logout
2. click on your user account
3. click on the gear icon aside "Enter" button and observe which session is currently selected
4. select another session
5. type a wrong password and press enter
6...gdm 3.30.3 on Arch Linux
1. do logout
2. click on your user account
3. click on the gear icon aside "Enter" button and observe which session is currently selected
4. select another session
5. type a wrong password and press enter
6. click on the gear icon again
Result: the selected session was reverted to the initially selected session
(observed in the step 3).
Expected: the session selected in the step 4 remains selected in the session menuhttps://gitlab.gnome.org/GNOME/gdm/-/issues/384Desktop is visible for a short time after resume from suspend (or opening lid...2023-10-16T17:37:27ZAaron HoneycuttDesktop is visible for a short time after resume from suspend (or opening lid) before lockingWhen you open the lid of the laptop after locking your system you can see the desktop and any applications and files that you have open for a few seconds before the time and date screen is shown. I've see this on Pop!_OS 18.04 and will t...When you open the lid of the laptop after locking your system you can see the desktop and any applications and files that you have open for a few seconds before the time and date screen is shown. I've see this on Pop!_OS 18.04 and will test Ubuntu 18.04 as well and report back.
Steps to recreate:
1. Lock computer and close lid
2. Open lid and see the screen flicker a few times showing the desktophttps://gitlab.gnome.org/GNOME/gdm/-/issues/172Ibus/anthy exposes password on lockscreen.2023-04-16T00:52:03ZBugzillaIbus/anthy exposes password on lockscreen.## Submitted by gli..@..ox.org
**[Link to original bug (#710357)](https://bugzilla.gnome.org/show_bug.cgi?id=710357)**
## Description
To reproduce:
1. install ibus-anthy, set up japanese-anthy.
2. `<special>`-space to switch to ja...## Submitted by gli..@..ox.org
**[Link to original bug (#710357)](https://bugzilla.gnome.org/show_bug.cgi?id=710357)**
## Description
To reproduce:
1. install ibus-anthy, set up japanese-anthy.
2. `<special>`-space to switch to japanese input (in my case, hiragana).
3. `<special>`-l to lock screen
4. start typing your user password to unlock. Your password is exposed.
I've marked this as major because a lockscreen is *really* not supposed to expose the password.https://gitlab.gnome.org/GNOME/gdm/-/issues/61Password field should be reset / cleared when re-locking the screen or at res...2023-04-16T01:02:23ZBugzillaPassword field should be reset / cleared when re-locking the screen or at resume when suspend is initiated from gdm## Submitted by François Michonneau
**[Link to original bug (#648900)](https://bugzilla.gnome.org/show_bug.cgi?id=648900)**
## Description
I realize that it's not something that is very likely to happen, but if you enter your login ...## Submitted by François Michonneau
**[Link to original bug (#648900)](https://bugzilla.gnome.org/show_bug.cgi?id=648900)**
## Description
I realize that it's not something that is very likely to happen, but if you enter your login information and then suspend the computer (before hitting enter), on resume the password information is still available and thus anybody with physical access to the computer can log in. It seems that it would be safe to clear the login information if suspend is initiated at the login screen.