Replies: 2 comments 7 replies
-
Various brain dump of thoughts:
Or maybe we just spin a standalone AppImage for them to use in this situation?
|
Beta Was this translation helpful? Give feedback.
-
Do you think enough user pressure would affect the policy of LTS/stable distros?
That's the bit I'm also struggling with; there's no user action that means the user can fix the problem. That said, at the moment people have no ideas that they're missing security updates because the client is too old. Maybe it's something we shout return in get-updates? e.g.
Agree, but I don't think we can do anything in that case as we don't enumerate the device. I think in the case of dbx updates the fwupd version is quite a common reason why it can't be deployed. |
Beta Was this translation helpful? Give feedback.
-
An idea someone suggested yesterday. At the moment, on refresh we have:
We might be in the situation where we're missing security updates because the local fwupd version is too old. What about something like:
Alternatively, we could do something like:
Other ideas welcome!
Beta Was this translation helpful? Give feedback.
All reactions