Qubes OS 4.2.0-rc3 is available for testing

solene · September 5, 2023, 11:55am

How do you configure split-ssh from the GUI?

solene · September 5, 2023, 2:38pm

I found a pretty nasty bug, I wonder if someone is able to trigger it? On 3 Qubes OS 4.2-RC3, only the one with the fresh install had this issue, but maybe it’s unrelated to upgrade vs fresh install

github.com/QubesOS/qubes-issues

4.2-RC3: user_salt isn't working

opened 11:58AM - 05 Sep 23 UTC

rapenne-s

T: bug P: default

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release Fresh install of 4.2-RC3 ### Brief summary I installed 4.2-RC3, enabled user-dirs in salt, imported my salt repo which work on other Qubes OS deployments (that are not fresh 4.2-RC3 but upgraded from 4.1), it fails in weird ways. dom0 related configuration are working 50% of the time **non-dom0** configuration aren't working, qubesctl report that no top file are matching their name, while it works on other computers. Although, adding `saltenv=user` make it work! ### Steps to reproduce - Enable user-dirs with `qubesctl state.sls qubes.user-dirs` - Modify `/srv/user_salt/top.sls` to look like ``` user: 'dom0': - qubes-vm ``` - Create `/srv/user_salt/qubes-vm.sls` with this content: ``` create-qubes-www: qvm.vm: - name: WWW - present: - template: fedora-38 - label: orange - prefs: - label: orange ``` - Run `qubesctl state.highstate` First run fails ``` [root@dom0 srv]# qubesctl --targets dom0 --show-output state.apply [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. [ERROR ] State 'qvm.vm' was not found in SLS 'qubes-vm' Reason: 'qvm.vm' is not available. local: ---------- ID: create-qubes-www Function: qvm.vm Name: WWW Result: False Comment: State 'qvm.vm' was not found in SLS 'qubes-vm' Reason: 'qvm.vm' is not available. Changes: Summary for local ------------ Succeeded: 0 Failed: 1 ------------ Total states run: 1 Total run time: 0.000 ms DOM0 configuration failed, not continuing ``` 2nd run works ``` [root@dom0 srv]# qubesctl --targets dom0 --show-output state.apply [CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable [CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. local: ---------- ID: topd-always-passes Function: test.succeed_without_changes Name: foo Result: True Comment: Success! Started: 10:23:00.000115 Duration: 0.588 ms Changes: ---------- ID: create-qubes-www Function: qvm.vm Name: WWW Result: True Comment: ====== ['present'] ====== [SKIP] A VM with the name 'WWW' already exists. ====== ['prefs'] ====== [SKIP] label : orange Started: 10:23:00.031787 Duration: 413.524 ms Changes: Summary for local ------------ Succeeded: 2 Failed: 0 ------------ Total states run: 2 Total run time: 414.112 ms ``` 3rd run doesn't work ``` [root@dom0 srv]# qubesctl --targets dom0 --show-output state.apply [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. [ERROR ] State 'qvm.vm' was not found in SLS 'qubes-vm' Reason: 'qvm.vm' is not available. local: ---------- ID: create-qubes-www Function: qvm.vm Name: WWW Result: False Comment: State 'qvm.vm' was not found in SLS 'qubes-vm' Reason: 'qvm.vm' is not available. Changes: Summary for local ------------ Succeeded: 0 Failed: 1 ------------ Total states run: 1 Total run time: 0.000 ms DOM0 configuration failed, not continuing ``` 4th run works ``` [root@dom0 srv]# qubesctl --targets dom0 --show-output state.apply [CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable [CRITICAL] Specified ext_pillar interface qvm_prefs is unavailable [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. local: ---------- ID: topd-always-passes Function: test.succeed_without_changes Name: foo Result: True Comment: Success! Started: 10:23:15.758674 Duration: 0.636 ms Changes: ---------- ID: create-qubes-www Function: qvm.vm Name: WWW Result: True Comment: ====== ['present'] ====== [SKIP] A VM with the name 'WWW' already exists. ====== ['prefs'] ====== [SKIP] label : orange Started: 10:23:15.788875 Duration: 328.364 ms Changes: Summary for local ------------ Succeeded: 2 Failed: 0 ------------ Total states run: 2 Total run time: 329.000 ms ``` ### Reproducer for template `user_salt` for templates is completely broken: - Enable user-dirs with `qubesctl state.sls qubes.user-dirs` - Modify `/srv/user_salt/top.sls` to look like ``` user: 'fedora-38': - package ``` - Create `/srv/user_salt/package.sls` with this content: ``` jq: pkg.installed ``` - Run `qubesctl --targets fedora-38 --skip-dom0 --show-output state.highstate` ``` [root@dom0 srv]# qubesctl --targets fedora-38 --skip-dom0 --show-output state.highstate fedora-38: An Exception occurred while executing state.highstate: Unable to render top file. No targets found. [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. [ERROR ] An Exception occurred while executing state.highstate: Unable to render top file. No targets found. [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. ``` It's possible to fix the command by adding `saltenv=user`: - Run `qubesctl --targets fedora-38 --skip-dom0 --show-output state.highstate saltenv=user` ``` [root@dom0 srv]# qubesctl --targets fedora-38 --skip-dom0 --show-output state.highstate saltenv=user fedora-38: ---------- ID: jq Function: pkg.installed Result: True Comment: All specified packages are already installed Started: 10:36:50.037392 Duration: 3369.414 ms Changes: Summary for fedora-38 ------------ Succeeded: 1 Failed: 0 ------------ Total states run: 1 Total run time: 3.369 s [WARNING ] top_file_merging_strategy is set to 'merge' and multiple top files were found. Merging order is not deterministic, it may be desirable to either set top_file_merging_strategy to 'same' or use the 'env_order' configuration parameter to specify the merging order. ``` ### Expected behavior It works ### Actual behavior mix of half working for dom0 and not working for non-dom0

solene · September 5, 2023, 8:16pm

Another issue that would be welcome to confirm with other devices. Attached USB audio devices don’t have sound, except if you change their profile using some tool like pavucontrol. I have this issues on all my Qubes OS 4.2 computers, with 3 different devices.

github.com/QubesOS/qubes-issues

4.2-RC3 - No sound for USB devices by default anymore

opened 08:15PM - 05 Sep 23 UTC

rapenne-s

T: bug P: default

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release 4.2-RC2 and 4.2-RC3 (not tested RC1) ### Brief summary When I attach an USB headset / headphones, I don't have any sound, this used to work out of the box on 4.1. If I run pavucontrol in the qube in which I attached the USB device, fiddling with the last tab "Configuration" and switching the device to "pro audio" profile often make it work. In the case of a Jabra Evolve 2 headset which has two modes: - using the usb dongle handling the bluetooth, and which appears as a sound card to the system, I can't have the microphone working anymore, even by trying other profiles - using an usb cable directly on the headset (so it's not wireless in that case), I can switch to pro audio or audio + mono microphone mode and I can get the mic working ### Steps to reproduce - Plug in an USB headset (tested with a Dragonfly Black DAC and a Jabra Evolve 2), attach it to a qube - there is no sound - go in pavucontrol last tab and try to switch profile - you may have sound, but maybe not microphone ### Expected behavior it works as it used to work on 4.1 ### Actual behavior no sound

szz9pza · September 6, 2023, 6:28pm

It would be nice to mention that [qubes-dom0-current-testing] need to be enabled to update to one RC to the other one (e.g. rc2 to rc3).
(Qubes OS Global Config > Updates > Enable all testing updates).

It may sound obvious for some, but not for others.

Btw, the unstable repo update are missing in this Updates tab.
It maybe on purpose …

solene · September 6, 2023, 6:33pm

tanks for sharing, that’s not really obvious to me

adw · September 6, 2023, 6:35pm

Oh, I didn’t know that. My mistake. Thank you for pointing it out. I’ve added the missing step:

quantum · September 6, 2023, 6:44pm

Network password not persistent using persistent Debian sys-XYZ service Qubes with a fresh 4.2.0-rc3 installation (tried multiple times and failed every time). I’ll submit a bug report if this isn’t something else I’m missing.

solene · September 7, 2023, 5:35pm

could you check your wifi device is always seen as the same device?

For instance, sometimes mine is wls6 and sometimes wls7, and network manager will associate that device to the wifi network… it’s not new in 4.2

balko · September 8, 2023, 12:29pm

Maybe somebody who uses R4.2 can install qbittorrent inside fedora-38 and check if the icon on a taskbar is a generic cube/lock or a proper one?

Installation inside template fedora-38:
sudo dnf install qbittorrent

I want to bump this issue for R4.2.

github.com/QubesOS/qubes-issues

Qubes not processing application icons correctly (likely due to different icon sizes)

opened 09:42AM - 18 Dec 20 UTC

jamke

T: bug C: other P: default needs diagnosis affects-4.1

**Qubes OS version** Qubes release 4.1 (R4.1). The same was on R4.0. Fedora 38… for templates (and at least 32). **Affected component(s) or functionality** GUI of dom0: icons on XFCE panel, window's icon and alt+tab windows list. **Brief summary** On some Fedora templates, including the latest Fedora-38) the icons of some applications (e.g. qBittorrent) in those appvm are not shown anywhere in dom0. The colored lock symbol is displayed. The majority of applications like Kate, Firefox, Thunderbird and others have proper icons. Template versions that act differently: * Fedora 30 and 29 had no such issue. * Fedora 32 had this issue. * Fedora 37 has no such issue * Fedora 38 has this issue. **How Reproducible** Always. **To Reproduce** Steps to reproduce the behavior: 1. Install Fedora-38 template in dom0 (sudo qubes-dom0-update qubes-template-fedora-38) 2. Install qBittorrent in fedora-38 3. Create AppVM based on this modified template. 4. Run qBittorrent in this AppVM. **Expected behavior** Icon is shown on XFCE panel of qBittorrent. **Actual behavior** No proper icon is shown on XFCE panel, nor qBittorrent window itself, nor in alt+tab list. The colored lock symbol is displayed instead. **Additional context** 1. Proper icon is shown for qBittorrent in "Application menu" of XFCE panel (it's small there as any other). 2. It you create a XFCE Launcher on the panel and add qBittorrent then it will have different size of the icon, smaller. Probably it's a reason of the issue. 3. The majority of applications like Kate, Dolphin, Firefox, Thunderbird and others have proper icons. **Solutions you've tried** None. **Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues** I found no issues about icon problem with only particular applications and after migration to Fedora latest template.

solene · September 8, 2023, 2:51pm

For me it looks like qbittorrent icon colored using the AppVM color, everything looks good. Worked fine in 4.1 before too.

balko · September 8, 2023, 2:53pm

So, on Fedora 38 and R4.1 it works fine for you, the icon on the taskbar in default XFCE is not a generic cube?

If that is true, I should look into my templates based on Fedora-38-minimal, maybe the issue is there.

solene · September 8, 2023, 2:56pm

ah, I only checked the systray, let me check again the other icons

solene · September 8, 2023, 3:01pm

so, with my red torrent qube based on fedora-38 template:

new Qube xfce menu: red qbittorent icon is there
old applications menu: red qbittorrent icon
xfce panel: red qube
xfce systray: red qbittorrent icon
alt+tab: red qube

balko · September 8, 2023, 3:07pm

@solene thank you, I appreciate your work.

You mean cube, right? So, I think the bug affects R4.2.
If you try fedora-37 my guess will be you will have proper icon in these 2 cases. If you have time please check it, too. Thanks.

DVM · September 8, 2023, 3:12pm

The answer is here:

balko · September 8, 2023, 3:19pm

No, I meant cube, not qube. This one: Cube - Wikipedia

solene · September 8, 2023, 3:30pm

oh yeah, I’m getting confused. Qubes OS’s cube icon

edit: same cubic icon in the virtual desktops windows list

DVM · September 8, 2023, 3:31pm

My bad, I thought you were talking about VMs.

resulin · September 8, 2023, 4:52pm

I had the same concern in the previous thread: Qubes OS 4.2.0-rc2 is available for testing - #19 by resulin

balko · September 9, 2023, 5:35am

The ticket Pipewire audio support · Issue #6358 · QubesOS/qubes-issues · GitHub was not closed because the Qubes developers forgot to do it.

The answer by @Demi about this:

I am not sure what the documentation status is.
PipeWire in dom0 is not officially supported. Audio playback and recording are known to work, but features such as sound volume save & restore don’t.
PipeWire in sys-audio and in qubes that connect to sys-audio is fully supported, at least to the extent that sys-audio is supported at all.