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

Thanks for reporting!

After several days and upgrades, it seems, that unattended-upgrades got removed automatically, so I don't bother anymore :)

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

unless it's a pure bugfix release

On PureOS Amber, running lsusb I get:

On my L13 v3 I get;

Running the command usb-devices the Librem Key is listed:

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 guess the best approach in resolving of the issue would be a collaboration between many parties interested in FSDG-compatible fork of Firefox.

I had face connectivity issues and quite regularly. I can not blame free vpn services as you wont pay to them, though mentioning some of them who create less issues(https://www.reviewsed.com/best-free-vpn-services/). But even i saw such issues in premium packages so i would also recommend to go with Expressvpn or surfshark as they have great advanced features that provide you smoothless service with out any disruption.

Do we need a new version of the library in amber, or is there a patch that we can apply to the amber version? Uploading a new upstream version always comes with some risk of breaking other stuff (unless it's a pure bugfix release).

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

@mak @jeremiah.foster this new version of libccid just landed in Byzantium.

a an issue that remains is that we don't have debug packages for regular pureos-amber. This can often be helped by using the ones from Debian but not always when e.g. pureos lacks a bit behind. This makes it unsafe to enable by default.

dbgsym packages for amber-phone-staging do work now via

@mladen ^^

This issue still persists in PureOS.

Perhaps this will also fix T803 ?

Contact NitroKey app developers and ask what is needed to accept the patch

Perhaps this will also fix T803 ?

@jeremiah.foster @mak can we consider the above?

New version of libccid ((1.4.32-1) ) has been released and it includes our upstream packages to include Support for the Librem Key USA (
https://salsa.debian.org/rousseau/CCID/-/tags/ccid-1.4.32)

wondering whether chromium (not the ungoogled variant) complies with FSF endorsement. Discussion ongoing in the forum...

Still there in 1.8.4
It's any custom action. Leaving the command blank, it kicks back "command not configured", but put anything in there and it crashes.

In T818#16690, @SagarPrakash wrote:

In T818#16052, @CarloDz wrote:

Online privacy is some how tricky to handle as things are becoming complicated but nevertheless online privacy tools like tor, vpn, password manager etc. As per the BuyBestVPN, most effected and widely use tool is VPN due to level of encryption and anonymity.

Thank you for sharing the valuable site which actually talks about privacy, security and online privacy tools.

In T818#16052, @CarloDz wrote:

Online privacy is some how tricky to handle as things are becoming complicated but nevertheless online privacy tools like tor, vpn, password manager etc. As per the thevpnexperts, most effected and widely use tool is VPN due to level of encryption and anonymity.

The OEM downloads link is broken. Should probably be replaced with either
https://downloads.puri.sm/9/oem/gnome/
or
https://downloads.puri.sm/amber/oem/gnome/

@mak main issue here is that i can't tell if the correct match string (so i did not use any wildcards) or if there are other devices with the same match that might break.

Like this?
https://github.com/systemd/systemd/pull/11516 or this https://github.com/systemd/systemd/issues/15360

Hmm, I don't have a Librem with a German keyboard so I can't test this and would have to apply this change blindly.
This looks like something that should also go into upstream systemd, right?

Oh btw, this has to be applied to v3 Librems as well, because the fix for the US keyboard breaks the | key on them as well.

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

Looks like a lot of the dependencies use old versions.

---------------------------------------------------------------------------------

That is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765936 and documented here documented in /usr/share/doc/libvirt-daemon/README.Debian.gz . It would be best to just set the correct capability in pureos (setcap cap_net_admin+ep /usr/lib/qemu/qemu-bridge-helper)

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.

@jeremiah.foster great! i'd skip amber-phone since it's just an overlay and we want to merge for byzantium anyways.

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

This is a workaround: https://gitlab.gnome.org/GNOME/epiphany/issues/838 (disable flat-volume option).

Definitely need this, had this fixed already several times, but it seems to get overwritten when doing updates.

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

@davidpluseipi Yep, this is the same problem. I don't think the package is maintained at the moment, so it's easier to uninstall 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 think the user manual mentioned on this page is missing sections that I and other users would find very helpful:

Yeah, i've seen that but that assume the user understands what is going on (and involves user intervention for s.th. that could be automatic).