Deviations from Debian are - in a way - tracked at a global level at http://master.pureos.net/synchrotron/ - going to a per-patch level would be nicer, but this page already gives an overview of packages that have been modified in PureOS and where a newer version of them is available in Debian.
That way currently, changes in PureOS are reviewed regularly, any time we merge in a newer package from Debian.

Well, we can already sync packages with Debian unstable or experimental, but those have to be recompiled in PureOS - otherwise we can not ensure they actually work with the software that is in PureOS (that's based on testing).
Also, pulling packages from non-testing suites is an explicit task that is currently done manually.

Another point to consider:
When implementing this we must consider that the Librem5 might have forks of important libraries with patches that are either:

• not upstream yet since they're still in review
• not in the version that is currently in Debian testing Therefore we should cater for a way to build packages on or own until we get the correct version from Debian.

I don't know. But only suggested solution, adding kvm group did change the error messages, but there is still some problem.

I think this is https://tracker.pureos.net/T292 ?

I think we could do two things here:

Adding my user to the kvm group worked (after reboot)

@chris.lamb I can reproduce this bug on both my Librem 13 and 15 both running PureOS pointing to green with the latest updates.

Also the log contains things like this:

Adding kvm to my user did solve something. Then I also installed libvirt-daemon-system manually, because it is only suggested.
But still I get some error when creating vm:

Issue has seemed to resolve itself. Update successful.

Thank you very much @mak !

I tried many things and couldn't reproduce this issue - please file a new one in case the problem persists.

Logo changed to the simple text version - it looks weird though:

Thanks. base-files=10.1pureos1 was considered a downgrade, but an apt update and upgrade doesn't upgrade. Must have come from an old deb source I don't use any more. I'll schedule a re-installation!

You can maybe resolve this by running sudo apt install base-files=10.1pureos1, but if this one package was upgraded for some reason, chances are that there are multiple other ones that also have wrong versions, making any bug happening on that system not a PureOS issue - so maybe a reinstallation is a safer bet.

Yeah, this PureOS has been messed with... How did you manage to install a base-files package from Trisquel?

This is impossible, something has severely messed up your system. What is the output of apt-cache policy base-files as well as cat /etc/apt/sources.list ; cat /etc/apt/sources.list.d/*?

Similarly, today an update re-triggered GNOME's "initial setup" wizard, and at the end invited me to start using Trisquel.

Split from https://tracker.pureos.net/T257

Renamed back and filed the 'default' issue as https://tracker.pureos.net/T364. These are two seperate issues AIUI.

.tar.bz2 files are not installable packages, they are just compressed archives like .zip/.tar.gz/.tar.xz files. They are to be uncompressed with an Archive Manager, and can't be installed with a tool like GNOME Software.

Software and Software Install does not install tar.bz2 files, in this case, Firefox.

Confirmed. Thanks!

I tried to use cvt -r 3840 2160 in order to produce a modeline for my system, and while I can see the resolution in the XFCE Display settings (after having configured xorg), I can't switch to it.

@kyle.rankin Thanks using xorg is a good work around for now. Just picking that at login is simple enough I thought it was going to require a more substantial and permanent tweak / swap between wayland / xorg

The pure-text logo will look really bad as window and toolbar icon, but I can use it anyway.
Thanks for updating the link!

I have fixed the link.

Should be resolved in network-manager-openvpn_1.8.0-2pureos2 uploaded with urgency=high.

@d3vid Thank you for the update. I'm a little hesitant to package the latest upstream as Debian have not done it yet and we might be introducing *other* problems to our users. I will go ahead and add and push though. Stay tuned.

Alternatively (from #nm IRC):

Apparently v1.8.2 was just released, could @chris.lamb look at packaging and releasing that?

Thanks for pushing this through. Updated to network-manager-openvpn v1.8.0-2pureos1 and network-manager-openvpn-gnome v1.8.0-2pureos1. Unfortunately the problem persists. Reporting the details upstream in https://bugzilla.gnome.org/show_bug.cgi?id=788226

This worked for me as a temporary solution (sorry I am a Linux noob and I dont know if it might be the same solution you provided and just done in an other way?)

@mak Great news!

This is fixed in calamares >= 3.2~rc3-0pureos2 now, but will also require a rebuild of the live images to be in full effect.
For some reason, Calamares doesn't create a swap partition right now, I am currently investigating that behavior (and playing with the idea of using swapfiles instead of swap partitions).
Once that issue is dealt with, I will build new live ISO images.

Does the update really fail (as in apt showing an error), or does it not boot, or what exactly happens here?
Packages being held back in landing is normal for that suite.

Fixed in initramfs-tools_0.130pureos1

A logo - any logo - would be nice by this point, since Calamares will be our default installer soon (the link above is no longer working).

I made this work now, but there is a bunch of other changes I would like to do first, still.
(Like installing on an unencrypted /boot by default)

*grin*

perfect. now to just get it work...

echo 1 > /proc/sys/i/care/about/freedom, huh? :)

Since the are decidedly not required I think it could move to Debug from Warning (or whatever level is below Warning where this message won't print by default).

@todd I worry this would be difficult to push back into Debian simply by hiding them as that would be somewhat of a poor experience for anyone who actually wanted to go ahead and install them. So, I wonder if we should add (or link to) a warning lecture about free software here , somewhat what like I propose in https://bugs.debian.org/888405. Thoughts?

• Matthias bumps urgency of the package

David Seaward wrote:

thx for your help.
It is not working.
even installng wine32 from a thrird-party repo...

1.233643] i915 0000:00:02.0: firmware: failed to load i915/akl_dmc_ver1_26. bin (~2)

Previous upload rejected, re-uploaded which was accepted.

This should be fixed in network-manager-openvpn version 1.8.0-2pureos1.

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)