Bug 400181

Summary: Not compatible with firmware version 0.1.4, requires >= 0.1.14
Product: [Applications] Discover Reporter: kevin.wallis
Component: discoverAssignee: Aleix Pol <aleixpol>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.14.1   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: A screenshot about the message in discover

Description kevin.wallis 2018-10-23 06:01:38 UTC
Created attachment 115842 [details]
A screenshot about the message in discover

Hello,

always when I open Discover, the message "Not compatible with firmware version 0.1.4, requires >= 0.1.14" pops up.

STEPS TO REPRODUCE
1. Open Discover 
2. Message automatically appears

OBSERVED RESULT
I don't know if this has any influence on the proper working of discover.

EXPECTED RESULT
The problem should be fixed and the message should not appear anymore. 

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.1
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
The attachment contains a screenshot.
Comment 1 Aleix Pol 2018-10-23 12:26:54 UTC
Just looked into this error message. It means that you have a firmware that is too old for fwupd to handle. I'll silence this warning, but you may want to look into updating your firmware.
Comment 2 Aleix Pol 2018-10-23 13:08:42 UTC
Git commit 084df9d90a5f3b2e377aef1aa5c3dec48b7e6dc1 by Aleix Pol.
Committed on 23/10/2018 at 12:28.
Pushed by apol into branch 'Plasma/5.14'.

fwupd: silence invalid file errors

It means that the firmware is too old for fwupd to be able to do
anything about it. Probably easier to just ignore it.

M  +1    -1    libdiscover/backends/FwupdBackend/FwupdBackend.cpp

https://commits.kde.org/discover/084df9d90a5f3b2e377aef1aa5c3dec48b7e6dc1
Comment 3 kevin.wallis 2018-10-23 15:29:49 UTC
Thanks for the hint, I did a firmware update on my system and the problem disappears!
Comment 4 kevin.wallis 2018-10-23 15:30:30 UTC
(In reply to kevin.wallis from comment #3)
> Thanks for the hint, I did a firmware update on my system and the problem
> disappeared!