Is there any relevant dmesg output? Can you monitor the kernel ring buffer with dmesg -w?
Mon, Jul 13
Fri, Jul 10
I can't reproduce this. I just installed apt-listchanges in Byzantium
Thu, Jul 9
@adaian What happens when you turn on the computer? What do you see? Can you write down any messages that the screen shows? The term 'brick' doesn't describe very much unfortunately. Do you have a USB device you can burn a live ISO to and boot from?
I'm getting a "page not found" for the depcheck byzantium issue.
Jul 1 2020
It looks like you're using the Sonic mirror.
Jun 30 2020
We no longer are going to maintain Purebrowser given upstream lack of support.
Jun 23 2020
Is this on reboot?
I can't reproduce;
I can't reproduce;
$ sudo apt install gnome-contacts
Which device is this @francois?
Jun 17 2020
My python version is;
Jun 16 2020
Jun 15 2020
Thanks for the update @alexngould
Jun 4 2020
I'm not sure - it looks like they do have a signed release file here: https://mirrors.sonic.net/pureos/repo/pureos/dists/byzantium/
You can try the main repos;
Jun 3 2020
Exciting - we should test this in Byzantium and hopefully we can close this bug.
May 29 2020
If you follow the upstream discussion you can see that they're already on it! :-)
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."
May 28 2020
May 27 2020
May 22 2020
Looks like this is the diff;
May 21 2020
Matthias is looking upstream to see if the fix has been already made in effort to de-duplicate work.
Has the PoC been tested with the app?
So, if I understand correctly, this repo holds the patched libnitrokey: https://source.puri.sm/joao.azevedo/libnitrokey/
May 20 2020
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.
May 19 2020
May 13 2020
@hansolo Yes, thank you! What I hope to do is to determine that any action we take affects only the Librems with a US keyboard. We're going to have to determine the best fix for the US keyboard and then deploy.
@mak Do you have a German keyboard now? Or is your L13 v4 US keyboard?
May 12 2020
I'm going turn this task into a milestone so we can track the release period.
May 11 2020
Both those mentions in the logs at boot time are "normal".
May 7 2020
Apparently an upstream bug: https://github.com/systemd/systemd/issues/12401
Thanks for reporting!
May 6 2020
The versions in Amber and Byzantium are not far apart; https://software.pureos.net/search_pkg?term=libccid
In Debian's Salsa it appears they're about 88 commits apart: https://salsa.debian.org/rousseau/CCID/-/compare/ccid-1.4.30...ccid-1.4.32
May 5 2020
On my L13 v3 I get;
May 4 2020
To confirm, I'm going to update to this commit: https://review.coreboot.org/cgit/flashrom.git/commit/?id=05c629be2964bcee368c03d805747da15281856d
Now one can just call docker and the version of the PureOS distro image you want, like this;
Apr 30 2020
I think this is worth looking into - let me see if I can upload a new version of the library packaged for Amber.
Apr 1 2020
Can we retry this with the later Byzantium images? This bug was filed before there was an updated image.
Mar 13 2020
Feb 27 2020
Thank you for that. It looks like you're using PureOS Amber (at least, that's the version of systemd that is in PureOS Amber).
Debian does talk about this as a configuration option in their wiki: https://wiki.debian.org/PulseAudio, but on cursory inspection, I don't see a bug filed for changing default settings. This may have to go further upstream to PulseAudio itself.
I can't reproduce this on my Librem 13 v3 running Byzantium. But, I will look into seeing how we can change the default.
Amber is now officially in Debian's debootstrap. Next is Byzantium. Do we want to have amber-phone as well?
Feb 25 2020
systemd should be version 241 in PureOS Amber and 242 in PureOS Byzantium.
Which version of systemd are you using?
There are policy decisions needed
- which key do we sign this with?
- the archive key?
- a new key?
It's difficult to automate due to security boundaries in the infrastructure and code needs to be written for it
Feb 24 2020
We can perhaps sign this file: https://downloads.puri.sm/byzantium/gnome/2020-02-15/checksums.sha256sum upon each release.
Closing because we've moved to Amber and this references Green.
Feb 7 2020
Jan 27 2020
I'd like to set up an OpenQA instance. But it looks like I can't use PureOS or Debian to do so. The only blocker is a MR in Salsa: https://salsa.debian.org/debian/os-autoinst/merge_requests/1/diffs which looks pretty reasonable. @jonas.smedegaard does Hideki Yamane-san hang out in the Debian-perl channel, perhaps we ask him to merge that diff there? Otherwise I'll go ahead and install on SuSE (heaven forbid.)
Jan 16 2020
Those fields are just inherited from the upstream because we bring in the package as a binary.
With regard to this policy change: https://puri.sm/posts/an-epiphany-regarding-purebrowser/ can we revisit this (and other Purebrowser issues) in PureOS so that we can determine the best course of action for deprecating Purebrowser.
As we're working on the search page right now, perhaps this is a good time to close this bug?