[Bug 1733557] Re: Login screen showing Authentication Failure Switch to greeter...

[Lex_Dysia]

I've experienced the same problem on a fully patched 16.04 LTS. 
This issue only occurred in the last few weeks & may have corresponded to when 
I added 3 new users to the machine.
I have previously used the first option in 
https://askubuntu.com/questions/859581/how-to-change-the-unity-lockscreen-wallpaper
 to modify my lock screen wallpaper.
After this recent "Authentication failure" issue occurred I recompiled the 
Greeter Schema as per the link above (sudo glib-compile-schemas 
/usr/share/glib-2.0/schemas) which has cured the problem on my machine at least.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733557

Title:
  Login screen showing Authentication Failure Switch to greeter...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 483205] Re: Mounts in /etc/fstab cannot yet be mounted

[Lex_Dysia]

similar story here. After upgrading from 9.04 to 9.10 on my wife's old
clunker, it locks up 4 out of 5 times during boot up. Like post #3
problems occur prior to log on screen. A message is flashed for 2-300 ms
(had to catch it with a camera) which reads:

  "One or more of the mounts listed in /etc/fstab cannot yet be mounted:
   swap: waiting for UUID= etc, etc (my etc's)
   press ESC to enter a recovery shell"

at which point everything locks up. Sometimes it locks with the round
timer type icon displayed, other times it locks with the screen
partially or fully covered with a garbled coloured display.

The fstab file seems good, & the UUID number corresponds with my swap
partition.

Booting to recovery mode gives the normal recovery menu, but with a message 
superimposed over the menu saying it is waiting for the swap file, but also 
"could not access PID for nmbd" 
Is this a clue that something errant is happening with Samba early in the boot 
process? Any ideas appreciated.

-- 
Mounts in /etc/fstab cannot yet be mounted
https://bugs.launchpad.net/bugs/483205
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs