I prefer and would advocate for option 2 because it instructs sites that (mistakenly or not) use browser versions to determine how to behave that PureBrowser is most compatible with a particular version of Firefox (which it is, having been almost entirely derived from that browser, with some modifications), while also informing the site that the browser is not in fact Firefox, but something else.

Before the ticket is closed for good, could you provide a User Agent string workaround (if that would work, otherwise some other workaround) so we have steps to present to another user who runs into this or similar problems?

This is not a bug in PureBrowser, but instead in that specific website.

From what I've read on https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/EDID/HOWTO.txt the kernel only includes EDIDs up to 1920x1080:

dbus-cpp now in NEW

process-cpp out of NEW

I was able to get a Librem 13v2 to output at 2560x1440 by switching to GNOME on Xorg at the GDM login prompt for my user and using the steps from here to generate a custom modeline.

process-cpp now in NEW

The Ubuntu 14.04 Live disk was able to see the full suite of resolutions from my external monitor up to 3840x2160 @ 30hz and 2560x1440 @ 60hz. It uses the 3.19.0-25-generic kernel so perhaps we are seeing some regression with Skylake on more recent 4.x kernels.

I've tested this so far with a few other Live disks including Tails (4.14.12-2 kernel), Fedora 27 (4.13.9-300.fc27.x86_64), Ubuntu 17.10 (4.13.0-21) and Ubuntu 16.04 (4.10.0-28-generic). All of those live disks had the same 1080p limitation.

Just to confirm this specific issue is resolved in PureBrowser 52.5.0. Thanks!

ITPs in Debian:

This issue does not in itself harm freedom.

I believe - since this was moved from T299 - that this issue is about version 52.5.0esr-1pureos2 of PureBrowser.

Thanks for reporting!

WIP on that is here: https://github.com/lamby/pkg-process-cpp

Packaging for dbus-cpp is here: https://github.com/lamby/pkg-dbus-cpp

Thanks for reporting these things.

The issue is already mentioned here https://tracker.pureos.net/T110 and here https://tracker.pureos.net/T156

Same issue here.
I had DuckDuckGo as default engine, and the "update" switched to Google.

This is fixed in the 2018-01-18 live ISO images from today :-)

This is a pretty long standing issue for me under PureOS, getting third party .deb files to install consistently. I'm wondering if we even need to have Archive Manager as a preinstalled application and shouldn't just remove it, leaving Software as the only option for installing third party .debs.

Oh? GNOME Software should register for the deb package mimetype... So, I wonder what went wrong there...

It's not for third party .debs. There are three noticeable things:

Also, check the link on the Purebrowser Start Page; it links to the same Firefox add-ons site.

@james.rufer Thanks for your response - as you can see from the recent history this specific issue is being resolved.

On a related not: I actually don't think anyone should be using gdebi in 2018 ;-) GNOME Software can install .deb packages,

In T257#5277, @alexgaley wrote:

No I wanted to precise the fact that if you are trying to install gdebi from Software Manager - which was james.rufer operation if I understood well - will lead of the installation of the "gdebi-kde" package from pureos repo.
Then I wanted to point this gdebi directory in pureos repo to show the several gdebi packages to james.rufer in case he was not familiar whith apt-cache operations.
The operations I am suggesting him to try to solve the issue are :

In T257#5271, @alexgaley wrote:

Desinstall gdebi from Software Manager
Then install the TRUE gdebi package from command line (root) :

apt install gdebi

You can now launch gdebi from Menu or from command line :

gdebi-gtk

Then I made a suggestion for pureos team to solve this issue in a broader way :

In T257#5271, @alexgaley wrote:

Issue to be solved : Install gdebi from Software Manager should install "gdebi" package instead of gdebi-kde

In T257#5206, @chris.lamb wrote:

@james.rufer The "$" is not part of the command but rather the prompt. Please re-run without the "$" prefix.

The package is in green now, please watch out for any issues.

Apparently it breaks a bunch of stuff (garmin-plugin etc.), but that looks like a false-positive to me. The real issues are the -dbg packages being seemingly broken due to the Firefox package taking over binaries from the existing PureBrowser package.
I'll enforce that migration manually.
http://master.pureos.net/migration/landing/green/excuses/firefox-esr/52.5.0esr-1pureos2

@zlatan.todoric : This one is not fixed, even with a fresh OEM PureOS ( I just tested).

Fresh install of PureBrowser today and the default search engine is Google.

My suggestion is that the search engine string is https://start.duckduckgo.com/?q=%s rather than https://duckduckgo.com/?q=%s. This means your search results and the DDG start page (if you click on the duck logo in your search results) don't have tips and cartoons. Although looking at the search engine options I'm not sure why I thought PureBrowser/Firefox could trivially be configured this way. I may have been confusing it with GNOME Web where it's a string not an add-on.

Thanks for the screenshot.

apparently green does not yet include PureBrowser 52.5.0esr-1pureos1 - or mysteriously reverted to include the older version again.

apparently something blocks http://repo.pureos.net/pureos/pool/main/f/firefox-esr/ from entering green.

see the pict attached

Yep!

@chris.lamb I have just tested Thunderbird 52.5.2 from Debian Sid and it fixes the AppArmor issue indeed.
So I guess that it is just a question of days before the fix gets to PureOS?

I don't have this issue; I have had a user-related issue when I leave the search box filled in with something, and forgot I was showing search results within a folder, and wonder where the unread are. But this was user error.

If users install PureBrowser after uninstalling it or on flavors where it was not installed by default, they will not get the privacy addons that come with it. Also, these addons are logically tied to PureBrowser, and not to the flavor metapackage, because it's PureBrowser that includes them, not the OS. Furthermore, having them in the flavor package means that they might get installed with PureBrowser or might not get removed when someone uninstalls the purebrowser package.

Needs packaging. Am on it :)

Pretty certain this is the same as T293, so merging there!

I created this task and you are mistaken: This is a "default in PureOS" task.

Hi QiZhi,