just for the record, I guess you mean it was uploadd to landing, @chris.lamb

I use Debian unstable on my laptop.

(just for the record: @chris.lamb in a chat discussion I was unaware of the existence of T439 and possibly Kyle was too, since our discussions was on whether it would be sensible or not to _open_ an issue regarding UK keyboards or maybe better to instead use a wiki for that.)

@heather.ellsworth Thanks for providing input on chris' keyboard issue - but since that is *not* a US keyboard it confuses matters to share that info here. Perhaps discuss with @kyle.rankin where to put your info as he has some ideas on where to most appropriately put it.

Thanks for the suggestion.

This was addressed in Debian today with the release of kodi 2:17.6+dfsg1-2.
Consequently should likely reach PureOS in ~1 month.

This is not really a duplicate of T255, but rather an issue concretely actionable since it is isolated to a specific package, whereas T255 is a meta-issue tracking the broader concept.

Keysafe is packaged for Debian - but only targeted experimental: https://tracker.debian.org/pkg/keysafe

ok. Please in future use chat for guidance - or the user support forum, perhaps - as issue tracker is better suited to track issues (bugs and pseudo-bugs like wishlist requests) tied to components of the Operating system.

I am confused: Did that actually fix the reported issue?

Seems an issue for @mak.

Seems an issue for @mak.

Seems an issue for @mak.

Seems an issue for @mak.

Seems an issue for @mak.

Seems an issue for @mak.

Seems an issue for @mak.

Please consider filing an RFP bug in Debian - and then reference the resulting bugnumber here: https://www.debian.org/Bugs/Reporting

Please consider filing an RFP bug in Debian - and then reference the resulting bugnumber here: https://www.debian.org/Bugs/Reporting

One way to inspect what is on encrypted volumes is typing lsblk in a terminal - volumes in branches off of a *_crypt entry is encrypted.

Perhaps you typed "255" in the popup dialog, where it expects "T255"?

At best, this is low priority.

Thanks for reporting!

Technically harmless - data reporting is disabled so only a rogue obsolete message tied with our rename from Mozilla to Purism (as per Mozilla trademark guidelines) - but bad user experience nevertheless.

ColorHug2 ordered - should be shipped tomorrow (from UK to Denmark, so if lucky arrives this week).

thanks for the input, @davidrevoy.

I co-maintain the package icc-profiles-free in debian where it would be appropriate to include ICC profiles once created.

this looks like an issue for @mak

What URL(s) are you talking about?

Hi Harvey,

The reason this was fixed by forking apparmor (not including an apparmor snippet with purebrowser package) was to address generally the need of application needing access to browser to also be granted that for PureBrowser.

Since firefox-esr 52.5.0esr-1pureos2 released 2017-12-19, this issue is solved by renaming only binary package (not source package as previous), to stay closer to Deban and ease sharing our patches with Debian and other derivatives wanting to do similar.

This was fixed since firefox-esr 52.5.3esr-1pureos2, released to PureOS landing 2018-01-21.

should be fixed in landing by now. Will keep this issue open until either someone using landing confirms, or it trickles into green and noone screams.

This issue is about following requirements defined by the GNU DFSG. Bug description is now updated to include relevant quotes from GNU FSDG.

Thanks for confirming, @francois.

I will fork apparmor with that change...

Ah, it seems AppAmor contains a hardcoded list of web browsers, and needs to be educated about the existence of PureBrowser in the file

/etc/apparmor.d/abstractions/ubuntu-browsers

That smells like a problem with AppArmor blocking too much for Document Viewer.

Please drop our fork of torbrowser-launcher: It violates GNU FSDG in that we lack control over what code ends on our users' systems.

I believe this issue relates not to the OS we develop, but instead to the infrastructure we use for developing it - and therefore should instead be tracked at https://code.puri.sm/Purism/Systems-Tasks

This is somewhat a design choice of Wayland: One application should not be allowed to "spy" on the windows of other applications.

Calibre seems installable again now.

To clarify - and address the comments from @heather.ellsworth above:

I am aware that we can recompile.

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.