devices not authorized at lightdm on initial boot even if enrolled

[graingert]

* Impact

some devices can't be used on the login screen

* Test case
try using a mouse/keyboard connected to a thunderbolt dock, they should work on the login scren

* Regression potential
check that your thunderbolt devices keep working fine on the login screen and during the user session

--------------------

eg I can't use my keyboard to login, until I've logged in at least once.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bolt 0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 21 10:30:26 2018
InstallationDate: Installed on 2018-05-30 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: bolt
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you give details on the keyboard you are using and how you are connecting to the computer?
Why do you think it's an issue with bolt?

[graingert (tagrain)]

@seb128 it's a simple USB mouse https://www.dell.com/en-uk/shop/wireless-combo-mk520/apd/a8831223/pc-accessories

because when I login boltctl authroizes my TB16 dongle

[graingert (tagrain)]

s/boltctl/bolt/

[graingert (tagrain)]

upstream bug: https://gitlab.freedesktop.org/bolt/bolt/issues/100

[graingert (tagrain)]

> I have to strong suspicion it is the "slow uevent race" that was reported against 0.3 as rhbz#1576379. I don't think I opened an issue for that here before. It should also be fixed in 0.4. Too bad 0.4 did not make it into ubuntu; maybe in some quiet moment I could set up a PPA. Or seb128 could maybe do a quick package with 0.4 to see if the issue goes away?

[Sebastien Bacher (seb128)]

Ok, I've uploaded 0.4 to cosmic and as a stable update for 18.04, let's see how that one works

[Launchpad Janitor (janitor)]

This bug was fixed in the package bolt - 0.4-0ubuntu2

---------------
bolt (0.4-0ubuntu2) cosmic; urgency=medium

  * debian/patches/git_glib_257.patch:
    - backport upstream patch to fix the build with glib 2.57

 -- Sebastien Bacher <email address hidden> Thu, 09 Aug 2018 16:13:36 +0200

[graingert (tagrain)]

@seb128, do you know how I can get that package?

[Łukasz Zemczak (sil2100)]

Hello graingert, or anyone else affected,

Accepted bolt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bolt/0.4-0ubuntu0.18.04.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!

[graingert (tagrain)]

@sil2000 ok it works for me, from lightdm. However the mouse and keyboard don't work in UEFI, grub or plymouth without booting into windows first

[Mario Limonciello (superm1)]

@grainert,

There is a BIOS option that will allow thunderbolt to work pre-boot, but FYI it's a security risk to do so.

[Launchpad Janitor (janitor)]

This bug was fixed in the package bolt - 0.4-0ubuntu0.18.04.1

---------------
bolt (0.4-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream version (lp: #1786265)
    - should resolve issues with devices not being authorized on initial
      boot e.g in lightdm (lp: #1778020)

 -- Sebastien Bacher <email address hidden> Thu, 09 Aug 2018 16:20:08 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for bolt 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.