Re: [qubes-users] choice of media player with minimal resources ?
Hello Am Mo., 14. Jan. 2019, 08:36 hat Ivan Mitev geschrieben: > [...] > Another less obvious reason for not having the laptop's fan constantly > on due to high CPU usage is to avoid clogging the heat sink with > dust/fibers (eg. when you have your laptop lay on a blanket when you're > in bed). > As a Thinkpa User I am running tlp and powertop in dom0 to get some more options here. - O -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2vpYE1X_cqDMMN6ZSrdsSxaxo08x8hWTpokvh2KmD6OXw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] choice of media player with minimal resources ?
Hi 799 :) On 1/14/19 9:05 AM, 799 wrote: > Am Mo., 14. Jan. 2019, 08:00 hat Ivan Mitev geschrieben: > >> Hi all, >> >> I'd be interested to know what people use for playing videos in VMs >> (without GPU passthrough). > > > For streaming content I use Google Chrome in a special "Multimedia AppVM", > which has no other purpose. > > I rarely have other sources for video, but if so I'm using VLC / VideoLAN > Client. Yes, I saw that's what you recommended in the multimedia doc. > I never cared about ressource consumption, as the multimedia task was often > the foremost task and I didn't do anything in this time. That's OK for a desktop PC (including laptops that stay plugged on a desk) but for mobile use performance/battery life is a concern. Another less obvious reason for not having the laptop's fan constantly on due to high CPU usage is to avoid clogging the heat sink with dust/fibers (eg. when you have your laptop lay on a blanket when you're in bed). -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ab3ce70d-0058-1157-f8c8-b9cc029c07d2%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] choice of media player with minimal resources ?
Am Mo., 14. Jan. 2019, 08:00 hat Ivan Mitev geschrieben: > Hi all, > > I'd be interested to know what people use for playing videos in VMs > (without GPU passthrough). For streaming content I use Google Chrome in a special "Multimedia AppVM", which has no other purpose. I rarely have other sources for video, but if so I'm using VLC / VideoLAN Client. I never cared about ressource consumption, as the multimedia task was often the foremost task and I didn't do anything in this time. - O -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2v0jTsF9GS%3DBN4Fq7YsF0WgDK--%2Bk6XEaEnvFxg8RMrJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] choice of media player with minimal resources ?
Hi all, I'd be interested to know what people use for playing videos in VMs (without GPU passthrough). I've tried mpv, mplayer, vlc, google-chrome and ffmpeg: mpv, vlc and ffmpeg were the worst in terms of CPU usage. google-chrome fared better, while mplayer seemed to consume the least resources. I guess it boils down to how well those players implement software rendering given the lack of hardware acceleration in qubes. I haven't looked at what library each player use for decoding (for instance mpv and vlc may use ffmpeg which would explain why they're all more or less in the same cpu resource usage group). Note: the tests I've done were with h264 640x480 videos and the way I measured CPU usage was very scientific: eyeballing the output of xentop and adding dom0's % with the vm's % I was playing the video in :) Cheers, Ivan -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ebc86146-ccb6-47ab-bcc9-b501a6dc92f4%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] dom0 downloads, but does not update packages
On 1/13/19 11:04 PM, pixel fairy wrote: > heres the output of qubes-dom0-update. it just stops after downloading. done > this for at least a week. > > Fedora 25 - x86_64 913 kB/s | 50 MB 00:56 > > Qubes Dom0 Repository (updates) 686 kB/s | 8.0 MB 00:11 > > determining the fastest mirror (15 hosts).. done..5 kB/s | 2.7 kB 00:00 > ETA > Qubes Templates repository 1.7 kB/s | 10 kB 00:06 > > Last metadata expiration check: 0:00:01 ago on Sun Jan 13 12:53:10 2019. > Dependencies resolved. > > Package Arch Version Repository > Size > > Reinstalling: > anaconda-corex86_64 1000:25.20.9-14.fc25 qubes-dom0-current 1.5 > M > anaconda-gui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 386 > k > anaconda-tui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 186 > k > anaconda-widgets x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 119 > k > python3-blivet noarch 2:2.1.6-5.fc25qubes-dom0-current 1.0 > M > python3-kickstartnoarch 1000:2.32-4.fc25 qubes-dom0-current 370 > k > qubes-anaconda-addon noarch 4.0.9-1.fc25 qubes-dom0-current 34 > k > xorg-x11-drv-ati x86_64 18.0.1-1.fc25 qubes-dom0-current 168 > k > xorg-x11-drv-intel x86_64 2.99.917-32.20171025.fc25 qubes-dom0-current 696 > k > > Transaction Summary > > > Total download size: 4.4 M > Installed size: 4.4 M > DNF will only download packages for the transaction. > Downloading Packages: > (1/9): anaconda-tui-25.20.9-14.fc25.x86_64.rpm 136 kB/s | 186 kB 00:01 > > (2/9): anaconda-widgets-25.20.9-14.fc25.x86_64. 709 kB/s | 119 kB 00:00 > > (3/9): anaconda-gui-25.20.9-14.fc25.x86_64.rpm 231 kB/s | 386 kB 00:01 > > (4/9): python3-blivet-2.1.6-5.fc25.noarch.rpm 914 kB/s | 1.0 MB 00:01 > > (5/9): python3-kickstart-2.32-4.fc25.noarch.rpm 367 kB/s | 370 kB 00:01 > > (6/9): qubes-anaconda-addon-4.0.9-1.fc25.noarch 585 kB/s | 34 kB 00:00 > > (7/9): anaconda-core-25.20.9-14.fc25.x86_64.rpm 543 kB/s | 1.5 MB 00:02 > > (8/9): xorg-x11-drv-ati-18.0.1-1.fc25.x86_64.rp 512 kB/s | 168 kB 00:00 > > (9/9): xorg-x11-drv-intel-2.99.917-32.20171025. 1.1 MB/s | 696 kB 00:00 > > > Total 860 kB/s | 4.4 MB 00:05 > > Complete! > The downloaded packages were saved in cache until the next successful > transaction. > You can remove cached packages by executing 'dnf clean packages'. > Qubes OS Repository for Dom0 27 MB/s | 37 kB 00:00 > Same here but with a slightly different list of packages. I don't remember interrupting any update process in dom0. I tried to clean the cache with `--clean` or directly with `rm` in sys-firewall but it didn't help. I then tried to redo the last dnf transaction (`dnf history redo ...`) but it failed with: [...] No package qubes-mgmt-salt-dom0-0:4.0.13-1.fc25.noarch installed. Error: An operation cannot be redone Oddly, `rpm -q qubes-mgmt-salt-dom0` returns a newer version of that package: qubes-mgmt-salt-dom0-4.0.14-1.fc25.noarch No idea how that's possible given that I'm redoing the *last* dnf transaction and I've never manually installed/updated packages in dom0. Not sure if this is related to the original problem. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6daed4cf-a28e-64ad-e72c-7a13cf15eb33%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Lenovo T480 freezes after resume on suspend
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/13/19 8:04 PM, maur...@disroot.org wrote: > Unfortunately this doesn't work for me. Detaching the USB > controller doesn't work. My sys-usb always hangs on resume. No > matter which update I make this problem continues to persist. You have 2 options to solve this issue: a, - - Make sure, you have the latest BIOS firmware. - - enable Thunderbolt Assist in BIOS b, - - disable Thunderbolt in BIOS (Hence, you will loose the USB-C connector) - -- Zrubi -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEmAe1Y2qfQjTIsHwdVjGlenYHFQ0FAlw8Iq8ACgkQVjGlenYH FQ1CMA//Vd7JgQFrXGxr3QKhjjWm39NCw8dOTBAOil864t1kMwOol1lZUmoY42tY znTXdmIT64UXf7/zgRKUsknWaKg1kQnx8uUZIMS+8FA9CiZGhe23psoJosXAhdVM sGfAd1ZmzrdynTGhxC7xYAwm8M2GOEaa2yuUFkOIMivmWHvptIUlP+inXaQKTq6i haFtCD5y53rhStcgamb9ePiBe2rrHHyfeN1Y7bfKkxJ6aNKASejLOF/o1X6edF8f g1fT90ncQm8X7UY9MFuLBEMvoBq4l4TZxWs5E1x5kEOrzwksv1CSIbdak+THe8Lk /DlnNh8qVWoo8mTj56+gbydUmqQtvlugBxFi2zANWFoP7EsLZqR9KAJubLhI8im8 TTJ3PgIiM5MULviT6MZr8DH6kga8489T+GAkIAA7tPkQ6XECZp4bLE1FyWjpWFss Sgo/p0KYcB5TM+jQ+T2cjf1jHCcToxZWcUPyCtrZi99d86Z0fVKDxIBnAqlGIUrl CcuZdDLwSMHDmdh2s5osmuzjtVvWr+VM/yuPTK8lvQA48b+1dIm2RUcAThbRKf9w Pu/WlIbr0XDSTzZtnZcqCePN7lQPoIdslRZSsFwt48x4g+Olm0I7cvJEhFTEmmkr RblAAauus2zvYVS9pxMcBvadrjn/yFHiZq0D//0/beea8fiEf6I= =JuWi -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c72277c0-d01f-6c5e-5ec8-f8b7ff92f22a%40zrubi.hu. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: sys-whonix-14 updates issues
On 1/13/19 6:24 AM, John S.Recdep wrote: > On 1/13/19 8:01 AM, Mathew wrote: >> Hello, >> >> Just to know if there is a solution for whonix-gw/whonix-ws updates ? >> Noted that I can update/upgrade sys-whonix-14 without any problems ! I have >> to do it again after rebooting though. >> >> $ sudo apt-get-update-plus dist-upgrade >> WARNING: Execution of /usr/bin/apt-get prevented by /etc/uwt.d/40_qubes.conf >> because no torified Qubes updates proxy found. >> >> Please make sure Whonix-Gateway (commonly called sys-whonix) is running. >> >> - If you are using Qubes R3.2: The NetVM of this TemplateVM should be set to >> Whonix-Gateway (commonly called sys-whonix). >> >> - If you are using Qubes R4 or higher: Check your _dom0_ >> /etc/qubes-rpc/policy/qubes.UpdatesProxy settings. >> >> _At the very top_ of that file. >> >> Should have the following syntax: >> Name-Of-Whonix-TemplateVM $default >> allow,target=Whonix-Gateway-TemplateBased-ProxyVM >> >> Example entry for Whonix-Gateway TemplateVM: >> whonix-gw-14 $default allow,target=sys-whonix >> >> Example entry for Whonix-Workstation TemplateVM: >> whonix-ws-14 $default allow,target=sys-whonix >> >> Try running in Whonix-Gateway (commonly called sys-whonix): >> sudo systemctl restart qubes-whonix-torified-updates-proxy-check >> >> If this warning message is transient, it can be safely ignored. >> >> Thanks ! >> >> Regards, >> Mathew >> > > > what is this all about, your telling people who may be having problems > what to do, but your not having a problem? am confused > > because I am unable to sudo apt-get update whonix-gw-14 which I am > trying to do because it's complaining again about time issues, and the > pop up suggestion doesn't fix the problemsigh > user@host:~$ sudo apt-get update Ign:1 http://deb.whonix.org stretch InRelease Ign:2 http://security.debian.org stretch/updates InRelease Ign:3 http://deb.qubes-os.org/r4.0/vm stretch InRelease Ign:4 http://ftp.us.debian.org/debian stretch InRelease Err:5 http://deb.whonix.org stretch Release 500 Unable to connect Err:6 http://ftp.us.debian.org/debian stretch Release 500 Unable to connect Err:7 http://security.debian.org stretch/updates Release 500 Unable to connect Err:8 http://deb.qubes-os.org/r4.0/vm stretch Release 500 Unable to connect Ign:9 tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion stretch InRelease Ign:10 tor+http://vwakviie2ienjx6t.onion/debian stretch InRelease Ign:11 tor+http://sgvtcaew4bxjd7ln.onion stretch/updates InRelease Err:12 tor+http://sgvtcaew4bxjd7ln.onion stretch/updates Release Connection failed Err:13 tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion stretch Release Connection failed Err:14 tor+http://vwakviie2ienjx6t.onion/debian stretch Release Connection failed Reading package lists... Done E: The repository 'http://deb.whonix.org stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://ftp.us.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'tor+http://sgvtcaew4bxjd7ln.onion stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'tor+http://deb.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'tor+http://vwakviie2ienjx6t.onion/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- You received this message because you are subscribed to
[qubes-users] Re: sys-whonix-14 updates issues
On 1/13/19 8:01 AM, Mathew wrote: > Hello, > > Just to know if there is a solution for whonix-gw/whonix-ws updates ? > Noted that I can update/upgrade sys-whonix-14 without any problems ! I have > to do it again after rebooting though. > > $ sudo apt-get-update-plus dist-upgrade > WARNING: Execution of /usr/bin/apt-get prevented by /etc/uwt.d/40_qubes.conf > because no torified Qubes updates proxy found. > > Please make sure Whonix-Gateway (commonly called sys-whonix) is running. > > - If you are using Qubes R3.2: The NetVM of this TemplateVM should be set to > Whonix-Gateway (commonly called sys-whonix). > > - If you are using Qubes R4 or higher: Check your _dom0_ > /etc/qubes-rpc/policy/qubes.UpdatesProxy settings. > > _At the very top_ of that file. > > Should have the following syntax: > Name-Of-Whonix-TemplateVM $default > allow,target=Whonix-Gateway-TemplateBased-ProxyVM > > Example entry for Whonix-Gateway TemplateVM: > whonix-gw-14 $default allow,target=sys-whonix > > Example entry for Whonix-Workstation TemplateVM: > whonix-ws-14 $default allow,target=sys-whonix > > Try running in Whonix-Gateway (commonly called sys-whonix): > sudo systemctl restart qubes-whonix-torified-updates-proxy-check > > If this warning message is transient, it can be safely ignored. > > Thanks ! > > Regards, > Mathew > what is this all about, your telling people who may be having problems what to do, but your not having a problem? am confused because I am unable to sudo apt-get update whonix-gw-14 which I am trying to do because it's complaining again about time issues, and the pop up suggestion doesn't fix the problemsigh -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c0b86093-4b26-6e0d-2164-440e595a831b%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: dom0 downloads, but does not update packages
On 1/13/19 11:04 AM, pixel fairy wrote: > heres the output of qubes-dom0-update. it just stops after downloading. done > this for at least a week. > > Fedora 25 - x86_64 913 kB/s | 50 MB 00:56 > > Qubes Dom0 Repository (updates) 686 kB/s | 8.0 MB 00:11 > > determining the fastest mirror (15 hosts).. done..5 kB/s | 2.7 kB 00:00 > ETA > Qubes Templates repository 1.7 kB/s | 10 kB 00:06 > > Last metadata expiration check: 0:00:01 ago on Sun Jan 13 12:53:10 2019. > Dependencies resolved. > > Package Arch Version Repository > Size > > Reinstalling: > anaconda-corex86_64 1000:25.20.9-14.fc25 qubes-dom0-current 1.5 > M > anaconda-gui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 386 > k > anaconda-tui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 186 > k > anaconda-widgets x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 119 > k > python3-blivet noarch 2:2.1.6-5.fc25qubes-dom0-current 1.0 > M > python3-kickstartnoarch 1000:2.32-4.fc25 qubes-dom0-current 370 > k > qubes-anaconda-addon noarch 4.0.9-1.fc25 qubes-dom0-current 34 > k > xorg-x11-drv-ati x86_64 18.0.1-1.fc25 qubes-dom0-current 168 > k > xorg-x11-drv-intel x86_64 2.99.917-32.20171025.fc25 qubes-dom0-current 696 > k > > Transaction Summary > > > Total download size: 4.4 M > Installed size: 4.4 M > DNF will only download packages for the transaction. > Downloading Packages: > (1/9): anaconda-tui-25.20.9-14.fc25.x86_64.rpm 136 kB/s | 186 kB 00:01 > > (2/9): anaconda-widgets-25.20.9-14.fc25.x86_64. 709 kB/s | 119 kB 00:00 > > (3/9): anaconda-gui-25.20.9-14.fc25.x86_64.rpm 231 kB/s | 386 kB 00:01 > > (4/9): python3-blivet-2.1.6-5.fc25.noarch.rpm 914 kB/s | 1.0 MB 00:01 > > (5/9): python3-kickstart-2.32-4.fc25.noarch.rpm 367 kB/s | 370 kB 00:01 > > (6/9): qubes-anaconda-addon-4.0.9-1.fc25.noarch 585 kB/s | 34 kB 00:00 > > (7/9): anaconda-core-25.20.9-14.fc25.x86_64.rpm 543 kB/s | 1.5 MB 00:02 > > (8/9): xorg-x11-drv-ati-18.0.1-1.fc25.x86_64.rp 512 kB/s | 168 kB 00:00 > > (9/9): xorg-x11-drv-intel-2.99.917-32.20171025. 1.1 MB/s | 696 kB 00:00 > > > Total 860 kB/s | 4.4 MB 00:05 > > Complete! > The downloaded packages were saved in cache until the next successful > transaction. > You can remove cached packages by executing 'dnf clean packages'. > Qubes OS Repository for Dom0 27 MB/s | 37 kB 00:00 > > ya I've got same thing except mine is just the two python packages, I posted here, but no one seems to have answered my query this persists through reboot of the 4.0.1 system now I am having whonix-14-gw unable to update as well, though, doubtful they are related -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/679cffec-1703-5c38-acf5-a54c34c8a9b8%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] xsel via qrexec fails to set clipboard, "conversion refused"
On Sunday, January 13, 2019 at 2:15:31 AM UTC-8, 799 wrote: > Hello Dave, > > > > On Fri, 28 Dec 2018 at 19:28, Dave C wrote: > I've written a qrexec script which, among other things, attempts to place > something into the clipboard, using `xsel`. > > xsel fails, with error: "xsel: Conversion refused" > > > > I don't know what xsel is doing. I have written a script which uses xclip > (which needs to be installed as an additional package). > > Maybe you can get some info from there: > > > > Copy content from the dom0clipboard to an AppVMs clipboard including a > notification > > https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-xclip-to-vm > > > > --- --- --- > #!/bin/bash > # name : qvm-xclip-to-vm > # purpose: Copy the clipboard of dom0 to the clipboard of an appvm > # Usage : qvm-xclip-to-vm > > > AppVM=$1 > xclip -o | qvm-run --pass-io $AppVM 'cat | xclip -selection clipboard > &>/dev/null' > notify-send --urgency low --icon image --expire-time=5000 "$0" "Clipboard > pasted from dom0 to $AppVM" > > --- 8< --- --- --- > > > The other way around: > > https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-xclip-from-vm > > > Additionaly there's a script to do the same for screenshots: > https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-screenshot-to-clipboard.sh > > > O. Hey, good idea. Not sure why I hadn't thought to try `xclip` earlier. While I'd still like to know what xsel is complaining about, I'm able to get it working with xclip. I've started making a qubes-specific version of `go-hash`, a tool for managing passwords. I like one feature in particular: open a URL while copying a password to the clipboard. I renamed my version `qpass`, and created command "appvm" which opens a URL in an appvm while copying the password to that appvm's clipboard. The "dispvm" command is similar, but opens a disposable vm. Work (still a bit in progress) is here: https://github.com/dncohen/qpass/tree/qpass The idea is to run `qpass` in a vault, and use it to launch URLs in app vms that have network access. While qubes copy/paste is pretty good, I find that I can get sloppy with it, sometimes manually pasting to the wrong vm. I'm hoping this approach is a little more idiot-proof. -Dave -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/119a7217-6184-48b2-8a05-eb85da6c641d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using a Desktop Computer with Qubes (R 4.0.1)
John Goold: Just discovered that there is only one USB controller (but 4 USB connector sockets). So when I tried to attach the USB controller to the appVM (had to set it to HVM), I lost the mouse and keyboard :-( I have got the impression from reading the documentation and posts to this forum that if I have disk encryption enabled, that I cannot create a sys-usb VM without losing the mouse+keyboard (and possibly not being able to enter the pass-phrase when powering up. Yea with only one usb controller you can't attach the whole controller to a VM without losing your usb keyboard/mouse. I'm in the same situation. It sounds like you've already looked at the docs but here's the link: https://www.qubes-os.org/doc/usb/ You have to have sys-usb to attach a usb device like a scanner to an appvm (unless you can just attach the whole usb controller, which you can't). I haven't done this myself but my understanding from reading the docs is it's still possible to have sys-usb, you just have to be careful not to lock yourself out (not able to control the system with usb mouse/keyboard, or not able to enter encryption passphrase at boot). According to the docs, if you're using 4.0, you can just use salt to set up a usb qube with the ability to use a usb keyboard with the command sudo qubesctl state.sls qvm.usb-keyboard The doc says that this will create the usb qube if it's not present, and that it will expose dom0 to usb devices on boot so you can enter the passphrase. After you do this though you still may want to check your grub/efi config file to make sure it doesn't have the "rd.qubes.hide_all_usb" line in it, just in case. Or you can follow the steps in the docs to do it manually, just make sure to add the required lines to the qubes.InputKeyboard and qubes.InputMouse files first, and don't add the "rd.qubes.hide_all_usb line to grub/efi config file. Also this has security implications since if your sys-usb is compromised an attacker could scoop up your keystrokes, but this should still be safer than attaching insecure usb devices to dom0. But it should work, unless i'm reading something wrong. -- Jackie -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fe249d79-6aba-d9ae-2343-a8890931aaad%40bitmessage.ch. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0.1 Live
If anyone is interested, I've put up a Live image for 4.0.1 at: https://qubes.3isec.org/Live The image only has Fedora and Debian templates, no sys-usb, (obviously) and nothing is set to autostart. Doesnt use swap. It will run off DVD or USB, and is serviceable in 8GB - the more memory the better. There's a desktop shortcut to install, but it doesnt work (as yet). unman -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190114013330.q3sd72paaq6zorkn%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian minimal template
On Fri, Jan 11, 2019 at 04:25:00PM +0100, Zrubi wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 1/10/19 1:14 AM, unman wrote: > > If any one is interested there's a prebuilt debian-9-minimal > > template currently available in itl-testing. > > would you mind sending the output of > dpkg -l > > Thanks. > - -- > Zrubi Of course: acl 2.2.52-3+b1 adduser 3.115 adwaita-icon-theme 3.22.0-1+deb9u1 amd64-microcode 3.20160316.3 apt 1.4.8 apt-listchanges 3.10 apt-transport-https 1.4.8 apt-utils1.4.8 aptitude 0.8.7-1 aptitude-common 0.8.7-1 aspell 0.60.7~20110707-3+b2 aspell-en2016.11.20-0-0.1 at-spi2-core 2.22.0-6+deb9u1 avahi-daemon 0.6.32-2 base-files 9.9+deb9u6 base-passwd 3.5.43 bash 4.4-5 bash-completion 1:2.1-4.3 bc 1.06.95-9+b3 bind9-host 1:9.10.3.dfsg.P4-12.3+deb9u4 binutils 2.28-5 bsdmainutils 9.0.12+nmu1 bsdutils 1:2.29.2-1+deb9u1 busybox 1:1.22.0-19+b3 bzip21.0.6-8.1 ca-certificates 20161130+nmu1+deb9u1 colord 1.3.3-2 colord-data 1.3.3-2 console-setup1.164 console-setup-linux 1.164 coreutils8.26-3 cpio 2.11+dfsg-6 cpp 4:6.3.0-4 cpp-66.3.0-18+deb9u1 crda 3.18-1 cron 3.0pl1-128+deb9u1 cryptsetup 2:1.7.3-4 cryptsetup-bin 2:1.7.3-4 cups 2.2.1-8+deb9u2 cups-browsed 1.11.6-3 cups-client 2.2.1-8+deb9u2 cups-common 2.2.1-8+deb9u2 cups-core-drivers2.2.1-8+deb9u2 cups-daemon 2.2.1-8+deb9u2 cups-filters 1.11.6-3 cups-filters-core-drivers1.11.6-3 cups-pk-helper 0.2.6-1+b1 cups-ppdc2.2.1-8+deb9u2 cups-server-common 2.2.1-8+deb9u2 dash 0.5.8-2.4 dbus 1.10.26-0+deb9u1 dbus-user-session1.10.26-0+deb9u1 dbus-x11 1.10.26-0+deb9u1 dconf-cli0.26.0-2+b1 dconf-gsettings-backend:amd640.26.0-2+b1 dconf-service0.26.0-2+b1 debconf 1.5.61 debconf-i18n 1.5.61 debian-archive-keyring 2017.5 debian-faq 8.1 debianutils 4.8.1.1 debugedit4.12.0.2+dfsg1-2 desktop-file-utils 0.23-1 dh-python2.20170125 dictionaries-common
Re: [qubes-users] Re: Can't open xterm from default fedora-29-minimal template
On Sun, Jan 13, 2019 at 04:36:32PM -0800, Tonyt wrote: > On Sunday, January 13, 2019 at 7:11:33 PM UTC, 799 wrote: > > Hello, > > > > > > after I had some problems rebuilding my fedora-28 based templates with > > fedora-29, I re-installed the template using: > > > > > > sudo qubes-dom0-update --action=reinstall qubes-fedora-29-minimal > > > > > > while the installation worked and I can start and qvm-shutdown the new > > template, I am unable to launch a xterm terminal. > > > > I tried it via the qubes menu, qvm-run fedora-29-minimal xterm, and also > > with the --user root option ... the AppVM starts, but no xterm is coming up. > > Is this something which came from a recent update (of dom0 or the template)? > > I knew that I didn't had this problems before. > > > > > > - O > > This sounds like this: > https://github.com/QubesOS/qubes-issues/issues/4671 > > Which I solved with this: > The problem: missing e2fsprogs, so /rw cannot be prepared. > quick workaround: qvm-run -u root --no-gui -p fedora-29-minimal 'dnf install > -y e2fsprogs' > There's an updated minimal template in templates-itl-testing -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190114004037.z76qb4l2sqikgle6%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] bind-dirs qubes 4.0.1
On Sun, Jan 13, 2019 at 09:00:27PM +, Robert Rettig wrote: > > Hi, > > > > with the current 4.0.1 even the "How does it work?" section as mentioned > > here > > https://groups.google.com/d/msg/qubes-users/m0qWwToAi8w/phdwx1hSCQAJ > > cannot be applied. > > > > Maybe because the file `bind-dirs.sh` is not available at the described > > location anymore? > > > > A file with the same name would be here `/usr/lib/qubes/init/bind-dirs.sh`. > > > > Created a template clone from `fedora-29` and installed `Docker CE` into it. > > > > ``` > > curl -fsSL https://get.docker.com -o get-docker.sh > > CHANNEL=stable sh get-docker.sh > > sudo usermod -aG docker user > > sudo systemctl enable docker > > ``` > > > > Shutdown that template and created an appvm from it. > > > > I added the bind-dir files as described. But it will not create symlinks > > or copy existing files. > > > > In which state the `bind-dir.sh` is running. Maybe docker daemon already > > created the files and no initial symlinks can be mounted by the script? > > > > > > Thanks for some hints. > > > > I inovked the script manually > > ``` > sudo /usr/lib/qubes/init/bind-dirs.sh > ``` > after that it seems to work. This was covered in the list recently. debian templates have a symlink in /usr/lib/qubes but Fedora templates seem to lack 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190114003820.7a2zq2bqq3u7fimo%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can't open xterm from default fedora-29-minimal template
On Sunday, January 13, 2019 at 7:11:33 PM UTC, 799 wrote: > Hello, > > > after I had some problems rebuilding my fedora-28 based templates with > fedora-29, I re-installed the template using: > > > sudo qubes-dom0-update --action=reinstall qubes-fedora-29-minimal > > > while the installation worked and I can start and qvm-shutdown the new > template, I am unable to launch a xterm terminal. > > I tried it via the qubes menu, qvm-run fedora-29-minimal xterm, and also with > the --user root option ... the AppVM starts, but no xterm is coming up. > Is this something which came from a recent update (of dom0 or the template)? > I knew that I didn't had this problems before. > > > - O This sounds like this: https://github.com/QubesOS/qubes-issues/issues/4671 Which I solved with this: The problem: missing e2fsprogs, so /rw cannot be prepared. quick workaround: qvm-run -u root --no-gui -p fedora-29-minimal 'dnf install -y e2fsprogs' -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/af3a4265-a6bb-4fd6-9c76-02e46f9c7a0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using OpenBSD as Qubes firewall
On Sun, Jan 13, 2019 at 08:28:58PM +0100, alexandre.belgr...@mailbox.org wrote: > Dear all, > > Pardon my ignorance, is it possible to use OpenBSD to provide firewalling to > Qubes? > I have nearly zero confidence in GNU/Linux although I use it everyday. > > Kind regards, If you search this list you'll see this has already been covered. You can install openBSD as HVM, and with some manipulation of basic Qubes networking, have it act as a netvm. Thus take place of sys-net or sys-firewall. You can find some notes that may help here: https://github.com/unman/notes/blob/master/openBSD_as_netvm unman -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190114003548.vx6xvpxqubjaoq5n%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using a Desktop Computer with Qubes (R 4.0.1)
On Sunday, 13 January 2019 17:56:10 UTC-3:30, John Goold wrote: > On Sunday, 13 January 2019 15:50:13 UTC-3:30, 799 wrote: > > Hello John, > > > > > > welcome to Qubes ;-) > > > > > > > > On Sun, 13 Jan 2019 at 18:49, John Goold wrote: > > > > This leads to my first issue: > > > > I seem unable to attach my scanner (it is a ScanSnap ix800 which is not a > > printer/scanner/copier, just a scanner) to an appVM. It does not appear in > > the Dom0 devices menu. If I plug in a USB drive, the drive shows up in the > > menu. > > > > Is there a straightforward way to attach the scanner to an appVM (it will > > not be a server, but will always be the same appVM, "personal")? > > > > > > > > I am not sure if I have understand you correctly, have you chosen to > > install a sys-usb-qube? > > If you didn't you can also do this after the installation. > > If you chose not to use sys-usb, you could try to pass through one of the > > usb-controllers to the AppVM to which you connect the scanner to. > > I have never used an Intel NUC before, but in case that you can run a Qube > > like sys-usb I suggest doing so. > > You can then run the following command from dom0: > > > > > > qvm-usb > > > > > > then attach the scanner to the AppVM > > qvm-usb attach sys-usb:NR-NR > > > > 2. I like to listen to a classical music radio station (CBC Music) and, > > when it is broadcasting other "stuff", streaming classical music from their > > website. > > > > I can play YouTube videos, including hearing the audio, but the above does > > not work (the website page gets stuck loading/waiting for an audio stream). > > > > > > > > Can you send me the link of the radio station you're trying to listen to? > > I'll give it a try to listen to it in my multimedia AppVM which is based on > > my howto here: > > https://www.qubes-os.org/doc/multimedia/ > > > > > > - O > > Just discovered that there is only one USB controller (but 4 USB connector > sockets). So when I tried to attach the USB controller to the appVM (had to > set it to HVM), I lost the mouse and keyboard :-( > > I have got the impression from reading the documentation and posts to this > forum that if I have disk encryption enabled, that I cannot create a sys-usb > VM without losing the mouse+keyboard (and possibly not being able to enter > the pass-phrase when powering up. > > The radio station is: https://www.cbc.ca/listen/live/cbcmusic > > The streaming music is: https://www.cbcmusic.ca/music-streams > > Thank you for responding... @799 I followed your multi-media templateVM how-to document. I installed VLC (haven't tried it yet) and Google Chrome. I do not know if it was the library that was added, but I can now listen to the radio and streaming music. I prefer Banshee to play my music which is all ripped from physical CDs I have bought over the decades (the sites I mentioned are the only ones I stream). However, I will check out VLC and see if it can handle my music library (it is organized differently than the organizations normally supported by music players, which is why I prefer Banshee -- I organized it using Banshee). VLC definitely works (tried "opening a folder"). I will have to learn how to navigate my library with it. THANK YOU. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3726ec26-c686-4a3a-ae11-33f09bf6a925%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Smart cards, split GPG, and timing attacks
That makes sense. Would it be okay to place them all in one VM and use QREXEC_REMOTE_DOMAIN to pick the key? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/13a44caa-a262-4f5b-ae66-e582c97d1d1a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using a Desktop Computer with Qubes (R 4.0.1)
On Sunday, 13 January 2019 15:50:13 UTC-3:30, 799 wrote: > Hello John, > > > welcome to Qubes ;-) > > > > On Sun, 13 Jan 2019 at 18:49, John Goold wrote: > > This leads to my first issue: > > I seem unable to attach my scanner (it is a ScanSnap ix800 which is not a > printer/scanner/copier, just a scanner) to an appVM. It does not appear in > the Dom0 devices menu. If I plug in a USB drive, the drive shows up in the > menu. > > Is there a straightforward way to attach the scanner to an appVM (it will not > be a server, but will always be the same appVM, "personal")? > > > > I am not sure if I have understand you correctly, have you chosen to install > a sys-usb-qube? > If you didn't you can also do this after the installation. > If you chose not to use sys-usb, you could try to pass through one of the > usb-controllers to the AppVM to which you connect the scanner to. > I have never used an Intel NUC before, but in case that you can run a Qube > like sys-usb I suggest doing so. > You can then run the following command from dom0: > > > qvm-usb > > > then attach the scanner to the AppVM > qvm-usb attach sys-usb:NR-NR > > 2. I like to listen to a classical music radio station (CBC Music) and, when > it is broadcasting other "stuff", streaming classical music from their > website. > > I can play YouTube videos, including hearing the audio, but the above does > not work (the website page gets stuck loading/waiting for an audio stream). > > > > Can you send me the link of the radio station you're trying to listen to? > I'll give it a try to listen to it in my multimedia AppVM which is based on > my howto here: > https://www.qubes-os.org/doc/multimedia/ > > > - O Just discovered that there is only one USB controller (but 4 USB connector sockets). So when I tried to attach the USB controller to the appVM (had to set it to HVM), I lost the mouse and keyboard :-( I have got the impression from reading the documentation and posts to this forum that if I have disk encryption enabled, that I cannot create a sys-usb VM without losing the mouse+keyboard (and possibly not being able to enter the pass-phrase when powering up. The radio station is: https://www.cbc.ca/listen/live/cbcmusic The streaming music is: https://www.cbcmusic.ca/music-streams Thank you for responding... -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ed93da87-501b-4c02-b5ba-7548d65a9619%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Install errors on Thinkpad P1 (aka X1 Extreme) with R4.0 and R4.0.1-rc2
On Sunday, January 13, 2019 at 10:51:14 AM UTC-5, awokd wrote: > Weird, not sure how it can detect that 14.3 device with it supposedly > disabled. Check sys-net's Qube Setting/Devices and remove 14.3 from the > right if it's there. Leave 1f.6/Ethernet enabled and assigned if it's > not causing problems, then try to start sys-net. It was a combination of me enabling/disabling multiple things. I got it going - though I've exhausted all the time I had to spend on Qubes on this laptop... I'm going to make a HCL with the information as well to help the next person, or when I get more time this summer to spend days/weeks with it again. >From a fresh install... * Make sure you have BIOS 1.17 or later for the Thinkpad P1. Anything earlier than that WILL BRICK your laptop with these instructions. * BIOS: switch to Discrete Graphics (nvidia only for now). * BIOS: Under Security -> I/O Port Access, disable "Ethernet LAN". This is the "I219-LM" onboard ethernet controller that causes the 00:1f.6 PCI error mentioned above, about how the sys-* VMs won't start because it can't reset it. Now, boot the media and install Qubes 4.0.1 normally. I wipe the entire disk and all Windows partitions personally, never a dual boot so I can't help with that. After the first install phase, it will reboot into the Post Install phase screen (where it asks you which VMs you want to configure). Go ahead and select what you want. However, the Post Install steps will fail at the end with the original error stated in the OP, or something close to it (perhaps 00:14.3 as well). Just ignore this for now. Press OK to "Finish Installation." Note: Do not step away from the laptop at this time. If you do, and the 10 minute timeout occurs after the post install/error message displays, the screensaver will kickin - and you won't get back. It was a number of ACPI errors in the logs. Power-off (hold power for 4 seconds) and start the Post Install phase again. You will get prompted to login. Go ahead and login. Or reboot for good measure. You will notice none of the sys-firewall, sys-usb, nor sys-net are running. The sys-net may start now, manually, but the others will continue to error. To confirm the error, open a Terminal in dom0 and run: $ sudo systemctl status qubes-vm@sys-net.service It should the errors I listed above, such as "PCI device dom0:00_14.3 does not exist" and when you run an "lspci" you don't see it either. There's nothing to do on this error. We're going to re-enable the Ethernet controller now. The 14.3 device is the Wireless card btw, but don't worry about this error - it will resolve itself when you fix the next error below. Reboot into BIOS and re-Enable the "Ethernet LAN" you disabled earlier above. F10, Save and reboot back into Qubes. If you press ESC after the disk encryption key, you'll see that sys-net nor sys-firewall starts (and maybe sys-usb may fail as well). That's fine, we're going to fix that now. Now that you have the I219-LM ethernet controller re-enabled, if you run the systemctl status command again you'll see a different error - the one I originally posted in the OP above, "Unable to reset PCI device :00:1f:6". To fix this one error, that also happens to resolve the 0:14.3 not found error, you need to detach the "1f:6" device from sys-net, and reattach it with special permissions: $ qvm-pci detach sys-net dom0:00_1f.6 $ qvm-pci attach --persistent --option permissive=true \ --option no-strict-reset=true sys-net dom0:00_1f.6 After this, you can qvm-start sys-net and then sys-firewall. You may want to reboot just for good measure. I think I also detached the reattached the 00:14.3 during my debugging. But I currently see I don't have the permissive nor no-strict-reset flags set on my 14.3 device - so that's not needed to get sys-net to start. The reason sys-firewall give the same error on "Unable to reset PCI device :00:1f:6" when trying to start them is, I can only guess, sys-firewall is dependent on sys-net running - and if sys-net fails to start with the error, that error message propagates up to the originally started vm, sys-firewall - showing the same error. Makes sense, as when the error message changes, they both had the same error under systemctl logging (and journalctl). I then spent several days trying to get Nvidia drivers loaded to no avail. Also, trying to get just the Intel card working (hybrid graphics) but I've hit a brick wall there - Xen just freezes on the initial splash screen of the 4 lines showing what kernel is loading. The system hard locks up there, with no logs. I highly prefer the Intel drivers for battery life. At this point, I'm just throwing Arch Linux on it and will come back and revisit it when I have time. It's too bad... I purposely bought this laptop specifically for Qubes. -- You received this message because you are subscribed to the Google Groups
[qubes-users] dom0 downloads, but does not update packages
heres the output of qubes-dom0-update. it just stops after downloading. done this for at least a week. Fedora 25 - x86_64 913 kB/s | 50 MB 00:56 Qubes Dom0 Repository (updates) 686 kB/s | 8.0 MB 00:11 determining the fastest mirror (15 hosts).. done..5 kB/s | 2.7 kB 00:00 ETA Qubes Templates repository 1.7 kB/s | 10 kB 00:06 Last metadata expiration check: 0:00:01 ago on Sun Jan 13 12:53:10 2019. Dependencies resolved. Package Arch Version Repository Size Reinstalling: anaconda-corex86_64 1000:25.20.9-14.fc25 qubes-dom0-current 1.5 M anaconda-gui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 386 k anaconda-tui x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 186 k anaconda-widgets x86_64 1000:25.20.9-14.fc25 qubes-dom0-current 119 k python3-blivet noarch 2:2.1.6-5.fc25qubes-dom0-current 1.0 M python3-kickstartnoarch 1000:2.32-4.fc25 qubes-dom0-current 370 k qubes-anaconda-addon noarch 4.0.9-1.fc25 qubes-dom0-current 34 k xorg-x11-drv-ati x86_64 18.0.1-1.fc25 qubes-dom0-current 168 k xorg-x11-drv-intel x86_64 2.99.917-32.20171025.fc25 qubes-dom0-current 696 k Transaction Summary Total download size: 4.4 M Installed size: 4.4 M DNF will only download packages for the transaction. Downloading Packages: (1/9): anaconda-tui-25.20.9-14.fc25.x86_64.rpm 136 kB/s | 186 kB 00:01 (2/9): anaconda-widgets-25.20.9-14.fc25.x86_64. 709 kB/s | 119 kB 00:00 (3/9): anaconda-gui-25.20.9-14.fc25.x86_64.rpm 231 kB/s | 386 kB 00:01 (4/9): python3-blivet-2.1.6-5.fc25.noarch.rpm 914 kB/s | 1.0 MB 00:01 (5/9): python3-kickstart-2.32-4.fc25.noarch.rpm 367 kB/s | 370 kB 00:01 (6/9): qubes-anaconda-addon-4.0.9-1.fc25.noarch 585 kB/s | 34 kB 00:00 (7/9): anaconda-core-25.20.9-14.fc25.x86_64.rpm 543 kB/s | 1.5 MB 00:02 (8/9): xorg-x11-drv-ati-18.0.1-1.fc25.x86_64.rp 512 kB/s | 168 kB 00:00 (9/9): xorg-x11-drv-intel-2.99.917-32.20171025. 1.1 MB/s | 696 kB 00:00 Total 860 kB/s | 4.4 MB 00:05 Complete! The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Qubes OS Repository for Dom0 27 MB/s | 37 kB 00:00 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4c68169b-c9f7-422c-a389-7421a4b27d4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] bind-dirs qubes 4.0.1
> Hi, > > with the current 4.0.1 even the "How does it work?" section as mentioned > here > https://groups.google.com/d/msg/qubes-users/m0qWwToAi8w/phdwx1hSCQAJ > cannot be applied. > > Maybe because the file `bind-dirs.sh` is not available at the described > location anymore? > > A file with the same name would be here `/usr/lib/qubes/init/bind-dirs.sh`. > > Created a template clone from `fedora-29` and installed `Docker CE` into it. > > ``` > curl -fsSL https://get.docker.com -o get-docker.sh > CHANNEL=stable sh get-docker.sh > sudo usermod -aG docker user > sudo systemctl enable docker > ``` > > Shutdown that template and created an appvm from it. > > I added the bind-dir files as described. But it will not create symlinks > or copy existing files. > > In which state the `bind-dir.sh` is running. Maybe docker daemon already > created the files and no initial symlinks can be mounted by the script? > > > Thanks for some hints. > I inovked the script manually ``` sudo /usr/lib/qubes/init/bind-dirs.sh ``` after that it seems to work. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bf558d91-56f5-9ff0-9649-806f90a3fdf8%40rettig.bayern. For more options, visit https://groups.google.com/d/optout.
[qubes-users] bind-dirs qubes 4.0.1
Hi, with the current 4.0.1 even the "How does it work?" section as mentioned here https://groups.google.com/d/msg/qubes-users/m0qWwToAi8w/phdwx1hSCQAJ cannot be applied. Maybe because the file `bind-dirs.sh` is not available at the described location anymore? A file with the same name would be here `/usr/lib/qubes/init/bind-dirs.sh`. Created a template clone from `fedora-29` and installed `Docker CE` into it. ``` curl -fsSL https://get.docker.com -o get-docker.sh CHANNEL=stable sh get-docker.sh sudo usermod -aG docker user sudo systemctl enable docker ``` Shutdown that template and created an appvm from it. I added the bind-dir files as described. But it will not create symlinks or copy existing files. In which state the `bind-dir.sh` is running. Maybe docker daemon already created the files and no initial symlinks can be mounted by the script? Thanks for some hints. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c1c001b6-624f-0372-de9f-ec066558f38e%40rettig.bayern. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can't open xterm from default fedora-29-minimal template
799 wrote on 1/13/19 7:11 PM: Hello, after I had some problems rebuilding my fedora-28 based templates with fedora-29, I re-installed the template using: sudo qubes-dom0-update --action=reinstall qubes-fedora-29-minimal while the installation worked and I can start and qvm-shutdown the new template, I am unable to launch a xterm terminal. I tried it via the qubes menu, qvm-run fedora-29-minimal xterm, and also with the --user root option ... the AppVM starts, but no xterm is coming up. Is this something which came from a recent update (of dom0 or the template)? I knew that I didn't had this problems before. Possibly related to this Debian issue? https://groups.google.com/d/msg/qubes-users/LPUEsF1zQps/btfvDr4gFAAJ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d1a8c0cc-5200-d422-8022-1a170718aa96%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using OpenBSD as Qubes firewall
Dear all, Pardon my ignorance, is it possible to use OpenBSD to provide firewalling to Qubes? I have nearly zero confidence in GNU/Linux although I use it everyday. Kind regards, -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/188087795.85612.1547407738605%40office.mailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using a Desktop Computer with Qubes (R 4.0.1)
Hello John, welcome to Qubes ;-) On Sun, 13 Jan 2019 at 18:49, John Goold wrote: > > This leads to my first issue: > I seem unable to attach my scanner (it is a ScanSnap ix800 which is not a > printer/scanner/copier, just a scanner) to an appVM. It does not appear in > the Dom0 devices menu. If I plug in a USB drive, the drive shows up in the > menu. > Is there a straightforward way to attach the scanner to an appVM (it will > not be a server, but will always be the same appVM, "personal")? > I am not sure if I have understand you correctly, have you chosen to install a sys-usb-qube? If you didn't you can also do this after the installation. If you chose not to use sys-usb, you could try to pass through one of the usb-controllers to the AppVM to which you connect the scanner to. I have never used an Intel NUC before, but in case that you can run a Qube like sys-usb I suggest doing so. You can then run the following command from dom0: qvm-usb then attach the scanner to the AppVM qvm-usb attach sys-usb:NR-NR > 2. I like to listen to a classical music radio station (CBC Music) and, > when it is broadcasting other "stuff", streaming classical music from their > website. > I can play YouTube videos, including hearing the audio, but the above does > not work (the website page gets stuck loading/waiting for an audio stream). > Can you send me the link of the radio station you're trying to listen to? I'll give it a try to listen to it in my multimedia AppVM which is based on my howto here: https://www.qubes-os.org/doc/multimedia/ - O -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2v5%2BAN8ijqTZPPbS%2Bx9ddGLL%2BOFrEG22h6DxsWmPeCiwQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Can't open xterm from default fedora-29-minimal template
Hello, after I had some problems rebuilding my fedora-28 based templates with fedora-29, I re-installed the template using: sudo qubes-dom0-update --action=reinstall qubes-fedora-29-minimal while the installation worked and I can start and qvm-shutdown the new template, I am unable to launch a xterm terminal. I tried it via the qubes menu, qvm-run fedora-29-minimal xterm, and also with the --user root option ... the AppVM starts, but no xterm is coming up. Is this something which came from a recent update (of dom0 or the template)? I knew that I didn't had this problems before. - O -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2sq9%2BP98UZMcteJ5d9vz6Tt6iiMCjt%2BPxjZwcBhqH4uVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 - ACPI Errors during boot
Anyone was able to solve this warning messages on boot without having to install a fresh Qubes? These messages show up on every boot. Thank you! April 29, 2018 5:48 PM, maur...@disroot.org (mailto:maur...@disroot.org) wrote: Hi Everyone! During the boot and before unlock the LuKS volume I'm getting a lot of ACPI errors regarding Namespace lookup failure: [ 1.726445] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.726525] ACPI Error: Method parse/execution failed _PR.CPU1._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.726609] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.726739] ACPI Error: Method parse/execution failed _PR.CPU2._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.726932] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.727136] ACPI Error: Method parse/execution failed _PR.CPU3._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.727332] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.727517] ACPI Error: Method parse/execution failed _PR.CPU4._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.727709] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.727896] ACPI Error: Method parse/execution failed _PR.CPU5._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.728105] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.728290] ACPI Error: Method parse/execution failed _PR.CPU6._CST, AE_NOT_FOUND (20170728/psparse-550) [ 1.728483] ACPI Error: [_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364) [ 1.728667] ACPI Error: Method parse/execution failed _PR.CPU7._CST, AE_NOT_FOUND (20170728/psparse-550) How can I solve this? Thank you -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cd56d2773f6e701919072e12a4b4778e%40disroot.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Lenovo T480 freezes after resume on suspend
Unfortunately this doesn't work for me. Detaching the USB controller doesn't work. My sys-usb always hangs on resume. No matter which update I make this problem continues to persist. Does anyone has any idea how to solve this? Thank you! May 17, 2018 4:32 PM, maur...@disroot.org (mailto:maur...@disroot.org) wrote: " I needed to remove the assignement of one of the USB controllers from sys-usb " What do you mean by that? Are you unloading a kernel module before suspending or the PCI controller? Which module is this? The sys-usb still freezes on resume, so for the time being I have to manually kill and start the vm again. Which drivers or USB assignments do you remove from your May 8, 2018 7:51 PM, maur...@disroot.org (mailto:maur...@disroot.org) wrote: I'm also experiencing the same issue. Whenever my laptop resumes after have being suspended, the sys-usb is frozen and all USB devices attached to it fail to work. I have to kill the appvm and start it again. This only affects the sys-usb though, the sys-net is working fine during the resume. The issue that describes this problem - https://github.com/QubesOS/qubes-issues/issues/3142 (https://github.com/QubesOS/qubes-issues/issues/3142) - was closed but the problem still persists. Any idea how can we resolve 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/695a0a91c1ee9826ea476f31bc646406%40disroot.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] VPN for Linux Dummies
On Sunday, January 13, 2019 at 3:03:49 PM UTC, Chris Laprise wrote: > On 01/11/2019 05:48 PM, seshu wrote: > > Chris, I recently got Nordvpn running on my 4.0.1 and I used their .deb > > package to install their app. > > > > The one thing I like about their app is that when it fires up it scans the > > hundreds of servers they have to identify the server that is best to > > connect to. The process that Qubes-vpn-support uses relies on the user > > manually deciding which of the hundreds plus servers to use right, and then > > creating a ln to that ovpn file? > > > > Do you think there could be a way to streamline or automate which ovpn file > > to use? > > > > Thanks! > > Its impossible to tell which servers for a given region a VPN provider > considers to be 'best'. Some providers like PIA allow you to specify a > region by domain name, and that domain name represents a bank of servers > from which a server is chosen at connection time; it appears to be a > standard load-balancing configuration. > > If you don't want to use one server IP all the time, you could add many > IPs to the conf file along with 'remote-random' which will choose one > randomly. Alternately, you could see if NordVPN has regional domain > names and use one of those in your conf. > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Ok thanks. that makes sense. I'll look into that aspect. >From a security perspective, checking for leaks, etc. is there a particular >tool or technique you like to use? this idea of leaks is new to me so I want >to check the nordvpn setup I have now to see how it compares. 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/492274b5-7a15-49d2-b1b6-9b6578365761%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] sys-whonix-14 updates issues
Hello, Just to know if there is a solution for whonix-gw/whonix-ws updates ? Noted that I can update/upgrade sys-whonix-14 without any problems ! I have to do it again after rebooting though. $ sudo apt-get-update-plus dist-upgrade WARNING: Execution of /usr/bin/apt-get prevented by /etc/uwt.d/40_qubes.conf because no torified Qubes updates proxy found. Please make sure Whonix-Gateway (commonly called sys-whonix) is running. - If you are using Qubes R3.2: The NetVM of this TemplateVM should be set to Whonix-Gateway (commonly called sys-whonix). - If you are using Qubes R4 or higher: Check your _dom0_ /etc/qubes-rpc/policy/qubes.UpdatesProxy settings. _At the very top_ of that file. Should have the following syntax: Name-Of-Whonix-TemplateVM $default allow,target=Whonix-Gateway-TemplateBased-ProxyVM Example entry for Whonix-Gateway TemplateVM: whonix-gw-14 $default allow,target=sys-whonix Example entry for Whonix-Workstation TemplateVM: whonix-ws-14 $default allow,target=sys-whonix Try running in Whonix-Gateway (commonly called sys-whonix): sudo systemctl restart qubes-whonix-torified-updates-proxy-check If this warning message is transient, it can be safely ignored. Thanks ! Regards, Mathew -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/324545cb-056a-4f45-8c54-1f58838fd1ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1
On Friday, January 11, 2019 at 10:35:11 AM UTC-8, John S.Recdep wrote: > On 1/11/19 8:08 AM, > scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > > Hello, > > > > I am a new user to Qubes and I like it very much. > > > > I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 > > templates. Below are the errors for both: > > > > Fedora-29: > > > > Fedora Modular 29 - x86_64 > > Error: Failed to synchronize cache for repo 'fedora-modular' > > Done. > > > > Debian-9 (snippet): > > > > Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release > > 500 Unable to connect > > Err:6 https://deb.debian.org/debian stretch Release > > Received HTTP code 500 from proxy after CONNECT > > Err:7 https://deb.debian.org/debian-security stretch/updates Release > > Received HTTP code 500 from proxy after CONNECT > > Err:8 https://deb.debian.org/debian jessie-backports Release > > Received HTTP code 500 from proxy after CONNECT > > E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian-security stretch/updates > > Release' does no longer have a Release file. > > E: The repository 'https://deb.debian.org/debian jessie-backports Release' > > does no longer have a Release file. > > > > TIA > > > > try doing it via a terminal in the templates > > $sudo dnf update > > $sudo apt-get update > sudo apt-get dist-upgrade > > fwiw for myself, the qubes manager fails or is so slow I only use it to > make appvms or change/add applications lately > > > so I guess this is a new install of yours? This was a new install of 4.0.1. I got the same errors when I terminal into the debian-9 and fedora-29 templates. Here is the errors I got from the debian-9 update: Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox y over Qubes RPC (127.0.0.1:59084). Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox y over Qubes RPC (127.0.0.1:59086). Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1: 8082-127.0.0.1:59082.service: Main process exited, code=exited, status=1/FAILURE Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1: 8082-127.0.0.1:59082.service: Unit entered failed state. Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1: 8082-127.0.0.1:59082.service: Failed with result 'exit-code'. Here is the errors I get from fedora-29: 2019-01-13T17:34:39Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failoverm ethod" does not exist 2019-01-13T17:34:39Z DEBUG repo: downloading from remote: fedora-modular 2019-01-13T17:34:39Z DEBUG error: Curl error (56): Failure when receiving data f rom the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular- 29=x86_64 [Received HTTP code 500 from proxy after CONNECT] (https://mirror s.fedoraproject.org/metalink?repo=fedora-modular-29=x86_64). 2019-01-13T17:34:39Z DEBUG Cannot download 'https://mirrors.fedoraproject.org/me talink?repo=fedora-modular-29=x86_64': Cannot prepare internal mirrorlist: Curl error (56): Failure when receiving data from the peer for https://mirrors.f edoraproject.org/metalink?repo=fedora-modular-29=x86_64 [Received HTTP code 500 from proxy after CONNECT]. 2019-01-13T17:34:39Z DDEBUG Cleaning up. 2019-01-13T17:34:39Z SUBDEBUG Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/dnf/repo.py", line 566, in load ret = self._repo.load() File "/usr/lib64/python3.7/site-packages/libdnf/repo.py", line 503, in load return _repo.Repo_load(self) RuntimeError: Failed to synchronize cache for repo 'fedora-modular' TIA -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a37d9151-8464-403b-a01b-d8d93a3c7d5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using a Desktop Computer with Qubes (R 4.0.1)
I am one of those Qubes newbies. I do have a "computer" background, having
started out on Mainframe computers — I have been retired for over 20 years;
however, I now use my computer as a tool (though I do some website development
to keep the neurons firing). I do not need a highly locked down computer, but
do want to use whatever security improvements I can reasonably get with Qubes
without the set-up and maintenance becoming a full-time job. I also prefer to
using a GUI when possible (spent decades using terminals).
___
Normally I would post each issue as a separate post to a forum such as this;
however, these are all related to the "Subject" and my getting started. I
always try searching for similar issues before posting, but (here) have not
found solutions (either here or in the documentation).
1. The NUC is an Intel desktop computer with a nice small foot-print (Intel
NUC7i7 BNH with 512 GB SSD and 32GB RAM). The only mouse and keyboard that
works are USB (there is no PS/1 port) — possibly bluetooth devices would work
but I do not want to get into the issues involved (I do use an Apple bluetooth
keyboard with Linux Mint on my HP laptop).
My disk is encrypted and the installation nicely reminded me of the warnings in
this forum about setting up sys-usb — so sys-usb is a non-starter. This leads
to my first issue:
I seem unable to attach my scanner (it is a ScanSnap ix800 which is not a
printer/scanner/copier, just a scanner) to an appVM. It does not appear in the
Dom0 devices menu. If I plug in a USB drive, the drive shows up in the menu.
Is there a straightforward way to attach the scanner to an appVM (it will not
be a server, but will always be the same appVM, "personal")?
2. I like to listen to a classical music radio station (CBC Music) and, when it
is broadcasting other "stuff", streaming classical music from their website.
I can play YouTube videos, including hearing the audio, but the above does not
work (the website page gets stuck loading/waiting for an audio stream).
I imagine this has something to do with proxy settings. Is this correct? I have
created an appVM ("entertainment") specifically to handle playing music, so I
am not worried about it getting compromised because I use less secure settings
for it.
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/b599cb54-08f0-4703-a375-d67458823c1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1
On Friday, January 11, 2019 at 10:35:11 AM UTC-8, John S.Recdep wrote: > On 1/11/19 8:08 AM, > scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote: > > Hello, > > > > I am a new user to Qubes and I like it very much. > > > > I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 > > templates. Below are the errors for both: > > > > Fedora-29: > > > > Fedora Modular 29 - x86_64 > > Error: Failed to synchronize cache for repo 'fedora-modular' > > Done. > > > > Debian-9 (snippet): > > > > Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release > > 500 Unable to connect > > Err:6 https://deb.debian.org/debian stretch Release > > Received HTTP code 500 from proxy after CONNECT > > Err:7 https://deb.debian.org/debian-security stretch/updates Release > > Received HTTP code 500 from proxy after CONNECT > > Err:8 https://deb.debian.org/debian jessie-backports Release > > Received HTTP code 500 from proxy after CONNECT > > E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian stretch Release' does no > > longer have a Release file. > > E: The repository 'https://deb.debian.org/debian-security stretch/updates > > Release' does no longer have a Release file. > > E: The repository 'https://deb.debian.org/debian jessie-backports Release' > > does no longer have a Release file. > > > > TIA > > > > try doing it via a terminal in the templates > > $sudo dnf update > > $sudo apt-get update > sudo apt-get dist-upgrade > > fwiw for myself, the qubes manager fails or is so slow I only use it to > make appvms or change/add applications lately > > > so I guess this is a new install of yours? This was a new install of 4.0.1. I got the same errors when I terminal into the debian-9 and fedora-29 templates using your commands. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a3ea9cdf-2e51-44fc-bf46-d4ef2514025a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] A way to have a qube close once all its windows are closed?
On 1/13/19 6:19 PM, Stumpy wrote: > I usually have lots of windows open but am finding that after a few days > I have lots of appvms open that arent being used... usually finding this > when i try to open (yet another) appvm and being told I am out of memory. > I have maxed out my memory slots, and shaved each appvm down to the > minimum amount of memory that it needs to operate so... > > Is there a way, like dispVMs, to have an appvm automatically close when > its not in use? "In use" defined as not having a window open? See https://github.com/QubesOS/qubes-app-shutdown-idle and the related issue: https://github.com/QubesOS/qubes-issues/issues/832#issuecomment-437303826 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/34bee960-bff7-93b8-ec26-b40b3d4ba335%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Ralink RT2870/RT3070 Wireless Adapter
Hi qubes-users, I'm using Qubes OS for my pentests at work, I have some issues trying to connect my Alfa network wireless USB card in my Kali AppVM though. I chose to install kali manually as explained here : https://www.qubes-os.org/doc/pentesting/kali/#templatevm-from-debian3_2 It works fine ! However, when I plug & add the wireless device to my kali AppVM I can't make it works. Here the lsusb result in my kali-rolling Template, I had to blacklist the rt2800usb module : $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Both firware-ralink and firmware-misc-nonfree are installed. Build-essential too. When I try to install the driver from the official website (https://www.alfa.com.tw/files/?dir=%5B1%5D%20WiFi%20USB%20adapter/AWUS036H/Linux), here the feedback : $ make make[1]: Entering directory '/lib/modules/4.14.74-1.pvops.qubes.x86_64/build' make[1]: *** No rule to make target 'WiFi'. Stop. make[1]: Leaving directory '/lib/modules/4.14.74-1.pvops.qubes.x86_64/build' make: *** [Makefile:15: all] Error 2 $ uname -r 4.14.74-1.pvops.qubes.x86_64 $ sudo dmesg [ 12.078758] Netfilter messages via NETLINK v0.30. [ 12.106149] nf_tables: (c) 2007-2009 Patrick McHardy [ 12.242556] nf_tables_compat: (c) 2012 Pablo Neira Ayuso [ 12.521504] nf_conntrack version 0.5.0 (2560 buckets, 10240 max) [ 12.887695] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 30.487105] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller [ 30.487171] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 1 [ 30.487501] vhci_hcd: created sysfs vhci_hcd.0 [ 30.487556] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 30.487575] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 30.487597] usb usb1: Product: USB/IP Virtual Host Controller [ 30.487616] usb usb1: Manufacturer: Linux 4.14.74-1.pvops.qubes.x86_64 vhci_hcd [ 30.487637] usb usb1: SerialNumber: vhci_hcd.0 [ 30.489603] hub 1-0:1.0: USB hub found [ 30.489628] hub 1-0:1.0: 8 ports detected [ 30.490953] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller [ 30.491249] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 2 [ 30.491298] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 30.491356] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 [ 30.491375] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 30.491397] usb usb2: Product: USB/IP Virtual Host Controller [ 30.491415] usb usb2: Manufacturer: Linux 4.14.74-1.pvops.qubes.x86_64 vhci_hcd [ 30.491436] usb usb2: SerialNumber: vhci_hcd.0 [ 30.491552] hub 2-0:1.0: USB hub found [ 30.491582] hub 2-0:1.0: 8 ports detected [ 30.640047] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0) [ 30.640073] vhci_hcd vhci_hcd.0: devid(196611) speed(3) speed_str(high-speed) [ 30.858179] usb 1-1: new high-speed USB device number 2 using vhci_hcd [ 30.976353] usb 1-1: SetAddress Request (2) to port 0 [ 31.015322] usb 1-1: New USB device found, idVendor=148f, idProduct=3070 [ 31.015404] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 31.015489] usb 1-1: Product: 802.11 n WLAN [ 31.015534] usb 1-1: Manufacturer: Ralink [ 31.015578] usb 1-1: SerialNumber: 1.0 [ 1854.054576] blkfront: xvdd: empty flush op failed [ 1854.054599] blkfront: xvdd: barrier or flush: disabled; persistent grants: enabled; indirect descriptors: enabled; [ 1974.675502] vhci_hcd: connection closed [ 1974.675558] vhci_hcd: stop threads [ 1974.675584] vhci_hcd: release socket [ 1974.675597] vhci_hcd: disconnect device [ 1974.675640] usb 1-1: USB disconnect, device number 2 [ 1978.730922] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(0) [ 1978.730950] vhci_hcd vhci_hcd.0: devid(196611) speed(3) speed_str(high-speed) [ 1978.954198] usb 1-1: new high-speed USB device number 3 using vhci_hcd [ 1979.072270] usb 1-1: SetAddress Request (3) to port 0 [ 1979.110312] usb 1-1: New USB device found, idVendor=148f, idProduct=3070 [ 1979.110397] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1979.110478] usb 1-1: Product: 802.11 n WLAN [ 1979.110612] usb 1-1: Manufacturer: Ralink [ 1979.110656] usb 1-1: SerialNumber: 1.0 Thank you for your help ! Regards, Mathew -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1d238b96-207c-4092-8141-87c7766e9ef2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: 4.0.1-RC2 Boot loop after install
On Thursday, 27 December 2018 20:49:14 UTC-3:30, John Goold wrote:
> On Thursday, 27 December 2018 16:24:23 UTC-3:30, Marek Marczykowski-Górecki
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Wed, Dec 26, 2018 at 09:24:01AM -0800, John Goold wrote:
> > > On Thursday, 20 December 2018 22:02:00 UTC-3:30, John Goold wrote:
> > > > Attached is screenshot, taken under my current OS, showing OS and
> > > > hardware info.
> > > >
> > > > After spending much too much time trying to track the problem down
> > > > (using the 4.0, 4.0.1-RC1 and 4.0.1-RC2 ISOs) I discovered why getting
> > > > the installer to run was failing...
> > > >
> > > > I had to unplug my external monitor (connected via an HDMI port).
> > > >
> > > > I was then able to boot the install DVD and install to an external USB
> > > > (SSD) drive (Seagate 2 TB). The install completed (supposedly
> > > > successfully), but attempts to boot from the USB drive fail.
> > > >
> > > > The boot process starts, with text being displayed starting in the top
> > > > left corner of the screen. It progresses to a point, then the screen
> > > > goes black and my computer starts to reboot.
> > > >
> > > > I have searched the mailing list and have failed to find a solution
> > > > (hours spent doing this). A lot of people seem to end up in boot-loops,
> > > > using various hardware.
> > > >
> > > > The attached file shows the hardware. The following information about
> > > > the BIOS/Firmware may be relevant:
> > > >
> > > > * Legacy Boot is enabled
> > > > * Virtualization Technology is enabled
> > > >
> > > > During the install I setup a user account. I did not enable disk
> > > > encryption (I will leave that until after I can get Qubes to boot).
> > > >
> > > > Comment: This boot-loop problem (or similar boot-loop problems) seems
> > > > to be a major issue with installing Qubes 4.x. Each time I come across
> > > > a posting about it, there seem to be different suggestions (some of
> > > > which work on the particular hardware involved) and some of which do
> > > > not.
> > > >
> > > > I believe that I tried R3.1 about a year or so ago and that it booted
> > > > alright. I cannot remember why I did not follow through on adopting
> > > > Qubes (if I could not get my external monitor working, that would be a
> > > > deal-breaker).
> > > >
> > > > Suggestions would be appreciated. I will provide any additional
> > > > information I am capable of.
> > >
> > > This thread is getting verbose, so I have replied to the original post
> > > and will attempt a brief summary of the rest of the thread (for context):
> > >
> > > Determining what is happening would be facilitated by seeing any entries
> > > in log files (assuming the boot got far enough to log anything).
> > >
> > > That means checking files on the USB drive used as the target of the
> > > install and which causes the boot-loop when attempting to boot.
> > >
> > > Since the boot is failing, I cannot look at the log files under the
> > > booted Qubes OS, so instead I attempted to look for the log files when
> > > booted into another OS (Linux Mint 19.1).
> > >
> > > Qubes is using LVM to handle allocating disk space (presumably to
> > > facilitate being able to add additional physical disks to an existing
> > > Qubes install). There appeared, at first glance to be 3 Logical volumes:
> > >
> > > pool00
> > > root
> > > swap
> > >
> > > Linux Mint mounted the LV "swap" automatically, but not the other two.
> > > The other two appear not to be "activated" and mount attempts failed.
> > > Attempts to "activate" the LVs fail.
> > >
> > > After searching the Net for information on LVM, I came across an article
> > > that helped me understand the Qubes setup better…
> > >
> > > There is one Logical Volume Group called "qubes_dom0".
> > > Within that there is a Logical Volume, "swap", that is detected and
> > > mounted automatically by my Linux Mint installation.
> > > Additionally, there is a "Thin Pool" allocated that uses up the rest of
> > > the space in the Volume Group. It is distinguished by information
> > > displayed by the lvdisplay command ("LV Pool metadata" and "LV Pool
> > > data").
> > >
> > > Within that "thin pool", a logical volume, "root" has been created that
> > > uses all the disk space currently assigned.
> >
> > Yes, that's right.
> >
> > - From what I've seen in this thread, you did it right, but the system you
> > used didn't support thin volumes. You can try Qubes installation image,
> > there is recovery mode ("Rescue" in boot menu in legacy mode).
> >
> >
> > Other things you can try is to press ESC during boot to see more
> > messages than just progress bar. If that doesn't really help, try
> > editing boot entry in grub and remove "quiet" and "rhgb" options from
> > there. This should give you more details when exactly system reboots.
> >
> > - --
> > Best Regards,
> > Marek
[qubes-users] Re: Set up a ProxyVM as a Wireguard instead of a OpenVPN gateway
Thank you all! I will try it and let you know! -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/33a4762d-745c-4f11-b117-974e68c7d1c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Set up a ProxyVM as a Wireguard instead of a OpenVPN gateway
Thank you all! I will try it and let you know! -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3aefeee8-1e10-4f56-871d-5320b85bbd17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] A way to have a qube close once all its windows are closed?
I usually have lots of windows open but am finding that after a few days I have lots of appvms open that arent being used... usually finding this when i try to open (yet another) appvm and being told I am out of memory. I have maxed out my memory slots, and shaved each appvm down to the minimum amount of memory that it needs to operate so... Is there a way, like dispVMs, to have an appvm automatically close when its not in use? "In use" defined as not having a window open? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1ad605e7-281a-3744-edd6-da27d2c9772b%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Problem installing 4.0.1 on an HP laptop model 15t-da000
billol...@gmail.com wrote on 1/12/19 7:50 PM: Folk, I am trying to install 4.0.1 on a new HP laptop model 15t-da000. It has one 250G SSD and one 1 TB SATA drives, i7 cpu, intel graphics. I have overwritten the Windows 10 default installation with KDE neon (ubuntu based), using about 100G of the 250G SSD. I am trying to make a dual boot with 4.0.1 on the remaining 130-ish Gig of the SSD. The installation seemed to start fine, though the default file system format of "LVM thin client" would not work, so I chose LVM. Installation chugged along until the end when I got the error "failed to install boot loader. To you want to continue? It will not be bootable..." or something to that effect. I indicated "yes" just to see what would happen, and it completed. On reboot, neither Qubes nor KDE neon would come up, no grub menu came up, and no explicit EFI locations came up in the BIOS boot menu -- though the two disk drives were mentioned (and would not boot). So, I reinstalled KDE neon, at which point the grub menu came up and gave me both Qubes and KDE options. Just for giggles, I chose Qubes, and the initial config screen came up. I chose the default config, and it gave me the error that the kernel file was not found and hung. KDE neon comes up fine. I tried to do an installation again, only I chose "standard partition" instead of "LVM." It didn't seem to make a difference -- it still hung at "failed to install boot loader." I stopped it at that point because I had some work to do and didn't want to have to reinstall the ubuntu partition. Any pointers would be appreciated. Thanks! billo Boot Qubes from rescue mode on the USB. Rebuild Qubes' grub and initramfs. It will be something like "sudo grub2-mkconfig -o /mnt/sysimage/boot/grub2/grub.cfg". Then reboot and try the Qubes option again from the grub menu. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/28263552-90c9-b53f-10cf-151162181050%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Install errors on Thinkpad P1 (aka X1 Extreme) with R4.0 and R4.0.1-rc2
Eric Duncan wrote on 1/13/19 3:50 AM: For the record, I am now using 4.0.1 since it released (same problems). On Monday, January 7, 2019 at 12:49:52 AM UTC-5, awokd wrote: Try temporarily disabling your wifi card for the install. Good idea! I disabled it, along with just about every device I could find. It generated a different GUI error during the Post installation qubes configuration screen, with everything disabled and disconnected: ['/usr/bin/qvm-start', 'sys-firewall'] failed: stdout: "" stderr: "PCI device dom0:00_14.3 does not exist" Once logged in, I see that Fedora in dom0 isn't detecting the 4K resolution like it has on my Thinkpad Yoga 3rd gen and Thinkpad Tablet 3rd gen devices - everything is tiny text. Running lspci shows me that 00_14.3 is described as the network controller (it has an onboard network card, along with the wifi card). Given, the PCIe device IDs could change since I have been disabling/enabling various devices at this point. But the error would seem to point to the onboard network card, even though it is Disabled in the bios. Now, I've noticed that none of the VMs startup (sys-firewall, sys-net, sys-usb). $ sudo systemctl status qubes-vm@sys-net.service This shows the exact same error message as above. Going into the bios and re-enabling everything, generates the original error in the first message in this thread. 00:1f.6 points to "Ethernet controller" 00:14.3 points to "Network controller" Going back into the bios and disabling "Wireless" and "Ethernet" devices (under Security), sys-usb is now able to start. However, sys-net and sys-firewall gives the exact same "00:14.3 does not exist" error on starting any VM. However, now it does not show under lspci with everything disable. Nor does 14.3 show up under any Qubes settings as attached to either sys-net or sys-firewall. I did another full install with everything disabled, and the same error of 14.3 does not exist keeps showing up, preventing sys-net and sys-firewall from starting. Weird, not sure how it can detect that 14.3 device with it supposedly disabled. Check sys-net's Qube Setting/Devices and remove 14.3 from the right if it's there. Leave 1f.6/Ethernet enabled and assigned if it's not causing problems, then try to start 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5fdb434f-d347-c606-b8a6-99a24b0159e4%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] VPN for Linux Dummies
On 01/11/2019 05:48 PM, seshu wrote: Chris, I recently got Nordvpn running on my 4.0.1 and I used their .deb package to install their app. The one thing I like about their app is that when it fires up it scans the hundreds of servers they have to identify the server that is best to connect to. The process that Qubes-vpn-support uses relies on the user manually deciding which of the hundreds plus servers to use right, and then creating a ln to that ovpn file? Do you think there could be a way to streamline or automate which ovpn file to use? Thanks! Its impossible to tell which servers for a given region a VPN provider considers to be 'best'. Some providers like PIA allow you to specify a region by domain name, and that domain name represents a bank of servers from which a server is chosen at connection time; it appears to be a standard load-balancing configuration. If you don't want to use one server IP all the time, you could add many IPs to the conf file along with 'remote-random' which will choose one randomly. Alternately, you could see if NordVPN has regional domain names and use one of those in your conf. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/420809af-4d30-c07a-6325-1af49ed50899%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel panic due to Ctrl+C interrupted dom0 update and reboot
Le samedi 12 janvier 2019 21:43:21 UTC+1, simon...@gmail.com a écrit : > Hi, > > Error message : > > [3.680649] Call Trace: > [3.680707] dump_stack+0x5c/0x85 > [3.680764] panic+0xe4/0x252 > [3.681184] mount_block_root+0x35b/0x52c > [3.681601] ? do_early_param+0x16e/0x16e > [3.682018] prepare_namespace+0x278/0x2d5 > [3.682434] ? do_early_param+0x16e/0x16e > [3.682851] kernel_init_freeable+0x2e8/0x32d > [3.683270] ? rest_init+0xb0/0xb0 > [3.683685] kernel_init+0xa/0x101 > [3.684101] ret_from_fork+0x35/0x40 > [3.684536] Kernel Offset: disabled. > > So, I booted into recovery mode prompt from a USB key (Troubleshooting and > Rescue a Qubes system (read-write choice). > > It seems that I can’t boot an older kernel version. > > # ls /boot > initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 > # > > I don't really know what to do to fix it. > > Your help will be greatly appreciated! > > Thank you a lot for your valued assistance Fixed :-) grub.cfg corrupted. Missing two lines : echo'Loading initial ramdisk ...' module --nounzip /initramfs-4.14. 74-1.pvops.qubes.x86_64.img I found a backup of the grub.cfg file in user's home directory (dated Sept. 26 2018). Fortunately I make backups. Reboot with an older kernel version and : sudo dracut /boot/initramfs-4.14.74-1.pvops.qubes.x86_64.img 4.14. 74-1.pvops.qubes.x86_64 sudo grub2-mkconfig -o /boot/grub2/grub.cfg It is now fully operationnal. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/69b31a54-d178-44a4-920d-edb2cd800083%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Set up a ProxyVM as a Wireguard instead of a OpenVPN gateway
On 01/12/2019 02:18 PM, Chris Laprise wrote: On 01/12/2019 10:47 AM, Ivan Mitev wrote: On 1/12/19 5:16 PM, Daniil Travnikov wrote: Does anyone know how could be configured the Wireguard (https://www.wireguard.com/) in Proxy VM? Maybe do you know some doc like https://www.qubes-os.org/doc/vpn/ where it is already described step by step? I understand that this is new technology, but maybe someone knows which OS is more preferable and what is the first step in the settings? The following thread might be helpful, although it's a bit old: https://groups.google.com/d/msg/qubes-users/MQaePIslfY8/k0s65DfaCQAJ Yeah, that's old and not really useful now. Currently you can get a full Qubes wireguard setup using Qubes-vpn-support, which has been tested with Mullvad's wireguard service: https://github.com/tasket/Qubes-vpn-support/ To change it from openvpn to wireguard after installation in a "proxy" provides-network appVM, look in the /rw/config/qubes-vpn-handler.service.d directory and rename '10_wg.conf.example' to '10_wg.conf'. You may also have to create your proxy VM as a standalone and run "qvm-prefs vmname kernel ''" to blank out the kernel setting. Then boot and install the 'wireguard' package. BTW, I'm working on an update to the wireguard page that is shorter and includes Qubes-vpn-support: https://github.com/tasket/Qubes-vpn-support/wiki/Wireguard-VPN-connections-in-Qubes-OS -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2be904ef-c9fb-c10d-7e4e-b5d80aacf33b%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel panic due to Ctrl+C interrupted dom0 update and reboot
Le samedi 12 janvier 2019 21:43:21 UTC+1, simon...@gmail.com a écrit : > Hi, > > Error message : > > [3.680649] Call Trace: > [3.680707] dump_stack+0x5c/0x85 > [3.680764] panic+0xe4/0x252 > [3.681184] mount_block_root+0x35b/0x52c > [3.681601] ? do_early_param+0x16e/0x16e > [3.682018] prepare_namespace+0x278/0x2d5 > [3.682434] ? do_early_param+0x16e/0x16e > [3.682851] kernel_init_freeable+0x2e8/0x32d > [3.683270] ? rest_init+0xb0/0xb0 > [3.683685] kernel_init+0xa/0x101 > [3.684101] ret_from_fork+0x35/0x40 > [3.684536] Kernel Offset: disabled. > > So, I booted into recovery mode prompt from a USB key (Troubleshooting and > Rescue a Qubes system (read-write choice). > > It seems that I can’t boot an older kernel version. > > # ls /boot > initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 > # > > I don't really know what to do to fix it. > > Your help will be greatly appreciated! > > Thank you a lot for your valued assistance I tried it without success : https://deniszanin.com/bad-grub-fixing-qubes-boot-missing-on-uefi/ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/57d395b1-5af5-49d9-b951-95ac54b375c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] fedora-29-minimal sys-net/firewall problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Jan 11, 2019 at 09:59:37PM -0800, rumsey.anth...@gmail.com wrote: > Thanks to Ivan, I figured it out (with a bit of luck). > > After comparing packages in his working template to my own, I first tried to > install: > > dbus-glib > ipcalc > iproute > iproute-tc > iputils > > That fixed it as far as I can tell. I now have a working sys-net and > sys-firewall with the fedora-29-minimal template. I'm assuming the ip* > packages were the key, but I don't really have any idea. Yes, it's iproute. Similar problem happened to Debian template[1] and it was fixed there, but apparently Fedora is also affected. I'll add relevant dependency. [1] https://github.com/QubesOS/qubes-issues/issues/4411 - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw7IWMACgkQ24/THMrX 1yzOFgf6AhFaa5Y+g2PHqKiSH908UIPM99+Xwf3lMlb/ISDfuX7EUsyqBLXI9yak UGjXuG7dcNs+QD9lESTCPxkYS86c1AQWb9zyPEe/Q2n1uJgYGzktEdyD6w51in/3 spZGvNdicSVDFUHeWyr+rdAR5feQETSebecxp3fha+GlG4D8tcDSZJzG13uZMZXk l9zetIJToWa5DANSEfdw70F1UpIt4BEBa8UxJJHNP3GOwYMulXFVLN6BJ8eJ3LMN PFfcDf5gK3OMTaLYu+5uj8WUf8dtQGgDwCd1Dzfzswmai8sMQ2EyzQEbuHuFQxvt sSIsnj4x6zK+BOZ/yqZwjpVRMDBwAQ== =py4N -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190113113043.GE6577%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] "Qubes Update" icon (Sun Looking icon on top right)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Jan 12, 2019 at 08:47:01AM -0800, 22...@tutamail.com wrote: > Just used this feature again...Debian-9, Fedora-29 and Dom0 updates(or lack > of) went fine i.e. My Fedora templates seemed to update and no updates were > needed for Dom0 or my Debian templates. > > My Whonix-14-GW and -WS however did deliver an error that might be related to > what you refer to Marek. The sun icon gives me the following > error(abbreviated): > > File "/var/tmp/.root_62a99a_saltimport salt.modules.cmdmod > File "/var/tmp/.root_62a99a_saltimport salt.util.http > File "/var/tmp/.root_62a99a_saltimport salt.util.events > > ... > ImportError: No module named concurrent...CancelledError > stdout: > > I manually updated the whonix-gw and -ws using the Qubes Manager OK. > > Any chance some one can share the commands to allow me to update using the > "sun icon"? Its nice to check all templates for updates and have them run in > the back ground one-by-one. I thought this would crash my system but worked > pretty slick appart from the whonix-gw and -ws error I got... You need to install python-concurrent.futures package there. Open terminal in whonix-gw (and -ws) and execute: sudo apt install python-concurrent.futures - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw7HMwACgkQ24/THMrX 1yxVWgf/WlABy9S2QcV8nlcNe82GoAjKqtxct7ZkwhSKzINrA0x/5nbJ9xcB2uEY Lam73TDc3l4ma4PaG/EdfRyIbFgO3Yeus6tKe36xCtdZYpp5JHSWaEOXiEyLheRP /hPizdgfyEV7iQXm8pM2oaV00r8nGyXH8P62br3wcbEXjd19bAtKPEKOrfhKHJh0 DodMoo0vzPlEm6fpirlQ/tZqrUk88yfLkAAPWNVTfUbgbE5Vl78w/wO1u0IVEXLF stf/qzpkvsf7MXz8OYUd9+h2dqWLsvoqGiS0x26kW66BcsaXYKqyJUAQAdTstYDN rU86N2eiuYUNQKT1ZdOA5AEZVrwaDw== =vXOe -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2019011307.GD6577%40mail-itl. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel panic due to Ctrl+C interrupted dom0 update and reboot
Le samedi 12 janvier 2019 21:43:21 UTC+1, simon...@gmail.com a écrit : > Hi, > > Error message : > > [3.680649] Call Trace: > [3.680707] dump_stack+0x5c/0x85 > [3.680764] panic+0xe4/0x252 > [3.681184] mount_block_root+0x35b/0x52c > [3.681601] ? do_early_param+0x16e/0x16e > [3.682018] prepare_namespace+0x278/0x2d5 > [3.682434] ? do_early_param+0x16e/0x16e > [3.682851] kernel_init_freeable+0x2e8/0x32d > [3.683270] ? rest_init+0xb0/0xb0 > [3.683685] kernel_init+0xa/0x101 > [3.684101] ret_from_fork+0x35/0x40 > [3.684536] Kernel Offset: disabled. > > So, I booted into recovery mode prompt from a USB key (Troubleshooting and > Rescue a Qubes system (read-write choice). > > It seems that I can’t boot an older kernel version. > > # ls /boot > initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 > # > > I don't really know what to do to fix it. > > Your help will be greatly appreciated! > > Thank you a lot for your valued assistance file is empty. sh-4.3# pwd sh-4.3# /mnt/sysimage/boot/efi/EFI/qubes sh-4.3# ls -al xen.cfg -rw-r--r-- 1 root root 0 Jan 6 11:14 xen.cfg It seems that the same errors that : https://github.com/QubesOS/qubes-issues/issues/3915 I don't know how to handle it without reinstalling. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bee3a2d9-c313-4630-b4e2-c0cd3ac8cf10%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Smart cards, split GPG, and timing attacks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, Jan 12, 2019 at 12:27:04PM -0800, demioben...@gmail.com wrote: > That makes sense. How should one best handle GitHub accounts? One per > project? GitHub does not seem to allow per-project SSH keys, sadly. Actually, you can have separate per-repository key, called deployment key. But you can't re-use the same key for multiple repositories, so if you have a project with 5 repositories, you need 5 keys... - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw7EqQACgkQ24/THMrX 1ywzWgf/c4ruiUidk5WARKvLGT0/2dM8Im17JJJy44+LaBw8EnK43YqxK9TK2fxz kG9K7jwT7w5Ym8oi7mLDpTO0XmV4usf15Vvi2PUUQBIWdJNxJCIViwaFMY0zA79v TKa/9EAbxi2JrZ16iP349yL1OWGxs2+bN+q7Mt3qd46BwQiUNHFJMKcxXXZ/iBGw G11XgeB4bllW7HyjR9nfNUEVl38oTVlpoPoYq8NZuLC011TafMhRSFlEQQto+MkD l9a600ifQCprSqWiUge9QiiJO3rtknTx7NnNdwgFnpfFMm2yIURGMVyJ9i3VxyE9 B0GWaB7FTzmISkNjnmIwuZOgA1niLg== =+lka -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190113102748.GC6577%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] xsel via qrexec fails to set clipboard, "conversion refused"
Hello Dave, On Fri, 28 Dec 2018 at 19:28, Dave C wrote: > I've written a qrexec script which, among other things, attempts to place > something into the clipboard, using `xsel`. > xsel fails, with error: "xsel: Conversion refused" > I don't know what xsel is doing. I have written a script which uses xclip (which needs to be installed as an additional package). Maybe you can get some info from there: Copy content from the dom0clipboard to an AppVMs clipboard including a notification https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-xclip-to-vm --- --- --- #!/bin/bash # name : qvm-xclip-to-vm # purpose: Copy the clipboard of dom0 to the clipboard of an appvm # Usage : qvm-xclip-to-vm AppVM=$1 xclip -o | qvm-run --pass-io $AppVM 'cat | xclip -selection clipboard &>/dev/null' notify-send --urgency low --icon image --expire-time=5000 "$0" "Clipboard pasted from dom0 to $AppVM" --- 8< --- --- --- The other way around: https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-xclip-from-vm Additionaly there's a script to do the same for screenshots: https://github.com/one7two99/my-qubes/blob/master/home/bin/qvm-screenshot-to-clipboard.sh O. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAJ3yz2ufc3_gzpKRH7nqCJWSFLkdg_Zp4MJXyWqKeVCXFuu03Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: screen brightness
On Friday, December 21, 2018 at 2:44:36 PM UTC-8, haaber wrote: I run Q4 on a dell notebook.The "screen brightness" key-combination leans qubes to show a screen brightness icon, but I cannot change brightness at all.Is this maybe a setting somewhere? Especially in evening hours this is really a pain in the eye ... Bernhard The key combination fn-f5 lowers brightness on my laptop. (fn-f5 raises it) But the lowest brightness available through the keyboard shortcut is still too bright at night. I find that brightness can be further lowered with the following, in dom0: xrandr --output eDP1 --brightness .75 Use `xrandr-q` to figure out what to replace "eDP1" with. And try .5 or lower to fine tune your brightness. That is awesome! Especially since my brigtness-key is dysfunctional :)) Thank you. Bernhard -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/efa1563a-f874-e9cd-dc09-d77d9bb07279%40web.de. For more options, visit https://groups.google.com/d/optout.
