@jonas.smedegaard I'm sure it was your idea :D

@jeremiah.foster There was a time when we were concerned about including tools like pip [1] in PureOS. My understanding is that we have since decided this is not a grave or urgent concern, but we would still prefer to issue a warning when the user installs a tool like this.

I'm not sure what tokens do, but I didn't mean to cycle like that :-)

This package is basically unmaintained, so I'll have to find another solution.

This is blocking https://tracker.pureos.net/w/pureos/tips/prevent_device_tracking_by_untrusted_access_points/

@jeremiah.foster Hello! I tested again (up-to-date libraries as in your comment) and still get the error.

@jeremiah.foster I'm afraid I didn't make a note of which ISO I used :( I guess if the issue doesn't recur on the latest ISO we can close it.

Recently retested with the same Logitech headset and these package versions. It's working again!

There is an RSS bot that reposts Purism blog posts in the #community-general:talk.puri.sm room. I'm afraid I don't have any details, and the person that implemented it is away. But if you can generate RSS output that might be a start!

Note that FSF give GitLab a C-grade "Acceptable hosting for a GNU package", noting "All JavaScript code served to the client is free, but does not work with LibreJS enabled."

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

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

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.

I don't have a straightforward way of reproducing this. Let me see if I can find someone who can...

Created https://tracker.pureos.net/w/troubleshooting/purebrowser_first_start/

It is a package manager. You can use it to install a .snap file (snap package) that you have downloaded by some other means, or that you have built yourself locally:

Knowledgeable users will already understand that PureBrowser is a privacy-respecting fork of Firefox (i.e. based on Mozilla technologies). But I suspect (untested) that an everyday user would wonder:

I've reassigned this to myself to post these steps on the https://tracker.pureos.net/w/troubleshooting/ page.

Looking forward to the fix! Created https://tracker.pureos.net/T534 for the Mozilla logo issue.

Still to do: check if the ping URL is configurable (and log an issue if it isn't)

Pings the URL http://network-test.debian.org/nm to test connectivity. Would https://www.debian.org/something be a better target? This would be protected from tampering, and indistinguishable from any other Debian website address.

Tested PureBrowser 52.9.0 with a fresh profile per https://tracker.pureos.net/T524 . Immediately visible issues (screenshot below):

Is this a duplicate of https://tracker.pureos.net/T202 ?

Tested PureBrowser 52.9.0 with a fresh profile per https://tracker.pureos.net/T524

Tested with a fresh profile per https://tracker.pureos.net/T524

You can create a fresh profile, launch PureBrowser and then delete the profile:

@SheepKid12 regarding the PureBrowser version, I get:

• Download the latest Twemoji/eosrei release from https://github.com/eosrei/twemoji-color-font/releases (in zip format)
• Extract TwitterColorEmoji-SVGinOT.ttf
• Delete /usr/lib/purebrowser/fonts/EmojiOneMozilla.ttf
• Copy TwitterColorEmoji-SVGinOT.ttf into that folder

Another option for a complete and regularly updated color emoji set is twemoji. It is not yet packaged for Debian afaik:

Note that this lead to strange emoji rendering in PureBrowser: https://tracker.pureos.net/T437

Considering that we target everyday users, and this affects the first-time experience of our default terminal, is it feasible to maintain a patch/fork of Tilix until the proper fix is applied upstream?

It appears the compatMode boolean no longer resolves this issue (tested with the uMatrix link above). I'm not sure what has changed, possibly AMO now requires a newer version of Firefox?

Thanks for confirming that @mak , much appreciated!

@mak I've been meaning to file this issue for a while, so it could be the update happened between my last install and me actually filing the issue. Since you've confirmed it I'm happy to close.

Ok, I'll try revert my configuration to something default looking and see if I can isolate the issue. Please consider this low priority in the meantime.

I understand, my comment was meant to be, er, self-answering or something.

User-friendly or paranoid? Why not both? Sounds great :D

Is it possible to just make the name friendlier? Perhaps name it on installation ($SYSTEMNAME-disk) or display it like a credit card: "disk ending -1234".

As a side note, I am now a happy user of "GNOME Packages", which does work in Wayland.

Just got these changes from an apt updated and rebooted. Works like a charm, thanks!

This package has arrived in green (got it via apt even though http://software.pureos.net/package/source/green/fontconfig still lists -4).

http://software.pureos.net/package/source/landing/plymouth migration excuses currently list:

@chris.lamb Thanks for the suggestion. I tried only Alt-F2 and it works no better (or worse) than button mashing without it.

1. Rough starting point (comments welcome)

We might want to also include Symbola (fonts-symbola) which in my experience fills the gaps on more obscure and newer emoji (and other bits of Unicode). It seems Symbola is not that great for emoji, so I withdraw this suggestion. Still good for ancient fonts, but I'm not sure those will see everyday use :D

Part of the solution may involve backing up (not syncing) your own GPG key, which could be achieved with something like Keysafe

Perhaps I should have been clearer, this was just a query about *how* to check that my second disk is encrypted. You have answered my query so I closed the ticket :)

Thanks! lsblk results: