Thank you! Changing back to "Area" worked

https://tracker.pureos.net/w/troubleshooting/secondary_touchpad_button_problem/

Hi @chris.lamb,
can you fast-track if this fix is in Debian yet and if not package quick fix for PureOS (and also ping Debian maintainers about it). Coordinate with @mak to get this fix in ASAP as it affects our users a lot.

Didn't upload the screenshot

This is from user ezs777 at forums.puri.sm:
You need to change the mouse settings in GNOME Tweaks back to “Area”; for some reason, the latest update changed it to something else.

Ok, I see what you mean!

This issue seems to resurface after an update to Chromium. Removing the /.config folder works temporarily but the crashing issue re-occurs.

Gnucash is not in PureOS either, because it has release critical issues in Debian which PureOS is derived from. Details at https://tracker.debian.org/pkg/gnucash

We might get assurance from Tor Project. That does not, however, change the fact that we rely on a third-party for governing our rules, which I find problematic.

Indeed I confused the terms. Thanks for spotting - corrected now.

Or can we get some kind of assurance from the Tor Project about the continued freedom of the Browser Bundle?

I think you mean "torbrowser-launcher" above?

I suspect the Debian-but-released-only-in-contrib package was done that way due to the slow release cycle of Debian and the need for potentially quick update of the code. If that is the case, then a solution (other than simply giving up and kicking out torbrowser-bundle from PureOS) would be to replace with new package torbrowser - which could be maintained in Debian but there flagged as unreleasable similar to how other fast-moving code like Bitcoin is handled.

Possibly related: I'm having a similar issue when trying to run several installers or standalone EXEs.
Doing "wine foo.exe" (where foo.exe is known to be fully compatible with wine) yields:

it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"

A lot of Windows applications are still distributed as 32-bit binaries to avoid compatibility issues, so this kind of makes sense. But wine32 is not in the main PureOS repo because (IIRC) PureOS is all 64-bit code. So i386 isn't an enabled architecture, nor does the repo distribute 32-bit software.

This issue was fixed since 52.6.0esr-2pureos1.

xul-ext-ublock-origin now recommended by the metapackages pureos-gnome and pureos-plasma.

xul-ext-https-everywhere now recommended by the metapackages pureos-gnome and pureos-plasma.

@francois Yup, it absolutely should. Edited.

@jwolf You second line should say :

From customer email :

Intel SGX is a technology that provides protection of predefined secrets even in a case of system compromise by creating SGX enclaves. I currently need to run several projects that makes use of SGX on the librem and that's why I need it enabled.

IT's done for l13v2 and l15v3, need to add the iommu patches for broadwell in the branch and test it for l13 v1 as well

Yep, and we will very gladly do so! thanks for the reminder!

@chris.lamb as noted in https://bugs.debian.org/889990 I think logind should adjust the ACL as it does for the dri and audio devices.

Can we close this one?

So, from PureOS's point of view, I wonder whether we should do any of:

That worked for me too. I did the killall libvirtd and so had to do /etc/init.d/libvirtd start to bring it back up without a reboot.

That worked for me too!

That seems to have worked. I ran into some additional issues with the storage pool, but that was mostly from me trying different things. Spun up a fresh user, added it to the kvm group, and successfully created & started a VM. Troubleshot the other issues on the main account, and successfully created & started a VM.

This issue persists on purebrowser 52.6.0esr-2pureos1.

sudo adduser <youruser> kvm

newgrp kvm
killall libvirtd
libvirtd

I think I've found the issue: Can you try to add the user to the KVM group and see if it helps?

same problem from a n00b - i can upload the same output info as above if helpful. have tried 3 different distros with the same result. help!