Thanks, cargo-mozilla is in.
Thu, Jan 26
Jan 2 2023
Nov 12 2022
Nov 10 2022
Oct 7 2022
Sep 30 2022
Sep 12 2022
Weird, I rebooted and now it works...
Interestingly, gedit seems to run find with sudo:
Sep 4 2022
Aug 26 2022
Aug 17 2022
Aug 13 2022
This doesn't seem to be causing an issue now. It can be closed, resolved.
Aug 3 2022
I do not represent Purism, but I look here occasionally for issues I may have. I see this issue is quite old now.
Jul 27 2022
I attempted to install PureOS to Mini from PureOS Live USB disk. I wanted to create an unencrypted installation and erasing whatever was installed before (Fedora) on the disk. However, the Next button in that dialog was never enabled after unchecking the encryption checkbox. So I wasn't able to create unencrypted installation with that option and had to resort to creating the partition layout manually.
Jul 17 2022
Jul 10 2022
There's some movement on the Debian side (thanks Carsten) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014327
Jul 6 2022
On Guido's recommendation, I tried rustc-mozilla, but that still needs newer cargo. https://gitlab.gnome.org/dcz/squeekboard/-/jobs/2106399
Jun 30 2022
I failed to build llvm-13, but it seems to be 1 of 2 needed dependencies. The other is wasi-libc.
Jun 29 2022
Jun 16 2022
Jun 13 2022
May 31 2022
would be very neat if apt-file would be usable:
I often only know the name of the binary I want to execute, but not necessarily the binary package that contains it
May 27 2022
May 25 2022
May 18 2022
May 17 2022
May 16 2022
Apr 23 2022
Apr 22 2022
Mar 29 2022
Firefox-esr is in Byzantium-security: https://software.pureos.net/package/bin/byzantium-security/firefox-esr
Mar 18 2022
Mar 17 2022
A quick search brought up https://bugzilla.mozilla.org/show_bug.cgi?id=1627713
Mar 16 2022
Mar 9 2022
Assuming this is closed, re-open please if problem persists.
Recently Francois noted that there was an interference by a firewall when trying to set up a printer. He reported that to pureos/dev Element channel and the preference was stated by the CSO that the two processes listening on 0.0.0.0 get switched to localhost.
Mar 7 2022
Has this been tested in the new PureOS 10 release?
Feb 27 2022
Feb 18 2022
Feb 17 2022
Thank you for the issue report! This problem should be resolved with the latest updates :-)
Should be fixed in a few hours :-)
Feb 16 2022
I installed firmware-misc-nonfree. But it didn't help. I tried different suggestions I found. More editing on Grub f. e.. But is also didn't help.
As far as I understood it's probably a kernel issue.
Patching firmware myself is a step to far for me. I'm still a linux beginner.
I will wait for a new kernel and hope, that the issue will be gone then.
Thanks for your help.
Feb 14 2022
A new version of Firefox-ESR will be coming into PureOS 10.
Feb 13 2022
Feb 9 2022
Feb 8 2022
I would start with patching firmware. I am not sure if you have any new firmware available but this would be my first thing to do. I had this issue regularly when I was using Ubuntu after I moved to PureOs and patched firmware it almost disappeared.
Unfortunately the issue reappeared. I could not reproduce it for a while, but since today it's back. And it makes no difference if an external disk is plugged in or not.
Feb 2 2022
Jan 28 2022
Jan 27 2022
@jbw Have you considered looking the package with debugging symbols in Debian? Debian has something called snapshot.debian.org which holds, among other things, packages with debug symbols. It is a little hard to navigate but try the search for the package you want and you may get lucky. Or post the package name and version here and I'll see if I can help find it.
can someone who knows what they are doing add step-by-step instructions (perhaps on the pureos wiki) for a user like me who has byzantium installed giving the exact steps that the user needs to take to enable use of the debug-symbol packages that pureos does build (which seem to be in landing rather than in byzantium) together with those of the debug-symbol packages that debian builds which are usable with a byzantium install. these instructions need to specify what exact strings need to be added to which exact configuration files and what exact commands need to be typed to get the necessary debug-symbol packages installed. unfortunately, as an end user, i do not have the spare days to keep trying to find the necessary strings and configuration files and commands until i succeed. thanks for any help you can provide!
Jan 26 2022
Jan 25 2022
Thank you. APT-GET fixed my issue.
This issue is easy to replicate, during the installation I just did not connect to the network.
I noticed the issue directly after upgrading from amber to byzantium. I did not update coreboot at that moment. I'm not sure about EC firmware. I think I can not install/update this on my Librem 15v3.
Jan 24 2022
This is a due to a stale cache that apt is stuck on. If you installed from an older ISO or older PureOS version this can happen. One way to fix this is to run apt-get update to see if this brings in new packages.
Did you update coreboot and EC firmware? I am having this issue but just putting PureOS to sleep once again helps.
Jan 23 2022
@mak does this mean that the most correct solution for many people will be to simply uninstall fwupd because it is useless for them? i don't remember installing it. it is "Recommends:" by pureos-gnome and gnome-software, but i don't have things configured to automatically install packages simply because they are mentioned in "Recommends:" fields. i think it came preinstalled on my librem 14.
Jan 22 2022
This is an annoying issue, as it is extremely hard (if not impossible currently) to fix properly. A proper fix would be to re-sign the fwupd-amd64-signed binary package, but we can not do that as we do not have any EFI signing facilities for PureOS...
This package has been removed from PureOS (as we don't support UEFI with secure boot signing enabled properly anyways), but users who have installed the package manually before will of course run into this issue now until they run an apt purge fwupd-amd64-signed. We could force the removal of this package via conflicts, but that may also not be an ideal solution here :-/
Jan 20 2022
I have see this message, "failed to update metadata for lvfs" a couple times now when checking for a software update. It doesn't happen often but running the following command seems to help.
Jan 19 2022
Thanks for the suggestions.
Please in future file one suggestion per issue report, to ease further tracking and discussion.
Jan 18 2022
Everything that gets uploaded to the archive gets built for arm64 (librem5) automatically.