Re: [qubes-users] Qubes Manager not honoring colour scheme selection
that should be the solution. Did it wrong also on my first try. After editing the /etc/environment , it works... a...@qubes-os.org schrieb am Dienstag, 26. Juli 2022 um 10:15:58 UTC+2: > On 7/25/22 4:53 PM, 'taran1s' via qubes-users wrote: > > I tried this but didn't succeed. > > > > sudo qubes-dom0-update qt5-qtstyleplugins > > sudo qubes-dom0-update > > export QT_QPA_PLATFORMTHEME=gtk2 > > > > cat /etc/environment QT_QPA_PLATFORMTHEME=gtk2 > > cat: 'QT_QPA_PLATFORMTHEME=gtk2': No such file or directory > > > > Qube Manager is still white ^^. Any ideas? > > > > You have to actually edit the file `/etc/environment` in order to insert > the string `QT_QPA_PLATFORMTHEME=gtk2` into that file, then reboot > afterward. > > P.S. -- Please avoid top-posting. > > > > > TheGardner: > >> Thanks very much Demi Marie. > >> Then this should be the correct way: > >> > >> Source & Info: https://github.com/QubesOS/qubes-issues/issues/7389 > >> > >> > >> Install the package qt5-qtstyleplugins with: > >> > >> sudo qubes-dom0-update qt5-qtstyleplugins > >> > >> then insert in /etc/environment: > >> > >> -[Start]- > >> QT_QPA_PLATFORMTHEME=gtk2 > >> -[End]--- > >> > >> in dom0 terminal do: > >> > >> export QT_QPA_PLATFORMTHEME=gtk2 > >> > >> --- > >> > >> finally you can check, if all changes were set & working: > >> > >> [TheGardner@dom0]$ cat /etc/environment > >> QT_QPA_PLATFORMTHEME=gtk2 > >> > >> [TheGardner@dom0]$ echo $QT_QPA_PLATFORMTHEME > >> gtk2 > >> > >> [TheGardner@dom0]$ sudo dnf info qt5-qtstyleplugins > >> Qubes OS Repository for Dom0 > >>1.9 MB/s | 3.0 kB 00:00 > >> Installed Packages > >> Name : qt5-qtstyleplugins > >> Version : 5.0.0 > >> Release : 39.fc32 > >> Architecture : x86_64 > >> Size : 1.2 M > >> Source : qt5-qtstyleplugins-5.0.0-39.fc32.src.rpm > >> Repository : @System > >> From repo: qubes-dom0-cached > >> Summary : Classic Qt widget styles > >> URL : https://github.com/qtproject/qtstyleplugins > >> License : LGPLv2 or GPLv2 > >> Description : Classic Qt widget styles, including cleanlooks, motif, > >> plastique, qgtk. > >> > >> Demi Marie Obenour schrieb am Samstag, 23. Juli 2022 um 04:07:18 UTC+2: > >> > >> On Fri, Jul 22, 2022 at 05:45:13PM -0700, TheGardner wrote: > >>>>> Great! It's working now with the following steps in dom0 terminal: > >>>>> > >>>>> Download qt5-qtstyleplugins RPM file from: > >>>>> > >>>>> > >> > https://kojipkgs.fedoraproject.org//packages/qt5-qtstyleplugins/5.0.0/39.fc32/x86_64/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm > >>>>> > >>>>> Move it from your AppVM to dom0 with: > >>>>> > >>>>> qvm-run --pass-io 'cat > >>>>> /home/user/Download/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm' > > >>>>> > >> > /home//Downloads/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm > >>>>> > >>>>> Install the package with: > >>>>> > >>>>> sudo dnf install -y qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm > >> > >> This is not safe. You can do: > >> > >> sudo qubes-dom0-update qt5-qtstyleplugins > >> > >> and it will work as with any other package. > >> > >> That reminds me: Marek, should we set repo_gpgcheck=1 and/or > >> %_pkgverify_level all in dom0, to protect against mistakes like this? > >>> > >> > > > > -- 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/9b3b1dec-a05b-4084-9f90-d1ac73656571n%40googlegroups.com.
Re: [qubes-users] Qubes Manager not honoring colour scheme selection
Thanks very much Demi Marie. Then this should be the correct way: Source & Info: https://github.com/QubesOS/qubes-issues/issues/7389 Install the package qt5-qtstyleplugins with: sudo qubes-dom0-update qt5-qtstyleplugins then insert in /etc/environment: -[Start]- QT_QPA_PLATFORMTHEME=gtk2 -[End]--- in dom0 terminal do: export QT_QPA_PLATFORMTHEME=gtk2 --- finally you can check, if all changes were set & working: [TheGardner@dom0]$ cat /etc/environment QT_QPA_PLATFORMTHEME=gtk2 [TheGardner@dom0]$ echo $QT_QPA_PLATFORMTHEME gtk2 [TheGardner@dom0]$ sudo dnf info qt5-qtstyleplugins Qubes OS Repository for Dom0 1.9 MB/s | 3.0 kB 00:00 Installed Packages Name : qt5-qtstyleplugins Version : 5.0.0 Release : 39.fc32 Architecture : x86_64 Size : 1.2 M Source : qt5-qtstyleplugins-5.0.0-39.fc32.src.rpm Repository : @System From repo: qubes-dom0-cached Summary : Classic Qt widget styles URL : https://github.com/qtproject/qtstyleplugins License : LGPLv2 or GPLv2 Description : Classic Qt widget styles, including cleanlooks, motif, plastique, qgtk. Demi Marie Obenour schrieb am Samstag, 23. Juli 2022 um 04:07:18 UTC+2: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On Fri, Jul 22, 2022 at 05:45:13PM -0700, TheGardner wrote: > > Great! It's working now with the following steps in dom0 terminal: > > > > Download qt5-qtstyleplugins RPM file from: > > > > > https://kojipkgs.fedoraproject.org//packages/qt5-qtstyleplugins/5.0.0/39.fc32/x86_64/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm > > > > Move it from your AppVM to dom0 with: > > > > qvm-run --pass-io 'cat > > /home/user/Download/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm' > > > > /home//Downloads/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm > > > > Install the package with: > > > > sudo dnf install -y qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm > > This is not safe. You can do: > > sudo qubes-dom0-update qt5-qtstyleplugins > > and it will work as with any other package. > > That reminds me: Marek, should we set repo_gpgcheck=1 and/or > %_pkgverify_level all in dom0, to protect against mistakes like this? > - -- > Sincerely, > Demi Marie Obenour (she/her/hers) > Invisible Things Lab > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmLbV8wACgkQsoi1X/+c > IsEEPA//XejMBSNBzh4aZJuxfWmvK1ie50x8oK7/NH8QpIEeFIWMRaZNZSs9RxVi > cMC17g62ZSyoxb9bwwFHsF3SLxmuSvl1ucBeHSQqfS5SdkwYOeiml38bNXauryaI > fGjVzq6CJFNSfBbhDMcskkP8wcKmBrQFXlK5yfSAZ7OL/Cv5i5yGeuXka1Ij9qLY > 8OY/qe331pAa++n4KyJp3Qvx3/tS/ZuaKna8Tt6GincXE6RdnsvWm2iP6HfFsIRb > lk3KSyM6fodA5uyCJGtcFAY6sJi9/5Fy8TlavMZxtv3xVQqVjZRVsKnMsld2TXnS > qPNSwGrKa6P9Z8gMUIufcLpNlNWccP5wvAOGtcJP6xVV9ALfXUGnnBP9scd3mGqo > 7RighrDtMdVhbxHu268iuduILHe/TWcWxpRigrOt2+oUNBD/PNAeUZkKx9slFisY > sof5/HDNDBNnfqwCPxjtn54PEfa+biK+cWwcjC0gov06otIRskp/Cwr193kwJi/D > K4KppbHsk1swCuQf06Cy/X2yvq67Xbe7g/HgqXrRgFPkPuWpSSpRWIeIdDaklCej > eXvQNQRbhAk6euYHJLjV8XMW1eC06Kaeo+ZvtEwBeZlBdnfkA1VlFc+XLfb2L3L/ > 9dff6pkqjr82mS64hGB9ocDRZgx3iikD5F79OL/X/ZcTF+uC+Wo= > =p8Nh > -END PGP SIGNATURE- > -- 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/099870c0-b61c-4b2e-8dd8-cd0619eeca65n%40googlegroups.com.
Re: [qubes-users] Qubes Manager not honoring colour scheme selection
Great! It's working now with the following steps in dom0 terminal: Download qt5-qtstyleplugins RPM file from: https://kojipkgs.fedoraproject.org//packages/qt5-qtstyleplugins/5.0.0/39.fc32/x86_64/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm Move it from your AppVM to dom0 with: qvm-run --pass-io 'cat /home/user/Download/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm' > /home//Downloads/qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm Install the package with: sudo dnf install -y qt5-qtstyleplugins-5.0.0-39.fc32.x86_64.rpm then insert in /etc/environment: -[Start]- QT_QPA_PLATFORMTHEME=gtk2 -[End]--- finally you can check, if all changes were set & working: [TheGardner@dom0]$ cat /etc/environment QT_QPA_PLATFORMTHEME=gtk2 [TheGardner@dom0]$ echo $QT_QPA_PLATFORMTHEME gtk2 [TheGardner@dom0]$ sudo dnf info qt5-qtstyleplugins Qubes OS Repository for Dom0 1.9 MB/s | 3.0 kB 00:00 Installed Packages Name : qt5-qtstyleplugins Version : 5.0.0 Release : 39.fc32 Architecture : x86_64 Size : 1.2 M Source : qt5-qtstyleplugins-5.0.0-39.fc32.src.rpm Repository : @System From repo: qubes-dom0-cached Summary : Classic Qt widget styles URL : https://github.com/qtproject/qtstyleplugins License : LGPLv2 or GPLv2 Description : Classic Qt widget styles, including cleanlooks, motif, plastique, qgtk. FINISHED! Just restart your machine and voila --> Qubes Manager in dark style! TheGardner schrieb am Freitag, 22. Juli 2022 um 12:39:31 UTC-4: > seems so, my dark Qubes Manager went white from 4.0 to 4.1 and I didn't > understand why and how to change, since today > > Qubes schrieb am Freitag, 22. Juli 2022 um 04:20:46 UTC-4: > >> Sven Semmler wrote: >> > This is quite easy to fix by installing qt5-qtsyleplugins in dom0 and >> > exporting QT_QPA_PLATFORMTHEME=gtk2 in /etc/environment >> > >> > --> https://github.com/QubesOS/qubes-issues/issues/7389 >> > >> >> Did the Qubes Manager implementation change from 4.0 to 4.1? I am just >> asking because i have checked my 4.0 installation and it neither has >> qt5-qtsyleplugins installed nor does it have an environment variable >> configured for it. >> >> It is just really odd that this would be needed now when it wasn't >> needed in the past. It sounds not right having to install software in >> dom0, something we guard against, just to get Qubes Manager to honor >> dark theme settings. >> >> Isn't Qubes Manager a GTK application? The qt5-qtsyleplugins and the >> corresponding environment variable should only be necessary for Qt (KDE) >> style applications. >> >> >> -- 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/d475e772-59bd-4e50-a14d-e4de0afb56b1n%40googlegroups.com.
Re: [qubes-users] Qubes Manager not honoring colour scheme selection
seems so, my dark Qubes Manager went white from 4.0 to 4.1 and I didn't understand why and how to change, since today Qubes schrieb am Freitag, 22. Juli 2022 um 04:20:46 UTC-4: > Sven Semmler wrote: > > This is quite easy to fix by installing qt5-qtsyleplugins in dom0 and > > exporting QT_QPA_PLATFORMTHEME=gtk2 in /etc/environment > > > > --> https://github.com/QubesOS/qubes-issues/issues/7389 > > > > Did the Qubes Manager implementation change from 4.0 to 4.1? I am just > asking because i have checked my 4.0 installation and it neither has > qt5-qtsyleplugins installed nor does it have an environment variable > configured for it. > > It is just really odd that this would be needed now when it wasn't > needed in the past. It sounds not right having to install software in > dom0, something we guard against, just to get Qubes Manager to honor > dark theme settings. > > Isn't Qubes Manager a GTK application? The qt5-qtsyleplugins and the > corresponding environment variable should only be necessary for Qt (KDE) > style applications. > > > -- 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/9f741701-4b4b-4703-acc9-42930722c4ban%40googlegroups.com.
Re: [qubes-users] Qubes Manager not honoring colour scheme selection
Ahh, thanks for that info! Wondered the last couple of month, if QubesOS team would fix that one any day in the future. No I can help myself... Cheers :) sv...@svensemmler.org schrieb am Freitag, 22. Juli 2022 um 00:59:06 UTC+2: > This is quite easy to fix by installing qt5-qtsyleplugins in dom0 and > exporting QT_QPA_PLATFORMTHEME=gtk2 in /etc/environment > > --> https://github.com/QubesOS/qubes-issues/issues/7389 > -- 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/2b34dfef-5aa6-423b-b3a4-9ac35dfbd2afn%40googlegroups.com.
[qubes-users] HCL report (2 machines)
Hi Sven, hier mal der report von meinen beiden Geräten. Beide über 'in-place-upgrade' nach 4.1 gehoben. (keine Auffälligkeiten) Grüße Steffen -- 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/9a09b67f-9507-06b7-7f2e-3f540ac4dbaf%40riseup.net. Qubes-HCL-LENOVO-20EQS12Q35-20220209-105959.yml Description: application/yaml Qubes-HCL-Nitrokey-NitroPC-20220209-171359.yml Description: application/yaml OpenPGP_0xB2C4A62318012DD4.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
[qubes-users] Re: Qubes OS 4.1-rc3 has been released!
If you want to get the lastest version, just install/upgrade to 4.1rc3. This version is already working for most of the things and I'm sure, it will work for your daily things also. I wouldn't bother with 4.0.4 any more at this point of stage. Scat schrieb am Dienstag, 28. Dezember 2021 um 22:48:56 UTC-5: > Long time Qubes user...I just bought an upgraded laptop from what I have > been using. I'd like to get the latest Qubes version and this release has a > lot of appeal, however I am not sure I am competent enough to provide > valuable feedback on this latest RC. > > Should I install the RC or version 4.0.4? I would like to build this > properly to start on my upgraded laptop... > > I have been able to handle making new templates as febora and debian > versions go end of lifeso no problem there. > Any advice appreciated! > > Sincerely, > > (PS Just donated before year end to the Qubes project...keep going > developers and community! You do great stuff!) > > On Wednesday, December 22, 2021 at 3:23:22 AM UTC-6 a...@qubes-os.org > wrote: > >> Dear Qubes Community, >> >> The third release candidate for Qubes 4.1 is here! There are no major >> changes to report. We've just focused on fixing bugs that were >> discovered and reported in the second release candidate. >> >> If you're currently using any Qubes 4.1 release candidate, a regular >> update [01] is sufficient to upgrade to the latest one. Otherwise, >> read on for more about how to get started with testing Qubes 4.1-rc3. >> >> >> What's new in Qubes 4.1? >> >> >> In case you still haven't heard, Qubes 4.1 includes several major new >> features, each of which is explained in depth in its own article: >> >> - Qubes Architecture Next Steps: The GUI Domain [02] >> - Qubes Architecture Next Steps: The New Qrexec Policy System [03] >> - New Gentoo templates and maintenance infrastructure [04] >> - Reproducible builds for Debian: a big step forward [05] >> >> There are also numerous other improvements and bug fixes listed in >> the release notes [06] and in the issue tracker [07]. >> >> Finally, Qubes 4.1 features the following updated default components: >> >> - Xen 4.14 >> - Fedora 32 in dom0 >> - Fedora 34 template >> - Debian 11 template >> - Whonix 16 Gateway and Workstation templates >> - Linux kernel 5.10 >> >> >> How to test Qubes 4.1-rc3 >> - >> >> If you're willing to test [08] this release candidate, you can help to >> improve the stable release by reporting any bugs you encounter [09]. >> Experienced users are strongly encouraged to join the testing team [10]! >> >> How to migrate to 4.1-rc3: >> >> - If you're already on any 4.1 release candidate, simply perform a >> normal update [01]. >> - If you're not on a 4.1 release candidate yet, you have two options: >> 1. Back up [11] your current installation, download [12] 4.1-rc3, >> perform a fresh install [13], then restore [14] from your backup. >> 2. Perform an in-place upgrade [15]. >> >> >> Release candidate planning >> -- >> >> With each new release candidate, Qubes 4.1 becomes more and more stable >> as our testers report more bugs, and our developers fix them. As >> explained in our general release schedule [16], this cycle will continue >> until no major bugs are discovered, at which point the last release >> candidate will be declared the stable 4.1 release. Until then, we plan >> to have new release candidates approximately every five weeks. >> >> >> [01] https://www.qubes-os.org/doc/how-to-update/ >> [02] https://www.qubes-os.org/news/2020/03/18/gui-domain/ >> [03] https://www.qubes-os.org/news/2020/06/22/new-qrexec-policy-system/ >> [04] >> >> https://www.qubes-os.org/news/2020/10/05/new-gentoo-templates-and-maintenance-infrastructure/ >> >> [05] >> >> https://www.qubes-os.org/news/2021/10/08/reproducible-builds-for-debian-a-big-step-forward/ >> >> [06] https://www.qubes-os.org/doc/releases/4.1/release-notes/ >> [07] >> >> https://github.com/QubesOS/qubes-issues/issues?q=milestone%3A%22Release+4.1%22+is%3Aclosed+-label%3A%22R%3A+duplicate%22+-label%3A%22R%3A+invalid%22+-label%3A%22R%3A+cannot+reproduce%22+-label%3A%22R%3A+not+an+issue%22+-label%3A%22R%3A+not+our+bug%22+-label%3A%22R%3A+won%27t+do%22+-label%3A%22R%3A+won%27t+fix%22+ >> >> [08] https://www.qubes-os.org/doc/testing/ >> [09] https://www.qubes-os.org/doc/issue-tracking/ >> [10] https://forum.qubes-os.org/t/joining-the-testing-team/5190 >> [11] >> >> https://www.qubes-os.org/doc/how-to-back-up-restore-and-migrate/#creating-a-backup >> >> [12] https://www.qubes-os.org/downloads/ >> [13] https://www.qubes-os.org/doc/installation-guide/ >> [14] >> >> https://www.qubes-os.org/doc/how-to-back-up-restore-and-migrate/#restoring-from-a-backup >> >> [15] https://www.qubes-os.org/doc/upgrade/4.1/ >> [16] https://www.qubes-os.org/doc/version-scheme/#release-schedule >> >> This
Re: [qubes-users] Re: sys-net dispVM forgetting wifi passwords
I'm fine with. I also can plugin a cable, having a wired connection, to save me from inserting wifi passwords. And as long as I'll using the wifi connection, I don't have any trouble in setting up the wifi password again and again. But seems, others can't understand, why they always have to do this by running sys-net on a dispVM. taran1s schrieb am Freitag, 3. Dezember 2021 um 08:40:09 UTC-5: > > > TheGardner: > > Mentioned already here and there. Thats one of the cons using a dispVM > for > > the sys-qubes. > > Next one is - you can't "restart"... > > > > r...@abtion.com schrieb am Donnerstag, 2. Dezember 2021 um 04:00:32 > UTC-5: > > > >> I have installed 4.1rc2 and chose a disposable sys-net, because I could > >> think of a reason not to. > >> But now that I have to type in the wifi password again and again, I > know a > >> reason to not choose dispVM for sys-net. > >> > >> Maybe it should be mentioned in the installation process what > consequences > >> it will have to choose disposable for sys-net? > >> > >> > > > > It should be just easy to use your offline debian-11 vault to save the > wifi passwords and insert it once you connect to a particular wifi. > > There is of course an advantage for your anti tracking setup (together > with other ones). So in this case if your sys-net gets compromised > (unlikely but still possible), an adversary could see all your stored > wifi connections which can give him unneeded advantage. This doesnt > happen with disp sys-net. > > The question is: What makes you more happy? Connect to the wifi > handsfree and possibly give out your wifi history intelligence to an > unknown parties, or you are more happy to insert the password from the > offline vault manually and be more safe? > -- 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/c3f6f087-56c8-442a-9e17-6cde2d913487n%40googlegroups.com.
[qubes-users] Re: sys-net dispVM forgetting wifi passwords
Mentioned already here and there. Thats one of the cons using a dispVM for the sys-qubes. Next one is - you can't "restart"... r...@abtion.com schrieb am Donnerstag, 2. Dezember 2021 um 04:00:32 UTC-5: > I have installed 4.1rc2 and chose a disposable sys-net, because I could > think of a reason not to. > But now that I have to type in the wifi password again and again, I know a > reason to not choose dispVM for sys-net. > > Maybe it should be mentioned in the installation process what consequences > it will have to choose disposable for sys-net? > > -- 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/a72447d1-ded4-4a00-9d02-5da37f43e207n%40googlegroups.com.
Re: [qubes-users] Qubes Update does not work for Whonix 16 templates ...
managed the download on 4.0.4 in the last days without any issues. Just did it with the qubes-dom0-update command and the enablerepo=community switch. No other commands or work. It just went through like it always do with downloads & installs of new templates. Sorry, if I couldn't help more. viktor@gmail.com schrieb am Dienstag, 9. November 2021 um 14:49:04 UTC-5: > Viktor Ransmayr schrieb am Sonntag, 7. November 2021 um 19:53:54 UTC+1: > >> 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? >> > > Any recommendation from someone in the community? > > 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/60475ee5-267b-4944-83b8-968cae637c1an%40googlegroups.com.
Re: [qubes-users] Updating Signal desktop
no real clue. would try to remove it again and install it new. or at least clone the current template (or reinstall it from scratch) and install signal-desktop there again. s.a.r...@gmail.com schrieb am Dienstag, 9. November 2021 um 05:30:39 UTC-5: > Thanks for testing that. > > Any idea on how can I debug it? > > > On 11/9/21 1:37 AM, TheGardner wrote: > > same on 4.0.4... no problems during install and tool opens w/o any error. > Workin' ! > Sorry, somethings seems to be wrong on your template/AppVM. > > TheGardner schrieb am Dienstag, 9. November 2021 um 01:06:08 UTC+1: > >> Don't think so. Would rather believe this happens to 4.1 more, than on >> 4.0.4 >> 4.1 still is under development... But can test an install on my 4.0.4 >> device. Let's see how this will look like. >> Keep you informed... >> >> Cheers Steffen >> s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:20:18 UTC-5: >> >>> I am running 4.0(R4.0). >>> >>> Do you think this might be the issue? >>> >>> >>> On 11/8/21 7:56 PM, TheGardner wrote: >>> >>> Strange. >>> Tested it on my 4.0.4 device and it's working like a charm. >>> >>> s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 18:56:35 >>> UTC+1: >>> >>>> That's what I did. >>>> >>>> >>>> I tried to removed Signal and install it one more time and still I have >>>> getting the same error message. >>>> >>>> >>>> On 11/8/21 5:26 PM, TheGardner wrote: >>>> >>>> Have you tried to get it from the copr repository? You should do this >>>> via: >>>> >>>> *sudo dnf copr enable luminoso/Signal-Desktop* >>>> >>>> and your (already) used command >>>> >>>> *sudo dnf install signal-deaktop* >>>> >>>> s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:38:33 >>>> UTC+1: >>>> >>>>> I ran this command on my Fedora template: >>>>> >>>>> sudo dnf install signal-deaktop >>>>> >>>>> It was working until signal release an update and after that i am not >>>>> able to use it. >>>>> >>>>> >>>>> On Mon, Nov 8, 2021, 10:31 AM Sven Semmler >>>>> wrote: >>>>> >>>>>> On 11/8/21 06:47, S.A.Rashidi wrote: >>>>>> > No, I am using a Fedora template. >>>>>> >>>>>> Than you installed it how? Using snap? >>>>>> >>>>>> Please make sure you reply to the list. >>>>>> >>>>>> /Sven >>>>>> >>>>>> -- >>>>>> public key: https://www.svensemmler.org/2A632C537D744BC7.asc >>>>>> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 >>>>>> >>>>> -- >>>> 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...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com?utm_medium=email_source=footer> >>>> . >>>> >>>> -- >>>> Amir Rashidi >>>> Signal: +1(202)560-3853 <(202)%20560-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...@googlegroups.com. >>> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/qubes-users/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/qubes-users/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> >>> -- >>> Amir Rashidi >>> Signal: +1(202)560-3853 <(202)%20560-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...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/1fa34ef5-a5d3-4c26-9a15-2a2dffc8683en%40googlegroups.com > > <https://groups.google.com/d/msgid/qubes-users/1fa34ef5-a5d3-4c26-9a15-2a2dffc8683en%40googlegroups.com?utm_medium=email_source=footer> > . > > -- > Amir Rashidi > Signal: +1(202)560-3853 <(202)%20560-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/3faede8b-4bf6-4981-b345-e504eff87b37n%40googlegroups.com.
Re: [qubes-users] Updating Signal desktop
same on 4.0.4... no problems during install and tool opens w/o any error. Workin' ! Sorry, somethings seems to be wrong on your template/AppVM. TheGardner schrieb am Dienstag, 9. November 2021 um 01:06:08 UTC+1: > Don't think so. Would rather believe this happens to 4.1 more, than on > 4.0.4 > 4.1 still is under development... But can test an install on my 4.0.4 > device. Let's see how this will look like. > Keep you informed... > > Cheers Steffen > s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:20:18 UTC-5: > >> I am running 4.0(R4.0). >> >> Do you think this might be the issue? >> >> >> On 11/8/21 7:56 PM, TheGardner wrote: >> >> Strange. >> Tested it on my 4.0.4 device and it's working like a charm. >> >> s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 18:56:35 UTC+1: >> >>> That's what I did. >>> >>> >>> I tried to removed Signal and install it one more time and still I have >>> getting the same error message. >>> >>> >>> On 11/8/21 5:26 PM, TheGardner wrote: >>> >>> Have you tried to get it from the copr repository? You should do this >>> via: >>> >>> *sudo dnf copr enable luminoso/Signal-Desktop* >>> >>> and your (already) used command >>> >>> *sudo dnf install signal-deaktop* >>> >>> s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:38:33 >>> UTC+1: >>> >>>> I ran this command on my Fedora template: >>>> >>>> sudo dnf install signal-deaktop >>>> >>>> It was working until signal release an update and after that i am not >>>> able to use it. >>>> >>>> >>>> On Mon, Nov 8, 2021, 10:31 AM Sven Semmler >>>> wrote: >>>> >>>>> On 11/8/21 06:47, S.A.Rashidi wrote: >>>>> > No, I am using a Fedora template. >>>>> >>>>> Than you installed it how? Using snap? >>>>> >>>>> Please make sure you reply to the list. >>>>> >>>>> /Sven >>>>> >>>>> -- >>>>> public key: https://www.svensemmler.org/2A632C537D744BC7.asc >>>>> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 >>>>> >>>> -- >>> 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...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com?utm_medium=email_source=footer> >>> . >>> >>> -- >>> Amir Rashidi >>> Signal: +1(202)560-3853 <(202)%20560-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...@googlegroups.com. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/qubes-users/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/qubes-users/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com?utm_medium=email_source=footer> >> . >> >> -- >> Amir Rashidi >> Signal: +1(202)560-3853 <(202)%20560-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/1fa34ef5-a5d3-4c26-9a15-2a2dffc8683en%40googlegroups.com.
Re: [qubes-users] Updating Signal desktop
Don't think so. Would rather believe this happens to 4.1 more, than on 4.0.4 4.1 still is under development... But can test an install on my 4.0.4 device. Let's see how this will look like. Keep you informed... Cheers Steffen s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:20:18 UTC-5: > I am running 4.0(R4.0). > > Do you think this might be the issue? > > > On 11/8/21 7:56 PM, TheGardner wrote: > > Strange. > Tested it on my 4.0.4 device and it's working like a charm. > > s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 18:56:35 UTC+1: > >> That's what I did. >> >> >> I tried to removed Signal and install it one more time and still I have >> getting the same error message. >> >> >> On 11/8/21 5:26 PM, TheGardner wrote: >> >> Have you tried to get it from the copr repository? You should do this via: >> >> *sudo dnf copr enable luminoso/Signal-Desktop* >> >> and your (already) used command >> >> *sudo dnf install signal-deaktop* >> >> s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:38:33 UTC+1: >> >>> I ran this command on my Fedora template: >>> >>> sudo dnf install signal-deaktop >>> >>> It was working until signal release an update and after that i am not >>> able to use it. >>> >>> >>> On Mon, Nov 8, 2021, 10:31 AM Sven Semmler >>> wrote: >>> >>>> On 11/8/21 06:47, S.A.Rashidi wrote: >>>> > No, I am using a Fedora template. >>>> >>>> Than you installed it how? Using snap? >>>> >>>> Please make sure you reply to the list. >>>> >>>> /Sven >>>> >>>> -- >>>> public key: https://www.svensemmler.org/2A632C537D744BC7.asc >>>> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 >>>> >>> -- >> 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...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com?utm_medium=email_source=footer> >> . >> >> -- >> Amir Rashidi >> Signal: +1(202)560-3853 <(202)%20560-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...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com > > <https://groups.google.com/d/msgid/qubes-users/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com?utm_medium=email_source=footer> > . > > -- > Amir Rashidi > Signal: +1(202)560-3853 <(202)%20560-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/ffe6324d-de74-4d14-9fd6-125f6d90fd9cn%40googlegroups.com.
Re: [qubes-users] Updating Signal desktop
Strange. Tested it on my 4.0.4 device and it's working like a charm. s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 18:56:35 UTC+1: > That's what I did. > > > I tried to removed Signal and install it one more time and still I have > getting the same error message. > > > On 11/8/21 5:26 PM, TheGardner wrote: > > Have you tried to get it from the copr repository? You should do this via: > > *sudo dnf copr enable luminoso/Signal-Desktop* > > and your (already) used command > > *sudo dnf install signal-deaktop* > > s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:38:33 UTC+1: > >> I ran this command on my Fedora template: >> >> sudo dnf install signal-deaktop >> >> It was working until signal release an update and after that i am not >> able to use it. >> >> >> On Mon, Nov 8, 2021, 10:31 AM Sven Semmler wrote: >> >>> On 11/8/21 06:47, S.A.Rashidi wrote: >>> > No, I am using a Fedora template. >>> >>> Than you installed it how? Using snap? >>> >>> Please make sure you reply to the list. >>> >>> /Sven >>> >>> -- >>> public key: https://www.svensemmler.org/2A632C537D744BC7.asc >>> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 >>> >> -- > 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...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com > > <https://groups.google.com/d/msgid/qubes-users/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com?utm_medium=email_source=footer> > . > > -- > Amir Rashidi > Signal: +1(202)560-3853 <(202)%20560-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/7277080d-a56b-4e17-bfa4-d8723f8992a7n%40googlegroups.com.
Re: [qubes-users] Updating Signal desktop
Have you tried to get it from the copr repository? You should do this via: *sudo dnf copr enable luminoso/Signal-Desktop* and your (already) used command *sudo dnf install signal-deaktop* s.a.r...@gmail.com schrieb am Montag, 8. November 2021 um 16:38:33 UTC+1: > I ran this command on my Fedora template: > > sudo dnf install signal-deaktop > > It was working until signal release an update and after that i am not able > to use it. > > > On Mon, Nov 8, 2021, 10:31 AM Sven Semmler wrote: > >> On 11/8/21 06:47, S.A.Rashidi wrote: >> > No, I am using a Fedora template. >> >> Than you installed it how? Using snap? >> >> Please make sure you reply to the list. >> >> /Sven >> >> -- >> public key: https://www.svensemmler.org/2A632C537D744BC7.asc >> fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 >> > -- 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/64d720a5-9ae6-45bb-b83a-b669f334e75bn%40googlegroups.com.
[qubes-users] Re: Q: Upgrading whonix-ws, auto-remove packages?
always use 'sudo apt autoremove' afterwards and never run into problems. So you probably can follow, what the upgrade function told you. Cheers :) Ulrich Windl schrieb am Dienstag, 5. Oktober 2021 um 23:53:02 UTC+2: > Hi! > > Following the instructions, my upgrade ended with this message: > The following packages were automatically installed and are no longer > required: > acl anon-iceweasel-warning apt-file binaries-freedom bsdmainutils bsdtar > command-not-found cpp-8 curl-scripts dctrl-tools dkms firejail > firejail-profiles firetools fonts-droid-fallback fonts-noto-mono > gpl-sources-download grub2-common initramfs-tools initramfs-tools-core > klibc-utils libapt-pkg-perl libasan5 libavdevice58 libavfilter7 > libbasicusageenvironment1 libbind9-161 libboost-iostreams1.67.0 > libboost-system1.67.0 libbotan-2-9 libc-ares2 libcdio-cdda2 > libcdio-paranoia2 libcdio18 libcdio19 libcodec2-0.8.1 libcroco3 > libcrypto++6 > libcrystalhd3 libcupsfilters1 libcupsimage2 libcwidget3v5 libdc1394-22 > libdns1104 libdns1110 libdouble-conversion1 libdvdread4 libebml4v5 > libegl1-mesa libenchant1c2a libev4 libevent-2.1-6 libexo-1-0 > libexo-helpers > libexporter-tiny-perl libfluidsynth1 libgroupsock8 libgs9 libgs9-common > libgssdp-1.0-3 libgupnp-1.0-4 libhavege1 libicu63 libijs-0.35 > libilmbase23 > libirs161 libisc1100 libisc1105 libisccc161 libisccfg163 libisl19 > libjsoncpp1 libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libklibc > liblist-moreutils-perl liblist-moreutils-xs-perl liblivemedia64 libllvm7 > liblwres161 libmatroska6v5 libmicrodns0 libmpdec2 libmpx2 libmysofa0 > libnfs12 libopenexr23 libperl5.28 libpgm-5.2-0 libpipewire-0.2-1 > libplacebo7 > libpocketsphinx3 libpoppler82 libpotrace0 libprotobuf-lite17 libpython2.7 > libpython3.7 libpython3.7-minimal libpython3.7-stdlib libreadline7 > libregexp-assemble-perl librubberband2 libsphinxbase3 libsqlcipher0 > libtoxcore2 libusageenvironment3 libvidstab1.1 libvpx5 libx264-155 > libx265-165 libxcb-util0 libxdot4 linux-base onionshare perl-modules-5.28 > python-apt-common python-pkg-resources python3-apt python3-asn1crypto > python3-flask python3-flask-httpauth python3-gevent python3-greenlet > python3-guimessages python3-itsdangerous python3-jinja2 > python3-markupsafe > python3-psutil python3-pycryptodome python3-simplegeneric > python3-werkzeug > python3-zope.event python3.7-minimal qtox > qubes-core-agent-passwordless-root > qubes-core-agent-thunar qubes-input-proxy-sender qubes-kernel-vm-support > qubes-usb-proxy rsyslog scurl telnet tor-ctrl usb.ids usbutils vim-common > vim-tiny virt-what > Use 'sudo apt autoremove' to remove them. > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > + true 'INFO: Setting a list of traditional dummy packages to automatically > installed so these can be removed the next time the user runs apt > autoremove.' > + apt-mark auto e2fslibs gnupg2 libcomerr2 mime-support > libgdk-pixbuf2.0-0 libiptc0 cryptsetup-run > + true 'INFO: Running sanity test...' > + dpkg-noninteractive --audit > + true 'INFO: Running sanity test...' > + dpkg-noninteractive --configure -a > + true 'INFO: Restart whonix-legacy service...' > + service whonix-legacy restart > + true 'INFO: Running sanity test...' > + dpkg-noninteractive --audit > + true 'INFO: Running sanity test...' > + dpkg-noninteractive --configure -a > + true 'INFO: OK. (release-upgrade version: 1.4) Release upgrade success.' > user@host:~$ > > > I'm wondering whether those qubes packages may actually be removed. > I'm afraid to break my system when doing so. > > Regards, > Ulrich > -- 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/901a4af4-c08a-4bc6-9320-6890ec70e1b0n%40googlegroups.com.
Re: [qubes-users] Dual booting different Qubes versions on same machine
Already was thinking about this too... Have both OSes on two different SSDs. 4.1 on a 1TB m.2 card (slot 1) and 4.0.4 on a 512 GB m.2 card (slot 2). 4.1 was installed on the P50 while th 4.0.4 version was plugged out. After 4.0.4 was plugged in again, both cards can be shown in BIOS but 4.1 is booting with it's boot screen cause it actually isn't aware of the second m.2 card, which should be quiet normal. GRUB have to be edited. unman schrieb am Dienstag, 22. Juni 2021 um 07:07:01 UTC-4: > On Tue, Jun 22, 2021 at 10:29:54AM +0100, River~~ wrote: > > Hi all, > > > > I noticed the new "alpha" level isos in the downloads and feel > > motivated to help testing it. > > > > I obviously do not want to go over to alpha for my normal work, but > > would be interested if I can install it alongside my existing current > > release. That way I would be testing that it works on the exact > > hardware that I would eventually be running it on when it reaches > > production quality. > > > > Do I proceed as for the instructions for installing Qubes as a second > > boot option to Linux? If not, what would be different? > > > > What additional risks might I introduce by running a development > > version of Qubes on the same physical machine as the production > > version? > > > > Obviously I would not have any files/partitions shared apart from the > > EFI partition. > > > > Would it make sense to install it onto an EFI partition on a different > > internal disk? Would it be better for any reason to install it onto a > > USB drive? (my guess to both of these is no, because when the test > > system is running the production system would be on the host even if > > not mounted) > > > > My current production version is R4.0.3 and I will shortly be > > replacing it with R4.0.4. At the time of writing the current alpha is > > R4.1.0 but that my (or may not) change by the time I get around to > > installing it. > > > > I thought I would dual boot the new R4.0.4 with the existing R4.0.3, > > then once R4.0.4 is verified as working for me I would transfer the > > user level files and then overwrite the older production version with > > the alpha test version. Anyone who can think why that might be a bad > > idea please speak now or forever hold your peace (as they say in > > English weddings) > > > > I did a google search for "dual boot qubes versions site:qubes-os.org" > > but it only pointed me to info about dual booting with non-Qubes > > systems. > > > > Once successful, would ppl welcome my spending time adding a section > > to the dual boot online documentation? I would be happy to do so if > > just one person thinks it might be useful > > > > WArmly > > River~~ > > With classic GRUB it's straightforward, and (imo) doesn't warrant new > docs. > I cant help with UEFI at all, and that probably *does*. > > That said, you would be running alpha software alongside your main > system. Having separate encrypted drives/partitions will undoubtedly aid > separation, but it's still a risk, and not something I would advocate if > you value your data. > If it's possible for you to swap out your drives, and have a separate > 4.1 drive, I would recommend that instead. > -- 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/5648120e-32fe-435f-8a93-a06cc62fd20en%40googlegroups.com.
[qubes-users] Re: Is swap necessary?
For me, it would be necessary, if you're running Qubes with 4-8GB of RAM. But with 16,32 or even 64 GB of RAM a swap partition may be useless... abra...@protonmail.com schrieb am Mittwoch, 19. Mai 2021 um 10:28:48 UTC+2: > The Qubes installer says swap is important. I did a Google search and it > turned out that Qubes hardly even uses swap. Specifically, I found this: > https://www.reddit.com/r/Qubes/comments/86evqe/swap_is_useless_on_qubes/dz32iof/?context=8=9 > > Is it at all important to install Qubes with a swap partition? Currently I > have it running without swap. > > > Sent with ProtonMail Secure Email. > > > -- 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/10e71535-cb7b-4a84-b345-b2494da020c1n%40googlegroups.com.
Re: [qubes-users] Disposable VMs starting with a QubesIncoming folder
Thanks for the help, but a start of the template wouldn't help, cause the /QubesIncoming folder wasn't build there. It was build in a dvm-VM. But found a way now. You have to start the dvm-VM via Qubes Manager and have to start a terminal via rightclick on the Q symbol in the info bar > dvm-Qube > Run Terminal. David Hobach schrieb am Samstag, 1. Mai 2021 um 13:43:56 UTC+2: > > Just start the template VM and remove the ~/QubesIncoming folder. > > -- 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/e80d336d-5729-4e35-8ada-82cb44cbaf50n%40googlegroups.com.
[qubes-users] Disposable VMs starting with a QubesIncoming folder
Since several days all my disposable VMs starting with a QubesIncoming folder (w/a personal folder and three files inside). Guess I accidentially moved these files to whonix- ws-15-dvm during a previous Move-to-vm command. Question now is: how can someone remove these files and clear the -dvm VM again? Is this somethings to be done in dom0? Cheers & Thanks for any ideas Steffen -- 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/dbbf7668-10da-4a48-94ea-cc194f595a93n%40googlegroups.com.
[qubes-users] Re: Can't get Debian-11 template updated
After Debian-11 isn't supported yet under Qubes and so I didn't took a deeper look into this. Still on Debian-10 and the Debial-11 qube was deleted right after awokd's post. Sorry, can't help here. peter.p...@gmail.com schrieb am Freitag, 30. April 2021 um 09:59:44 UTC+2: > On Monday, August 10, 2020 at 6:00:21 PM UTC+2 TheGardner wrote: > >> I recently got some templates (bullseye, kali and Debian-11) installed on >> my system, but I can't get them updated. So speaking first about Denian-11, >> I always get the following message, when I try to update the qube via >> "Update Qube" function: >> >> >> >> *Failed to apply DSA-4371 fix: dpkg-query: package 'libapt-pkg5.0' is not >> installed and no information is availableUse dpkg --info (= dpkg-deb >> --info) to examine archive files.* >> *Error: Failed to get apt version.* >> >> Anyone, who could point me to the next steps to get this working? dpkg >> --info and/or dpkg-deb --info didn't help to find out, whats wrong here. >> >> btw. a 'sudo qubes-dom0-update qubes-template-debian-11' always brings up >> a 'No match for argument qubes-template-debian-11' altough my Debian11 >> template is called Debian-11 >> >> Thanks & Cheers >> Steffen >> > > Did you fix it? > > I can update my Debian-11 template by clicking on the update arrow in > qubes manager, but not via the tray icon. It executes: > > [user@dom0 ~]$ sudo qubesctl --skip-dom0 --targets=debian-11 --show-output > state.sls update.qubes-vm > debian-11: > -- > _error: > Failed to return clean data > retcode: > 1 > stderr: > Traceback (most recent call last): > File "/var/tmp/.root_dd8a91_salt/salt-call", line 27, in > > salt_call() > File "/var/tmp/.root_dd8a91_salt/pyall/salt/scripts.py", line > 445, in salt_call > client.run() > File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/call.py", line > 48, in run > caller = salt.cli.caller.Caller.factory(self.config) > File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/caller.py", > line 64, in factory > return ZeroMQCaller(opts, **kwargs) > File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/caller.py", > line 329, in __init__ > super(ZeroMQCaller, self).__init__(opts) > File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/caller.py", > line 89, in __init__ > self.minion = salt.minion.SMinion(opts) > File "/var/tmp/.root_dd8a91_salt/pyall/salt/minion.py", line > 912, in __init__ > opts["grains"] = salt.loader.grains(opts) > File "/var/tmp/.root_dd8a91_salt/pyall/salt/loader.py", line > 825, in grains > ret = funcs[key]() > File "/var/tmp/.root_dd8a91_salt/pyall/salt/grains/core.py", > line 2384, in ip_fqdn > ret["ipv6"] = > salt.utils.network.ip_addrs6(include_loopback=True) > File "/var/tmp/.root_dd8a91_salt/pyall/salt/utils/network.py", > line 1353, in ip_addrs6 > return _ip_addrs(interface, include_loopback, > interface_data, "inet6") > File "/var/tmp/.root_dd8a91_salt/pyall/salt/utils/network.py", > line 1333, in _ip_addrs > ret.add(addr) > File "/usr/lib/python3.9/ipaddress.py", line 1920, in __hash__ > return hash((self._ip, self._scope_id)) > AttributeError: _scope_id > stdout: > [user@dom0 ~]$ > > and fails... > > Any idea? > > -- 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/ba1316c1-a24b-4135-84fc-30bdcab4e3cfn%40googlegroups.com.
[qubes-users] Re: installing Trezor wallet on qubes
what about creating the folder qubes-rpc with sudo mkdir qubes-rpc and a 'cd qubes-rpc' followed by vi trezord-service and insert the 'socat...' line there, followed with a saving of the file finally. Alaa Ashkar schrieb am Samstag, 6. Februar 2021 um 16:51:02 UTC+1: > Hi, > > I am trying to follow the instructions described at the following link: > https://wiki.trezor.io/Qubes_OS > in order to install and use Trezor HW wallet on my qubes. > > in my qubes i have 2 users, the normal one and a root user. > > i have succeeded to run the first instructions part (dom0). > but i failed to run the sys-usb part, it says: > > *in sys-usb:* > > sudo vim /usr/local/etc/qubes-rpc/trezord-service > > add this line: > socat - TCP:localhost:21325 > > but i couldnt find the path /usr/local/etc/qubes-rpc/ in sys-usb (in > terminal), so i couldnt create the file and add the line into it, i tried > both in the root and the normal user. > > can you please help? i am new to qubes, sorry for any inconvenience. > -- 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/1c92185e-394f-4c83-8515-818d5bdbabccn%40googlegroups.com.
Re: [qubes-users] Qubes updater icon never gets cleared
Worked for me! Update sign is gone at the taskbar. Thanks a bunch Victor. Here's my output: [user@fedora-32 ~]$ sudo dnf update --best --allowerasing Last metadata expiration check: 0:11:37 ago on Sat Dec 5 20:32:06 2020. Dependencies resolved. === Package Arch Version Repository Size === Upgrading: pulseaudio x86_64 14.0-1.fc32 updates1.0 M pulseaudio-libs x86_64 14.0-1.fc32 updates690 k pulseaudio-libs-glib2 x86_64 14.0-1.fc32 updates 18 k pulseaudio-module-bluetooth x86_64 14.0-1.fc32 updates 78 k pulseaudio-module-x11 x86_64 14.0-1.fc32 updates 31 k pulseaudio-utilsx86_64 14.0-1.fc32 updates 72 k Removing dependent packages: pulseaudio-qubesx86_64 4.0.31-1.fc32 @qubes-vm-r4.0-current 41 k qubes-vm-recommendednoarch 4.0.7-1.fc32 @qubes-builder-vm-r4.0-current-testing 0 Transaction Summary === Upgrade 6 Packages Remove 2 Packages Total download size: 1.9 M Is this ok [y/N]: y Downloading Packages: (1/6): pulseaudio-libs-glib2-14.0-1.fc32.x86_64.rpm 15 kB/s | 18 kB 00:01 (2/6): pulseaudio-libs-14.0-1.fc32.x86_64.rpm 331 kB/s | 690 kB 00:02 (3/6): pulseaudio-14.0-1.fc32.x86_64.rpm 421 kB/s | 1.0 MB 00:02 (4/6): pulseaudio-module-bluetooth-14.0-1.fc32.x86_64.rpm 63 kB/s | 78 kB 00:01 (5/6): pulseaudio-module-x11-14.0-1.fc32.x86_64.rpm 76 kB/s | 31 kB 00:00 (6/6): pulseaudio-utils-14.0-1.fc32.x86_64.rpm 217 kB/s | 72 kB 00:00 --- Total 431 kB/s | 1.9 MB 00:04 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading: pulseaudio-libs-14.0-1.fc32.x86_64 1/14 Running scriptlet: pulseaudio-libs-14.0-1.fc32.x86_64 1/14 Running scriptlet: pulseaudio-14.0-1.fc32.x86_64 2/14 Upgrading: pulseaudio-14.0-1.fc32.x86_64 2/14 Running scriptlet: pulseaudio-14.0-1.fc32.x86_64 2/14 Upgrading: pulseaudio-utils-14.0-1.fc32.x86_64 3/14 Upgrading: pulseaudio-module-x11-14.0-1.fc32.x86_64 4/14 Upgrading: pulseaudio-module-bluetooth-14.0-1.fc32.x86_64 5/14 Upgrading: pulseaudio-libs-glib2-14.0-1.fc32.x86_64 6/14 Cleanup : pulseaudio-module-x11-13.99.1-4.fc32.x86_64 7/14 Cleanup : pulseaudio-module-bluetooth-13.99.1-4.fc32.x86_64 8/14 Cleanup : pulseaudio-utils-13.99.1-4.fc32.x86_64 9/14 Cleanup : pulseaudio-libs-glib2-13.99.1-4.fc32.x86_64 10/14 Erasing : qubes-vm-recommended-4.0.7-1.fc32.noarch 11/14 Erasing : pulseaudio-qubes-4.0.31-1.fc32.x86_64 12/14 Running scriptlet: pulseaudio-13.99.1-4.fc32.x86_64 13/14 Cleanup : pulseaudio-13.99.1-4.fc32.x86_64 13/14 Cleanup : pulseaudio-libs-13.99.1-4.fc32.x86_64 14/14 Running
[qubes-users] Re: Qubes OS: .onion and links
What happens, if you have set "Prioritize .onion sites when known." to ALWAYS under Privacy & Security - Browser Privacy ? Cheers :) Ulrich Windl schrieb am Montag, 30. November 2020 um 21:16:31 UTC+1: > Hi! > > I noticed when I click the link "upgrading Fedora TemplateVMs" found on > the onion version of the page (using the tor browser of whonix), you are > directed to a non-onion page > (https://www.qubes-os.org/doc/template/fedora/upgrade/), and you'll have > to switch to onion again. > > In contrast when I click news items on > http://qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/news/ > I remain on onion sites. > > Regards, > Ulrich > -- 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/e6d5020b-5d5d-483f-8816-53b98ef90a0an%40googlegroups.com.
[qubes-users] Re: Resizing storage in Windows 10 StandaloneVMs
This should work like the documentation tells. But I would only change the count for "System Storage Max Size", cause Windows don't have really any use of the "Private storage...". The latter just would create/increase a second partition, which Windows usually leaves blank. Cheers Steffen Knut von Walter schrieb am Dienstag, 17. November 2020 um 11:19:33 UTC+1: > Hi, > > At the moment I am still happy with my freshly configured Windows 10 > StandaloneVM. But now I want to resize it from 30 GB to 60 GB. I have read > the documentation on, link: > https://www.qubes-os.org/doc/resize-disk-image/ . However Windows 10 > StandaloneVMs are not explicitly mentioned. Therefore to make it absolutely > sure I am asking about best practice on how to resize Windows 10 > StandaloneVMs? > > All help is appreciated. > > Thank you. > > Best Knut > -- 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/f87ae444-59dc-4438-a9eb-0e4d53c4cc28n%40googlegroups.com.
[qubes-users] Can't get Debian-11 template updated
I recently got some templates (bullseye, kali and Debian-11) installed on my system, but I can't get them updated. So speaking first about Denian-11, I always get the following message, when I try to update the qube via "Update Qube" function: *Failed to apply DSA-4371 fix: dpkg-query: package 'libapt-pkg5.0' is not installed and no information is availableUse dpkg --info (= dpkg-deb --info) to examine archive files.* *Error: Failed to get apt version.* Anyone, who could point me to the next steps to get this working? dpkg --info and/or dpkg-deb --info didn't help to find out, whats wrong here. btw. a 'sudo qubes-dom0-update qubes-template-debian-11' always brings up a 'No match for argument qubes-template-debian-11' altough my Debian11 template is called Debian-11 Thanks & Cheers Steffen -- 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/92eef065-a980-4a3a-86ff-3e9e379586e4n%40googlegroups.com.
Re: [qubes-users] Upgrading to Fedora 32...
You can! I always wait for a news on the Qbs news blog, when they announce a new template is ready (for download). Then I'll download and run it beside the old one - changing it on all VMs later VM by VM. ...and so on with the next version... Am Sonntag, 14. Juni 2020 22:41:06 UTC+2 schrieb Andrew Sullivan: > > > I'll take that as a "No" then! If I don't upgrade to Fedora 31 now, will > I beable to go straight to Fedors 32 when it's available, or can't you > "jump" a release? > > Thanks > -- 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/2a33c073-f49f-436b-b5d4-dd2b20412003o%40googlegroups.com.
[qubes-users] Re: Getting started with Qubes (in steps)
Can try to help you with screenshots or others. Whats your current status of the system? Is it started, but not connected to the net? Cheers :) Am Freitag, 12. Juni 2020 19:33:42 UTC+2 schrieb E. Foster: > > Greetings, > > I've been having a lot of difficulty over the past year with Qubes and I > wanted to know if I could get some help with the parameters, and > dependencies. > > *1 set up the network connections* > i.e. Wifi > > *2 set up sys-firewall* > > *3 set up the sys-net* > to use Wifi and Firewall > > *4 set up sys-Whonix-gw* > to use the wifi, firewall and/sys-net > > And a random DSVM that I could use to visit the net for instance. > > ***With the most general/secure parameters so that my system works. > Please be mindful, some of the automatic default settings might have > changed while I was tinkering with the Qubes OS. > > In the past I worked on making clones but due to the dependencies I can't > delete/fix some of the VMs. > > *Question:* > > Would you know if this is the proper sequence of setting to set up a Qubes > system with the respective dependencies? > > *and...* > > Or perhaps, a hyperlink to a post where I could copy the commands or steps > to get these basic VM/services and my system working-online. > > Once, secured and connected, I can update all the applications included in > the Qubes full install version. > > Please forgive me, if I am not posting in sequence in other topical > threads. > > Thanks, > -- 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/37663ed0-7369-4dda-96a5-72232df1ae43o%40googlegroups.com.
[qubes-users] Re: Replacing SSD with larger SSD on Qubes System
Did this in the past with a - clon of the entire (smaller) in Tails - Drives on a extern backup dive - replace the old drive with the new one - and extend the written partition later up to 1TB A fresh install is also a way. Just backup all your VMs and restore them later on the new system. I -for myself- would do such a new install / rename all new and fresh vms to somewhat "original-x" and then restore the backup. So you have your old system beside fresh installed original cubes from a actual Qbs installation. Am Samstag, 6. Juni 2020 21:27:32 UTC+2 schrieb Verifiable List: > > Hello All, > > I'm a long-time user of Qubes. I'm upgrading my laptop from a 256GB SSD > to a 1TB SSD. I wanted to check whether it is preferable to clone the > existing drive to the new one and expand the volumes, or whether I > should do a fresh Qubes install on the new drive and restore from > backup. I've not had great luck with Qubes' restore process in the past, > but it's been a long time since I've needed to use it. Also, if the > fresh install/restore method is preferable, should I install Qubes with > the "Do not configure anything" option checked so that none of the > default VMs are created? > > Thanks. > -- 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/6e032ee9-bdaf-4fc4-9668-b0c5b7e091dao%40googlegroups.com.
Re: [EXT] [qubes-users] Libreoffice window sized tiny every time
This issue is in Fedora-32 too. There isn't currently a workaround, but from what I read in the last weeks, they're on it to fix that. Am Freitag, 5. Juni 2020 23:18:16 UTC+2 schrieb Ulrich Windl: > > On 5/22/20 12:05 PM, qtpie wrote: > > Anyone else having this issue or know a solution? > > > > -- 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/e9a4a026-1339-4627-98ab-09855df14854o%40googlegroups.com.
Re: [qubes-users] Re: Updating sys-usb template
Hi unman, you mean, those crashes didn't happen on Fedora-31 ? Cheers :) Am Dienstag, 2. Juni 2020 01:38:42 UTC+2 schrieb unman: > > > And *that* is exactly why I suggest testing first with an automatic roll > back to use the original 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/a9f7e0df-2ed1-438e-a52f-5d1ee74bbae7%40googlegroups.com.
[qubes-users] Re: Updating sys-usb template
Always using for updates of sys-usb the following commands in Terminal in dom0: Just a restart: qvm-shutdown --wait sys-usb; qvm-start sys-usb A change of the (already installed) new template, when all other vms already working with this new template: qvm-shutdown --wait sys-usb; qvm-prefs -s sys-usb template ; qvm-start sys-usb So for an update to Fedora-32 it would work with: qvm-shutdown --wait sys-usb; qvm-prefs -s sys-usb template fedora-32; qvm-start sys-usb Sometimes it crash and the cube won't starting proper again, so I have to turn the machine off and start new, but in 80% of the cases it's working this way. The changes definitely are done in all cases, so you will run your sys-usb with the new Ttemplate then. Cheers Steffen :) Am Donnerstag, 28. Mai 2020 20:34:40 UTC+2 schrieb Zbigniew Łukasiak: > > My sys-usb uses a very old template. I tried some googling - but > failed to find any advice about update it without locking me out of > the system. > I guess I could remove it - there is a description on how to do that > in https://www.qubes-os.org/doc/usb-qubes/ - and then add it again > with a new template. But it is kind of complicated and looks > dangerous. > > -- > Zbigniew Lukasiak > https://medium.com/@zby > http://brudnopis.blogspot.com/ > -- 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/459b0f06-41f9-44b6-9489-f2b900d6fa32%40googlegroups.com.
Re: [qubes-users] Re: Install of the Fedora-32 templateVM failed
understood. Guess I have to do some backups, which I have to move to my NAS. The new machine will take two months longer. Have to come out with the current space until then. Am Montag, 18. Mai 2020 23:52:08 UTC+2 schrieb dhorf-hfr...@hashmail.org: > > On Mon, May 18, 2020 at 02:38:34PM -0700, TheGardner wrote: > > [user@sys-firewall ~]$ df -h /var/lib/qubes/dom0-updates > > /dev/xvda3 9.6G 8.7G 450M 96% / > > > sudo mkfs.ext4 /dev/xvdc3 > > sudo mount /dev/xvdc3 /var/lib/qubes/dom0-updates > > > Do I have to change (back) somethings, after I installed the template > and > > removed the noarch.rpm file from dom0-updates ? > > xvdc is the "volatile" volume. > so this change will vanish on its own the next time you restart > sys-firewall. > > > > -- 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/9b5d7c99-5258-4bde-86fc-ebada4621d08%40googlegroups.com.
Re: [qubes-users] Re: Install of the Fedora-32 templateVM failed
Okay, df -h /var/lib/qubes/dom0-updates delivered the following: [user@sys-firewall ~]$ df -h /var/lib/qubes/dom0-updates Filesystem Size Used Avail Use% Mounted on /dev/xvda3 9.6G 8.7G 450M 96% / so, clear now! Thanks a buch! After: sudo mkfs.ext4 /dev/xvdc3 sudo mount /dev/xvdc3 /var/lib/qubes/dom0-updates it already worked like a charm and download the 1.3G file. Do I have to change (back) somethings, after I installed the template and removed the noarch.rpm file from dom0-updates ? Cheers :) Am Montag, 18. Mai 2020 12:56:59 UTC+2 schrieb dhorf-hfr...@hashmail.org: > > On Mon, May 18, 2020 at 03:33:02AM -0700, TheGardner wrote: > > - Setting the space up to 4096 on sys-firewall > same result > > the default download location in udaptevm is /var/lib/qubes/dom0-updates > so with a default appvm layout that is inside the rootfs (or its overlay). > you can check if this is the limiting factor by running > "df -h /var/lib/qubes/dom0-updates" in your updatevm (sys-firewall). > > to temporarily make more space available there, you can try ... > > > > -- 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/357eaea6-c601-4244-97ac-225f8b6e2f56%40googlegroups.com.
[qubes-users] Re: Install of the Fedora-32 templateVM failed
No chance! Whatever I do, it always breaks after around 360mb. Really feels like there isn't enough space. Wonder where I can see this. - Setting the space up to 4096 on sys-firewall > same result - setting the boost and minimal cube emory (for dom0) up > same result Anyone which an idea, what I'm doing wrong? Am Samstag, 16. Mai 2020 15:25:37 UTC+2 schrieb TheGardner: > > Currently try to install the Fedora-32(-testing) template on my Qubes-OS > and it always fail during the initial download (after around 350mb). > Question now is - is the disk space of my updateVM full? And if - can I > check this with a command? > > -- 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/19fb0f98-5b2a-4fc3-b178-c430d966fcd0%40googlegroups.com.
[qubes-users] Re: HCL search facility
copied all in a excel/calc sheet and filtered out Lenovos P50. Looking now for a 64GB version of the i7-6820... Am Donnerstag, 14. Mai 2020 21:30:11 UTC+2 schrieb Andrew Sullivan: > > Good evening > > Is there a way to search the HCL? If not, could such a function be > provided? The list is long, and presumably will get longer, so it would > save a lot of scrolling. > > Just a thought. > > -- 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/e14be4b1-cb82-41b9-8c58-de688a9d0866%40googlegroups.com.
[qubes-users] Install of the Fedora-32 templateVM failed
Currently try to install the Fedora-32(-testing) template on my Qubes-OS and it always fail during the initial download (after around 350mb). Question now is - is the disk space of my updateVM full? And if - can I check this with a command? Downloading the 1.3G file manually works, but I dunno, how to install the downloaded .noarch.rpm.file...? The cache should be empty, cause a 'dnf clean packages' always brings up a 'files 0' message. Reboot also done several times... Anyone an idea? Thanks! -- 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/6ee0fc66-8e08-4011-a011-104dbd09d84a%40googlegroups.com.
[qubes-users] Re: Hallo, es kann langsam losgehen mit Qubes Deutschland Forum, sowie mit der Software Übersetzung in deutsche Sprache
Puhh, da haste Dir ja was vorgenommen! Forensoftware schonmal interessant. Habs selten gesehen, dass mal einer mit phpBB startet. Kann Dir dort helfen, wenn mal Not am Mann ist. Hab selbst 4 phpBB Foren am Laufen seit 2003. Dir muss aber eins klar sein, die Leute die das hier (Google-Groups/Newsgroups) gewöhnt sind, sind schwer an die Bulletin Foren zu gewöhnen. Bleibt zu hoffen, das die Qubes Gemeinde auch in Deutschland weiter wachsen wird, dass dort mehr und mehr Leute auftauchen und es nen echter Sammelplatz wird. Da es das bisher noch nicht gibt, hast Du schonmal den Vorteil, damit jetzt (schon) gestartet zu sein! Glückwunsch & maximale Erfolge! Grüße Steffen Am Freitag, 15. Mai 2020 19:27:06 UTC+2 schrieb wirsin...@gmail.com: > > Hallo liebe Mädels und Jungs, > > das ist jetzt mein Qubes Forum in deutsche Sprache. > > https://qubes-deutschland-forum.gegenseitige-hilfe.org/index.php > > Gruß > > -- 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/52c6689b-5919-489f-a22e-635d3edf7eba%40googlegroups.com.
