Can we rebuild this package with this patch applied:

Can we rebuild this package with this patch applied: https://git.gnome.org/browse/network-manager-openvpn/commit/?id=b83f028a6da067dcc9b31555c15411f0288ebda1

In the meantime, found a better workaround using nmcli (recorded downstream in Purist ticket). Still not suitable for an everyday user.

Upstream confirmed this is a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=788226 which has been resolved (but not released?)

@netnut404 If you are willing to use X instead of Wayland, you can switch to that and follow my steps above to generate modelines for the resolutions you want.

I have tried several 4k monitors and and 3 OS's (pureos qubes and even windows 10) trying go get 4k on my new machine (it just arrived 5 days ago) and was getting concerned without having any positive results. I am anxiously looking for a way to achieve the 3840x2160 and 2560x1440 resolutions from this machine.

Checking reverse dependencies...
# Broken Build-Depends:
pinto: cpanminus (>= 1.6916)

Dropping pinto as well.

(solution was to set general.useragent.compatMode.firefox to True)

This has been mentioned elsewhere, but just to document Mozilla's take on all this:

Found a temporary workaround on 52.6.0esr-2pureos1:

Updated upstream bug with a debug log.

Systemd v238 with the workaround (https://github.com/systemd/systemd/blob/master/hwdb/60-keyboard.hwdb) is released.

Error persists with network-manager 1.10.4-1+b1 (same version of network-manager-openvpn)

Thank you! Changing back to "Area" worked

https://tracker.pureos.net/w/troubleshooting/secondary_touchpad_button_problem/

Hi @chris.lamb,
can you fast-track if this fix is in Debian yet and if not package quick fix for PureOS (and also ping Debian maintainers about it). Coordinate with @mak to get this fix in ASAP as it affects our users a lot.

Didn't upload the screenshot

This is from user ezs777 at forums.puri.sm:
You need to change the mouse settings in GNOME Tweaks back to “Area”; for some reason, the latest update changed it to something else.

Ok, I see what you mean!

This issue seems to resurface after an update to Chromium. Removing the /.config folder works temporarily but the crashing issue re-occurs.

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.

Or can we get some kind of assurance from the Tor Project about the continued freedom of the Browser Bundle?

I think you mean "torbrowser-launcher" above?

I suspect the Debian-but-released-only-in-contrib package was done that way due to the slow release cycle of Debian and the need for potentially quick update of the code. If that is the case, then a solution (other than simply giving up and kicking out torbrowser-bundle from PureOS) would be to replace with new package torbrowser - which could be maintained in Debian but there flagged as unreleasable similar to how other fast-moving code like Bitcoin is handled.

Possibly related: I'm having a similar issue when trying to run several installers or standalone EXEs.
Doing "wine foo.exe" (where foo.exe is known to be fully compatible with wine) yields:

it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"

A lot of Windows applications are still distributed as 32-bit binaries to avoid compatibility issues, so this kind of makes sense. But wine32 is not in the main PureOS repo because (IIRC) PureOS is all 64-bit code. So i386 isn't an enabled architecture, nor does the repo distribute 32-bit software.

This issue was fixed since 52.6.0esr-2pureos1.

xul-ext-ublock-origin now recommended by the metapackages pureos-gnome and pureos-plasma.

xul-ext-https-everywhere now recommended by the metapackages pureos-gnome and pureos-plasma.

@francois Yup, it absolutely should. Edited.

@jwolf You second line should say :