Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 (1766...@bugs.launchpad.net) kirjoitti: > @Ads2 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 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
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 (1766...@bugs.launchpad.net) 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 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.la
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 <1766...@bugs.launchpad.net> 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 -, 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 > 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
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 <1766...@bugs.launchpad.net> 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 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
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 -, 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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
On Wed, May 30, 2018 at 03:45:17PM -, 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 [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 (moisan...@gmail.com) 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 (1766...@bugs.launchpad.net) > 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 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 Ca
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 (1766...@bugs.launchpad.net) 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 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
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 (daniel.van.v...@canonical.com) 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 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blan
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1766137/+attachment/5141399/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/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/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/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 ibus: Yhdistäminen ei onnistunut: Yhteys torjuttu touko 18 20:55:47 ThinkPad-X301 gnome-shell[934]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.free touko 18 20:55:47 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1468]: reference to undefined property " touko 18 20:55:49 ThinkPad-X301 gnome-shell[934]: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWin touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined propert touko 18 20:56:06 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyAct touko 18 20:56:07 ThinkPad-X301 gnome-shell[1545]: Telepathy is not available, chat integration will be disabled. touko 18 20:56:09 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1027]: unreachable touko 18 20:56:11 ThinkPad-X301 gnome-shell[1545]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner getUniqueBusNameSync@ /usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:56:12 ThinkPad-X301 gnome-shell
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 0x73031450 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #1 0x730314b0 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #2 0x73031580 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #3 0x730315f0 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4 0x561a8f6df7a0 pe 18. toukok. 2018 klo 21.01 Heikki Moisander (moisan...@gmail.com) 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 > 0x-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x0009ec00-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x000dc000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x0010-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd6a1000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd6a7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd7b7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd80f000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8c7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d2000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d5000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d9000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8dd000-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 > 0x
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 0x-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0009ec00-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x000dc000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0010-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a1000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd7b7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd80f000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8c7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d2000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d5000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d9000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8dd000-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 0x-0x0009ebff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0009ec00-0x0009] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x000dc000-0x000f] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0010-0xbd6a0fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a1000-0xbd6a6fff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a7000-0xbd7b6fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd7b7000-0xbd80efff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd80f000-0xbd8c6fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8c7000-0xbd8d1fff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d2000-0xbd8d4fff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d5000-0xbd8d8fff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d9000-0xbd8dcfff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8dd000-0xbd8d] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8e-0xbd906fff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd907000-0xbd907fff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd908000-0xbdb0efff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdb0f000-0xbdb9efff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdb9f000-0xbdbfefff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdbff000-0xbdbf] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdc0-0xbfff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xe000-0xefff] reserved huhti 27 22:06:
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
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 > 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 > 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 > 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 > 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 > 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 > 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 > 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 > 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 > 2018-05
