[regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Chris A]

[ Description ]

Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only.

[ Test case ]

1. Boot to GDM
2. Click your username
3. Type the wrong password a couple of times, pressing enter after each time
4. Type the right password

If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure.

[ Fix ]

Marco and I worked upstream on this fix. We found out that there was a problem like this-

The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection.

For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed.

[ Regression potential ]

Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases.

[ Original report ]

WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again.

---

Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem.

I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console.

This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 22 20:31:13 2018
InstallationDate: Installed on 2018-04-22 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Maybe this is related to bug 1765261. Some people have suggested there are key repeat problems so if a key is getting unexpectedly repeated in bug 1765261 then that would count as an incorrect password.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[corrado venturini (corradoventu)]

Same problem on a fresh install from Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421)
updated today
corrado@corrado-p7-bb-0421:~$ inxi -Fx
System: Host: corrado-p7-bb-0421 Kernel: 4.15.0-15-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Gnome 3.28.1 (Gtk 3.22.30-1ubuntu1) Distro: Ubuntu Bionic Beaver (development branch)
Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017
CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
           clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
           version: 4.5 Mesa 18.0.0-rc5 Direct Render: Yes
Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.15.0-15-generic
Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86
Drives: HDD Total Size: 1000.2GB (1.4% used)
           ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB
Partition: ID-1: / size: 32G used: 5.3G (18%) fs: ext4 dev: /dev/sda7
           ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 40.5C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info: Processes: 243 Uptime: 12 min Memory: 1188.3/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.191) inxi: 2.3.56
corrado@corrado-p7-bb-0421:~$

[Daniel van Vugt (vanvugt)]

I think I might have hit this finally. The blank purple screen with a mouse cursor probably means the shell failed to start. And indeed I have no gnome-shell process running for my UID. The journalctl shows:

pr 23 14:33:47 haz gnome-shell[912]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

[Daniel van Vugt (vanvugt)]

Please try to log in to the machine via ssh first, and start monitoring the system log before reproducing the problem:

  journalctl -f

Then reproduce the bug (log in graphically) and let us know what the output from journalctl -f was at the time the bug occurred.

[Chris A (c-arderne)]

Here is the output from journalctl (extra spacing around probably the most interesting line). Also when I got back to the login screen, I very briefly saw a message under the password form saying 'Authentication error'.

/usr/lib/gdm3/gdm-x-session[1915]: (II) UnloadModule: "libinput"
/usr/lib/gdm3/gdm-x-session[1915]: (II) systemd-logind: releasing fd for 13:65
/usr/lib/gdm3/gdm-x-session[1915]: (II) UnloadModule: "libinput"
/usr/lib/gdm3/gdm-x-session[1915]: (II) systemd-logind: releasing fd for 13:69
/usr/lib/gdm3/gdm-x-session[1915]: (II) UnloadModule: "libinput"
/usr/lib/gdm3/gdm-x-session[1915]: (II) systemd-logind: releasing fd for 13:67
PackageKit[1352]: search-file transaction /372_adaeccdc from uid 1000 finished with success after 602ms
/usr/lib/gdm3/gdm-x-session[1915]: (II) Server terminated successfully (0). Closing log file.
gdm-password][1906]: pam_unix(gdm-password:session): session closed for user chris
gnome-shell[1128]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
systemd[1]: Starting Stop ureadahead data collection...
systemd[1]: Started Stop ureadahead data collection.

gdm-password][2437]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=chris

systemd-logind[904]: Removed session 4.
gdm-password][2440]: pam_unix(gdm-password:session): session opened for user chris by (uid=0)
systemd-logind[904]: New session 5 of user chris.
systemd[1]: Started Session 5 of user chris.
gnome-shell[1128]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
kernel: xhci_hcd 0000:39:00.0: remove, state 4
kernel: usb usb4: USB disconnect, device number 1
kernel: xhci_hcd 0000:39:00.0: USB bus 4 deregistered
kernel: xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
kernel: xhci_hcd 0000:39:00.0: remove, state 4
kernel: usb usb3: USB disconnect, device number 1
kernel: xhci_hcd 0000:39:00.0: Host halt failed, -19
kernel: xhci_hcd 0000:39:00.0: Host not accessible, reset failed.
kernel: xhci_hcd 0000:39:00.0: USB bus 3 deregistered
upowerd[1133]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb4/4-0:1.0
upowerd[1133]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-0:1.0
boltd[1351]: [d4030000-0092-XPS13 9360 ] removed (/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/domain0/0-0)
upowerd[1133]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3
boltd[1351]: [d4030000-0092-XPS13 9360 ] dbus: unexported
upowerd[1133]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb4

[Ads20000 (ads20000)]

I use persistent logging and got this (entered incorrect passwords and then the correct one, after the last message there's nothing for over 10 seconds (hanging on purple screen) and then I hard shutdown, I'm on a ThinkPad T430 with an SSD so it usually logs in very fast (and does when I get the password correct on the first attempt)).

[Ads20000 (ads20000)]

Sorry must've copypasted badly, here's a better version

[Ads20000 (ads20000)]

I think the relevant parts of the log are from 15:27:15.

I'm not sure how to get the full (unabbreviated) without SSH and I have no devices to use to SSH in unfortunately :(

[Ads20000 (ads20000)]

On Sebastien Bacher's request I've filed this upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/227

[Daniel van Vugt (vanvugt)]

NOTE: This bug is not about a login failure. Login is succeeding as shown in comment #7. It's only the shell that's failing to start:

gdm-password][2440]: pam_unix(gdm-password:session): session opened for user chris by (uid=0)
systemd-logind[904]: New session 5 of user chris.
systemd[1]: Started Session 5 of user chris.
gnome-shell[1128]: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

That is the same behaviour as I see.

Ads20000 might be experiencing something slightly different.

[Daniel van Vugt (vanvugt)]

For an actual authentication failure, please see bug 1765261 instead.

[Ads20000 (ads20000)]

Daniel thanks for your work here to try and get this filed correctly. If the logs are different for me and for this bug then perhaps my bug is different? Ray Strode (upstream) thinks the key part of my log is

```
Apr 23 17:43:40 adam-thinkpad-t430 gdm3[2997]: GdmSession: Emitting 'session-opened' signal
[...]
Apr 23 17:43:40 adam-thinkpad-t430 gdm3[2997]: GdmSession: external connection closed
```

Chris A, please could you (as Ray suggested to me) put `Enable=true` (without backticks (``)) in the `[debug]` section of `/etc/gdm/custom.conf`, reboot, reproduce and post the updated logs? Maybe then we'll be able to see if this issue is the same as mine or not (and if not then maybe Chris A's problem needs a separate upstream bug).

[Nafallo Bjälevik (nafallo)]

 Hi,

As discussed with duflu on irc, here are the steps I took to reproduce and produce a log:

 1. Enable debug in /etc/gdm3/custom.conf
 2. Reboot
 3. From other laptop; ssh wendigo journalctl -f
 4. Intentially login with a faulty password first, which made GDM just prompt as normal
 5. Login with the correct password, which caused the purple screen + mouse
 6. Copy the log up to this point
 7. Press a bunch of ctrl+alt+fn+f-key combos until I got back to login screen
 8. Login as normal, ctrl+c the SSH session and scp the file.

[Ads20000 (ads20000)]

I've added a workaround to the bug description (and to the upstream bug description), do comment if the workaround doesn't work for you :)

[Andrew Hayzen (ahayzen)]

To add more info, the following steps cause this issue on my machine and are reproducible.

- Start machine login to user A
- Logout of user A
- Try to login to user B
- Now have a purple display, need to use the cancel workaround (next login will work)

[Bart Van Rillaer (bartvr)]

Also often stuck at purple screen after login. Mouse cursor can still be moved around. Another workaround is switching to console and back using CTRL-F1/CTRL-F2/... In my logs I also see the
G_IS_DBUS_CONNECTION (connection) error.

[Joseph Maillardet (jokx)]

Same here with a 18.04 upgraded from 17.10

Workaround :
* Hitting Alt+F1 return to GDM who complain about a “login fail” and ask another time my password.
* Another successful password attempt finally launch Gnome correctly.

Side effect :
* Hitting Alt+F3,4,5,... give me ugly graphic mashup.

Try :
* Uncommenting the line bellow in /etc/gdm3/custom.conf file to use Xorg by default don't change anything :
#WaylandEnable=false

Note :
* The blanked screen is always GDM, I don't see the top menu-bar but clicking the right place show the GDM style system menu with only few option like shutdown button and no user sub-menu
* I not obtain blank purple screen but grey screen because I choose original Gnome CSS alternative...
`sudo update-alternatives --set gdm3.css /usr/share/gnome-shell/theme/gnome-shell.css`

[Zihang Ye (jerry-yezihang)]

I'm using a 18.04 upgraded from 17.10 and I have the same issue but slightly different.
The difference is that if I lock the screen for more than a certain amount of time, when I wake it up, I find myself logged out.
And to get away the blanked screen, I used Alt+F2 and then Alt+F1, and the gdm says "Authentication failed", which is quite similar to #19.
And I'm using gnome-session with Wayland.

[Daniel van Vugt (vanvugt)]

Joseph, Zihang, that is bug 1765261. Not this one.

Also, if you find yourself logged out unexpectedly, please look for crash files in /var/crash and report them using the 'ubuntu-bug' command.

Finally, if anyone is experiencing this particular bug then please help upstream to debug it here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/227

[gabriele (gigi-ga90)]

Had the same issue after a clean install of Ubuntu 18.04. After installing the proprietary drivers of the NVIDIA graphic card it did not happened again!

[Joseph Maillardet (jokx)]

Daniel, I don't encounter problem with first attempt if I enter the right password. I only encounter problem with second attempt _after_ a failed first attempt.

[Wayne Carr (blues72)]

I see the same thing as #17 (Andrew). I type in the password correctly each time. I login to a user (successfully, no errors) and then log out. After that, I login as a different user and I get the purple screen without the desktop showing. I typed the correct password. If I switch users leaving the first user still running (instead of logging that user out) the error does not happen. This happens on 3 different PCs that I've updated to 18.04.

[Davide (tarski10)]

Ads20000
The cancel button is not visible (purple screen),
your workaround is for another problem.
I think it's better to remove it from the bug description.

[coolhandlewk (thomaselewis)]

Davide

Ads2000 means to hit cancel before retyping your password. Hit cancel, then re-select user, then retype password, all before hitting enter... and hence the purple screen. I believe it's the same problem. This workaround works for me.

[Davide (tarski10)]

coolhandlewk
You are right, I misunderstood.
It works for me too, thanks.

[Sum Sim (draugr200)]

I have a kinda similar problem on xubuntu 18.04. And had that problem on xubuntu 16.04.

After I type the password, there is only desktop wallpaper and mouse pointer (it moves). Then I press Ctr-Alt-Del and go back to password screen again (screen resolution changes to low), then I enter password and suddenly all works, everything is upsie-daisy.

I believe it somehow connected to nvidia drivers. Under nvidia-384 it problem doesn't existed, but on nvidia-390 and 396 it does.

[Soham Dongargaonkar (a3y3)]

Confirmed, entering an incorrect password and then trying to log in with the correct one leads to a purple screen.

[Carterclan (carterclan)]

Sum Sim

Not sure it is the Nvidia driver, I have had the same problem on both the Nvidia-390 and the X-org Nouveau display driver.
There seems to be a lot of talk about error occurring with incorrect password input, this is inconsistent with my experience.
The best workaround I have seen so far is mentioned by Wayne Carr (above), rather than log-out when switching users, use the switch-user option. This obviously leaves all profiles active but the fault does not occur.

[Heikki Moisander (moisander)]

Work around does not work for. It is not about nvidia driver. Lets face it, it is a showstopper for ubuntu 18.04 until bug is fixed.

[daniel chagas (dchagas)]

Besides the login problem (wrong first attempt to login, then right password ,leads to a purple screen and nothing else happens) there is another problem when you are in gnome-shell if you issue ctrl-alt
f4 you cannot get back with ctrl-alt f7

[Daniel van Vugt (vanvugt)]

That's not a bug. There's nothing on F7.

Your session is on F2, and the login screen is F1.

[Arunachaleshwar k (starbug7)]

Is there a fix for this or not?. Please tell me there is -^-

[Daniel van Vugt (vanvugt)]

To monitor the latest news about a fix look at:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/227

And when that's available, we will update this bug with information about an Ubuntu fix.

[Marco Trevisan (Treviño) (3v1n0)]

It could be that fixing this would also fixes lp:1703300 https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1

[Ken Wilson (ken.wilson)]

I upgraded from Ubuntu 17.10 to 18.04 and all was fine for a couple weeks. I think an update yesterday (5/7) caused the problem. I have two accounts on the system. I can initially log into either fine but switching to the other causes the purple screen with cursor only. It does not matter if I log out of the first account or switch user, either way I have the problem. The password seems to be accepted fine. It seems that the windows don't start or start correctly.

I'm using an HP dv7-2043cl Notebook

[Tom F (n411303)]

Not on first login but on switch user after entering correct password I get purple screen and mouse.

Sometimes after a long delay I can get back to the login screen. I can usually force it back to the login screen by hitting a few random cycles of ctl+alt + F1, ctl+alt F2 and ctl+alt + F3.

At this point, if I click on the the user that failed it shows a message about authorization problem (but the password was correct). At login of this user it then allows access.

I know on subsequent logins it is going to fail as soon as I see the purple screen. If I see initial black, I know it is going to work OK.

I noticed this issue on an initial clean build on erased disks. Concerned about my hardware, I rebuilt again from clean and the problem is the same. I do not have a graphics card. I have: Intel® Core™ i7-4790 CPU @ 3.60GHz × 8. Ram = 24g.

[Bodinux (bodinux)]

The gnome bug is now here : <https://bugzilla.gnome.org/show_bug.cgi?id=795940>

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mark Kin (mgkubuntu)]

Exact same issue as Tom F.

Intel i7 920, 24gb ram and AMD graphics.

Upgraded from 17.10 and I get constant purple screen of death followed by something about an authentication failure, even though my password is fine.

[aeronutt (aeronutt)]

Same problem here. I can no longer log into 18.04. First password entry fails, then on second entry, I get purple screen with working mouse pointer. But hangs there. This has been an intermittent problem for me over the past few weeks, but today seems to be 100%.

[HouseSessions (koen-bulcke)]

Hi,

Being new around here, seen the high impact on a lot of users, is there anyway or chance that Canonical can set prio with GNOME or deliver the fix themselves to upstream?

thanks,
Koen.

[aeronutt (aeronutt)]

FYI, I (temporarily?) switched to SDDM, so far so good (although a bit cumbersome as delivered). It also allows Wayland sessions.

[Iain Lane (laney)]

Packages coming your way soon. They work for me/us, but please give confirmation/denial. There will be a message when they're accepted into bionic for testing.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdm3 - 3.28.0-0ubuntu2

---------------
gdm3 (3.28.0-0ubuntu2) cosmic; urgency=medium

  * debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
    debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
    Cherry-pick two patches from the 3.28 branch. These fix a refcounting bug
    in the GDM Client object, which had meant that the DBus connection was
    being disposed too early in some cases, particularly when logging in after
    a failed attempt. The symptom of that was that the system hung on a
    "blank" screen. (LP: #1766137)

 -- Iain Lane <email address hidden> Thu, 17 May 2018 11:56:14 +0100

[Brian Murray (brian-murray)]

Hello Chris, or anyone else affected,

Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.0-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Bodinux (bodinux)]

Tested this gdm3/3.28.0-0ubuntu1.1 from bionic-proposed.

Bad password entry followed by correct password entry works correctly.

I then tried to switch user, Bad password entry followed by correct password entry : screen with the grayed password box, nothing happening.
crtl-alt-f1, ctrl-alt-f2, log back to previous session ok
I then tried to switch user, correct password entry : screen with the grayed password box, nothing happening.
ctrl-alt-f1, ctrl-alt-f2, log back to previous session ok

(this might be another bug …?) but the test as I did failed.

[Daniel van Vugt (vanvugt)]

Bodinux,

It sounds like maybe you hit bug 1765261. That one will be fixed separately in gnome-shell 3.28.2.

[Davide (tarski10)]

gdm3/ 3.28.0-0-0ubuntu1.1
if I enter the wrong password once or twice and then I enter the correct password now I can access,
but if I enter the wrong password three times I return to the user choice screen and after clicking on my username and entering the correct password the screen freezes and nothing happens.
I can still shutdown or restart.

[Bodinux (bodinux)]

I could not reproduce what Davide (tarski10) did.

I enter the wrong password three times I return to the user choice screen and after clicking on my username and entering the correct password I could successfully login.

[Ken Wilson (ken.wilson)]

Brian,
I attempted to install the proposed package: 3.28.0-0ubuntu1.1 but it failed. Initially I thought it installed correct but when switching users I got a notification of a timeout and a package not installed. In the process of looking at the notification it went away and I don't know how to get it back. I have included the dpkg log below. I have reverted back to the standard release and things are working as they were.

NOTE: the install could be operator error.

DPKG Log
2018-05-18 07:53:27 startup archives unpack
2018-05-18 07:53:38 upgrade gdm3:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1
2018-05-18 07:53:38 status half-configured gdm3:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:38 status unpacked gdm3:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:38 status half-installed gdm3:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:38 status triggers-pending dbus:amd64 1.12.2-1ubuntu1
2018-05-18 07:53:38 status triggers-pending systemd:amd64 237-3ubuntu10
2018-05-18 07:53:38 status triggers-pending ureadahead:amd64 0.100.0-20
2018-05-18 07:53:39 status triggers-pending hicolor-icon-theme:all 0.17-2
2018-05-18 07:53:40 status triggers-pending man-db:amd64 2.8.3-2
2018-05-18 07:53:40 status half-installed gdm3:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1
2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1
2018-05-18 07:53:41 upgrade libgdm1:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1
2018-05-18 07:53:41 status triggers-pending libc-bin:amd64 2.27-3ubuntu1
2018-05-18 07:53:41 status half-configured libgdm1:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:41 status unpacked libgdm1:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:41 status triggers-pending libglib2.0-0:amd64 2.56.1-2ubuntu1
2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:41 status triggers-pending libglib2.0-0:i386 2.56.1-2ubuntu1
2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:42 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1
2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1
2018-05-18 07:53:42 upgrade gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1
2018-05-18 07:53:42 status half-configured gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:42 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:42 status half-installed gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:43 status half-installed gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1
2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1
2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1
2018-05-18 07:53:43 startup packages configure
2018-05-18 07:53:43 trigproc ureadahead:amd64 0.100.0-20 <none>
2018-05-18 07:53:43 status half-configured ureadahead:amd64 0.100.0-20
2018-05-18 07:53:44 status installed ureadahead:amd64 0.100.0-20
2018-05-18 07:53:44 trigproc libglib2.0-0:amd64 2.56.1-2ubuntu1 <none>
2018-05-18 07:53:44 status half-configured libglib2.0-0:amd64 2.56.1-2ubuntu1
2018-05-18 07:53:46 status installed...

[Heikki Moisander (moisander)]

I installed proposed updates. Now it freeze a bit earlier and even more
often. Login screen remain visible and no cursor movement while before in
looked like progressing with blank screen with cursor movement until final
freeze.

pe 18. toukok. 2018 klo 19.20 KenWilson (<email address hidden>)
kirjoitti:

> Brian,
> I attempted to install the proposed package: 3.28.0-0ubuntu1.1 but it
> failed. Initially I thought it installed correct but when switching users I
> got a notification of a timeout and a package not installed. In the process
> of looking at the notification it went away and I don't know how to get it
> back. I have included the dpkg log below. I have reverted back to the
> standard release and things are working as they were.
>
> NOTE: the install could be operator error.
>
> DPKG Log
> 2018-05-18 07:53:27 startup archives unpack
> 2018-05-18 07:53:38 upgrade gdm3:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:38 status half-configured gdm3:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:38 status unpacked gdm3:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:38 status half-installed gdm3:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:38 status triggers-pending dbus:amd64 1.12.2-1ubuntu1
> 2018-05-18 07:53:38 status triggers-pending systemd:amd64 237-3ubuntu10
> 2018-05-18 07:53:38 status triggers-pending ureadahead:amd64 0.100.0-20
> 2018-05-18 07:53:39 status triggers-pending hicolor-icon-theme:all 0.17-2
> 2018-05-18 07:53:40 status triggers-pending man-db:amd64 2.8.3-2
> 2018-05-18 07:53:40 status half-installed gdm3:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:41 upgrade libgdm1:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:41 status triggers-pending libc-bin:amd64 2.27-3ubuntu1
> 2018-05-18 07:53:41 status half-configured libgdm1:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:41 status unpacked libgdm1:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:amd64
> 2.56.1-2ubuntu1
> 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:i386
> 2.56.1-2ubuntu1
> 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:42 status half-installed libgdm1:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:42 upgrade gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1
> 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:42 status half-configured gir1.2-gdm-1.0:amd64
> 3.28.0-0ubuntu1
> 2018-05-18 07:53:42 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1
> 2018-05-18 07:53:42 status half-installed gir1.2-gdm-1.0:amd64
> 3.28.0-0ubuntu1
> 2018-05-18 07:53:43 status half-installed gir1.2-gdm-1.0:amd64
> 3.28.0-0ubuntu1
> 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1
> 2018-05-18 07:53:43 star...

[Marco Trevisan (Treviño) (3v1n0)]

Looks weird, can you attach the output of
  journalctl /usr/bin/gnome-shell

?

[Davide (tarski10)]

Bodinux

after clicking your name, wait a while before entering the correct password.

[Heikki Moisander (moisander)]

Not sure what came out but this is out come of running journalctl right
after booting after freeze.
I need clear guidance to get something else more relevant.

Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33
EE
huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic
(buildd@
huhti 27 22:06:06 ThinkPad-X301 kernel: Command line:
BOOT_IMAGE=/boot/vmlinuz-4
huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus:
huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel
huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD
huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls
huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations
huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE
huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM
map:
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x0000000000000000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x000000000009ec00-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000000dc000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x0000000000100000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd6a1000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd6a7000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd7b7000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd80f000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd8c7000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd8d2000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd8d5000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd8d9000-0x000
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000bd8dd000-0x000
lines 1-23...skipping...
-- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18
20:56:33 EEST. --
huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic
(buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
#21-Ubunt
huhti 27 22:06:06 ThinkPad-X301 kernel: Command line:
BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
root=UUID=bf89dfab-58a9-4161-a23c-18da35c20198 ro quie
huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus:
huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel
huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD
huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls
huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations
huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE
huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM
map:
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x0000000000000000-0x000000000009ebff] usable
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x000000000009ec00-0x000000000009ffff] reserved
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x00000000000dc000-0x00000000000fffff] reserved
huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
0x0000000000100000-0x000000...

[Heikki Moisander (moisander)]

sorry this is the out come of journalctl /usr/bin/gnome-shell

-- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18
21:03:51 EE
huhti 27 22:06:13 ThinkPad-X301 org.gnome.Shell.desktop[762]: glamor: EGL
versio
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:17 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]: Error looking up
permission: G
huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]:
nma_mobile_providers_database_
huhti 27 22:06:20 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: Telepathy is not
available, c
huhti 27 22:06:49 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[/usr/share/gnome
huhti 27 22:06:54 ThinkPad-X301 gnome-shell[1812]:
[AppIndicatorSupport-DEBUG] R
huhti 27 22:06:56 ThinkPad-X301 gnome-shell[1812]: Object St.BoxLayout
(0x561a90
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: == Stack
trace fo
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #0
0x7ffff3031450
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #1
0x7ffff30314b0
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #2
0x7ffff3031580
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #3
0x7ffff30315f0
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4
0x561a8f6df7a0

pe 18. toukok. 2018 klo 21.01 Heikki Moisander (<email address hidden>)
kirjoitti:

> Not sure what came out but this is out come of running journalctl right
> after booting after freeze.
> I need clear guidance to get something else more relevant.
>
> Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33
> EE
> huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic
> (buildd@
> huhti 27 22:06:06 ThinkPad-X301 kernel: Command line:
> BOOT_IMAGE=/boot/vmlinuz-4
> huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus:
> huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel
> huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD
> huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls
> huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations
> huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE
> huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM
> map:
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x0000000000000000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x000000000009ec00-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000000dc000-0x000
> huhti 27 22:06:06 ThinkPad-X30...

[Heikki Moisander (moisander)]

Really sorry about spamming, but I only now figured out how to get output
from relevenant time ( I hope)
                                                  getUniqueBusNameSync@
/usr/share/gnome-shell/extensions/
<email address hidden>/util.js:58:20

 traverseBusNames/<@/usr/share/gnome-shell/extensions/
<email address hidden>/util.js:82:34
touko 18 20:53:49 ThinkPad-X301 gnome-shell[1490]: Error looking up
permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.fre
touko 18 20:53:50 ThinkPad-X301 gnome-shell[1490]:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient
disconnected from message bus with
touko 18 20:53:53 ThinkPad-X301 gnome-shell[1490]: GNOME Shell started at
Fri May 18 2018 20:53:45 GMT+0300 (EEST)
touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: Some code accessed the
property 'getUniqueBusNameSync' on the module 'util'. That property was
defin
touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]:
[AppIndicatorSupport-DEBUG] Registering StatusNotifierItem
:1.70/StatusNotifierItem
touko 18 20:53:58 Thin
getUniqueBusNameSync@/usr/share/gnome-shell/extensions/
<email address hidden>/util.js:58:20

 traverseBusNames/<@/usr/share/gnome-shell/extensions/
<email address hidden>/util.js:82:34
touko 18 20:53:49 ThinkPad-X301 gnome-shell[1490]: Error looking up
permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.fre
touko 18 20:53:50 ThinkPad-X301 gnome-shell[1490]:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient
disconnected from message bus with
touko 18 20:53:53 ThinkPad-X301 gnome-shell[1490]: GNOME Shell started at
Fri May 18 2018 20:53:45 GMT+0300 (EEST)
touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: Some code accessed the
property 'getUniqueBusNameSync' on the module 'util'. That property was
defin
touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]:
[AppIndicatorSupport-DEBUG] Registering StatusNotifierItem
:1.70/StatusNotifierItem
touko 18 20:53:58 ThinkPad-X301 gnome-shell[1490]: Some code accessed the
property 'refreshPropertyOnProxy' on the module 'util'. That property was
def
touko 18 20:54:08 ThinkPad-X301 gnome-shell[1490]: JS WARNING:
[resource:///org/gnome/shell/ui/endSessionDialog.js 763]: reference to
undefined propert
touko 18 20:54:11 ThinkPad-X301 gnome-shell[1490]: gnome-shell: Fatal IO
error 0 (Onnistui) on X server :0.
-- Reboot --
touko 18 20:55:42 ThinkPad-X301 org.gnome.Shell.desktop[934]: glamor: EGL
version 1.4 (DRI2):
touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING:
[resource:///org/gnome/shell/ui/main.js 340]: reference to undefined
property "MetaStage"
touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING:
[resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined
property "MetaWind
touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING:
[resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to
undefined property
touko 18 20:55:45 ThinkPad-X301 gnome-shell[934]: JS WARNING:
[resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined
property "CallyActo
touko 18 20:55:46 ThinkPad-X301 gnome-shell[934]: Unable to connect to
ibu...

[Bodinux (bodinux)]

Following #51 and #56 from Davide (tarski10)

I was able to reproduce. *<Some comments added>*.

gdm3/ 3.28.0-0-0ubuntu1.1
if I enter the wrong password once or twice and then I enter the correct password now I can access,
but if I enter the wrong password three times I return to the user choice screen and after clicking on my username *<and waiting a few seconds>* and entering the correct password the screen freezes *<with my login visible>* and nothing happens

*<I can move my mouse, select characters in password box, doing the ctrl-alt-F1 / ctrl-alt-f2 trick doesn't help, reboot needed>*

[Ken Wilson (ken.wilson)]

As requested I have attached the result. Hopefully this posts in the bug
list, not sure?

Ken

On 05/18/2018 10:25 AM, Marco Trevisan (Treviño) wrote:
> Looks weird, can you attach the output of
> journalctl /usr/bin/gnome-shell
>
> ?
>

--
*Ken Wilson*
forest

[Jehandan Jeyaseelan (jehanjey)]

I have tested the login process as follows:

a) Install gdm3 from bionic-proposed version 3.28.0-0ubuntu1.1 - in Ubuntu 18.04 LTS and reboot.
b) When login screen appears, click on my username and enter incorrect password.
c) Enter correct password and press enter or click on sign in. Login successful.

However I have encountered the following issue:

a) Log out of Ubuntu 18.04 LTS.
b) Click on my username and enter my password correctly to login again and click on sign in or press enter.

The login prompt freezes, cannot click on cancel or the signin button. When I click on the button to perform a restart or shutdown, it indicates that I am still logged in therefore there appears to be an issue logging out.

I also confirm that the issue as reported by Bodlinux in post #60 also occurs exactly as described.

In this case clicking on the button to perform a restart or shutdown indicates that I am logged in but haven't moved past the login screen to the desktop so again an issue there.

I have only installed the gdm3 update from bionic-proposed, do we need additional updates in order for the login system to be tested properly or will the gdm3 update suffice?

[Daniel van Vugt (vanvugt)]

I have verified this bug is fixed on bionic using version 3.28.0-0ubuntu1.1

However I have also verified what the above comments allude to, in that there are also other login bugs we will need to deal with later.

[Daniel van Vugt (vanvugt)]

Hmm, actually it is arguably worse with version 3.28.0-0ubuntu1.1

The problem with that version is that you can't log in more than once without encountering a new login screen freeze, that is unlike this one.

Not sure if we want to continue with version 3.28.0-0ubuntu1.1 and deal with that separately or call it a blocker.

[Jehandan Jeyaseelan (jehanjey)]

Following on from post #62:

According to Bodinux's post and my testing, the login hang is reproducible and I was able to replicate the issue every time I tested it. It sounds like the login and logout process is working but not processing properly.

[Jehandan Jeyaseelan (jehanjey)]

I am thinking that the fix has resulted in more issues than before therefore I call it a blocker (due to increased issues). The fix needs further testing and development.

[Iain Lane (laney)]

This is what the testing procedure is for. Marco is going to take a further look, thanks.

[sacredwow (mesquunclub)]

It seems 3.28.0-0ubuntu1.1 isn't help to us. Now instead blank screen with cursor we get hung after password entered and even Alt+Ctrl+F2 / Alt+Ctrl+F1 can't help.

[merinodanilo (merinodanilo)]

Hi,
I just fix the problem uninstalling the gnome extension "Workspace to Dock". Because i couldnt use my mouse and keyboard in the desktop i change to TTY with ctl+alt+F3 and remove that extension.

# rm -f -r $HOME/.local/share/gnome-shell/extensions/<NAME_EXTENSION>

or

# sudo rm -f -r /usr/local/share/gnome-shell/extensions/<NAME_EXTENSION>

Then

# gnome-shell --replace

After that didnt work so I reboot it, and it work.

I found this, because the problem appears to me after a fresh install and installing some softwares, so i rebooted everytime i install mayor software, or software that could modify the desktop. After a bunch I install all the gnome extension i like and after a reboot the problem appear.

The instructions for uninstalling an extension was found here: http://bernaerts.dyndns.org/linux/76-gnome/345-gnome-shell-install-remove-extension-command-line-script

Let me know if this helps you.

Regards

[dualshock3nerd (dualshock3nerd)]

I just found out yesterday that, if you enable auto-login, gdm never hangs like this anymore.

This is kinda bad for security and debugging/testing but hopefully it can still be of use to someone until this bug gets fixed.

Also this is not related to bad gnome extensions as, on my machine, gdm still got stuck on a purple screen with no local extensions installed.

[Daniel van Vugt (vanvugt)]

Does anyone feel like logging a new bug for the regression in 3.28.0-0ubuntu1.1/3.28.0-0ubuntu2 ?

It's a real bug now, since 3.28.0-0ubuntu2 was released in cosmic.

[Sum Sim (draugr200)]

When are you gonna fix this bug? It says "Fix committed", but the bug is still exist. I can't login to my Xubuntu like a month already!

[Ads20000 (ads20000)]

The fix was committed but 'verification-failed-bionic' which means that it didn't work well enough. We have to wait for the developers to come up with a better fix, and there's no ETA on that, unless you're a developer yourself and know how to fix the issue we just have to wait. It's not ideal but _there's nothing else we can do_, we just have to click Cancel after entering an incorrect password and retrying for now :)

[Ads20000 (ads20000)]

Oh, nothing else we can do short of ensuring others affected mark themselves as affected so the bug heat is increased even further (which demonstrates how serious the issue is without leaving impatient comments!) :)

[calvin (jcalvin)]

Sorry for my English, I'm French, this is a google translation of what I mean.

@ Ads20000 (ads20000)
The problem is more complicated than that. When we enter our password and we validate it, we sometimes end up with a purple screen without cancel button visible, the only possibility is to do "crtl + Alt + F1 then crtl + alt + F2 to find GDM

[Marco Trevisan (Treviño) (3v1n0)]

So, fix for this is actually in the upstream branch [1]. And that's handled in gdm 3.28.1, so we should rebase on that in order to fix this.

[1] https://gitlab.gnome.org/GNOME/gdm/commit/85a68ab14aad3d83abe1317d0c067f4d80a4dc82

[Marco Trevisan (Treviño) (3v1n0)]

Ops, sorry... Pasted the wrong commit, the right one is https://gitlab.gnome.org/GNOME/gdm/commit/4085d689

That's already included in gdm 3.28.1

[Daniel van Vugt (vanvugt)]

Marco,

It sounds like you're talking about the secondary bug. So let's reopen the cosmic task, awaiting that second fix. Cosmic presently has gdm3 3.28.0-0ubuntu2.

[Heikki Moisander (moisander)]

Mostly I don't understand this discussion and probably I should not take
part in it. There has been no progress visible to me. The bug I reported
was assigned as duplicate to this, so if this is now fixed, should I report
the bug again?

Anyhow it appears to me, that to ordinary users sharing the PC, 18.04 is
useless without changing back to lightdm (I hope that still works after
latest development.) In practice that is not an option to most basic users,
so going back to 16.04 or another distro is likely the choice. I am
confused after reading all this development discussion. I would assume this
is being fixed, but getting worried.

ti 29. toukok. 2018 klo 5.05 Daniel van Vugt (<email address hidden>)
kirjoitti:

> Marco,
>
> It sounds like you're talking about the secondary bug. So let's reopen
> the cosmic task, awaiting that second fix. Cosmic presently has gdm3
> 3.28.0-0ubuntu2.
>
> ** Changed in: gdm3 (Ubuntu)
> Status: Fix Released => In Progress
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
> [regression] Password accepted but login fails (blank purple screen
> and mouse pointer only)
>
> Status in gdm:
> Fix Released
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in gdm3 package in Ubuntu:
> In Progress
> Status in gnome-shell package in Ubuntu:
> Invalid
> Status in gdm3 source package in Bionic:
> In Progress
> Status in gnome-shell source package in Bionic:
> Invalid
>
> Bug description:
> [ Description ]
>
> Due to a refcounting bug, a GDBusConnection was getting disposed when
> it was still required. The symptom of this was that you couldn't log
> in on the second attempt if you'd got your password wrong on the first
> attempt. All you'd see is a blank purple screen and mouse pointer
> only.
>
> [ Test case ]
>
> 1. Boot to GDM
> 2. Click your username
> 3. Type the wrong password a couple of times, pressing enter after each
> time
> 4. Type the right password
>
> If the bug is happening, after 4. the system hangs at a blank screen
> with the mouse cursor. If you then switch to a VT or otherwise connect
> to the machine, you can examine the journal and you'll see a
> G_IS_DBUS_CONNECTION failure.
>
> [ Fix ]
>
> Marco and I worked upstream on this fix. We found out that there was a
> problem like this-
>
> The GdmClient has a shared GDBusConnection for its operations. The
> first time someone calls for it, it is created and stored in the
> object's private structure. Subsequent calls return *a new reference*
> to this same object. It turned out that the asynchronous method to get
> the connection was accidentally unreferencing its object before giving
> it to the caller if it was returning an already-existing connection.
>
> For this to work properly, we need to nullify the pointer we stored
> when the connection goes away, so we know when to make a new one.
> There were some cases where we didn't add the weak references required
> to do that. Those are also fixed.
>
> [ Regression potential ]
>
> Now we share...

[Daniel van Vugt (vanvugt)]

Yes, a fix is coming but not released yet. Apparently the fix is in gdm3 version 3.28.1.

[Łukasz Zemczak (sil2100)]

Hello Chris, or anyone else affected,

Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Heikki Moisander (moisander)]

heikki@ThinkPad-X301:~$ apt-cache policy gdm3
gdm3:
  Asennettu: 3.28.2-0ubuntu1.1
  Ehdokas: 3.28.2-0ubuntu1.1
  Versiotaulukko:
 *** 3.28.2-0ubuntu1.1 500
        500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
        100 /var/lib/dpkg/status
     3.28.0-0ubuntu1 500
        500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

I seem to have fixed version now. It does not work for me any different
from the previous version. Nothing happens while trying to change user or
log in with different user account. After trying I can get back to login
screen but then only way to login is boot.

ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (<email address hidden>)
kirjoitti:

> Hello Chris, or anyone else affected,
>
> Accepted gdm3 into bionic-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance!
>
> ** Changed in: gdm3 (Ubuntu Bionic)
> Status: In Progress => Fix Committed
>
> ** Tags removed: verification-failed-bionic
> ** Tags added: verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
> [regression] Password accepted but login fails (blank purple screen
> and mouse pointer only)
>
> Status in gdm:
> Fix Released
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in gdm3 package in Ubuntu:
> In Progress
> Status in gnome-shell package in Ubuntu:
> Invalid
> Status in gdm3 source package in Bionic:
> Fix Committed
> Status in gnome-shell source package in Bionic:
> Invalid
>
> Bug description:
> [ Description ]
>
> Due to a refcounting bug, a GDBusConnection was getting disposed when
> it was still required. The symptom of this was that you couldn't log
> in on the second attempt if you'd got your password wrong on the first
> attempt. All you'd see is a blank purple screen and mouse pointer
> only.
>
> [ Test case ]
>
> 1. Boot to GDM
> 2. Click your username
> 3. Type the wrong password a couple of times, pressing enter after each
> time
> 4. Type the right password
>
> If the bug is happening, after 4. the system hangs at a blank screen
> with the mouse cursor. If you then switch to a VT o...

[Heikki Moisander (moisander)]

Sorry I commented too quickly below after first tryout. After couple of
boots and tryouts it did finally succeed after longer wait time and now
after testing some 5 times I have managed to log with different user after
loging out. it is slow, but it will get there. So certainly I see good
progress, looks better now.

ti 29. toukok. 2018 klo 22.47 Heikki Moisander (<email address hidden>)
kirjoitti:

> heikki@ThinkPad-X301:~$ apt-cache policy gdm3
> gdm3:
> Asennettu: 3.28.2-0ubuntu1.1
> Ehdokas: 3.28.2-0ubuntu1.1
> Versiotaulukko:
> *** 3.28.2-0ubuntu1.1 500
> 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 3.28.0-0ubuntu1 500
> 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
>
> I seem to have fixed version now. It does not work for me any different
> from the previous version. Nothing happens while trying to change user or
> log in with different user account. After trying I can get back to login
> screen but then only way to login is boot.
>
> ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (<email address hidden>)
> kirjoitti:
>
>> Hello Chris, or anyone else affected,
>>
>> Accepted gdm3 into bionic-proposed. The package will build now and be
>> available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1
>> in a few hours, and then in the -proposed repository.
>>
>> Please help us by testing this new package. See
>> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
>> to enable and use -proposed.Your feedback will aid us getting this
>> update out to other Ubuntu users.
>>
>> If this package fixes the bug for you, please add a comment to this bug,
>> mentioning the version of the package you tested and change the tag from
>> verification-needed-bionic to verification-done-bionic. If it does not
>> fix the bug for you, please add a comment stating that, and change the
>> tag to verification-failed-bionic. In either case, without details of
>> your testing we will not be able to proceed.
>>
>> Further information regarding the verification process can be found at
>> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
>> advance!
>>
>> ** Changed in: gdm3 (Ubuntu Bionic)
>> Status: In Progress => Fix Committed
>>
>> ** Tags removed: verification-failed-bionic
>> ** Tags added: verification-needed-bionic
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1768619).
>> https://bugs.launchpad.net/bugs/1766137
>>
>> Title:
>> [regression] Password accepted but login fails (blank purple screen
>> and mouse pointer only)
>>
>> Status in gdm:
>> Fix Released
>> Status in Release Notes for Ubuntu:
>> Fix Released
>> Status in gdm3 package in Ubuntu:
>> In Progress
>> Status in gnome-shell package in Ubuntu:
>> Invalid
>> Status in gdm3 source package in Bionic:
>> Fix Committed
>> Status in gnome-shell source package in Bionic:
>> Invalid
>>
>> Bug description:
>> [ Description ]
>>
>> Due to a refcounting bug, a GDBusConnection was getting disposed when
>> it was still required. The symptom of this w...

[Marco Trevisan (Treviño) (3v1n0)]

Ah, thanks for saying that since I was testing in my other machine and wasn't unable to reproduce this anymore...
My second user has no password set, but there's no much difference in terms of the issue.

[Jehandan Jeyaseelan (jehanjey)]

Hi I tested gdm3 - 3.28.2-0ubuntu1.1 on Ubuntu 18.04 LTS.

I ran the following tests:

a) Boot Ubuntu 18.04 LTS, attempt login with correct password - pass.
b) Log out and then log back in with correct password - pass.
c) Log out and then enter the wrong password a few times then enter the correct password press enter to login - pass.
d) Reboot Ubuntu 18.04 LTS, enter the wrong password a few times then enter the correct password, press enter to login - pass.
e) Login then allow the screen to blank, attempt unlock with correct password - pass.
f) Login then allow the screen to blank, attempt unlock with wrong password then enter correct password and press enter - pass.
g) Click on the lock button, attempt unlock with incorrect password a few times then enter correct password and press enter - pass.
h) Click on the lock button, attempt unlock with correct password - pass.

Fix therefore works now and appears to have no issues so far.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdm3 - 3.28.2-1ubuntu1

---------------
gdm3 (3.28.2-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian. Remaining changes:
    + README.Debian: update for correct paths in Ubuntu
    + control.in:
      - Don't recommend desktop-base
      - Depend on bash for ubuntu_config_error_dialog.patch
      - Update Vcs field
    + rules:
      - Don't override default user/group
      - --enable-gdm-xsession to install upstream Xsession script
      - override dh_installinit with --no-start to avoid session being killed
    + rules, README.Debian, gdm3.8.pod:
      Use upstream custom.conf instead of daemon.conf
    + gdm3.{postinst,postrm}: rename user and group back to gdm
    + gdm3.postinst: don't kill gdm on upgrade
    + gdm3.*.pam: Make pam_env read ~/.pam_environment (LP: #952185)
    + gdm3.install:
      - Stop installing default.desktop. It adds unnecessary clutter
        ("System Default") to the session chooser.
      - Don't install debian/Xsession
    + Add ubuntu_run_xsession.d.patch
    + Add ubuntu_xresources_is_a_dir.patch
      - Fix loading from /etc/X11/Xresources/*
    + Add ubuntu_nvidia_prime.patch:
      - Add hook to run prime-offload (as root) and prime-switch if
        nvidia-prime is installed (LP: #1262068)
    + Add revert_override_LANG_with_accountservices.patch:
      - On Ubuntu accountservices only stores the language and not the
        full locale as needed by LANG.
    + Add ubuntu_dont_set_language_env.patch:
      - Don't run the set_up_session_language() function, since it
        overrides variable values set by ~/.pam_environment (LP: #1662031)
    + Add ubuntu_config_error_dialog.patch:
      - Show warning dialog in case of error in ~/.profile etc. and
        don't let a syntax error make the login fail (LP: #678421).
    + Add debian/default.pa
      - Disable Bluetooth audio devices in PulseAudio from gdm3.
    + debian/gdm3.install
      - Added details of the default.pa file
    + debian/gdm3.postinst
      - Added installation of default.pa and creation of dir if it doesn't
        exist.
  * Dropped changes:
    + Changes related to the transition from lightdm to gdm3 by default. This
      was across an LTS cycle now.
    + debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
      debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
      These are included in this upstream release.
  * We think this is going to fix the "can't login after wrong password" bug
    for real this time. (LP: #1766137)

gdm3 (3.28.2-1) unstable; urgency=medium

  * New upstream release 3.28.2
    - Reference counting fixes for GdmClient
    - ensure plymouth is quit properly even when local greeter is disabled
    - make sure GDM doesn't hang when called with unknown command line arguments

gdm3 (3.28.1-1) unstable; urgency=medium

  * New upstream release

gdm3 (3.28.0-1) unstable; urgency=medium

  * New upstream release
  * Have libgdm-dev depend on libglib2.0-dev
  * Release to unstable

 -- Iain Lane <email address hidden> Tue, 29 May 2018 12:03:39 +0100

[Ken Wilson (ken.wilson)]

All,
My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password issue; however, it creates a new issue. As such I don’t think this update should be released.

I installed gdm3 3.28.0-0ubuntu1.1 and rebooted my system (Ubuntu 18.04 LTS). Making sure I typed the password correct I was able to login to each account on the system. I then logged out and performed the following steps to ensure the password issue was resolved.

For two accounts I performed the following steps three times for each. Each time succeeded.

    1. I typed a bad password and pressed enter. I did this two times. Each time I was returned to the login screen and received a message the login didn’t work.
    2. I then typed a correct password and successfully logged in.
    3. I then locked the screen and performed steps one and two and each time it worked as it should.
    4. I then logged out of the account and performed steps one and two and each time it worked as it should.
Based on this testing I would say recovering from a bad password is fixed.

The next test I performed was to login into one account and then switch to the other account. I was able to successfully switch to the other account. I then tried to switch back to the first account but I was never able to successfully switch back. I tried it at least six times and in no case did it work. It did not matter which account I logged into first I was never able to switch to the other then switch back. In each case when I switched the second time the system hung and I could not find a way to recover. I tried CTRL+ALT+F2, CTRL+ALT+F1, CTRL+ALT+F2 but there was still unable to login. I was not able to login to any account even when being extremely careful the password was correct.

I then reinstalled gdm3 3.28.0-0ubuntu1 and tried switching between accounts. As long as I ensure I type the password correct I can switch between accounts multiple times without issue. If I type an incorrect password I can do CTR+ALT+F2, CTRL+ALT+F1, CTRL+ALT+F2 to recover.

With package gdm3 3.28.0-0ubuntu1.1 the only way I was able to regain control (after trying to switch accounts a second time) was with a system reboot. To me, having to reboot is a catastrophic failure and therefor this package should not be released.

[Iain Lane (laney)]

On Wed, May 30, 2018 at 03:45:17PM -0000, KenWilson wrote:
> All,
> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect
> password issue; however, it creates a new issue. As such I don’t think
> this update should be released.

That verison is superseded by 3.28.2-0ubuntu1.1. Please try this one.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

[Ken Wilson (ken.wilson)]

I installed package 3.28.2-0ubuntu1.1 and performed the testing again. I
restricted testing to only switching between accounts. Same result, it
did not work.

Listing... Done
gdm3/bionic-proposed,now 3.28.2-0ubuntu1.1 amd64 [installed]
gdm3/bionic 3.28.0-0ubuntu1 amd64

After installation I rebooted my system. I successfully logged into
“account A”. I successfully switched to “account B”. I then tried to
switch back to “account A” but was not successful. I am stuck at the
login screen. I cannot login to either “account A” or “account B”. I had
to reboot to gain control of my system.

Ken

On 05/30/2018 09:06 AM, Iain Lane wrote:
> On Wed, May 30, 2018 at 03:45:17PM -0000, KenWilson wrote:
>> All,
>> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect
>> password issue; however, it creates a new issue. As such I don’t think
>> this update should be released.
> That verison is superseded by 3.28.2-0ubuntu1.1. Please try this one.
>

--
*Ken Wilson*
lake

[Heikki Moisander (moisander)]

Did you test : 3.28.2-0ubuntu1.1 ?
I thought that is The version having The fix

ke 30. toukokuuta 2018 klo 18.51 KenWilson <email address hidden>
kirjoitti:

> All,
> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password
> issue; however, it creates a new issue. As such I don’t think this update
> should be released.
>
> I installed gdm3 3.28.0-0ubuntu1.1 and rebooted my system (Ubuntu 18.04
> LTS). Making sure I typed the password correct I was able to login to
> each account on the system. I then logged out and performed the
> following steps to ensure the password issue was resolved.
>
> For two accounts I performed the following steps three times for each.
> Each time succeeded.
>
> 1. I typed a bad password and pressed enter. I did this two times.
> Each time I was returned to the login screen and received a message the
> login didn’t work.
> 2. I then typed a correct password and successfully logged in.
> 3. I then locked the screen and performed steps one and two and each
> time it worked as it should.
> 4. I then logged out of the account and performed steps one and two
> and each time it worked as it should.
> Based on this testing I would say recovering from a bad password is fixed.
>
> The next test I performed was to login into one account and then switch
> to the other account. I was able to successfully switch to the other
> account. I then tried to switch back to the first account but I was
> never able to successfully switch back. I tried it at least six times
> and in no case did it work. It did not matter which account I logged
> into first I was never able to switch to the other then switch back. In
> each case when I switched the second time the system hung and I could
> not find a way to recover. I tried CTRL+ALT+F2, CTRL+ALT+F1, CTRL+ALT+F2
> but there was still unable to login. I was not able to login to any
> account even when being extremely careful the password was correct.
>
> I then reinstalled gdm3 3.28.0-0ubuntu1 and tried switching between
> accounts. As long as I ensure I type the password correct I can switch
> between accounts multiple times without issue. If I type an incorrect
> password I can do CTR+ALT+F2, CTRL+ALT+F1, CTRL+ALT+F2 to recover.
>
> With package gdm3 3.28.0-0ubuntu1.1 the only way I was able to regain
> control (after trying to switch accounts a second time) was with a
> system reboot. To me, having to reboot is a catastrophic failure and
> therefor this package should not be released.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
> [regression] Password accepted but login fails (blank purple screen
> and mouse pointer only)
>
> Status in gdm:
> Fix Released
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in gdm3 package in Ubuntu:
> Fix Released
> Status in gnome-shell package in Ubuntu:
> Invalid
> Status in gdm3 source package in Bionic:
> Fix Committed
> Status in gnome-shell source package in Bionic:
> Invalid
>
> Bug description:
> [ Description ]
>
> Due to a refcounting bug, a GDBusConnection ...

[Heikki Moisander (moisander)]

I had similar experience yesterday after installing 3.28.2 and I reported
that it does not work. But after couple of boots I have been testing every
now and then maybe some 15 times and every time it has logged in - very
slowly but success anyway. To me that is quite clear that any kind of
success is better that need to boot every time. It is not about speed, but
we can not accept the situation user get frozen screen every time login in
after someone else. So if anything better is not available please take this
into production.

ke 30. toukokuuta 2018 klo 20.11 KenWilson <email address hidden>
kirjoitti:

> I installed package 3.28.2-0ubuntu1.1 and performed the testing again. I
> restricted testing to only switching between accounts. Same result, it
> did not work.
>
> Listing... Done
> gdm3/bionic-proposed,now 3.28.2-0ubuntu1.1 amd64 [installed]
> gdm3/bionic 3.28.0-0ubuntu1 amd64
>
> After installation I rebooted my system. I successfully logged into
> “account A”. I successfully switched to “account B”. I then tried to
> switch back to “account A” but was not successful. I am stuck at the
> login screen. I cannot login to either “account A” or “account B”. I had
> to reboot to gain control of my system.
>
> Ken
>
>
> On 05/30/2018 09:06 AM, Iain Lane wrote:
> > On Wed, May 30, 2018 at 03:45:17PM -0000, KenWilson wrote:
> >> All,
> >> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect
> >> password issue; however, it creates a new issue. As such I don’t think
> >> this update should be released.
> > That verison is superseded by 3.28.2-0ubuntu1.1. Please try this one.
> >
>
> --
> *Ken Wilson*
> lake
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
> [regression] Password accepted but login fails (blank purple screen
> and mouse pointer only)
>
> Status in gdm:
> Fix Released
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in gdm3 package in Ubuntu:
> Fix Released
> Status in gnome-shell package in Ubuntu:
> Invalid
> Status in gdm3 source package in Bionic:
> Fix Committed
> Status in gnome-shell source package in Bionic:
> Invalid
>
> Bug description:
> [ Description ]
>
> Due to a refcounting bug, a GDBusConnection was getting disposed when
> it was still required. The symptom of this was that you couldn't log
> in on the second attempt if you'd got your password wrong on the first
> attempt. All you'd see is a blank purple screen and mouse pointer
> only.
>
> [ Test case ]
>
> 1. Boot to GDM
> 2. Click your username
> 3. Type the wrong password a couple of times, pressing enter after each
> time
> 4. Type the right password
>
> If the bug is happening, after 4. the system hangs at a blank screen
> with the mouse cursor. If you then switch to a VT or otherwise connect
> to the machine, you can examine the journal and you'll see a
> G_IS_DBUS_CONNECTION failure.
>
> [ Fix ]
>
> Marco and I worked upstream on this fix. We found out that there was a
> problem like this-
>
> The GdmClient has a shared GDBusConnection for its operations. The
>...

[Marco Trevisan (Treviño) (3v1n0)]

I think the issue is getting is there but maybe different from the one originating this bug, so maybe to be handled in a different one...

So please, test this:

 1. Create another user
 2. Login with your user (or the other, as you wish)
 3. Lock the session -> Switch to other user from lockscreen
 4. Once back on GDM, select another user... Then you can login and redo what
    said in 3. or just go back.
 5. From GDM, again try to unlock the 1st user, it fails.

Also `ps aux | grep <the-user-logged-in>` shows running processes for that session, while gdm seems to try to initialize a new one.

Anyway, while it's true this could be a regression of this change, I think it might be still better to release the version we have in proposed as this kind of issue can be handled in a different bug.
In any case I'm looking at it right now.

[Sergei (markovs-i-mail)]

I don't think you should release this because this produces more critical bug. This bug has some kind of workaround (cancel button), but I will have to disable updates if there is an upcoming update that will totally break an ability to switch users without any workaround.
I believe I'm not the only one who has multiple users on my PC.

[Ken Wilson (ken.wilson)]

Regarding gdm3 3.28.2-0ubuntu1.1; regardless of what I do I cannot make it work. Switching between users 100% of the time results in failure.

Here is what I have done:

Someone mentioned that after rebooting their system three times (something like that) it started working albeit slow. I have rebooted my system more than three times and it still doesn’t work.

Someone mentioned they switch users by locking the screen then from the locked screen switch to a different user. What I have been doing is clicking in the upper right corner, click on my name then click on switch user. I have tried both methods with the same result, doesn’t work. I can switch from ‘account A’ to ‘account B’ but I have not been able to switch back to ‘account A’.

I have logged into ‘account A’ and then switched to ‘account B’. I can logout of ‘account B’ and then login to ‘account B’ again, that works. If I try to switch to ‘account A’ or logout of ‘account B’ and login to ‘account A’ I get locked out. I have the login screen for the two accounts but cannot login to either. After a delay I am returned to the login screen. At this point I did a CTRL-ALT-F4 to get a condole, which worked. I logged into the console as ‘account A’, which worked. I then did CTRL-ALT-F2 to return to windows and logged in to ‘account A’ which sort of worked. I was logged in but things were not setup correct. For instance I could not launch a terminal window; however, I could launch Thunderbird. While in the console I did (as someone suggested) ps aux | grep <user account>, for the two accounts. I saved the output to a file which I will attach (NOTE: for anonymity I will change the account names to ‘account A’ and ‘account B’. Hopefully this will help someone better understand the problem.

[Bodinux (bodinux)]

For information, I have had switching users issues since the fresh install of 18.04 on top of not being able to login myself.

I let the gnome people continue to work on this issue and thank them for their work. In the meantime, my workaround is to turn back to lightdm which works very well for me (as it as done for some many years now):
-no login issues
-no multiple users switching issues
-automatic keyboard layout selection as per the user preference (we use different layout in my family)
-working on screen keyboard (displays other layout than qwerty).

I'll probably join ubuntu mainstream packages when these issues will be solved.

[Jehandan Jeyaseelan (jehanjey)]

Hi,

Confirm that there are switching user issues.

I logged in as user A, then created a second user - user B. I clicked on Switch User and logged in successfully as User B.

I then proceeded to switch to User A by clicking on Switch User then clicking on User A and entering the password. Resulted in being unable to log back into User A.

Therefore fix still has issues and I agree with others here that it cannot be released.

I think the fix should not be released until all issues associated with it are resolved. If another bug is causing the switch user problem then both bugs should be fixed before the gdm3 update with fixes is released.

Login functionality is critical to an operating system and should be working perfectly. Having multiple users created in an Ubuntu 18.04 LTS install is a very likely scenario.

[Jehandan Jeyaseelan (jehanjey)]

Hi,

In addition to my post #96 above, I downgraded gdm3 back to the release version - 3.28.0-0ubuntu1 and am able to confirm that switching users works perfectly between two users for me.

Therefore sounds like the fix for gdm3 - 3.28.2-0ubuntu1.1 - has introduced further issues.

[Daniel van Vugt (vanvugt)]

Given that the same code has now been released in 18.10 (3.28.2-1ubuntu1), we should treat it as a new bug and maybe not complicate the discussion here.

Can someone please log a bug against 18.10?

[Sergei (markovs-i-mail)]

Switching users sometimes hangs since gnome shell 3.22. The bug exists in debian stable. But it's not 100% reproducible.

[Heikki Moisander (moisander)]

Fresh install 18.04 gdm3 did succeed occasionally, but mostly froze
completely so that power button was only way out.
There was a fix that was available in proposed repository (or something)
that made things a bit different. Failure became a rule, but it was
possible to get back with ctrl+alt+F1/F2 (randomly pressing both)
Now this latest version is the first one that seems to work everytime. My
personal wish would be that please stop complicating the thing and put it
in production.

to 31. toukok. 2018 klo 6.55 Jehandan Jeyaseelan (<email address hidden>)
kirjoitti:

> Hi,
>
> In addition to my post #96 above, I downgraded gdm3 back to the release
> version - 3.28.0-0ubuntu1 and am able to confirm that switching users
> works perfectly between two users for me.
>
> Therefore sounds like the fix for gdm3 - 3.28.2-0ubuntu1.1 - has
> introduced further issues.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
> [regression] Password accepted but login fails (blank purple screen
> and mouse pointer only)
>
> Status in gdm:
> Fix Released
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in gdm3 package in Ubuntu:
> Fix Released
> Status in gnome-shell package in Ubuntu:
> Invalid
> Status in gdm3 source package in Bionic:
> Fix Committed
> Status in gnome-shell source package in Bionic:
> Invalid
>
> Bug description:
> [ Description ]
>
> Due to a refcounting bug, a GDBusConnection was getting disposed when
> it was still required. The symptom of this was that you couldn't log
> in on the second attempt if you'd got your password wrong on the first
> attempt. All you'd see is a blank purple screen and mouse pointer
> only.
>
> [ Test case ]
>
> 1. Boot to GDM
> 2. Click your username
> 3. Type the wrong password a couple of times, pressing enter after each
> time
> 4. Type the right password
>
> If the bug is happening, after 4. the system hangs at a blank screen
> with the mouse cursor. If you then switch to a VT or otherwise connect
> to the machine, you can examine the journal and you'll see a
> G_IS_DBUS_CONNECTION failure.
>
> [ Fix ]
>
> Marco and I worked upstream on this fix. We found out that there was a
> problem like this-
>
> The GdmClient has a shared GDBusConnection for its operations. The
> first time someone calls for it, it is created and stored in the
> object's private structure. Subsequent calls return *a new reference*
> to this same object. It turned out that the asynchronous method to get
> the connection was accidentally unreferencing its object before giving
> it to the caller if it was returning an already-existing connection.
>
> For this to work properly, we need to nullify the pointer we stored
> when the connection goes away, so we know when to make a new one.
> There were some cases where we didn't add the weak references required
> to do that. Those are also fixed.
>
> [ Regression potential ]
>
> Now we share connections more than we did before. We also more
> carefully track when to clear our object. If we g...

[Marco Trevisan (Treviño) (3v1n0)]

So, the latest two commits of this branch:
 - https://gitlab.gnome.org/3v1n0/gdm/commits/client-connection-reference-fix-3-28

Should fix all the problems that I've tested so far.
Packaging will follow.

[Jehandan Jeyaseelan (jehanjey)]

Hi, in response to Marco's post #101,

I was wondering if a package will be released for bionic proposed so we can test it out before it is released?

I can see that one is released for cosmic that is newer than the one for bionic.

[Robert Clayton (rnctx)]

gdm3_3.28.2-0ubuntu1.1_amd64.deb, gir1.2-gdm-1.0_3.28.2-0ubuntu1.1_amd64.deb, libgdm1-dbgsym_3.28.2-0ubuntu1.1_amd64.ddeb, gdm3-dbgsym_3.28.2-0ubuntu1.1_amd64.ddeb, libgdm1_3.28.2-0ubuntu1.1_amd64.deb, and libgdm-dev_3.28.2-0ubuntu1.1_amd64.deb do not fix these issues by themselves.

on a fresh install:

lightdm cannot log in (failed password over and over)
gdm3 can only log into a wayland UI, not any other

[Daniel van Vugt (vanvugt)]

In progress again. See the "Related branches" links near the top of the bug.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdm3 - 3.28.2-2ubuntu1

---------------
gdm3 (3.28.2-2ubuntu1) cosmic; urgency=medium

  [ Iain Lane ]
  * Merge with Debian. Remaining changes:
    + README.Debian: update for correct paths in Ubuntu
    + control.in:
      - Don't recommend desktop-base
      - Depend on bash for ubuntu_config_error_dialog.patch
      - Update Vcs field
    + rules:
      - Don't override default user/group
      - --enable-gdm-xsession to install upstream Xsession script
      - override dh_installinit with --no-start to avoid session being killed
    + rules, README.Debian, gdm3.8.pod:
      Use upstream custom.conf instead of daemon.conf
    + gdm3.{postinst,postrm}: rename user and group back to gdm
    + gdm3.postinst: don't kill gdm on upgrade
    + gdm3.*.pam: Make pam_env read ~/.pam_environment
    + gdm3.install:
      - Stop installing default.desktop. It adds unnecessary clutter
        ("System Default") to the session chooser.
      - Don't install debian/Xsession
    + Add ubuntu_run_xsession.d.patch
    + Add ubuntu_xresources_is_a_dir.patch
      - Fix loading from /etc/X11/Xresources/*
    + Add ubuntu_nvidia_prime.patch:
      - Add hook to run prime-offload (as root) and prime-switch if
        nvidia-prime is installed
    + Add revert_override_LANG_with_accountservices.patch:
      - On Ubuntu accountservices only stores the language and not the
        full locale as needed by LANG.
    + Add ubuntu_dont_set_language_env.patch:
      - Don't run the set_up_session_language() function, since it
        overrides variable values set by ~/.pam_environment
    + Add ubuntu_config_error_dialog.patch:
      - Show warning dialog in case of error in ~/.profile etc. and
        don't let a syntax error make the login fail
    + Add debian/default.pa
      - Disable Bluetooth audio devices in PulseAudio from gdm3.
    + debian/gdm3.install
      - Added details of the default.pa file
    + debian/gdm3.postinst
      - Added installation of default.pa and creation of dir if it doesn't
        exist.

  [ Marco Trevisan (Treviño) ]
  * debian/patches/ubuntu_nvidia_prime.patch:
    - Fix install file paths

gdm3 (3.28.2-2) unstable; urgency=medium

  * debian/patches/libgdm-drop-support-for-serializing-multiple-opens.patch,
    debian/patches/libgdm-fix-pointer-boolean-task-confusion.patch,
    debian/patches/libgdm-don-t-keep-manager-proxy-around-longer-than-we-nee.patch,
    debian/patches/libgdm-use-g_object_unref-instead-of-g_clear_object-for-w.patch,
    debian/patches/libgdm-get-connection-explicitly.patch,
    debian/patches/libgdm-Drop-weak-refs-on-the-GDBusConnection.patch,
    debian/patches/libgdm-Unref-the-manager-propagated-from-task.patch,
    debian/patches/libgdm-Don-t-double-ref-the-connection-got-from-task.patch,
    debian/patches/libgdm-Don-t-leak-connection-on-sync-re-authentication.patch,
    debian/patches/libgdm-Use-auto-pointers-and-cleanup-code.patch,
    debian/patches/libgdb-Try-to-reuse-connections-from-the-available-proxie.patch,
    debian/patches/libgdm-Don-t-save-manager-address.patch,
    debian/patches/libgdm-Return-NULL-on-invalid-client-instances.patch:
    - Cherry picks comm...

[Łukasz Zemczak (sil2100)]

Hello Chris, or anyone else affected,

Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Ken Wilson (ken.wilson)]

** Tag verification-done-bionic

tested the following:
gdm3/3.28.2-0ubuntu1.2/amd64

Tested multiple bad password followed with a good password. PASS
Tested switching from user A to user B; multiple bad password followed by good password. PASS
Tested switching from user B back to user A; multiple bad password followed by good password. PASS

I found no issues... everything worked as expected.

Ken

[tom (tombuntus)]

Can someone take time to explain to a newb how/where to read in this bug report when this fix will be pushed out?

Like, I see "Fix Released", but when does "sudo apt upgrade" see this fix?

[Daniel van Vugt (vanvugt)]

"Fix Released" will always occur for the development release first (Ubuntu 18.10). Then existing stable versions after that.

You can see a fix for 18.04 is in proposed (not yet released) here:
  https://launchpad.net/ubuntu/+source/gdm3
So is only hours/days away from release.

[tom (tombuntus)]

Thanks Daniel!

So, my question is, how do I decipher (approximately) how many hours/days away from release for 18.04 this fix is?

It's probably very obvious to old hands, but it's totally illegible to a newb. Like, can I see what "branch" or "version" will have this fix? And then, how do I see when that "branch" or "version" hits the normal (18.04) distribution?

[Daniel van Vugt (vanvugt)]

Nobody can predict the future exactly, but given that the fix for 18.04 has now been verified I would *expect* it to be fully released later today. Mainly waiting for Europe to wake up...

Tip: Make sure you're using the main archive to receive updates and not a mirror, as mirrors will take longer to update. See: Software & Updates > Download from = Main server.

[tom (tombuntus)]

Wow! So once status is Fix Released that means, probably, usually, hopefully, wait no more than 24 hours for the fix to hit your machine if you sudo apt upgrade daily?

[Daniel van Vugt (vanvugt)]

That's not quite right. Fix Released means a fix has been released. The only question is in which Ubuntu release. Presently you can see:

gdm3 (Ubuntu) Fix Released <-- Ubuntu 18.10 release completed
       Bionic Fix Committed <-- Ubuntu 18.04 soon to be released

[Sum Sim (draugr200)]

How long will it will be tested in "proposed"? A week? Two weeks, a month?

[Daniel van Vugt (vanvugt)]

As already stated, I expect to see the release within hours (less than a day).

[Tuya (tuya0081)]

Do you know how to potentially unlock the situation even temporarily?

[Daniel van Vugt (vanvugt)]

Yes. See "WORKAROUND" in the bug description.

[Tuya (tuya0081)]

Namely for my part to solve the connection problems via auto connection. However, it still freezes a few more times in use

[OliFre (freyermuth)]

Since it's still in proposed and a day is mostly over (and Europe is asleep again) - could somebody outline / point me to the conditions for a package to be moved from proposed to released?

This would be good to know to understand what is missing (and potentially help?) instead of entering a lengthy discussion here, with almost a 100 affected people and hence spamming lots of subscribers.

[Jehandan Jeyaseelan (jehanjey)]

Hi,

Tested the fix again - 3.28.2-0ubuntu1.2 on a fresh install of Ubuntu 18.04 LTS.

I went through all scenarios:

a) Login initially with incorrect password then correct password - Pass
b) Login by entering incorrect password multiple times then correct password - Pass
c) Created a second user (User B) then switched to that user entering correct password - Pass
d) Switched back to User A entering correct password - Pass
e) Switch between User A and B multiple times - Pass
e) Switched to User B entering incorrect password first then correct password - Pass
f) Switched to User A entering incorrect password first then correct password - Pass
g) Performed logout of User A, then unlocked User B with correct password - Pass
h) Performed logout of User B, then logged in to User A with correct password - Pass.

Fix now works perfectly. All good.

[HouseSessions (koen-bulcke)]

Hi,

I'd like to test too - though being new here - can I (to avoid to switch to proposed repo) just download and install the AMD64 .deb files listed under proposed / 3.28.2-0ubuntu1.2 ?

thanks,
br, Koen

[Ads20000 (ads20000)]

The conditions for the package to move to release are here: https://wiki.ubuntu.com/ProposedMigration#Migrating_packages_from_-proposed_to_release

It's possible that the update breaks something in release, though I'm not sure what. It's also possible that we _just need to be more patient_, it's only been a few days since it was put in proposed. I don't see how spamming this bug is going to help the situation.

[OliFre (freyermuth)]

@Ads20000 Thanks for the link. Sadly, gdm3 is neither in the autopkgtest-list, nor update-excuses, nor update-list, so it seems things are stuck at an earlier stage and the documentation does not clarify where to find out at which point help could be needed.

My intention was not to spam this report, but to find out where things are stuck (it's not obvious) and how to give support.
It's also not about my personal (im)patience, but we have >200 desktops and >2000 Ubuntu containers and have had to stop the migration after the first 10 desktops due to this bug (and three(!) other ones which all have been known *before* release and should either have been release blockers or been mentioned as "Known Issues" with the new LTS to prevent people from hopping onto the new supposedly-stable). For the other critical issues, QA apparently was even worse, since Debian and in one case also RHEL have already released fixes months or even a year ago, and there has been no reaction on Launchpad whatsoever yet. Since we are also still affected by critical bugs in 16.04 which have been open since 16.04's release and could only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu still is a valid choice for institutional use, but this discussion certainly goes off topic here.

Just let us know if there is something people could help with (testing etc.). As it stands, the status is completely unclear apart from the statement _to be patient_ - without indicating what the actual point is where things are stuck.

[Heikki Moisander (moisander)]

3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical
in our environment). It has been few days since it was supposed to be
coming and I figured that it is safe now to start installing 18.04, but
fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work.

su 10. kesäk. 2018 klo 17.25 OliFre (<email address hidden>) kirjoitti:

> @Ads20000 Thanks for the link. Sadly, gdm3 is neither in the
> autopkgtest-list, nor update-excuses, nor update-list, so it seems
> things are stuck at an earlier stage and the documentation does not
> clarify where to find out at which point help could be needed.
>
> My intention was not to spam this report, but to find out where things are
> stuck (it's not obvious) and how to give support.
> It's also not about my personal (im)patience, but we have >200 desktops
> and >2000 Ubuntu containers and have had to stop the migration after the
> first 10 desktops due to this bug (and three(!) other ones which all have
> been known *before* release and should either have been release blockers or
> been mentioned as "Known Issues" with the new LTS to prevent people from
> hopping onto the new supposedly-stable). For the other critical issues, QA
> apparently was even worse, since Debian and in one case also RHEL have
> already released fixes months or even a year ago, and there has been no
> reaction on Launchpad whatsoever yet. Since we are also still affected by
> critical bugs in 16.04 which have been open since 16.04's release and could
> only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu
> still is a valid choice for institutional use, but this discussion
> certainly goes off topic here.
>
> Just let us know if there is something people could help with (testing
> etc.). As it stands, the status is completely unclear apart from the
> statement _to be patient_ - without indicating what the actual point is
> where things are stuck.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1768619).
> https://bugs.launchpad.net/bugs/1766137
>
> Title:
> [regression] Password accepted but login fails (blank purple screen
> and mouse pointer only)
>
> Status in gdm:
> Fix Released
> Status in Release Notes for Ubuntu:
> Fix Released
> Status in gdm3 package in Ubuntu:
> Fix Released
> Status in gnome-shell package in Ubuntu:
> Invalid
> Status in gdm3 source package in Bionic:
> Fix Committed
> Status in gnome-shell source package in Bionic:
> Invalid
>
> Bug description:
> [ Description ]
>
> Due to a refcounting bug, a GDBusConnection was getting disposed when
> it was still required. The symptom of this was that you couldn't log
> in on the second attempt if you'd got your password wrong on the first
> attempt. All you'd see is a blank purple screen and mouse pointer
> only.
>
> [ Test case ]
>
> 1. Boot to GDM
> 2. Click your username
> 3. Type the wrong password a couple of times, pressing enter after each
> time
> 4. Type the right password
>
> If the bug is happening, after 4. the system hangs at a blank screen
> with the mouse cursor. If you then switch to a VT or othe...

[Sergei (markovs-i-mail)]

Release package is already unstable and isn't able to it's job.
I don't see any reasons not to deploy this excepting bureaucracy.

[Alex Noble (swinkid-x)]

This is a blocker for deployment of 18.04 to ~200 workstations within my company. Any ETA on a release?

My steps to reproduce:
1. Boot Machine
2. Enter username
3. Enter incorrect password
4. Enter correct password
5. Stuck on purple screen

[Brian Murray (brian-murray)]

The policy for Stable Release Updates is to let them age a minimum of 7 days in the -proposed pocket before releasing them to the -updates pocket. Reading the comments here I've noticed that the automated SRU testing comment doesn't make any reference to that 7 day period nor does it point to the wiki page that documents the aging period. I'll work getting that fixed shortly.

Speaking with another SRU team member we've decided to waive the 7 day period and will release the fixed version of gdm3 today.

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for gdm3 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gdm3 - 3.28.2-0ubuntu1.2

---------------
gdm3 (3.28.2-0ubuntu1.2) bionic; urgency=medium

  * debian/patches/libgdm-drop-support-for-serializing-multiple-opens.patch,
    debian/patches/libgdm-fix-pointer-boolean-task-confusion.patch,
    debian/patches/libgdm-don-t-keep-manager-proxy-around-longer-than-we-nee.patch,
    debian/patches/libgdm-use-g_object_unref-instead-of-g_clear_object-for-w.patch,
    debian/patches/libgdm-get-connection-explicitly.patch,
    debian/patches/libgdm-Drop-weak-refs-on-the-GDBusConnection.patch,
    debian/patches/libgdm-Unref-the-manager-propagated-from-task.patch,
    debian/patches/libgdm-Don-t-double-ref-the-connection-got-from-task.patch,
    debian/patches/libgdm-Don-t-leak-connection-on-sync-re-authentication.patch,
    debian/patches/libgdm-Use-auto-pointers-and-cleanup-code.patch,
    debian/patches/libgdb-Try-to-reuse-connections-from-the-available-proxie.patch,
    debian/patches/libgdm-Don-t-save-manager-address.patch,
    debian/patches/libgdm-Return-NULL-on-invalid-client-instances.patch:
    - Cherry picks commits from upstream 3.28 branch to propely fix ref-counting
      issues on GdmClient (LP: #1766137)

gdm3 (3.28.2-0ubuntu1.1) bionic; urgency=medium

  * debian/gbp.conf: Add with 'bionic' configuration.
  * debian/control{,.in}: Update Vcs-* for git.
  * New upstream release (LP: #1773968):
    - Reference counting fixes for GdmClient (LP: #1766137)
    - ensure plymouth is quit properly even when local greeter is disabled
    - make sure GDM doesn't hang when called with unknown command line arguments
  * debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
    debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
    Drop, included in this release.

gdm3 (3.28.0-0ubuntu1.1) bionic; urgency=medium

  * debian/patches/0001-libgdm-Don-t-unref-a-connection-that-s-in-use.patch,
    debian/patches/0002-libgdm-add-weak-pointer-for-connection-object.patch:
    Cherry-pick two patches from the 3.28 branch. These fix a refcounting bug
    in the GDM Client object, which had meant that the DBus connection was
    being disposed too early in some cases, particularly when logging in after
    a failed attempt. The symptom of that was that the system hung on a
    "blank" screen. (LP: #1766137)
  * debian/control{,.in}: Update for bionic

 -- Marco Trevisan (Treviño) <email address hidden> Tue, 05 Jun 2018 11:58:41 +0100

[matt scott (mgshightech)]

9-8-018 fresh install with updates .. some user switches work, some don't logout is also crashing with irresponsive black screen. When the user switch fails, the description is slightly different from above. If the mouse pointer comes in at lower right, the user switch works. If it comes in upper right, then the mouse fails, alt-F1 etc. all do nothing, and rather than blank purple screen, I have what appears to be a successful login, but the system is completely non-responsive.

dell optiplex 755
SSd
3.16 GHZ core 2 duo

[matt scott (mgshightech)]

gdm3 info. for above comment

matt@Wallace:~$ apt list gdm3
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
matt@Wallace:~$ apt list gdm3 -a
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
gdm3/bionic 3.28.0-0ubuntu1 amd64

[Daniel van Vugt (vanvugt)]

matt,

The fix is in gdm3 version 3.28.2-0ubuntu1.1 and later.

You only have version 3.28.0-0ubuntu1 installed.

If you can't easily update then you might have more luck installing version 18.04.1 directly (which might contain the fix if 18.04 didn't)...

https://www.ubuntu.com/download/desktop/thank-you?version=18.04.1&architecture=amd64

[Daniel van Vugt (vanvugt)]

matt,

Please also note that a Core 2 Duo will suffer from bug 1727356 too. Please apply the workaround from that bug.

[Erik Koning (erikkoning)]

This bug affected me, but got past it by adding "nouveau.modeset=0" after the text "quiet splash" in the bootparameters for Ubuntu in the grub menu.

[Daniel van Vugt (vanvugt)]

This bug is closed so please open a new bug if you have any problems at all.