- User Since
- Nov 30 2018, 13:26 (104 w, 23 h)
@joao.azevedo I'll have to update and/or repackage youtube-dl ASAP.
Tue, Nov 24
Thu, Nov 5
Wed, Nov 4
Mon, Nov 2
Excellent - we'll get to work on that. :-)
Oct 15 2020
Hi @Moop - thanks for reporting this. A new live image has been released. May I ask that you test again?
FWIW Linode provides 250 Gigs for $5 a month. We could get a Terrabyte with them of web addressable storage for USD 20 per month ($240 per year).
So from a quick check it looks like /dev/md3 is the disk that holds our repos;
/dev/md3 1.8T 822G 919G 48% /srv
Oct 14 2020
I don't have a power meter but I will use powertop. :-)
So how do we do this test in a way that produces useful data? Do we run it at two different settings on two laptops concurrently? Or should I measure battery level over time at specific intervals with each setting on the same device?
Oct 13 2020
Following Guido's link, I ran
Oct 12 2020
I'm working on pushing youtube-dl_2020.09.14 from byzantium to amber.
Oct 9 2020
Yes, let me look into how quickly we can get this into Byzantium. (There are two routes - wait for an update from upstream packaging, e.g. Debian, or upload our own package directly amber.) Uploading the new package directly to amber is likely the fastest way to close this bug.
Oct 6 2020
Can you try again? I cannot reproduce this issue on Byzantium.
gnome-control-center is updated: https://software.pureos.net/package/src/byzantium/gnome-control-center
Do you know what model your Wifi adapter is? It may require proprietary drivers to function which we do not include in PureOS.
An administrator has to remove accounts from the command line. Alternatively, an admin can "disable" your account which stops mail and your ability to login - is this sufficient or would you like the information permanently deleted?
Sep 18 2020
This points to file corruption I think. It appears that people have had success in deleting files in
and re-running apt.
Sep 11 2020
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.
Aug 29 2020
Run cpu-x. Get this message;
Aug 26 2020
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/