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.

@jeremiah.foster people are stepping on this while trying to bootstrap amber on Debian - would you take a stab of trying to get this into mainline deboostrap so boostrapping pureos becomes simpler everywhere in the future? I'm happy to help here.

Then current options don't include general CardDAV and CalDAV support.

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

Perhaps. But I imagine you'd want to ask upstream in GNOME to determine for sure

There's no older kernel to boot from so I can't run update-initramfs. Looks like I would need to reinstall if I want to use PureOS. Thanks for your help.

@nicole We are already tracking this here: https://tracker.pureos.net/T298

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.

I just wanted to point out, that it doesn't seem to be added via an update (but it should - in my opinion, if that's not an option it should be probably added in the wiki?)
I'm fine with the manual edit. :)

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.

@jeremiah.foster ^

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.

Just came across this thread after consistently having issues in video conferences at work with Librem15 v4.

Sorry for my confusion @guido .

I don't know how many people use this feature on Debian but I doubt that many people concerned about privacy, as Librem users are, will want to switch this feature on.

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

Thanks for your input @jeremiah.foster.

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?

In T837#15974, @jeremiah.foster wrote:

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

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/

If this feature is really important for the PureOS team, then we should keep it.

related https://source.puri.sm/Librem5/Apps_Issues/issues/162 - i think it would be a good feature to have if people opt in - it's by no means about convenience but to give us enough data to fix issues. It's also data that might be hard for the user to provide.

No, I turned it on for the first time followed the prompts, wrote down my passwords / passphrases and ran the typical sudo apt update and sudo apt upgrade.

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

As @stefannagy references, its just CardDAV and CalDAV in general, not just Nextcloud/Owncloud as he already said.

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.

After running the following command

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 can only speculate that it might be a Gnome-specific issue. I have no idea. I'm sure it'll be fixed eventually.

The wording has improved. Words such as GNU, Linux, Gnome, Plasma and distribution have been cleverly avoided, which is a good thing IMHO. A bit of redundancy is immediately obvious though. But overall it's going in the right direction. I'm pretty certain that 1 installer for both flavors is the right approach.

In T822#15824, @jeremiah.foster wrote:

This might be better addressed upstream, presumably uBlock Origin itself audits the remote lists?

Thanks for your response.

This should be fixed in amber now :-)
Thanks for reporting the issue!

I've created a dpkg reppo at

@mak gcr secmem is similar to what gpg's gtksecentry does using

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.

There are no resource limits on the container, so I have no idea what goes wrong here.
Does this code access a device that is maybe unavailable?
Unfortunately I am traveling in the next weeks, so I don't know if I'll have time to look into this.

@jeremiah.foster @mak Can you look into this?

@jeremiah.foster Can you please help with this?

Done :-)
The update should be available once it passes QA and the regular delay period.

just to add the detail how things will break for users

Well, it seems quite easy to me to fix T663 (blacklist all non-free services). But you can't whitelist CardDAV and CalDAV support, it needs to be implemented first… The upstream bug report is pending for six years now.

Its like two POVs about the same.

Oh, I didn't see that. However, this report is not about the promotion of non-free services (like T663) but about the missing support (and thus promotion) of common open standard protocols.

I already made a report about the freedom respecting options in GNOME Online Accounts here --> https://tracker.pureos.net/T663

Yes, and that means that by default (to my knowledge) PureOS supports

• Google
• Microsoft Exchange and
• Nextcloud/Owncloud

for calendar and addressbook sync. The only freedom respecting option is Nextcloud/Owncloud (which uses these standard protocols by the way).

This is a report for GNOME. It seems is not solved yet here. The logo changed but to this. But thank you, then it seems is truly specific from GNOME.

@mladen Thank you for your explanation.

Evolution is on PureOS repositories but not installed by default.

I can confirm this issue.

@EchedeyLR No, I am communicating with the reported via Purism support channels, we determined this is a hardware issue.

I think it could be "incomplete" because the information is very generic but ofc could be a software issue.

Not a software issue, closing.

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. :-)

This might be better addressed upstream, presumably uBlock Origin itself audits the remote lists?

Agreed. For now it has though we'll see what happens when upstream support for 60.9.0esr is done and we forced to go back to 68esr.

Might be related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934504

The first kernel message regarding firmware can be safely ignored.
The second message from cryptsetup needs to be resolved by ensuring that you give the correct password (in the correct case and with the correct keyboard layout, e.g. NumLK off, etc.)

@gorgeous Any news? I think a reinstallation with the latest builds will be highly beneficial, let us know if that worked.
https://pureos.net/download/

Seemingly the Plasma flavor has received some love after all. Thank you so much!

Thank you for fixing it.