- User Since
- Nov 30 2018, 13:26 (94 w, 4 d)
Fri, Sep 18
This points to file corruption I think. It appears that people have had success in deleting files in
/var/lib/apt/lists/ ``` and re-running apt.
Fri, Sep 11
Can one install PureOS wihout a monitor and mouse? I.e. using only a keyboard.
Fascinating. I believe this is a bug in GNOME. I'll see if there is a suitable place for it upstream.
Is this a duplicate for #T935?
There are parts of the EFI stack that are proprietary, this is why we do not include them in our installer. Other projects may include them in their "non-free" repos but because we're a FSF compliant Free Software distro we don't include non-free repositories. We continue to investigate if there is a way to support GPT.
Sat, Aug 29
Run cpu-x. Get this message;
Wed, Aug 26
Aug 14 2020
Is this in Amber, or Byzantium? (/etc/os-release should have this info.)
I think that this might be an "okay" situation as it is. The point is that adding deb-src repos is more of a power user thing, no?
Will do. Thanks for keeping it such good shape Jonas. :-)
Jul 13 2020
Is there any relevant dmesg output? Can you monitor the kernel ring buffer with dmesg -w?
Jul 10 2020
I can't reproduce this. I just installed apt-listchanges in Byzantium
Jul 9 2020
@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.