Thanks @mladen.pejakovic that does, sort of, solve the issue. However @jeremiah.foster , we're shipping a browser with menu items that go nowhere when users try to ad addons... how could they possibly know to go into the browser registry about:config ?

Thank you @mladen.pejakovic. From what I can see, this essentially solves the issue no? I think we should close this issue. If we need discussion Sean on the list of add-ons you specified (DuckDuckGo Privacy Essentials, Decentraleyes, Privacy Badger, Privacy Possum, Exodify, TOS;DR, Polisis), let's use a separate bug to track that issue.

The helper script has now been split out into a new dbus-activated daemon. It's not the quality thing that I want yet, as the code needs some refactoring to work properly in an async way and the interface is quite crude, but it's good enough for a start.
See https://source.puri.sm/pureos/core/pureos-init-disk-crypto

For #2 see the note here: https://tracker.pureos.net/w/troubleshooting/firefox_compat_mode/

Shouldn't #1 be in the form of a wiki page or other policy document? Then we can take whatever concrete issues or features that need to be worked on by engineering in atomic, bite-size peices?

So this issue still exists for me, namely I'm unable to install extensions. Here is the user agent that PureBrowser left in my logs;

Followed up in: https://bugs.debian.org/906609#90

Sure thing. Guilhem's Librem Key has arrived and is playing with it. :)

@Jeremiah thanks for weighing in.

I have two perspectives, one on the content and one on work flow. As far as content is concerned I think it is addressed by folks who know the issues better than I, so I'm not going to wade in on that. As far as work flow is concerned I defer to Jonas who has to use the tool to be efficient, so he gets to decide how the work is broken down.

It probably makes sense to keep this open until the package shows up in PureOS (having it in Debian is nice, but not sufficient). Once it makes its way into PureOS then sure, close the ticket.

@jeremiah.foster adding you for your perspective on this.

thanks @mladen.pejakovic that is helpful. I made some slight wording changes to the warning so we don't scare away users. I'll be working with Jeremiah on this to see if we can come up with a smoother solution, but this wiki entry is much needed in the meantime.

Wiki entry for TorBrowser: https://tracker.pureos.net/w/pureos/tips/torbrowser/

This just got fixed with yesterday's updates. Excellent!

Indeed - package has already entered landing so should migrate to green in few days: http://software.pureos.net/search_pkg?term=pyotherside

Looks like the package has got new maintainer and is progressing in Debian. I presume it will then end up at PureOS as well.

This was actually pushed back too many times, and I should address this sooner - especially since there is other pending work on this module.

That doesn't help, the journal also contains the changes.
The good thing is that you'll only ever be able to read the password if you have root access on a drive that has already been unlocked using that password.

In the mean time could you add a task that erases/truncates /var/log/auth.log after that script runs?

I am aware of this for a long time, it can only properly be fixed by making a proper service out of this tool, which I have not had the time to do yet due to piles upon piles of other critical tasks.
I might actually implement the service soon though, in the process of fixing swap-related boot issues.

Updating the command not found database didn't work as there are no Contents files (/var/lib/apt/lists/*Contents*) which are required by update-command-not-found.

I assume that building the database failed (though update-command-not-found didn't issue any message), as /var/lib/command-not-found is empty, which seems to be the (new?) place of the database (according to `/usr/share/command-not-found/CommandNotFound/CommandNotFound.py).

I am getting the shutdown issue in laptop and also getting the error code 1001 in my system. I also try on system error 1001 for the help purpose but did not get any response.

There is another work around that I am using. It's an extension: Fix Dark Theme Input Boxes by https://gitlab.com/Roboe/userscripts

There is a file, /var/lib/AccountsService/users/rah, that contains the following:

[User]
Language=en_US.UTF-8
XSession=
SystemAccount=false

Confirmed issue is occurring with the package versions below...

Confirmed issue is occurring with the package versions below...

Indeed https://gist.githubusercontent.com/lamby/e45c7a221defe75db026ee529d00c789/raw no longer cleanly applies, will need to redo...

Link dump:

and, as luck has it, we have movement there:

https://tracker.debian.org/news/1005629/accepted-cryptsetup-2205-2-source-amd64-all-into-unstable/ was just uploaded to Debian, closing https://bugs.debian.org/888916 and https://bugs.debian.org/903163

Updated: https://bugs.debian.org/906609#71

ACK and I even looked at this ticket yesterday - we are still semi-blocking on the cryptroot and other refactorings in the Debian stuff but after that we will be able to merge this quickly. :)

This looks like a duplicate of https://tracker.pureos.net/T559

Non-urgent ping? Every time I boot I'm hoping to see it. (Only after an upgrade, otherwise that would be *truly* wishful thinking.)

I've closed this as invalid since I can't reproduce it.

@kyle.rankin Thanks for adding me to this ticket and apologies that it took longer than anticipated to get around to replying; I not only had to read the extended discussion here, I also had to do some research in order to work out what the situation is.

Filed MR as https://salsa.debian.org/qa/jenkins.debian.net/merge_requests/15

(Of course will keep this open; was just following-up here)

Thanks for the update. Let's leave this ticket open to track the work in bringing the updated cryptsetup package into PureOS. Once that package exists in PureOS we can close this ticket.

Pinged https://bugs.debian.org/906609#51

Pinged Debian bug...

FYI discussion and work on this is mostly happening on https://bugs.debian.org/903163

This was uploaded a while ago and is now in Debian, so closing.. (no further obvious action here...)

My recommendation for this would be only privacy-respecting choices:

@sean.obrien I now clarified scopes of issues T110 and T156, and here.

This issue is now about PureBrowser linking to DuckDuckGo non-free JavaScript.

Even if this was meant (also) as a duplicate of T110, we can reuse it to track (only) the related issue of avoiding Javascript not Free licensed.

It seems to me that the issue here is the question of the licensing status of JavaScript loaded by DuckDuckGo.

Sorry for you that your hardware cannot work with Free software.