Re: [qubes-users] Updating Signal desktop
How did you install it? If you used a debian template and the instructions on the signal website, you just need to update the template. -- 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/f4b08d8a-653a-955a-f712-c9685ab53397%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] best way to disable a linux service in a AppVM
lik...@gmx.de: Hi! What's the best way to disable a linux service "e.g. systemctl disable --now systemd-resolved.service &" in a AppVM. I don't want to disable the service in my template because it's used by other AppVMs. Currently, I'm doing this in /rw/config/rc.local by "sleep 5s && sudo systemctl disable --now systemd-resolved.service &". But it's probably not the best way as it relies on the startup timing. Thanks in advance and best, P I think the canonical way to do that is to use the services tab of the qube to identify which service(s) to start or stop. I am a bit unclear on how that is done exactly, though. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/35050c1a-d79b-f8fc-c77b-df5156efcdab%40danwin1210.me.
Re: [qubes-users] Qubes Update does not work for Whonix 16 templates ...
Hello 'unman', unman schrieb am Sonntag, 7. November 2021 um 15:36:50 UTC+1: > On Sun, Nov 07, 2021 at 04:07:13AM -0800, Viktor Ransmayr wrote: > > I've installed Whonix 16 on my Qubes OS R4.0 system - and - have > switched > > 'sys-whonix' to 'whonix-gw-16' as well as 'anon-whonix' to > 'whonix-ws-16'. > > > > Everything seems to work fine - but - Qubes Updater reports that updates > > are available for 'whonix-[gw | ws]-16' but always fails to update the > > templates with error msgs similar to > > > > ### > > > > Updating whonix-gw-16 > > > > Error on updating whonix-gw-16: Command '['sudo', 'qubesctl', > > '--skip-dom0', '--targets=whonix-gw-16', '--show-output', 'state.sls', > > 'update.qubes-vm']' returned non-zero exit status 20 > > whonix-gw-16: > > -- > > ID: update > > Function: pkg.uptodate > > Result: False > > Comment: E: Release file for > > tor+ > https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease > > is not valid yet (invalid for another 14min 36s). Updates for this > > repository will not be applied. > > Started: 11:15:16.396556 > > Duration: 8366.294 ms > > Changes: > > -- > > ID: notify-updates > > Function: cmd.run > > Name: /usr/lib/qubes/upgrades-status-notify > > Result: False > > Comment: Command "/usr/lib/qubes/upgrades-status-notify" run > > Started: 11:15:24.765086 > > Duration: 2514.791 ms > > Changes: > > -- > > pid: > > 1782 > > retcode: > > 100 > > stderr: > > stdout: > > > > Summary for whonix-gw-16 > > > > Succeeded: 0 (changed=1) > > Failed: 2 > > > > Total states run: 2 > > Total run time: 10.881 s > > > > Updating whonix-ws-16 > > > > Error on updating whonix-ws-16: Command '['sudo', 'qubesctl', > > '--skip-dom0', '--targets=whonix-ws-16', '--show-output', 'state.sls', > > 'update.qubes-vm']' returned non-zero exit status 20 > > whonix-ws-16: > > -- > > ID: update > > Function: pkg.uptodate > > Result: False > > Comment: E: Release file for > > tor+ > https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease > > is not valid yet (invalid for another 16min 48s). Updates for this > > repository will not be applied. > > Started: 11:13:10.907970 > > Duration: 2607.219 ms > > Changes: > > -- > > ID: notify-updates > > Function: cmd.run > > Name: /usr/lib/qubes/upgrades-status-notify > > Result: False > > Comment: Command "/usr/lib/qubes/upgrades-status-notify" run > > Started: 11:13:13.517469 > > Duration: 2907.295 ms > > Changes: > > -- > > pid: > > 1789 > > retcode: > > 100 > > stderr: > > stdout: > > > > Summary for whonix-ws-16 > > > > Succeeded: 0 (changed=1) > > Failed: 2 > > > > Total states run: 2 > > Total run time: 5.515 s > > > > ### > > > > What are the recommended steps to resolve this issue? > > > > With kind regards, > > > > Viktor > > > > PS: I obviously tried this several time - but - the error msg stays the > > same - only - with changing "invalid for ..." times ... > > > > Fix the time on your update qube,( and possibly your target). It is, as > you can see, wrong. > Thanks a lot for your feedback! - Using 'timedatectl set-time ...' for 'whonix-[gw | ws]-16' did resolve the issue. I started to read more on this topic now - but - did not (yet) find best practice recommendations on how to ensure that AppVMs & TemplateVMs are time-synced automatically, when they are started. Do you have any recommendation? 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/56c69f16-55cb-4450-9724-bdf00c6810dan%40googlegroups.com.
Re: [qubes-users] Qubes Update does not work for Whonix 16 templates ...
On Sun, Nov 07, 2021 at 04:07:13AM -0800, Viktor Ransmayr wrote: > I've installed Whonix 16 on my Qubes OS R4.0 system - and - have switched > 'sys-whonix' to 'whonix-gw-16' as well as 'anon-whonix' to 'whonix-ws-16'. > > Everything seems to work fine - but - Qubes Updater reports that updates > are available for 'whonix-[gw | ws]-16' but always fails to update the > templates with error msgs similar to > > ### > > Updating whonix-gw-16 > > Error on updating whonix-gw-16: Command '['sudo', 'qubesctl', > '--skip-dom0', '--targets=whonix-gw-16', '--show-output', 'state.sls', > 'update.qubes-vm']' returned non-zero exit status 20 > whonix-gw-16: > -- > ID: update > Function: pkg.uptodate > Result: False >Comment: E: Release file for > tor+https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease > is not valid yet (invalid for another 14min 36s). Updates for this > repository will not be applied. >Started: 11:15:16.396556 > Duration: 8366.294 ms >Changes: > -- > ID: notify-updates > Function: cmd.run > Name: /usr/lib/qubes/upgrades-status-notify > Result: False >Comment: Command "/usr/lib/qubes/upgrades-status-notify" run >Started: 11:15:24.765086 > Duration: 2514.791 ms >Changes: > -- > pid: > 1782 > retcode: > 100 > stderr: > stdout: > > Summary for whonix-gw-16 > > Succeeded: 0 (changed=1) > Failed:2 > > Total states run: 2 > Total run time: 10.881 s > > Updating whonix-ws-16 > > Error on updating whonix-ws-16: Command '['sudo', 'qubesctl', > '--skip-dom0', '--targets=whonix-ws-16', '--show-output', 'state.sls', > 'update.qubes-vm']' returned non-zero exit status 20 > whonix-ws-16: > -- > ID: update > Function: pkg.uptodate > Result: False >Comment: E: Release file for > tor+https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease > is not valid yet (invalid for another 16min 48s). Updates for this > repository will not be applied. >Started: 11:13:10.907970 > Duration: 2607.219 ms >Changes: > -- > ID: notify-updates > Function: cmd.run > Name: /usr/lib/qubes/upgrades-status-notify > Result: False >Comment: Command "/usr/lib/qubes/upgrades-status-notify" run >Started: 11:13:13.517469 > Duration: 2907.295 ms >Changes: > -- > pid: > 1789 > retcode: > 100 > stderr: > stdout: > > Summary for whonix-ws-16 > > Succeeded: 0 (changed=1) > Failed:2 > > Total states run: 2 > Total run time: 5.515 s > > ### > > What are the recommended steps to resolve this issue? > > With kind regards, > > Viktor > > PS: I obviously tried this several time - but - the error msg stays the > same - only - with changing "invalid for ..." times ... > Fix the time on your update qube,( and possibly your target). It is, as you can see, wrong. -- I **never** presume to speak for the Qubes team. When I comment in the Forum or in the mailing lists I speak for myself. -- 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/YYfkfi1uucy1jcWK%40thirdeyesecurity.org.
[qubes-users] Updating Signal desktop
Hi, I am having a problem with Signal Desktop. Signal released new update and as a result the desktop version is not working anymore. What is the best way to update Signal desktop? Thanks, -- Amir Rashidi Signal: +1(202)560-3853 GPG Fingerprint: 5EDE 7C56 33AB 43FF A85A EF04 FAA2 6FE8 7DA4 C124 -- 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/62cfad3d-e270-58e7-ad6b-06d1d982f42b%40gmail.com.
[qubes-users] Qubes Update does not work for Whonix 16 templates ...
I've installed Whonix 16 on my Qubes OS R4.0 system - and - have switched 'sys-whonix' to 'whonix-gw-16' as well as 'anon-whonix' to 'whonix-ws-16'. Everything seems to work fine - but - Qubes Updater reports that updates are available for 'whonix-[gw | ws]-16' but always fails to update the templates with error msgs similar to ### Updating whonix-gw-16 Error on updating whonix-gw-16: Command '['sudo', 'qubesctl', '--skip-dom0', '--targets=whonix-gw-16', '--show-output', 'state.sls', 'update.qubes-vm']' returned non-zero exit status 20 whonix-gw-16: -- ID: update Function: pkg.uptodate Result: False Comment: E: Release file for tor+https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease is not valid yet (invalid for another 14min 36s). Updates for this repository will not be applied. Started: 11:15:16.396556 Duration: 8366.294 ms Changes: -- ID: notify-updates Function: cmd.run Name: /usr/lib/qubes/upgrades-status-notify Result: False Comment: Command "/usr/lib/qubes/upgrades-status-notify" run Started: 11:15:24.765086 Duration: 2514.791 ms Changes: -- pid: 1782 retcode: 100 stderr: stdout: Summary for whonix-gw-16 Succeeded: 0 (changed=1) Failed:2 Total states run: 2 Total run time: 10.881 s Updating whonix-ws-16 Error on updating whonix-ws-16: Command '['sudo', 'qubesctl', '--skip-dom0', '--targets=whonix-ws-16', '--show-output', 'state.sls', 'update.qubes-vm']' returned non-zero exit status 20 whonix-ws-16: -- ID: update Function: pkg.uptodate Result: False Comment: E: Release file for tor+https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease is not valid yet (invalid for another 16min 48s). Updates for this repository will not be applied. Started: 11:13:10.907970 Duration: 2607.219 ms Changes: -- ID: notify-updates Function: cmd.run Name: /usr/lib/qubes/upgrades-status-notify Result: False Comment: Command "/usr/lib/qubes/upgrades-status-notify" run Started: 11:13:13.517469 Duration: 2907.295 ms Changes: -- pid: 1789 retcode: 100 stderr: stdout: Summary for whonix-ws-16 Succeeded: 0 (changed=1) Failed:2 Total states run: 2 Total run time: 5.515 s ### What are the recommended steps to resolve this issue? With kind regards, Viktor PS: I obviously tried this several time - but - the error msg stays the same - only - with changing "invalid for ..." times ... -- 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/0ba6fc35-5cc7-4bac-a1bc-7ed2d3c8ba52n%40googlegroups.com.
[qubes-users] Re: best way to disable a linux service in a AppVM
On 11/6/21 18:06, unman wrote: > On Sat, Nov 06, 2021 at 04:34:02PM +, liked2-mmb7mzph...@public.gmane.org > wrote: >> On 11/6/21 16:23, badgateway wrote: >>> Is it an option to clone your current template and disable the services >>> permanently in your new template? >>> >> >> It is an option. But in this case I'd prefer the way using >> /rw/config/rc.local not to maintain another template. >> >> I've learned there must be 3 alternatives, otherwise you've not done enough >> research. Maybe there's a 3rd way? >> > > There is indeed a third way, which fits nicely in to the Qubes > framework, and is used by qvm-service. Instead of disabling the > service, control it. > > If your service is foo.service: > Create a folder foo.service.d, and create a file 10_qubes.conf with > something like > ``` > [Unit] > ConditionPathExists=/var/run/qubes/service/foo > After=qubes.sysinit.service > ``` > > Now you can control with `qvm-service --enable foo` in qubes > where you want the service to run. > > You could invert the sense of control by using > ConditionPathExists=! but this may lead to confusion. > Thanks unman, that's exactly what I was looking for. Except, there's a 4th way. :) -- 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/66c2bbb6-e02c-89ef-95b7-f9425b4f9d51%40gmx.de.
