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.

I filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946476

Fixed this way;

Removing libmutter may not be an option;

The Yubikey has a USB Keyboard driver included on the key. This may affect the way it appears in different operating systems.

Similar? -> https://github.com/projecthamster/hamster-shell-extension/pull/238

Should be there: https://software.pureos.net/sw/org.gnome.Lollypop :-)

This is the content of a Matrix chat I had with the Felix Häcker in this room https://riot.im/app/#/room/#shortwave:matrix.org

Upstream developers claim it does support things like CalDAV. Please discuss this with upstream.

Do you need git-all? Usually git-core is sufficient. git-all brings in things that require a different init system, this is why important system packages get removed.

https://salsa.debian.org/installer-team/debootstrap/merge_requests/37 Merge request sent upstream.

I agree completely and I thought actually that the "amber" dist was already upstream, but apparently not. I'll investigate and try and ensure the amber definition is in Debian's bootstrap.

Good point - I will add it to the wiki. I will also dig into why it is not coming via an update, although I suspect it may be because it is not available in the upstream configuration.

In T285#16002, @hansolo wrote:

In T285#14573, @mladen wrote:

Another solution is to add:

### Enable Echo/Noise-Cancellation
load-module module-echo-cancel use_master_format=1 aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" source_name=echoCancel_source sink_name=echoCancel_sink
set-default-source echoCancel_source
set-default-sink echoCancel_sink
# automatically switch to newly-connected devices
load-module module-switch-on-connect ignore_virtual=no

to ~/.config/pulse/default.pa or to the bottom of the /etc/pulse/default.pa file.

NOTE: You need to logout and login again or to restart pulseaudio with pulseaudio -k command for the changes to come into effect.

I don't have this snippet (or any sign of echo-cancelling) in my default.pa, running a fully updated PureOS.

Okay, agreed. Let's move this to the Apps_Issues bug tracker so that developers can see this and take action.

There is a certain amount of professionalism having this as a option - I believe it shows that we want to fix issues and that we're open about the issues we have. This can be empowering for users, most of whom come from closed, proprietary worlds where they never see the data that the send to nor see their issues fixed in a timely manner. At the same time, I agree with Francois that this may appear to be an invasion of privacy even if you can turn it off. The reason is that users don't know clearly what information is gathered and how. "Reports" are sent on "technical problems". I feel this is very vague and I imagine most people will turn it off, so my preference is to have this turned off by default and perhaps not part of the initial setup. If a user reports issues we can ask them to turn it on. Also, where does the collected information show up?

That would means that without a Nextcloud/Owncloud account I could set up a CardDAV/CaldDAV service using the option dedicated for Nextcloud?

I think that the upgrade may have brought in a new kernel and changed boot files. You may need to run update-initramfs or follow one of these solutions: https://tracker.pureos.net/w/troubleshooting/broken_upgrade/

Okay, but I believe that Nextcloud provides a standards compliant CalDAV interface which GOA can use. I'll double check.

GNOME Online accounts already works with free services like Nextcloud;

Confirmed that using ENV{PRODUCT}=="316d/4c4b/101" works as expected. Closing this issue, going to add documentation here: https://docs.puri.sm/Librem_Key/Getting_Started/User_Manual.html#automatically-lock-the-desktop-when-removing-the-librem-key

Wow, that is really cool Neil. I ran udevadm monitor as well, but I did not try to change the ENV variable to {PRODUCT}. I'll test that now.

So I'm not sure what's happening here but it cannot boot because it can't find your disks. Usually /dev/mapper maps your disk UUIDs to the luks encryption and /etc/fstab holds the info on your boot disk. Those are unavailable for some reason on your system.

Simply

apt install macchanger

I'll look into this as best I can - so far it looks like this may be an issue with libcrypt and may be intentional behavior.

https://tracker.pureos.net/w/installation_guide/mirrors/
We now have a mirror in North America. New mirrors will be vetted on an ad hoc basis.

Nicely done -- installing on your Mac is pretty cool. :-)