Can we retry this with the later Byzantium images? This bug was filed before there was an updated image.
Mon, Mar 30
Looks like a lot of the dependencies use old versions.
Wed, Mar 25
That is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765936 and documented here documented in /usr/share/doc/libvirt-daemon/README.Debian.gz . It would be best to just set the correct capability in pureos (setcap cap_net_admin+ep /usr/lib/qemu/qemu-bridge-helper)
Sat, Mar 21
Fri, Mar 20
Wed, Mar 18
Fri, Mar 13
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.
@jeremiah.foster great! i'd skip amber-phone since it's just an overlay and we want to merge for byzantium anyways.
Amber is now officially in Debian's debootstrap. Next is Byzantium. Do we want to have amber-phone as well?
This is a workaround: https://gitlab.gnome.org/GNOME/epiphany/issues/838 (disable flat-volume option).
Definitely need this, had this fixed already several times, but it seems to get overwritten when doing updates.
Feb 26 2020
$ systemd --version systemd 241 (241) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid
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
@davidpluseipi Yep, this is the same problem. I don't think the package is maintained at the moment, so it's easier to uninstall it.
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 22 2020
I think the user manual mentioned on this page is missing sections that I and other users would find very helpful:
Feb 21 2020
Feb 20 2020
Yeah, i've seen that but that assume the user understands what is going on (and involves user intervention for s.th. that could be automatic).
Feb 19 2020
I know this thread is closed but it's the only place anyone seems to be discussing this. Im happy to open a new issue or post to another.
We have made a wiki entry for users to be able to migrate their profile from ~/.purism/purebrowser to ~/.mozilla/firefox/(randomstringhere).default-esr
Feb 18 2020
I use this:
Feb 17 2020
Now, a bigger issue I see is that the usb key is not required for login. Having it launch the screensaver automatically is cute but not really that helpful. Are there other librem key docs that detail adding more security such as two factor logins? Should we be using the nitro key site?
What about the status of the original request which was to add a package to do this work for the user?
for anyone reading this thread, here are 4 different udev rules you might use to make this work:
There are a few other issues with the docs that could be clarified.
Feb 15 2020
With unbreak i mean it prints the symbols shown on the buttom instead of '#' which left the user pretty stranded when doing math stuff (or wanting to use the pipe symbol in the shell)
Feb 13 2020
Feb 10 2020
Feb 8 2020
Support for the Librem Key has been merged into CCID : https://salsa.debian.org/rousseau/CCID/commit/ebd991f05c1ea2ba55bc431f624c7682c14ca623
Feb 7 2020
Ok, finally managed to send a message to the developer via email that did not bounced back.
Jan 27 2020
@jeremiah.foster I am not sure but I don't think Yamane-san is hanging out on irc
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 26 2020
Jan 24 2020
Jan 23 2020
I think this is the same problem that has been mentioned before and was never fixed. You might wish to start here for more discussion.
Jan 22 2020
Jan 21 2020
Thanks a lot Joao.
Jan 20 2020
This shows that you have the Flathub third party repository added to your system:
Do you have any flatpak applications installed? First time you install a Flatpak application from Flathub, it asks you if you want to add Flathub repository to your software sources.
Seems the emails sent to the developers bounced back. Checking it with our sysadmins and looking for alternative ways to contact them
Jan 19 2020
Jan 18 2020
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.