@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.

systemd should be version 241 in PureOS Amber and 242 in PureOS Byzantium.

Which version of systemd are you using?

From @mak;

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

@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.

I think the user manual mentioned on this page is missing sections that I and other users would find very helpful:

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).

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

I use this:

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.

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)

Support for the Librem Key has been merged into CCID : https://salsa.debian.org/rousseau/CCID/commit/ebd991f05c1ea2ba55bc431f624c7682c14ca623

Ok, finally managed to send a message to the developer via email that did not bounced back.

@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.)

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.

Thanks a lot Joao.

This shows that you have the Flathub third party repository added to your system:

Hi Joao.

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

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.

Just a headsup that this should be fixed.

As we're working on the search page right now, perhaps this is a good time to close this bug?

Yes, this needs review and triage.

This problem has gone away. Its not clear why.

youtube-dl version 2019.09.28 available in Debian testing solves this issue:

Whoops, looks like I completely forgot to close this... Thanks!

Kodi is not installed by default anymore.

The developer of libccid has been contacted.

The only thing I can say at the moment that we will have this done for the next release of PureOS. I know this is kind of vague, but at the moment I can't make a more definitive statement about it, sorry.
Most likely this feature will come with a complete overhaul of the process we use to build images for PureOS.

I also experience the issue described by @soapergem. The boot process sometimes hangs when running the start job for the encrypted swap partition.

Is there an estimated time for this please?

core part of OpenQA is already in Debian: https://tracker.debian.org/pkg/os-autoinst