On Tue, Mar 12, 2019 at 4:30 PM Ryan Goodfellow wrote: > I am the proud owner of a Thinkpad X1 that has just been bricked by a Debian > recommended update visa-vis the Gnome software app and LVFS.
I'm sorry to hear that. Just for the record, Debian doesn't have any influence over which firmware updates are recommended by LVFS. > While the root cause of this seems to be Lenovo's lack of interest in quality > control and testing, this cornucopia of agony should not be mindlessly spoon > fed by Debian. Since history shows in many cases more than my own, that > firmware updates from vendors cannot be trusted, I propose that Debian not > actively advertise a firmware release to users until the release has been in > the wild for at least 6 months or has been rigorously tested by a trusted > third party or Debian developers. I think that this discussion needs to be had with the LVFS admins, I've bounced your mail to fwupd upstream and added them to the CC list. Perhaps they can recommend a way to recover from this. Probably the right solution is some sort of web based mechanism for reporting bad updates. I think fwupd has a way to report updates that failed but that usually won't be helpful for bricked devices. > Note that I am not seeking technical advice for my specific issue, but rather > to start a discussion about policy governing how firmware updates are > distributed in Debian. So far Debian itself mainly distributes loadable firmware rather than flashable firmware, and mostly in non-free. Our page documenting mechanisms for manual firmware updates is on the wiki: https://wiki.debian.org/Firmware/Updates -- bye, pabs https://wiki.debian.org/PaulWise
