Re: [qubes-users] Need help after a failed in-place upgrade attempt

2024-02-16 Thread 'haaber' via qubes-users
Hi I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the "qubes-dist-upgrade" script. The upgrade failed - and - now the system is in a 'weird' state. None of the Fedora- or Debian-based VM have 'external / public' network access anymore. The 'anon-whonix' VM however still does

Re: [qubes-users] Updating fedora-38: "b'warning: runaway fork() in Lua script\n'"

2024-02-16 Thread 'mov' via qubes-users
On Friday, February 16th, 2024 at 6:32 PM, Ulrich Windl wrote: > > > Hi! > > > I saw these messages when upading fedora-38 today. I didn't run QuebesOS > for a while, so there were a lot of updates, but "runaway fork()" > worries me a bit... I've seen these messages too, during

[qubes-users] Updating fedora-38: "b'warning: runaway fork() in Lua script\n'"

2024-02-16 Thread Ulrich Windl
Hi! I saw these messages when upading fedora-38 today. I didn't run QuebesOS for a while, so there were a lot of updates, but "runaway fork()" worries me a bit... Kind regards, Ulrich --- Updating fedora-38 b'warning: runaway fork() in Lua script\n' b'warning: runaway fork() in Lua

Re: [qubes-users] Where do I verify the gpg key? Do the docs need updating?

2024-02-16 Thread Andrew David Wong
On 2/16/24 12:38 PM, Allen Schultz wrote: > Hi, > > I''m trying to verify the key I downloaded from the Qubes Download page > . According to the documentation on > the Verfying Signatures > , it looks

[qubes-users] Where do I verify the gpg key? Do the docs need updating?

2024-02-16 Thread Allen Schultz
Hi, I''m trying to verify the key I downloaded from the Qubes Download page . According to the documentation on the Verfying Signatures , it looks like there may be a discrepancy between the two.

[qubes-users] Need help after a failed in-place upgrade attempt

2024-02-16 Thread Viktor Ransmayr
Hello community, I tried to upgrade my Qubes OS system from 4.1.2 to 4.2.0 using the "qubes-dist-upgrade" script. The upgrade failed - and - now the system is in a 'weird' state. None of the Fedora- or Debian-based VM have 'external / public' network access anymore. The 'anon-whonix' VM