You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I connected my H05 headphones, I saw them in the get-devices but they only had the flags "updatable|registered". Then I ran fwupdmgr refresh && fwupdmgr get-updates which refreshed the repository, but fwupdmgr get-updates didn't list any updates for my H05 headphones even if there were some. But after unplugging and replugging my headphones the flags changed to updatable|supported|registered, and now fwupdmgr get-updates lists an update for my headphones as it should.
This only affects devices which go from unsupported to supported, but maybe it would be nice if fwupdmgr rescanned supported flags when refreshing metadata to avoid this confusion again.
The SUPPORTED flag is used when a device appears in the AppStream metadata of
any enabled remote, so when we rescan the modified store also ensure the flag
state is still correct.
Fixes https://github.com/hughsie/fwupd/issues/363
The SUPPORTED flag is used when a device appears in the AppStream metadata of
any enabled remote, so when we rescan the modified store also ensure the flag
state is still correct.
Fixes https://github.com/hughsie/fwupd/issues/363
When I connected my H05 headphones, I saw them in the get-devices but they only had the flags "updatable|registered". Then I ran fwupdmgr refresh && fwupdmgr get-updates which refreshed the repository, but fwupdmgr get-updates didn't list any updates for my H05 headphones even if there were some. But after unplugging and replugging my headphones the flags changed to updatable|supported|registered, and now fwupdmgr get-updates lists an update for my headphones as it should.
This only affects devices which go from unsupported to supported, but maybe it would be nice if fwupdmgr rescanned supported flags when refreshing metadata to avoid this confusion again.
The text was updated successfully, but these errors were encountered: