Inclusion of LibreJS addon now tracked as separate issue T270.

Now that PureBrowser has bumped to version 52.5.0, please test if this issue still persist.

Those PNG images look like they were generated from a vector-based source. Also, they lack information about copyright holder and licensing.

Thanks, I will check out those files, and get back to you...

Branding with different logo sizes has been done previously. At that time Hema made me replace all the logo files from Firefox so I guess that the licensing was the same as in Firefox?

Hi @ben.trister, thank you for the report. After some experimentation I am unable to reproduce this. Can you let me know:

whoops, sorry - meant to ping @francois

@geppuzo ping!

This is how GNOME developers designed it as you can't really be sure a service/daemon got updated and properly works so it requires a reboot. This is aimed at less experienced users and updates aren't always booletproof. Anyway, this is upstream design atm - not really sure if we should change it (Windows does updates in similar fashion).

Fixed with an update, a few days later.

Fixed in https://code.puri.sm/pureos/gimp/commit/d08880cc1da453421dddb31643fedb40fdf8e4d0 / 2.8.20-1pureos1

@francois can you have a look at this?

Ok, I take over from here. Pick something fun to work on (or take a break, I am sure noone minds!).

concern for you: You have fought this issue for a long time and mentioned frustration about it on irc recently.

Thanks for reporting this!

Reason for my cautious wording of comment T147#4606 was concern for you: You have fought this issue for a long time and mentioned frustration about it on irc recently. I want to help but am genuinely uncertain what you consider helpful here.

I have the exact same issues. I am not able to run Puremail and I have problems with PGP key import and links with Thunderbird.

@jonas.smedegaard First, perhaps I am accidentally reading something in your messages that is not there but I truly hope there is no animosity or something other that purely technical discussion here? If there is, then let's fix that and move on. :)

Thanks for raising the issue here.

I see 3 options:

@chris.lamb Please do tell me if you would like me to finalize the packaging that I have succesfully test-built.

Previus comment updated to clarify the sloppy and confusing use of "fail".

No as in not-how-Debian-maintainer-intended-for-sid - e.g. causing rendering artifacts.

As in FTBFS? Wfm, but also do note that this package uses a control.in...

It seems *only* renaming package will fail (EDIT: or so I guess - it regenerates control file dropping build-dependency on gcc-6) due to our change of target suite, and (at least, haven't tried yet) this patch is needed:

This issue seems _not_ solved: Current povray package in PureOS green is 1:3.7.0.4-2pureos1 (the version which I explicitly requested to _drop_ as part of this issue).

The issue disappeared after a system update but it comes back few days ago now.

It's been merged, so yeay!
https://github.com/corna/me_cleaner/pull/70

Considered fixed.

Whoops, I forgot to close this...
The package has been force-synced with Debian and is now tracking Debian Testing again.

Tried to check if the same will happen with Puremail (Thunderbird fork) but after installation can't even run it:

marek@librem:~$ puremail
XPCOMGlueLoad error for file /usr/lib/puremail/libxul.so:
libhunspell-1.4.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.