-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not disable tracker and evolution-data-server in AppVMs #450
Conversation
Contrary to initial tests, disbling those do break some applications. So, do not disable them by default in AppVMs. But keep them disabled in system vms, as user applications are not expected there. QubesOS/qubes-issues#8372
cc @Rudd-O |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.2&build=2023080903-4.2&flavor=pull-requests New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.2&build=2023071104-4.2&flavor=update
Failed tests9 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/77326#dependencies 23 fixed
Unstable tests
|
PR looks fine to me but I would still like the ability to, as a user, explicitly disable them using |
FYI e-d-s forcibly disabled breaks evolution and GNOME calendar. Tracker disabled breaks the music player insofar as it will not be able to list music the user has in user folders. It would be nice, however, if the startup process did NOT actually start these when unneeded by apps. |
It should work this way already: |
Contrary to initial tests, disbling those do break some applications.
So, do not disable them by default in AppVMs.
But keep them disabled in system vms, as user applications are not
expected there.
QubesOS/qubes-issues#8372