Very strange. Are we using different repositories?

The issue is resolved on my side too. The version of libhandy is now correct.

Yes, not only on first boot where you made the initial setup also second boot and go on

Is this on reboot?

I can't reproduce;

I can't reproduce;

$ sudo apt install gnome-contacts

Which device is this @francois?

@jeremiah.foster If it is ok for you I would like to take a shot at this task as a weekend learning experience.

Found this issue because I had the same idea, it is a really cool app :D

I think this might also be the cause of this problem: https://tracker.pureos.net/T915

I just found out that the python3-apt package in Byzantium is not up to date and is at version 1.8.4, which is the same version as Debian stable, which is not compatible with python 3.8 : https://packages.debian.org/buster/python3-apt

@jeremiah.foster I get the same output from the same command.

My python version is;

0.0.11-1pureos1 can be removed from buzantium and we can switch to the Debian version. There's no downstream changes in there, it was just a rebuilt since the package wasn't in Debian at that time.

@jeremiah.foster I am still getting the same error after updating and upgrading.

Looks like a dup for T907

I did;

Considering that we phased out Purebrowser in Favor of Epiphany and Firefox-ESR and that the bug was closed in Debian.

After trying to install gnome-software again, I now get the following error :

Thanks for the update @alexngould

Switched my sources.list back to the mirrors.sonic.net repositories today, and now it seems to work without any errors.

Nitrokey app folked merged support for the Librem Key upstream yesterday: https://github.com/Nitrokey/libnitrokey/pull/163

@mak Considering that Purebrowser has been phased out in favor of Epiphany/Firefox-ESR can this ticket be closed?

I'm not sure - it looks like they do have a signed release file here: https://mirrors.sonic.net/pureos/repo/pureos/dists/byzantium/

That works. It must be a problem with mirrors.sonic.net.

You can try the main repos;

Thank you @mak ! I will retry in a few days then. Do you know how many days?

What do you mean with "breaks"? Does it crash? Is it not installable? In the former case, a backzrace or at least console output would be nice.

This should be fixed now, but the update will need a few days to migrate out of landing.

Exciting - we should test this in Byzantium and hopefully we can close this bug.

Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928893 indicates that this has been fixed.

@jeremiah.foster Perhaps this might help:

I am sorry that did not help.

Thank you @Wayne, but I don't find a solution there or something that could help me.

You may want to check and track this post. It may be related to your issue.

they're already on it!

If you follow the upstream discussion you can see that they're already on it! :-)

ok, so we should contact the Litrokey app devs? To see if they merge that request?

Debian maintainer states "I'm concerned that the addition of vendor_id might cause an ABI break. There are multiple packages that use libnitrokey in Debian (not just nitrokey-app) and so we can't silently change the ABI."

I've pulled down the Debian packaging from Salsa and reused that. I've added in the patches from upstream and built package for PureOS Amber and Byzantium.

Please note that this issue is about whether or not a package in PureOS is violating policies defined by Debian and/or FSF.

I wanted to add to this issue that Geogebra is no longer updated in Debian due to the license, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692728. The problem is not only the documentation is licensed for non-commercial, but also the language files. As a result, it seems impossible to me to have a package with the free parts only, because such a version would not include any strings and hence be unusable?

I tried octave in Byzantium and the bug is not present (at least the proposed example above works).

Looks like this is the diff;

Matthias is looking upstream to see if the fix has been already made in effort to de-duplicate work.

Yes, it has. The PoC is basically replacing the nitrokey pro device and vendor ID with the Librem Key device and vendor ID

Has the PoC been tested with the app?

No, that repo is a poc.

So, if I understand correctly, this repo holds the patched libnitrokey: https://source.puri.sm/joao.azevedo/libnitrokey/

Thanks @selea.

This does not break an install, that is correct.

I'm happy to work on this TODAY but this is not "Unbreak Now!" because it is not breaking anything for our users and, we have a perfectly viable alternative that is a tiny bit better, namely the Librem Key.

I confirm that it is working properly in debian-live with Gnome 3.

I forgot to say that the version of debian 10 I tested was using XFCE. I will try with Gnome so maybe the error is related to that,