Hi @james.rufer
I can't seem to reproduce this. gdebi installs fine for me, and launches fine both from the Applications menu and from the command line. Can you clarify exactly how you are trying to run it? Note that gdebi-gtk is the command, not gdebi.

• lam—

Thanks for the update. So, this is quite a common problem that affects Chromium generally (Google it!) and, alas, has an almost infinite number of causes AFAICT.

I moved the config directory as you suggested and it seems to have fixed the problem. Thanks!

I have updated the file (same URL).

Regarding license: Please open Document properties, and fill out "Metadata" and "License".

Thanks! That SVG is usable as-is to generate all but one of the PNGs.

I don't understand which timeline you are talking about.

Yes @jonas.smedegaard I have an SVG version of the icon. You can get it here : https://pureos.net/downloads/icons/purebrowser-icon.svg

If we're using DuckDuckGo and want a stripped back user experience, I'd suggest the base URL of https://start.duckduckgo.com rather than https://duckduckgo.com

This one was uploaded *after* I reverted the previous changes. Now I can't do that anymore without a fake upload, since the PureOS version is newer than in Debian.

@jonas.smedegaard I would actually prefer that PureBrowser recommends the extensions we want to ship with it - it would make logical sense for the browser package to pull in the extensions we recommend, instead of the system's seed depending on those directly.
By having PureBrowser just recommend the package, users can still easily uninstall it later.

If you have an SVG image then I need that, yes.

Well, I am not sure to understand correctly. Do you need the SVG image of the icon with some kind of tag within the file as the license?

Thank you all, installing texlive-full works for me now!

This issue is believed fixed with the recent upgrade of PureBrowsr to version 52.5.0esr-1pureos1.

texlive-full in PureOS green is now 2017.20171128-1.

PureBrowser has been repackaged, based on a newer Firefox: Please test if this issue persist.

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

For the record, I do not personally agree with this issue (I don't use said addon myself): This issue is derived from T147 which in turn is derived from a request by @zlatan.todoric

Consider this issue to be about privacy (T110 is about nonfree services which duckduckgo is as well)

While it might be colateral, this issue is separate from issue T147 tracking the PureBrowser package restructuring.

As explained by Matthias on irc, package ban is source-specific: Banning Debian as source of firefox-esr continue to make sense and does not block upload of same-named firefox-esr ourselves.

Package purebrowser now (since release 52.5.0esr-1pureos1) depends on neither xul-ext-ublock-origin nor xul-ext-adblock-plus.

Package purebrowser used to depend on package xul-ext-ublock-origin (and xul-ext-adblock-plus too? See issue T108), but we better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

This issue was originally reported as part of issue T108 but separated: We better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

This issue was originally reported as T108 but separated: We better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

Inclusion of Privacy Badger now tracked as separate issue T271.

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