I guess Adrian isn't active on this any longer, so reassigning back you to, @jeremiah.foster

@ChriChri Just for some extra context:

available since some time (entered Debian 2018-12-21)

available in Debian since 2018-12-21

I have not been able to use nuitka at all because the only version available in byzantium depends on a too-new version of base-files.

@guido Your assumption about the version we want is correct, I haven't looked at the current version within Debian yesterday. Due this I was also not wondering about the not visible new Debian version on the synchronization dashboard, seems there is a issue on not detecting the higher version in Debian, Matthias will be the only person I guess which can demystify this.

@carsten.schoenert I think we want base-files 11.1+debu11u1 + pureos changs, yes but @mak should confirm. What puzzles me is that it doesn't show up at https://master.pureos.net/sync/landing

Ah, I see it now: the older version mentioned by Carsten is the one currently in PureOS Byzantium.

which version of nuitka has such tight dependency on base-files, and why?

Seems your are right. That will require a update of base-files for byzantium.

This seems to have been resolved in the intervening period - due to updates I guess.

I am running a Librem14 (5.10.0-9-amd64) and was experiencing this same issue. Instead of purging gufw I needed to purge ufw. Before purging I noticed the ufw service was in a masked state after removing the package with apt. I also cleaned up /etc/ufw after the purge. I used the iptables rules in this bug report as a workaround and saved those to /etc/iptables/rule.v4 and .v6 so iptables-persistent would see them and rebooted. This fixed my issue, the networking was restored and the machine no longer would hang after decrypting the drive.

A user found out possible cause:

@mladen Feel free to direct people to enter more details of their issue here, I get notification quickly.

Reopened to collect other issues and hopefully other solutions.

@jeremiah.foster some people still report the issue, even though they have the latest ca-certificates (both on amber and byzantium). Any way to troubleshoot this further?

On my amber instance here, running an upgrade just of ca-certificates would work but I've already done it and get an expected result;

$ apt upgrade ca-certificates
Reading package lists... Done
Building dependency tree       
Reading state information... Done
ca-certificates is already the newest version (20200601~deb10u2).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Updating ca-certificates is the same as updating any other package, simply do

@jeremiah.foster could you please explain how to update ca-certificates?

@guido updated the tag on screenshot

We consider byzantium to be stable now. Awesome list btw!

Screenshot works for me (it's not adaptive and only capturing the full screen works) but I use it all the time.

This is resolved now - please test the images available on https://downloads.pureos.net/byzantium/ (preferably the latest ones built ^^) as I could only test this on a few systems and configurations that I had available. The images should support UEFI, as long as secure boot is not enforced, as the necessary pieces are not signed.

@lo0 You may be right. My original URL was tested and now fails. I'm having trouble connecting to the new URL however so cannot confirm.

@jeremiah.foster I believe the sonic url is actually https://mirrors.sonic.net/pureos/repo/pureos/

Updating ca-certificates on Byzantium solves this issue.

Amber works now but Byzantium still fails.

...or in this case, package repos (plural) as this issue affects both Amber and Byzantium.

thanks, @evangelos.tzaras - but you guessed correct: please only close when done from a user perspective, i.e. when fix has reached target repo.

With https://source.puri.sm/Librem5/debs/pkg-phosh/-/merge_requests/21 merged this can be closed (unless it's preferred to wait for a new release incorporating those changes reaches the archive)

My understanding was that in Debian they updated the buildd chroots. In any case, Stelios writes; "very likely an issue client side. a few days ago intermediate lets-encrypt certificates expired ,workaround on older debian systems was to drop the line DST from /etc/ca-certificates.conf and run update-ca-certificates its not a server side issue its a client side issue".

We certainly can't update the system's certificates store, as that would mean people couldn't get the update that lets them get updates again :-P

It looks like updating the certs for repo.puri.sm is the workaround. Asked systeam to do this and then we can test again.

More here: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1944481

On Debian 11 this works;

Same thing occurs in Byzantium and GnuTLS

@jonas.smedegaard
Ahh, right! Thanks for pointing. I happily agree an that.

Please (for future sake, if not this one) note that this issue tracker should be tracking user-visible targets, not staging targets like "landing".
I.e. not option e) but option g) at https://tracker.pureos.net/T553#18719

With the help by Guido we managed to get this addition into landing. So closing this issue.
https://software.pureos.net/package/src/landing/lollypop

The packaging effort for seahorse has now reached landing so this issue can be closed.
https://software.pureos.net/package/src/landing/seahorse

Since I just saw this issue on the byzantium board I've opened https://source.puri.sm/Librem5/debs/pkg-phosh/-/merge_requests/21
/cc @guido

This should be resolved in byzantium already :-)

Does this issue still exist? I changed the image build process quite a bit, so the current images are not comparable to the old ones.

This should be fixed in landing/byzantium for a while now :-)

I would rather add a search function to this, as this page can get extremely large (to the point of hanging up a browser tab).
Currently, the database has indices (no dedicated fulltext searches), but with that one could already implement a simple search. Added to the todo list, but as usual, patches welcome :-)

I guess this is changing. I found: 0001-general-Remove-option-to-bypass-delete-confirmation.patch. I guess I will look for a new File Manager that lets me work the way I wish. Thanks.

Actually, this bug doesn't just affect alt-menu symlink creation - anything done with a nautilus alt-menu is affected and kills nautilus (even simply clicking outside of the alt-menu)

Please help me to understand. Why would an upstream change be reflected in Purism's version, but not Debian 11 (bullseye) at the same level?

It may have been upstream that made these changes, if so, the bug ought to go there.

We need more information. Perhaps the version of Plasma they're using and a screenshot if possible?

dpkg is now at version 1.20.9pureos2 thanks to uploads by Sebastian this July.

nice, I have no criticism :D

Feedback in the Debian derivatives list agrees with Carstens proposal, so I withdraw my alternative proposal.