I am not able to reproduce this issue on the latest beta.

Todd, can you try adding your username to the following additional groups , this should solve the packagekit failing and will prompt for the authentication.

OK, what configuration change do we need within PureOS to have this be the default?

The following works
$ su -

1. export DISPLAY=:1
2. gnome-software

the change is applied in the gnome-mime xml file for purebrowser,

The new gdm screen part of the gnome-session package is uploaded,

The contents of /etc/modprobe.d/purism-psmouse.conf are not in a working state. The line needs to start with the keyword "options".

This is quite important as the website clearly advertises HTTPS EveryWhere and PrivacyBadger as shipping with PureOS.

new revision is uploaded containing the changes mentioned above.

new revision is uploaded containing the changes mentioned above.

new revision is uploaded containing the changes mentioned above.

@hema.prathaban is working on this one (francois gave us the needed images)

@francois can you test with latest beta?

Can you test latest beta?

As we will focus on calamares, this one fades out as not important to us anymore.

This is for sure on our top list but it will take effort (anyone interested in what cypress opened with their documentation can contact even for hire).

Closing it now, be sure to repopen if you detect the same bug again.

I checked and it works. Anyone feel free to reopen bug if it is not resolved. Also, we removed Firefox entirely from repo.

Epiphany is now working by adding:

New purebrowser package is uploaded to address this.

can you also add /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProces in the list and check

Works :)

I will look into this.

Everything works now :-)

purebrowser might need to provide firefox-esr and iceweasel as virtual packages...

That request to add another repository is something I have also seen every once in a while a few months ago - I think it's an upstream bug.
Let's see if that happens again when this issue is resolved.

This should be fixed automatically in a few hours when the archive files have been regenerated.

@todd Hmm, that's not much information... But it's pretty safe to say that grsec prevents some action executed by the polkit daemon or frontend service which leads to a successful grant of permissions.

Why is the source "none" - that does not make sense.
I guess some label is set incorrectly in appstream-generator or dak.

From my tests, it is grsec related. We will need to dig deeper into this before we put grsec as default.

Please run sudo journalctl -f in a separate terminal while trying to perform the privileged action, and paste the output here. That might give us a hint on what is going on.

I can't reproduce this issue here, might be related to running a grsec kernel.
I'll try with that in an hour (and I also have a couple of other ideas, but grsec being the problem seems likely).

Hmm... Is policykit-1-gnome and policykit-1 installed? I'll have to look into that...

I tried both of these:

This should be resolved with the last GS upload.
Will come back every time GS is updated in Debian until we rebuild packages for PureOS (but I'll keep an eye on it).

This should be resolved with the last GS upload.
Will come back every time GS is updated in Debian until we rebuild packages for PureOS (but I'll keep an eye on it).

Adding /usr/bin/epiphany-browser to paxctld doesn't solve this?

This needs to be solved within PureBrowser package (which @hema.prathaban will take care) as Iceweasel shouldn't be part of our archive (I already explained this to Hema day or two ago).

I could install it from command prompt: