[SRU] Update to 0.3

Bug #1773332 reported by Sebastien Bacher on 2018-05-25
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bolt (Ubuntu)
Low
Unassigned
Bionic
Low
Sebastien Bacher

Bug Description

* Impact

That's a new component and a piece of hardware enablement. The update is having dbus API changes and is not a bugfix only version, but we believe it's better to follow improvements in that new stack than stay on an early version which is incomplete and unmaintained.

The service has no rdepends out of gnome-shell which already works fine with the new version

* Test case
- log into an Ubuntu session
- connect a new Thunderbolt device
- check that gnome-shell displays the request for authentication for the device and that the authentication can be validated/the device can be used

* Regression potential

There are quite some code changes but bolt is limited to authentication of Thunderbolt devices, we need to test that the boltctl command line and the GNOME integration keep working to auth/revoke devices.

Sebastien Bacher (seb128) wrote :

The summary of the changes from 0.3 is available there
https://gitlab.freedesktop.org/bolt/bolt/tags/0.3

Changed in bolt (Ubuntu):
importance: Undecided → Low
Sebastien Bacher (seb128) wrote :

Upstream confirmed that current gnome-shell is fine with bolt 0.3, https://gitlab.gnome.org/GNOME/gnome-shell/commit/fb509dfc is a cleanup change but is not required (and isn't in gnome-3-28 upstream either)

Changed in bolt (Ubuntu):
status: New → Fix Released
Jeremy Bicha (jbicha) on 2018-05-25
description: updated
Changed in bolt (Ubuntu Bionic):
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Sebastien Bacher (seb128)
tags: added: bionic upgrade-software-version

Hello Sebastien, 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.3-0ubuntu0.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 bolt (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Betty Lin (bettyl) wrote :

Verified that gnome-shell displays the request for authentication for the device and that the authentication can be validated/the device can be used with bolt 0.3-ubuntu0.1 on 18.04 machine.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Robie Basak (racb) wrote :

Thank you for verifying the test case.

The Regression Potential report also says that the boltctl CLI should be tested. Could you also verify this, please?

Betty Lin (bettyl) wrote :

@Robie

#######################
u@u-XPS-13-9370:~$ dpkg -l | grep bolt
ii bolt 0.3-0ubuntu0.1 amd64 system daemon to manage thunderbolt 3 devices
u@u-XPS-13-9370:~$ boltctl --help
Usage:
  boltctl [OPTION…] [COMMAND]

Commands:
  authorize Authorize a device
  enroll Authorize and store a device in the database
  forget Remove a stored device from the database
  info Show information about a device
  list List connected and stored devices
  monitor Listen and print changes
#########################

All of them were working, only one problem:
If use "authorize" to authorize a device, and then use "enroll" to store the device to database, it will return:
wrong device state: 5

Sebastien Bacher (seb128) wrote :

The "enroll" issue is not new from that SRU but already existing in 0.2 in bionic. It has been fixed upstream now with this commit

https://gitlab.freedesktop.org/bolt/bolt/merge_requests/86
"Manager.Enroll will now store already authorized devices"

Which is going to be part of the next version/update, no reason to block the current SRU on that one

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bolt - 0.3-0ubuntu0.1

---------------
bolt (0.3-0ubuntu0.1) bionic; urgency=medium

  * New upstream version (lp: #1773332)
  * debian/control:
    - lower the libglib requirement and build-depends on libsystemd-dev

 -- Sebastien Bacher <email address hidden> Fri, 25 May 2018 10:47:17 +0200

Changed in bolt (Ubuntu Bionic):
status: Fix Committed → Fix Released

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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers