Is this on reboot?

I can't reproduce;

I can't reproduce;

$ sudo apt install gnome-contacts

Which device is this @francois?

My python version is;

I did;

Thanks for the update @alexngould

I'm not sure - it looks like they do have a signed release file here: https://mirrors.sonic.net/pureos/repo/pureos/dists/byzantium/

You can try the main repos;

Exciting - we should test this in Byzantium and hopefully we can close this bug.

If you follow the upstream discussion you can see that they're already on it! :-)

Debian maintainer states "I'm concerned that the addition of vendor_id might cause an ABI break. There are multiple packages that use libnitrokey in Debian (not just nitrokey-app) and so we can't silently change the ABI."

I've pulled down the Debian packaging from Salsa and reused that. I've added in the patches from upstream and built package for PureOS Amber and Byzantium.

Looks like this is the diff;

Matthias is looking upstream to see if the fix has been already made in effort to de-duplicate work.

Has the PoC been tested with the app?

So, if I understand correctly, this repo holds the patched libnitrokey: https://source.puri.sm/joao.azevedo/libnitrokey/

Thanks @selea.

I'm happy to work on this TODAY but this is not "Unbreak Now!" because it is not breaking anything for our users and, we have a perfectly viable alternative that is a tiny bit better, namely the Librem Key.

@hansolo Yes, thank you! What I hope to do is to determine that any action we take affects only the Librems with a US keyboard. We're going to have to determine the best fix for the US keyboard and then deploy.

@mak Do you have a German keyboard now? Or is your L13 v4 US keyboard?

I'm going turn this task into a milestone so we can track the release period.

Both those mentions in the logs at boot time are "normal".

Apparently an upstream bug: https://github.com/systemd/systemd/issues/12401

Thanks for reporting!

The versions in Amber and Byzantium are not far apart; https://software.pureos.net/search_pkg?term=libccid
In Debian's Salsa it appears they're about 88 commits apart: https://salsa.debian.org/rousseau/CCID/-/compare/ccid-1.4.30...ccid-1.4.32

On my L13 v3 I get;

To confirm, I'm going to update to this commit: https://review.coreboot.org/cgit/flashrom.git/commit/?id=05c629be2964bcee368c03d805747da15281856d

Now one can just call docker and the version of the PureOS distro image you want, like this;

I think this is worth looking into - let me see if I can upload a new version of the library packaged for Amber.

Can we retry this with the later Byzantium images? This bug was filed before there was an updated image.

Thank you for that. It looks like you're using PureOS Amber (at least, that's the version of systemd that is in PureOS Amber).

Debian does talk about this as a configuration option in their wiki: https://wiki.debian.org/PulseAudio, but on cursory inspection, I don't see a bug filed for changing default settings. This may have to go further upstream to PulseAudio itself.

I can't reproduce this on my Librem 13 v3 running Byzantium. But, I will look into seeing how we can change the default.

Amber is now officially in Debian's debootstrap. Next is Byzantium. Do we want to have amber-phone as well?

systemd should be version 241 in PureOS Amber and 242 in PureOS Byzantium.

Which version of systemd are you using?

From @mak;

There are policy decisions needed

• which key do we sign this with?
• the archive key?
• a new key?

It's difficult to automate due to security boundaries in the infrastructure and code needs to be written for it

We can perhaps sign this file: https://downloads.puri.sm/byzantium/gnome/2020-02-15/checksums.sha256sum upon each release.

Closing because we've moved to Amber and this references Green.

I'd like to set up an OpenQA instance. But it looks like I can't use PureOS or Debian to do so. The only blocker is a MR in Salsa: https://salsa.debian.org/debian/os-autoinst/merge_requests/1/diffs which looks pretty reasonable. @jonas.smedegaard does Hideki Yamane-san hang out in the Debian-perl channel, perhaps we ask him to merge that diff there? Otherwise I'll go ahead and install on SuSE (heaven forbid.)

Those fields are just inherited from the upstream because we bring in the package as a binary.

With regard to this policy change: https://puri.sm/posts/an-epiphany-regarding-purebrowser/ can we revisit this (and other Purebrowser issues) in PureOS so that we can determine the best course of action for deprecating Purebrowser.

As we're working on the search page right now, perhaps this is a good time to close this bug?

Yes, this needs review and triage.

I've been using an opensnitch deb in regular, daily usage for a while now. It is functional, not so buggy in terms of interface and functionality. It does leak memory and can take up a significant chunk of my 16 available gigs of RAM, more than 80%, which slows my machine down to a crawl. That said, we might be able to work with the developer. Having this in PureOS is a powerful security story.

Thank you Adrian - where are the packages, on 'slat'? Or are we building this in the CI?

I'm not sure if this is complete, but I'm confident Adrian and I can finish this task off if it is not.