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 (1766...@bugs.launchpad.net) 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 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 libglib2.0-0:amd64 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 trigproc libglib2.0-0:i386 2.56.1-2ubuntu1 <none> > 2018-05-18 07:53:46 status half-configured libglib2.0-0:i386 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:47 status installed libglib2.0-0:i386 2.56.1-2ubuntu1 > 2018-05-18 07:53:47 configure libgdm1:amd64 3.28.0-0ubuntu1.1 <none> > 2018-05-18 07:53:47 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status half-configured libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status installed libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:48 trigproc libc-bin:amd64 2.27-3ubuntu1 <none> > 2018-05-18 07:53:48 status half-configured libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 status installed libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 trigproc systemd:amd64 237-3ubuntu10 <none> > 2018-05-18 07:53:48 status half-configured systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:51 status installed systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:51 trigproc man-db:amd64 2.8.3-2 <none> > 2018-05-18 07:53:51 status half-configured man-db:amd64 2.8.3-2 > 2018-05-18 07:53:54 status installed man-db:amd64 2.8.3-2 > 2018-05-18 07:53:54 trigproc dbus:amd64 1.12.2-1ubuntu1 <none> > 2018-05-18 07:53:54 status half-configured dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 status installed dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 trigproc hicolor-icon-theme:all 0.17-2 <none> > 2018-05-18 07:53:54 status half-configured hicolor-icon-theme:all 0.17-2 > 2018-05-18 07:53:55 status installed hicolor-icon-theme:all 0.17-2 > 2018-05-18 07:53:55 configure gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 <none> > 2018-05-18 07:53:55 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:55 status half-configured gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:55 status installed gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:55 configure gdm3:amd64 3.28.0-0ubuntu1.1 <none> > 2018-05-18 07:53:55 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:56 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:57 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:57 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:57 status half-configured gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:59 status installed gdm3:amd64 3.28.0-0ubuntu1.1 > > -- > 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 if you'd got your password wrong. > > [ 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) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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 if you'd got your password wrong. [ 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) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
