Description of problem: After I enroll my Thunderbolt Cable and Thunderbolt Dock with boltctl and reboot, the Thunderbolt Dock isn't automatically re-authorized after reboot. Version-Release number of selected component (if applicable): bolt-0.3-1.fc28.x86_64 How reproducible: 100% with my hardware Steps to Reproduce: 1. enroll Thunderbolt Cable and Thunderbolt Dock 2. reboot Actual results: Only Thunderbolt Cable is authorized on reboot, while Thunderbolt Dock stays 'connected'. This prevents proper function of devices connected to Thunderbolt Dock. Expected results: Both Thunderbold Cable and Thunderbolt Dock are authorized after reboot. Additional info: $ boltctl list ● Dell Thunderbolt Cable ├─ type: peripheral ├─ name: Thunderbolt Cable ├─ vendor: Dell ├─ uuid: aaaaaaaa-bbbb-cccc-ffff-ffffffffffff ├─ status: authorized │ ├─ authflags: none │ ├─ authorized: 2018-05-09T10:10:21 UTC │ └─ connected: 2018-05-09T10:10:18 UTC └─ stored: yes ├─ when: 2018-05-09T09:52:11 UTC ├─ policy: auto └─ key: no ● Dell Thunderbolt Dock ├─ type: peripheral ├─ name: Thunderbolt Dock ├─ vendor: Dell ├─ uuid: cccccccc-dddd-eeee-ffff-ffffffffffff ├─ status: connected │ ├─ authflags: none │ └─ connected: 2018-05-09T10:10:18 UTC └─ stored: yes ├─ when: 2018-05-09T09:52:19 UTC ├─ policy: auto └─ key: no /var/lib/boltd/devices/aaaaaaaa-bbbb-cccc-ffff-ffffffffffff [device] name=Thunderbolt Cable vendor=Dell type=peripheral [user] policy=auto storetime=1525859531 /var/lib/boltd/devices/cccccccc-dddd-eeee-ffff-ffffffffffff [device] name=Thunderbolt Dock vendor=Dell type=peripheral [user] policy=auto storetime=1525859539
Can you attach the output of "journalctl -b0 -u bolt", please?
Created attachment 1433724 [details] bolt jounral
I think I have an idea what is going on. The uevent is too slow and therefore the status is already updated to authorized and the "maybe-authorize-child-devices" logic does not kick in. I actually recently fixed that in master. Let me roll a dev snapshot RPM for you to test.
Sorry, that took longer then expected, but a current build is now available at the "gicmo/bolt" copr. https://copr.fedorainfracloud.org/coprs/gicmo/bolt/ Would be great if you could test it and report if that fixes it for you.
bolt-0.4-0.20180509gite93aa7d.fc28.x86_64 works as expected. Thanks for the quick response!
bolt-0.4-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c421a9e86b
bolt-0.4-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-58ddbe925b
bolt-0.4-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-58ddbe925b
bolt-0.4-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c421a9e86b
bolt-0.4-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
bolt-0.4-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.