This bug was fixed in the package bolt - 0.9.1-2~ubuntu20.04.2
---------------
bolt (0.9.1-2~ubuntu20.04.2) focal; urgency=medium
* debian/patches/git_initialize_syspath.patch:
- cherrypick an upstream that should help with some of the crashers
which have been reported against 0.9 (lp: #1989971)
-- Sebastien Bacher <[email protected]> Fri, 16 Sep 2022 16:08:09
+0200
** Changed in: bolt (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1989971
Title:
Correctly initialize a variable to avoid errors
Status in bolt package in Ubuntu:
Fix Released
Status in bolt source package in Focal:
Fix Released
Bug description:
* Impact
The error tracked got some reports of issues since 0.9 was SRUed to
focal which has been halting the update.
* Test Case
Check the error tracker for focal reported issue, the one which
started with the 0.9 SRU should stop being reported after the update.
Confirm that the boltctl correctly list authorized devices and that
connecting a new one triggers a prompt on the desktop, then that
settings correctly include the newly authorized device
* Regression potential
The patch only correctly initialize the syspath variable of the device
structure to null. If that was not handled correctly by the code the
service could crash or fail to detect properly connected devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1989971/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
