Add flatpak update notification and auto proxy config - #604
Conversation
b78279d to
5cb8b88
Compare
5cb8b88 to
0e8a2e6
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #604 +/- ##
=======================================
Coverage 71.10% 71.10%
=======================================
Files 3 3
Lines 481 481
=======================================
Hits 342 342
Misses 139 139 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Automatic proxy config for flatpak in TemplateVMs. Notify dom0 if system-wide (in TemplateVM) flatpaks are outdated. A separate patch to `qubes-core-admin-linux` & `vmupdate` will enable easy update of (in Template) flatpaks via the updater. related: QubesOS/qubes-issues#2766
0e8a2e6 to
659e8e6
Compare
|
There is one rough edge to document - proxy won't work just after installing flatpak package - you need to restart the template for that. |
Another option would be writing individual post-install hooks per package manager? (dnf, apt, pacman, ...)? But it would a little bit painful. And where to document? |
Just looked at the Flatpak documentation again. For Archlinux, Debian, Ubuntu, ...; they already advise user to restart the system anyways: So only a hook is needed for Qubes Fedora templates (which do not have it installed by default). |
https://doc.qubes-os.org/en/latest/user/how-to-guides/how-to-install-software.html seems like a good place to add section about Flatpak. I don't think there need to be any automatic restart or anything like that, keep it simple. |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025112000-4.3&flavor=pull-requests Test run included the following:
Upload failures
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025111104-4.3&flavor=update
Failed tests30 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/158999#dependencies 13 fixed
Unstable testsDetailsPerformance TestsPerformance degradation:26 performance degradations
Remaining performance tests:153 tests
|
|
Why sudo change you affect this? I didn't use sudo to run flatpak... does it use it internally? |
|
Converting to draft, as it needs to be merged together with the other PR that is draft too. Feel free to un-draft it when the other PR is ready. |
|
I tested the changes in One way around this could be to disable |
A better solution would be to disable network access by default in flatpak apps, using flatpak overrides. This approach, combined with the changes already done in The following configurations can be inserted in the This is a contribution I would like to make to complement the solution. |
|
Does this have to be in the user home dir? Can it be another XDG directory? (because it's going to be ugly to put it in templates only) |
5 participants
Automatic proxy config for flatpak in TemplateVMs. Notify dom0 if system-wide (in TemplateVM) flatpaks are outdated.
A separate patch to
qubes-core-admin-linux&vmupdatewill enable easy update of (in Template) flatpaks via the updater.related: QubesOS/qubes-issues#2766