Has this been tested in the new PureOS 10 release?

Thank you for the issue report! This problem should be resolved with the latest updates :-)

Should be fixed in a few hours :-)

I installed firmware-misc-nonfree. But it didn't help. I tried different suggestions I found. More editing on Grub f. e.. But is also didn't help.
As far as I understood it's probably a kernel issue.
Patching firmware myself is a step to far for me. I'm still a linux beginner.
I will wait for a new kernel and hope, that the issue will be gone then.
Thanks for your help.

A new version of Firefox-ESR will be coming into PureOS 10.

I would start with patching firmware. I am not sure if you have any new firmware available but this would be my first thing to do. I had this issue regularly when I was using Ubuntu after I moved to PureOs and patched firmware it almost disappeared.

Unfortunately the issue reappeared. I could not reproduce it for a while, but since today it's back. And it makes no difference if an external disk is plugged in or not.

@jbw See https://developer.puri.sm/Librem5/Development_Environment/Boards/Troubleshooting/Debugging.html#installing-debug-packages

@jbw Have you considered looking the package with debugging symbols in Debian? Debian has something called snapshot.debian.org which holds, among other things, packages with debug symbols. It is a little hard to navigate but try the search for the package you want and you may get lucky. Or post the package name and version here and I'll see if I can help find it.

can someone who knows what they are doing add step-by-step instructions (perhaps on the pureos wiki) for a user like me who has byzantium installed giving the exact steps that the user needs to take to enable use of the debug-symbol packages that pureos does build (which seem to be in landing rather than in byzantium) together with those of the debug-symbol packages that debian builds which are usable with a byzantium install. these instructions need to specify what exact strings need to be added to which exact configuration files and what exact commands need to be typed to get the necessary debug-symbol packages installed. unfortunately, as an end user, i do not have the spare days to keep trying to find the necessary strings and configuration files and commands until i succeed. thanks for any help you can provide!

Thank you. APT-GET fixed my issue.
This issue is easy to replicate, during the installation I just did not connect to the network.

I noticed the issue directly after upgrading from amber to byzantium. I did not update coreboot at that moment. I'm not sure about EC firmware. I think I can not install/update this on my Librem 15v3.

This is a due to a stale cache that apt is stuck on. If you installed from an older ISO or older PureOS version this can happen. One way to fix this is to run apt-get update to see if this brings in new packages.

Did you update coreboot and EC firmware? I am having this issue but just putting PureOS to sleep once again helps.

@mak does this mean that the most correct solution for many people will be to simply uninstall fwupd because it is useless for them? i don't remember installing it. it is "Recommends:" by pureos-gnome and gnome-software, but i don't have things configured to automatically install packages simply because they are mentioned in "Recommends:" fields. i think it came preinstalled on my librem 14.

This is an annoying issue, as it is extremely hard (if not impossible currently) to fix properly. A proper fix would be to re-sign the fwupd-amd64-signed binary package, but we can not do that as we do not have any EFI signing facilities for PureOS...
This package has been removed from PureOS (as we don't support UEFI with secure boot signing enabled properly anyways), but users who have installed the package manually before will of course run into this issue now until they run an apt purge fwupd-amd64-signed. We could force the removal of this package via conflicts, but that may also not be an ideal solution here :-/

I have see this message, "failed to update metadata for lvfs" a couple times now when checking for a software update. It doesn't happen often but running the following command seems to help.

Thanks for the suggestions.
Please in future file one suggestion per issue report, to ease further tracking and discussion.

Everything that gets uploaded to the archive gets built for arm64 (librem5) automatically.

Will this automagically get built for the Librem 5 or do we have to put it into the build process for the Librem 5?

Pushed my minor changes to the repo. (pureos/packages/gpodder-adaptive.git)
Uploaded to the repo.

Thank you both for the replies - I'll try and fix up and build.

W: gpodder source: inconsistent-appstream-metadata-license share/metainfo/org.gpodder.gpodder.appdata.xml (cc0-1.0 != gpl-3+)

Are we changing the defaults?

Are we changing the defaults?

I'll try and fix the E: error but the one I worry about is this;

W: gpodder source: inconsistent-appstream-metadata-license share/metainfo/org.gpodder.gpodder.appdata.xml (cc0-1.0 != gpl-3+)

If you didn't touch the licensing then this is not an issue, if you did something with AppStream we should try to figure out this inconsistency.

So I ran the build with;

gbp buildpackage --git-debian-branch="pureos/master"

Lintian says;

E: gpodder source: invalid-version-number-for-derivative 3.10.21-1-1 (must end with pureosX)
W: gpodder source: inconsistent-appstream-metadata-license share/metainfo/org.gpodder.gpodder.appdata.xml (cc0-1.0 != gpl-3+)
W: gpodder: unusual-interpreter usr/share/gpodder/extensions/rm_ogg_cover.py #!/usr/bin/python
W: gpodder: unusual-interpreter usr/share/gpodder/extensions/rockbox_convert2mp4.py #!/usr/bin/python
W: gpodder: unusual-interpreter usr/share/gpodder/extensions/tagging.py #!/usr/bin/python
W: gpodder: wrong-bug-number-in-closes #T1096 in the installed changelog (line 3)
`

Thanks for including the pristine-tar branch. Would be cool if you were to mention how you're building this. For example, just pasting the commands you did to build the deb?

Are you using gbp? What's your conf look like?

@guido any feedback here? ^^^ yay, nay, something else? :D

ok packaged the adaptive version of gpodder at: https://source.puri.sm/pureos/packages/gpodder-adaptive

Packaging an adaptive Gpodder for Byzantium is most welcome - thank you @joao.azevedo

Also AFIK there is no deb version of gpodder adaptive in debian experimental, unlike with other packages like dino-im.

A couple of more reports about this issue in our forums:

In T1091#20414, @ctowne wrote:

Distribution upgrade worked for me.

sudo apt dist-upgrade

Distribution upgrade worked for me.

Another report from a user:

another report:

The patch has been merged and a new release made: https://source.puri.sm/librem5-apps/Stream/-/merge_requests/3

@joao.azevedo Sorry for the spurious ping. :-)

@jeremiah.foster you pinged the wrong João ;)

From what I can see the instructions for telegram-desktop 3.1.1+ds-1~bpo11+1 are the same as for other versions. That is to say, the build instructions appear to require you have API credentials;

Thanks for the clarification!

The patch adds no new features, it just makes the app work again

@jonas.smedegaard yes, this targets Byzantium.

@joao.azevedo did the outside World change, so that this is a regression, or is this a functionality which *never* worked on Stream and the patch is effectively a feature addition?

I assume this issue is targeted byzantium - tagging accordingly.

@jeremiah.foster pinging you here because you packaged Stream for PureOS.

thanks, this is working for now!