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!

Adding the full syslog error containing all of the call traces{F44013}

Show. The installation Worked =) thanks.

@tharvill That was the case. Did:

I had a similar experience. I believe (not sure) that PureBrowser switched it's app dir from ~/.purism/firefox to ~/.purism/purebrowser. When I fiddled with profiles.ini in the two I could get back my add-ons, etc.

It looks like the bug is in debian too: https://bugs.debian.org/889990

Possibly related: I had a couple of Firefox extensions installed prior to upgrade that I can no longer install via addons.mozilla.org - I was previously able to, but now I get an error saying I need to install Firefox in order to install.

In GNOME Tweaks, change "Mouse Click Emulation" back to "Area".

In T267#5207, @chris.lamb wrote:

Can you confirm this is being run with *no* ~/.config/chromium ? (eg. moved out of the way prior to running?) I cannot reproduce this, alas.

Ideally, Software would automagically open and install third party .debs and no one would have to even worry about gdebi or Archive Manager wanting to install the app.

Sure, but not with gdebi!

That is not a job of PureOS and this is PureOS tracker. Also PureOS is only 64bit and last time I checked, steam was still usually 32bit built so you would need plethora of 32bit libs.

I'm not suggesting that Steam be included in PureOS. These are packages needed to run the Steam client. Are they non-free? If a customer chooses to install and run Steam, they should be able to.

You surely want a way to open compressed zip/tar.gz/tar.xz etc. archives in the default install.

Steam client is nonfree software so it will never be part of PureOS.

Either povray 1:3.7.0.4-2pureos1 went through NEW when I uploaded it on November 27 - three days _before_ your changes, or in went through NEW caused by your interventions.

The package went through NEW after I synchronized it with Debian, which leads to this situation now:
INFO: Can not sync povray: Target version '1:3.7.0.4-2pureos1' is newer/equal than source version '1:3.7.0.4-2'.
So, we can only properly sync this with Debian when the Debian version is newer (the archive will not allow downgrades).

Done

Reopening but lowering to low priority: Package is currently fixed but likely to be dropped (see T330) and may then reappear and if so need fix reapplied.

If this is happening on Librem 13v2 laptop, please see this: https://tracker.pureos.net/T328

tested with windows on corebeoot. No issues. Only when we install and test pureos that have this issue.

I have to add, that this is a clean install. (WIth AMI bios)

Any chance somebody could run the above

(w/no patches.)

Will do! Thanks!

OK, it may be from an older install or something has gone wrong on my side for some reason...