This is more a debian thing but I figured i would ask here anyway.
This shows up when i try to refresh the list of software on a miniv2 running pureos 10.
gnome software center or snap ui or whatever its called says that there is a problem and it
says it cant load the list of updates
this the line in /var/log/messages:
gnome-software: not GsPlugin error FwupdError:10: The name :1.101 was not provided by any .service files
I have read elsewhere that this is an issue with snap and that I can un-install and re-install gnome-software.
I have not been around here for a while and I just cheked the main website.
They are offering qubes pre-friggin installed on the mini or the 14
Damn that is tempting.
Anyway - does anyone else deal with the above when trying to check for updates?
For what its worth:
After a reboot the message no longer appeared.
Not yet anyway.
I am getting this occasionally as well. Reboots seem to do the trick, but I am curious as to the cause of the error.
it will reaperar , it seems to be related with fwupd, that sometimes fail to calculate checksums for downloaded firmware repository.
At least I know what to do next time. Just ignore it until after the next reboot.
Hi I found something that made this error go away and allows me to use gnome software UI thing on my mini.
I ran the suggestions from this post:
Can someone help me resolve the following?
[Screenshot from 2021-12-23 10-22-59]
I’m on a Librem 14 with PureBoot & Librem Key. I had to reinstall PureOS a couple of weeks ago.
If I try to download it I get:
[Screenshot from 2021-12-23 10-52-22]
I’m relatively new to Linux. This feels like my check engine light is on and I want to fix it.
Trying to update and upgrade in Terminal gives me:
The following packages have been kept back:
0 upgraded, 0 newly installed, 0 to remove and 1…
then I think I ran
fwupdmgr refresh again.
Now I can update via the gnome-software thing again.
I was afraid to run apt full-upgrade, because , well it sounds scary - but it worked. Thanks to
@mladen and @Quarnero from the other post for the solution.
I waited a bit to see if the glitch returned but so far no problems.