Public bug reported:

I'm trying to follow the 19.04 Xubuntu QA-Test post-install script which is why 
this bug report.
It's really petty/minor & could be just how I interpret the steps to follow.

On locking screen, the displays power-save & go dark almost instantly.

To wake them so I can see the password entry screen I hit <Enter>
(bottom right corner of keyboard) and instead of a password entry
screen, a bright blue bar tells me I've entered my password incorrectly.
It took the <Enter> I used to 'wake' my screen as a password was entered
& I want to return to my session.

I did it again & used <Shift> which was the expected result (my screen
wakes on touch of key, with no entry into password prompt). I do it
again and this time try and wake my keyboard using a random letter, it
does wake the screen but I've got a "o" (black circle representing a
character entered into the password field) on the display.  I believe
the first key should do nothing but wake the screen, not be interpreted
as a password entry screen because the field hasn't appeared on screen

This is really minor - users will adjust to the way it is, and I
probably only noticed it because I was following instructions as per QA-

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: light-locker 1.8.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Apr 16 13:35:43 2019
InstallationDate: Installed on 2019-04-16 (0 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.1)
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: light-locker (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-bug disco

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  19.04 QA-test post-install really minor cosmetic issue

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to