Reproducible Qube Manager crash on launching a qube's Settings

[UndeadDevel]

Qubes OS release

4.2rc5

Brief summary

Reproducable on my machine 100% of times so far. It seems to only resolve itself (settings available again) when the 5 minutes are up (firewall full access rule).

Steps to reproduce

1. create new AppVM (in my case based on debian-12-xfce) with default networking (sys-firewall as netVM)
2. open this qube's Settings via the domains widget and set firewall rules to "limit outgoing connections" and put checkmark on "allow full access for", press ok
3. Run (from dom0; I assume that the qube's name has been stored in qube):

qvm-prefs $qube netvm None
qvm-prefs $qube netvm -D

4. Try to open this qube's Settings again via the domains widget and observe error message (see "Actual behavior")

Expected behavior

no errors or crashes

Actual behavior

Text in that error window:

----
line: self.temp_full_access_time.setValue(
func: set_fw_model
line no.: 1464
file: /usr/lib/python3.11/site-packages/qubesmanager/settings.py
----
line: self.set_fw_model(model)
func: __init__
line no.: 192
file: /usr/lib/python3.11/site-packages/qubesmanager/settings.py
----
line: window = window_class(qt_app, qubes_app)
func: run_synchronous
line no.: 558
file: /usr/lib/python3.11/site-packages/qubesmanager/utils.py
----
line: utils.run_synchronous(functools.partial(VMSettingsWindow, vm, args.tab))
func: main
line no.: 1540
file: /usr/lib/python3.11/site-packages/qubesmanager/settings.py
----
line: sys.exit(load_entry_point('qubesmanager==4.2.7', 'console_scripts', 'qubes-vm-settings')())
func: <module>
line no.: 33
file: /usr/bin/qubes-vm-settings

dom0 sudo journalctl output when subsequently trying to open the Qubes Manager via the domains widget list item (very large):
journalctl_output_when_subsequently_trying_to_open_the_qube_manager_via_qube_widget_link.log

[qubesos-bot]

Automated announcement from builder-github

The package manager has been pushed to the r4.2 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing bullseye-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package manager has been pushed to the r4.2 testing repository for the CentOS centos-stream8 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package manager has been pushed to the r4.2 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing bookworm-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component manager (including package manager) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component manager (including package manager) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component manager (including package manager) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package manager has been pushed to the r4.2 stable repository for the CentOS centos-stream8 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package manager has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package manager has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component manager (including package manager) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component manager (including package manager) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The component manager (including package manager) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:

sudo dnf update

Changes included in this update

[UndeadDevel]

This is still not fixed, can still reproduce in an up-to-date Debian-12 based AppVM. Also, this issue seems to be a duplicate of #8685.

Edit: oh and I see that the manager update is actually still in testing...disregard above then, except for this being a duplicate.

[andrewdavidwong]

This is still not fixed, can still reproduce in an up-to-date Debian-12 based AppVM. Also, this issue seems to be a duplicate of #8685.

Edit: oh and I see that the manager update is actually still in testing...disregard above then, except for this being a duplicate.

Ordinarily, you're correct that we would close #8757 (the newer issue) as a duplicate of #8685 (the older issue). However, since #8757 is already closed as fixed, and the commits are associated with #8757, we can close #8685 as a duplicate instead.

[UndeadDevel]

This seems to have been fixed only for float operand types, not int and str...so the issue is still reproducible under the same conditions, but now with a different error message (TypeError: unsupported operand type(s) for-: 'int' and 'str' at line 33 of file /usr/bin/qubes-vm-settings):
See this comment for the error window, and comment below for new error log, but it seems it was decided to deal with this new error message in the other issue (#8685).