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

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

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/

I got it to work by pulling down the ci-repo.key, and adding this line to sources.list; deb https://ci.puri.sm/ scratch librem5

I can use add-apt-repository without issue, but I get other problems with the repo;

The workaround is to comment out the call to UbuntuDrivers python module in usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py
Line 61 to 65 starting with

I see similar behavior;

On the KDE Plasma release from 31 August when I try to run the memtest menu entry it merely says "/live/memtest not found." I'll test the latest build from today but are we including the memtest binary?

I tested the ISO from August 31st. It worked well and looks good, tempting to switch to KDE. :-)
I'll find a way to add a button for downloading Plasma on the web site.

I think this is a good idea. I'll test the ISO since it's recently been rebuilt.

An error occurred during a connection to error.woolyss.com.
This problem can sometimes be caused by disabling or refusing to accept cookies.

WebKit is in fact the same browser engine that Apple's Safari uses. https://webkitgtk.org/

The plan is actually to deprecate PureBrowser as Mozilla doesn't share the same goals we put forward and that makes it a lot of work to ensure that our user's privacy is protected.

top and htop are great tools for measuring CPU usage and diagnosing this issue. Fans usually start running at a certain temperature threshold and the CPU reaches that threshold when it is heavily used. The tools show which processes are using CPU, for how long, etc. If we could start with either a screen grab (try screen shot tool) or simply put in your "load average:" data - that would be a great start towards diagnosing issues.

In this case;

Yes, I think you're right. We'll discuss this and assign internally.

Between this and the subtask added by Jeremiah, is this a hardware issue or software issue?

Did you check the hashsums on the USB drive for the image?

When I surf to the https://giantitp.com I get this message, which seems to point to some serious misconfiguration;

First test image created: https://cloud.docker.com/repository/docker/miahfost/pureos

I found Guido's pureos.sh script upstream: https://github.com/agx/debuerreotype/blob/pureos/pureos.sh

@guido If you were to outline the steps you took for creating the 'green' docker image, I could follow that and put them into a pureos.sh script to submit upstream. I'm also setting this up to be automated.

https://tracker.pureos.net/T298 May be useful here as well.

That URL looks good and has some good resources. It also fits with my understanding of EDID and KMS.

In T809#15183, @richard.kolla wrote:

PureOS defaults to Wayland and has for sometime as per my testing of old ISOs. Both the customer and myself are using Wayland. He tried X.org and got the same result he said.

There is a way at least find the capabilities of your graphics card to see if the card support's your screen's resolution;

reportbug is a debian-native package. This means its only meant to work with Debian. We'd have to do code refactoring for PureOS.