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 have 'external / public'
network access - and - the update of templates through the Qubes
Updater is also still working ...


OK, I am not an expert on THIS question. Some general remarks: the
network card seems to work, right? So you need to check where the chain
breaks.

- go to sys-net (open terminal via widget) type ping 8.8.8.8 and see if
you come out

- go to sys-firewall (terminal via widget) and do the same.

if these two work, and an app-vm has no network, its config got lost.
Look at network settings of the corresponding appVM. It should be
sys-firewall in std setting, apart anon-whonix, of corse which uses
sys-whonix.


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/42cd7c79-7c3c-41b1-bc8c-cf504952201a%40web.de.


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 updates, for what it's worth - I also 
don't know what they're about.

- mov

> 
> 
> Kind regards,
> 
> Ulrich
> 
> ---
> 
> Updating fedora-38
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> b'Generating grub configuration file ...\nFound linux image:
> /boot/vmlinuz-6.6.11-100.fc38.x86_64\nFound initrd image:
> /boot/initramfs-6.6.11-100.fc38.x86_64.img\nfgrep: warning: fgrep is
> obsolescent; using grep -F\nFound linux image:
> /boot/vmlinuz-6.6.9-100.fc38.x86_64\nFound initrd image:
> /boot/initramfs-6.6.9-100.fc38.x86_64.img\nfgrep: warning: fgrep is
> obsolescent; using grep -F\nFound linux image:
> /boot/vmlinuz-6.6.11-100.fc38.x86_64\nFound initrd image:
> /boot/initramfs-6.6.11-100.fc38.x86_64.img\nfgrep: warning: fgrep is
> obsolescent; using grep -F\nFound linux image:
> /boot/vmlinuz-6.6.9-100.fc38.x86_64\nFound initrd image:
> /boot/initramfs-6.6.9-100.fc38.x86_64.img\nfgrep: warning: fgrep is
> obsolescent; using grep -F\nfgrep: warning: fgrep is obsolescent; using
> grep -F\nAdding boot menu entry for UEFI Firmware Settings ...\ndone\n'
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> b'warning: runaway fork() in Lua script\n'
> 
> Installed packages:
> cirrus-audio-firmware ['202401152.fc38']
> intel-audio-firmware ['202401152.fc38']
> nxpwireless-firmware ['202401152.fc38']
> tiwilink-firmware ['202401152.fc38']
> Updated packages:
> kernel-modules-core 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 ->
> 
> 6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
> kernel-core 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 ->
> 
> 6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
> kernel-modules 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 ->
> 
> 6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
> kernel 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 ->
> 
> 6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
> linux-firmware-whence 202312111.fc38 -> 202401152.fc38
> 
> xorg-x11-server-common 1.20.1428.fc38 -> 1.20.1429.fc38
> 
> xen-licenses 4.17.25.fc38 -> 4.17.26.fc38
> 
> amd-gpu-firmware 202312111.fc38 -> 202401152.fc38
> 
> amd-ucode-firmware 202312111.fc38 -> 202401152.fc38
> 
> atheros-firmware 202312111.fc38 -> 202401152.fc38
> 
> brcmfmac-firmware 202312111.fc38 -> 202401152.fc38
> 
> intel-gpu-firmware 202312111.fc38 -> 202401152.fc38
> 
> mt7xxx-firmware 202312111.fc38 -> 202401152.fc38
> 
> nvidia-gpu-firmware 202312111.fc38 -> 202401152.fc38
> 
> realtek-firmware 202312111.fc38 -> 202401152.fc38
> 
> linux-firmware 202312111.fc38 -> 202401152.fc38
> 
> python3-dnf-plugins-qubes-hooks 4.2.271.fc38 -> 4.2.281.fc38
> 
> vim-filesystem 9.1.0311.fc38 -> 9.1.0762.fc38
> 
> vim-data 9.1.0311.fc38 -> 9.1.0762.fc38
> 
> tzdata 2023d1.fc38 -> 2024a1.fc38
> 
> perl-Module-CoreList 5.202312301.fc38 -> 5.202401291.fc38
> 
> ncurses-base 6.43.20230114.fc38 -> 6.47.20230520.fc38
> 
> glibc-gconv-extra 2.3716.fc38 -> 2.3718.fc38
> 
> ncurses-libs 6.43.20230114.fc38 -> 6.47.20230520.fc38
> 
> glibc 2.3716.fc38 -> 2.3718.fc38
> 
> bash 5.2.211.fc38 -> 5.2.261.fc38
> 
> glibc-common 2.3716.fc38 -> 2.3718.fc38
> 
> glibc-langpack-en 2.3716.fc38 -> 2.3718.fc38
> 
> systemd-libs 253.141.fc38 -> 253.152.fc38
> 
> gstreamer1 1.22.81.fc38 -> 1.22.91.fc38
> 
> alsa-lib 1.2.102.fc38 -> 1.2.112.fc38
> 
> grub2-common 2.06108.fc38 -> 2.06114.fc38
> 
> libdrm 2.4.1171.fc38 -> 2.4.1201.fc38
> 
> gstreamer1-plugins-base 1.22.81.fc38 -> 1.22.91.fc38
> 
> gstreamer1-plugins-good 1.22.81.fc38 -> 1.22.91.fc38
> 
> gstreamer1-plugins-good-qt 1.22.81.fc38 -> 1.22.91.fc38
> 
> gstreamer1-plugins-bad-free-libs 1.22.83.fc38 -> 1.22.91.fc38
> 
> audit-libs 3.1.25.fc38 -> 3.1.28.fc38
> 
> at-spi2-core 2.48.31.fc38 -> 2.48.41.fc38
> 
> atk 2.48.31.fc38 -> 2.48.41.fc38
> 
> libidn2 2.3.42.fc38 -> 2.3.71.fc38
> 
> systemd-networkd 253.141.fc38 -> 253.152.fc38
> 
> systemd-pam 253.141.fc38 -> 253.152.fc38
> 
> systemd-resolved 253.141.fc38 -> 253.152.fc38
> 
> systemd 253.141.fc38 -> 253.152.fc38
> 
> gnutls 3.8.22.fc38 -> 3.8.31.fc38
> 
> samba-common 4.18.91.fc38 -> 4.18.101.fc38
> 
> systemd-udev 253.141.fc38 -> 253.152.fc38
> 
> libwpe 1.14.02.fc38 -> 1.14.21.fc38
> 
> xen-libs 4.17.25.fc38 -> 4.17.26.fc38
> 
> qubes-libvchan-xen 4.2.11.fc38 -> 4.2.31.fc38
> 
> grub2-pc-modules 2.06108.fc38 -> 2.06114.fc38
> 
> bluez-libs 5.712.fc38 -> 5.721.fc38
> 
> pipewire 1.0.02.fc38 -> 1.0.31.fc38
> 
> pipewire-libs 1.0.02.fc38 -> 1.0.31.fc38
> 
> flexiblas-netlib 3.3.15.fc38 -> 

[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 script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'Generating grub configuration file ...\nFound linux image: 
/boot/vmlinuz-6.6.11-100.fc38.x86_64\nFound initrd image: 
/boot/initramfs-6.6.11-100.fc38.x86_64.img\nfgrep: warning: fgrep is 
obsolescent; using grep -F\nFound linux image: 
/boot/vmlinuz-6.6.9-100.fc38.x86_64\nFound initrd image: 
/boot/initramfs-6.6.9-100.fc38.x86_64.img\nfgrep: warning: fgrep is 
obsolescent; using grep -F\nFound linux image: 
/boot/vmlinuz-6.6.11-100.fc38.x86_64\nFound initrd image: 
/boot/initramfs-6.6.11-100.fc38.x86_64.img\nfgrep: warning: fgrep is 
obsolescent; using grep -F\nFound linux image: 
/boot/vmlinuz-6.6.9-100.fc38.x86_64\nFound initrd image: 
/boot/initramfs-6.6.9-100.fc38.x86_64.img\nfgrep: warning: fgrep is 
obsolescent; using grep -F\nfgrep: warning: fgrep is obsolescent; using 
grep -F\nAdding boot menu entry for UEFI Firmware Settings ...\ndone\n'

b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'

Installed packages:
cirrus-audio-firmware ['202401152.fc38']
intel-audio-firmware ['202401152.fc38']
nxpwireless-firmware ['202401152.fc38']
tiwilink-firmware ['202401152.fc38']
Updated packages:
kernel-modules-core 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 -> 
6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
kernel-core 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 -> 
6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
kernel-modules 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 -> 
6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38
kernel 6.6.8100.fc38', '6.6.9100.fc38', '6.6.11100.fc38 -> 
6.6.9100.fc38', '6.6.11100.fc38', '6.7.4100.fc38

linux-firmware-whence 202312111.fc38 -> 202401152.fc38
xorg-x11-server-common 1.20.1428.fc38 -> 1.20.1429.fc38
xen-licenses 4.17.25.fc38 -> 4.17.26.fc38
amd-gpu-firmware 202312111.fc38 -> 202401152.fc38
amd-ucode-firmware 202312111.fc38 -> 202401152.fc38
atheros-firmware 202312111.fc38 -> 202401152.fc38
brcmfmac-firmware 202312111.fc38 -> 202401152.fc38
intel-gpu-firmware 202312111.fc38 -> 202401152.fc38
mt7xxx-firmware 202312111.fc38 -> 202401152.fc38
nvidia-gpu-firmware 202312111.fc38 -> 202401152.fc38
realtek-firmware 202312111.fc38 -> 202401152.fc38
linux-firmware 202312111.fc38 -> 202401152.fc38
python3-dnf-plugins-qubes-hooks 4.2.271.fc38 -> 4.2.281.fc38
vim-filesystem 9.1.0311.fc38 -> 9.1.0762.fc38
vim-data 9.1.0311.fc38 -> 9.1.0762.fc38
tzdata 2023d1.fc38 -> 2024a1.fc38
perl-Module-CoreList 5.202312301.fc38 -> 5.202401291.fc38
ncurses-base 6.43.20230114.fc38 -> 6.47.20230520.fc38
glibc-gconv-extra 2.3716.fc38 -> 2.3718.fc38
ncurses-libs 6.43.20230114.fc38 -> 6.47.20230520.fc38
glibc 2.3716.fc38 -> 2.3718.fc38
bash 5.2.211.fc38 -> 5.2.261.fc38
glibc-common 2.3716.fc38 -> 2.3718.fc38
glibc-langpack-en 2.3716.fc38 -> 2.3718.fc38
systemd-libs 253.141.fc38 -> 253.152.fc38
gstreamer1 1.22.81.fc38 -> 1.22.91.fc38
alsa-lib 1.2.102.fc38 -> 1.2.112.fc38
grub2-common 2.06108.fc38 -> 2.06114.fc38
libdrm 2.4.1171.fc38 -> 2.4.1201.fc38
gstreamer1-plugins-base 1.22.81.fc38 -> 1.22.91.fc38
gstreamer1-plugins-good 1.22.81.fc38 -> 1.22.91.fc38
gstreamer1-plugins-good-qt 1.22.81.fc38 -> 1.22.91.fc38
gstreamer1-plugins-bad-free-libs 1.22.83.fc38 -> 1.22.91.fc38
audit-libs 3.1.25.fc38 -> 3.1.28.fc38
at-spi2-core 2.48.31.fc38 -> 2.48.41.fc38
atk 2.48.31.fc38 -> 2.48.41.fc38
libidn2 2.3.42.fc38 -> 2.3.71.fc38
systemd-networkd 253.141.fc38 -> 253.152.fc38
systemd-pam 253.141.fc38 -> 253.152.fc38
systemd-resolved 253.141.fc38 -> 253.152.fc38
systemd 253.141.fc38 -> 253.152.fc38
gnutls 3.8.22.fc38 -> 3.8.31.fc38
samba-common 4.18.91.fc38 -> 4.18.101.fc38
systemd-udev 253.141.fc38 -> 253.152.fc38
libwpe 1.14.02.fc38 -> 1.14.21.fc38
xen-libs 4.17.25.fc38 -> 4.17.26.fc38
qubes-libvchan-xen 4.2.11.fc38 -> 4.2.31.fc38
grub2-pc-modules 2.06108.fc38 -> 2.06114.fc38
bluez-libs 5.712.fc38 -> 5.721.fc38
pipewire 1.0.02.fc38 -> 1.0.31.fc38
pipewire-libs 1.0.02.fc38 -> 1.0.31.fc38
flexiblas-netlib 3.3.15.fc38 -> 3.4.11.fc38
flexiblas 3.3.15.fc38 -> 3.4.11.fc38
flexiblas-openblas-openmp 3.3.15.fc38 -> 3.4.11.fc38
libadwaita 1.3.51.fc38 -> 1.3.61.fc38
libcloudproviders 0.3.21.fc38 -> 0.3.51.fc38
readline 8.23.fc38 -> 8.24.fc38
bluez 5.712.fc38 -> 5.721.fc38
zenity 4.0.01.fc38 -> 4.0.11.fc38
pipewire-jack-audio-connection-kit-libs 1.0.02.fc38 -> 1.0.31.fc38
pipewire-pulseaudio 1.0.02.fc38 -> 1.0.31.fc38
qubes-core-qrexec-libs 4.2.161.fc38 -> 4.2.171.fc38
libjcat 0.1.131.fc38 -> 0.2.11.fc38
fwupd-plugin-flashrom 1.9.111.fc38 -> 1.9.121.fc38

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 like 
> there may be a discrepancy between the two.
> 
> The site says the key is:
> 
> 0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
> and I have the following:
> 
>  ~  which gpg  
> /usr/bin/gpg
>  ~  ls -al /usr/bin/gpg 
> -rwxr-xr-x 1 root root 1151616 Nov 28 14:24 /usr/bin/gpg
>  ~  ls -al /usr/bin/gpg2
> lrwxrwxrwx 1 root root 3 Nov 28 14:24 /usr/bin/gpg2 -> gpg
>  ~  gpg --import ~/Downloads/ISOs/qubes-release-4.2-signing-key.asc 
> gpg: key 0xE022E58F8E34D89F: 1 signature not checked due to a missing key
> gpg: key 0xE022E58F8E34D89F: public key "Qubes OS Release 4.2 Signing Key" 
> imported
> gpg: Total number processed: 1
> gpg:   imported: 1
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: Note: signatures using the SHA1 algorithm are rejected
> gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> gpg: next trustdb check due at 2025-01-04
>  ~  gpg --fingerprint Qubes
> pub   rsa4096/0xE022E58F8E34D89F 2022-10-04 [SC]
>   Key fingerprint = 9C88 4DF3 F810 64A5 69A4  A9FA E022 E58F 8E34 D89F
> uid   [ unknown] Qubes OS Release 4.2 Signing Key
> 
> Any help will be appreciated.
> 
> Thank you.
> 

You downloaded only the Qubes 4.2 release signing key (RSK), not the Qubes 
Master Signing Key (QMSK). Please carefully read and follow this section:

https://www.qubes-os.org/security/verifying-signatures/#how-to-import-and-authenticate-the-qubes-master-signing-key

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dc96fa1a-c29c-4f38-9c04-410e7a85dd36%40qubes-os.org.


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

The site says the key is:

0x427F11FD0FAA4B080123F01CDDFA1A3E36879494
and I have the following:

 ~  which gpg  
/usr/bin/gpg
 ~  ls -al /usr/bin/gpg 
-rwxr-xr-x 1 root root 1151616 Nov 28 14:24 /usr/bin/gpg
 ~  ls -al /usr/bin/gpg2
lrwxrwxrwx 1 root root 3 Nov 28 14:24 /usr/bin/gpg2 -> gpg
 ~  gpg --import ~/Downloads/ISOs/qubes-release-4.2-signing-key.asc 
gpg: key 0xE022E58F8E34D89F: 1 signature not checked due to a missing key
gpg: key 0xE022E58F8E34D89F: public key "Qubes OS Release 4.2 Signing Key" 
imported
gpg: Total number processed: 1
gpg:   imported: 1
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: Note: signatures using the SHA1 algorithm are rejected
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2025-01-04
 ~  gpg --fingerprint Qubes
pub   rsa4096/0xE022E58F8E34D89F 2022-10-04 [SC]
  Key fingerprint = 9C88 4DF3 F810 64A5 69A4  A9FA E022 E58F 8E34 D89F
uid   [ unknown] Qubes OS Release 4.2 Signing Key

Any help will be appreciated.

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/44675806-54db-4b95-94ed-df90b03f104cn%40googlegroups.com.


[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 however still does have 'external / public' network 
access - and - the update of templates through the Qubes Updater is also 
still working ...

I did perform a backup a backup of all VMs before starting the script - but 
- would like to skip a new install if possible ! - Any advice / ideas ?

With kind regards,

Viktor

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ab1202ed-95e9-4b44-b4fb-11a087311141n%40googlegroups.com.