Are you sure the branding will be an issue? Afterall, the Plymouth bootsplash is branded as well.

I can confirm that it has been fixed now.

You also need to have base-files >= 9.6pureos2 to make this work. All the necessary changes should happen via a regular update.

Apparently not fixed as you still get the same issue after applying the latest updates.

This is resolved now, please ensure you update to python-apt 1.4.0~beta3+pureos1 (should be available via regular updates soonish).
If the issue is not fixed, please feel free to reopen the bug.

This should get rid of all the branded wallpapers (that will always be a problem with the FSF) and only leave the latest (landscape) ones.

Thanks Chris! It fixes the issue for me.

@mak, sorry for the late answer, I was away on holiday.

I disagree there is any issue here at all, and recommend to *not* apply the Parabola patch, as it seems to be a result of simple search'n'replace for _potentially_ bad strings - without then checking sanity of the resulting changes.

The diff I had already done, but your description on *why* you changed as you did is quite helpful.

Reimported all available dscs. Not all are available for some reason.

Possible relevant upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=763005

Can this help:

1. Import purebrowser from firefox-esr:45.4.0esr-2
2. Add Hema's work as a branch or somehow diff the two
3. Cherry-pick the relevant/kept changes
4. Fix actual issues! \o/

Hmm, looks like Hema forgot to write XML definitions for almost all of the images...
I'll do that as soon as we know how many images we want to keep in the default install.

For the record, the compressed size of the images bundle is 50MB (!) now, the installed size is even higher. I really think we should reduce the amount of wallpapers that we ship by default.

I worry about bitrot for PureOS too.

We now have a *massive* amount of wallpapers in the theme package, I think it makes sense to remove some wallpapers that we don't need.
You can view all wallpapers currently in the package at https://github.com/purism/pureos-artwork/tree/master/gnome/backgrounds/pureos

This is the list which contains only free drumkits: https://tracker.pureos.net/P2
I have removed drumkits clearly labeled as non-free as well as others without license.

I'll examine manually all drumkits offered in Debian package the online repo. If there really are some not allowed by FSF, can we simply patch the package?

After a lot of investigating and comparing sites that do and do not work, this is caused by some bug or misconfiguration where the browser does not handle SSL extended master secrets correctly. To cut a very long story short, we can work around it by setting security.ssl.enable_alpn to false.

Can reproduce.

turns out the package hydrogen-drumkits contain roughly the free parts of what is offered online, so setting up a curated live list is really no gain.

The list curated by Parabola seems to permit non-commercial CC licenses and does therefore not comply with Debian Free Software Guidelines.

Patch applied to Debian package, queued for release in 5 days (unless Debian maintainer intervenes).

Actually, not related. After researching this a bit, I came to conclusion that this problem might be even with systemd. Here's GNOME documentation explanation about this "Offline updates" feature:

I "fixed" the issue by removing that row. I was previously hoping to make a new version of that file, but this is clearly not happening and I don't see much point in a PDF spec sheet vs the live-updated products comparison table anyway, so I just removed it now.

Hi Zlatan,

After I stumbled upon this: https://lists.parabola.nu/pipermail/assist/2015-December/000586.html

This is not a PureOS bug.

We will aways try offer latest snapshot and that is what we want users to use. This is rolling release, so offering more option is not something we want, nor ideal and can create a situation of users reporting bugs that are already fixed in new updates.

Can you check the latest snapshot https://downloads.puri.sm/snapshots/2017-07-08/pureos-8.0-live-amd64.hybrid.iso

Fixed.

erm...how is this even pureos bug?

This is on the proverbial "to do" list in the coming months.

References T130.

Also, why is there a Firefox on the list of programs on a freshly installed PureOS? Firefox works, but PureBrowser does not.