[qubes-users] NO SOUND after debian 9 (stretch) upgrade + workaround
Hi, I wonder if anyone using debian 9 upgrade recently facing the same problem. Luckily, I have the template backup before doing this major upgrade on stretch. Upgrading the template by 'apt upgrade -t stretch-testing' to enable latest qubes candidates to grab latest 'qubes-gui-agent' doesn't solve this issue yet. ii libpulse-mainloop-glib0:amd64 10.0-1 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 10.0-1 amd64PulseAudio client libraries ii libpulsedsp:amd64 10.0-1 amd64PulseAudio OSS pre-load library ii pulseaudio 10.0-1 amd64PulseAudio sound server ii pulseaudio-utils 10.0-1 amd64Command line tools for the PulseAudio sound server PulseAudio daemon failed to start after this major upgrade. E: [pulseaudio] main.c: Daemon startup failed. So, right now I will hold the old 'pulseaudio 9.0' package until Marek push the right tools on stretch-testing repo. -- I have found the solution for this after looking around at 'qubes-gui-agent' source code. It seems that 'module-vchan-sink.so' doesn't appeared on '/usr/lib/pulse-10.0/modules/' after upgrading pulseaudio 10 on Debian 9. What I did was just copying the module to the right directory. After that starting back the PulseAudio daemon and it's working as usual. Until the new 'qubes-gui-agent' available on the 'stretch-testing' repo. I think this method will just work for me right now. Hope this help everyone who got the same issue like above. -- 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/d359cb50-0f17-f513-dabb-1911d2738d1d%40gmail.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] No SOUND after debian 9 (stretch) upgrade
Hi, I wonder if anyone using debian 9 upgrade recently facing the same problem. Luckily, I have the template backup before doing this major upgrade on stretch. Upgrading the template by 'apt upgrade -t stretch-testing' to enable latest qubes candidates to grab latest 'qubes-core-agent' doesn't solve this issue yet. ii libpulse-mainloop-glib0:amd64 10.0-1 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 10.0-1 amd64PulseAudio client libraries ii libpulsedsp:amd64 10.0-1 amd64PulseAudio OSS pre-load library ii pulseaudio 10.0-1 amd64PulseAudio sound server ii pulseaudio-utils 10.0-1 amd64Command line tools for the PulseAudio sound server PulseAudio daemon failed to start after this major upgrade. E: [pulseaudio] main.c: Daemon startup failed. So, right now I will hold the old 'pulseaudio 9.0' package until Marek push the right tools on stretch-testing repo. -- 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/d0ed30b5-d32a-1ac6-1d6b-bdb4320a8e0e%40gmail.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: I have a bank vm, how do you restrict
On Saturday, February 11, 2017 at 9:08:56 PM UTC-5, Andrew David Wong wrote: > > You should try to the method I described here: > > https://groups.google.com/d/topic/qubes-users/fSiFkQeoqGE/discussion > The difference being instead of google.com use 74.125.192.113, 74.125.192.100, 74.125.192.102, 74.125.192.138 etc? And instead of accounts.google.com use 172.217.5.237? -- 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/82e95bd9-909b-47e3-a8f0-445f739a2148%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] windows7 hangs on installation
On Sunday, February 12, 2017 at 2:33:53 AM UTC, griz...@gmail.com wrote: > On Friday, October 28, 2016 at 1:36:56 PM UTC-5, scheu...@googlemail.com > wrote: > > Thanks for your answer. > > I wait about 6 hours but nothing happens. > > Of course you´re right. I just installed the QWT to dom0. > > Did you figure this out? I'm seeing this same problem now. These instructions worked for me. https://github.com/QubesOS/qubes-issues/issues/2488 -- 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/85b957aa-bf42-4283-a450-47dd151a6c09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] windows7 hangs on installation
On Friday, October 28, 2016 at 1:36:56 PM UTC-5, scheu...@googlemail.com wrote: > Thanks for your answer. > I wait about 6 hours but nothing happens. > Of course you´re right. I just installed the QWT to dom0. Did you figure this out? I'm seeing this same problem now. -- 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/6fd794d8-949f-4502-9836-bb64f8940554%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Two factor LUKS decryption
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-02-11 05:06, Alex Clark wrote: > Hi, Is possible to obtain something like that: > https://www.masarlabs.com/article/two-factor-luks-decription/ in > Qubes Os and after that install Anti Evil Maid protection? > Regards, Alex > See: https://www.qubes-os.org/doc/yubi-key/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYn8cdAAoJENtN07w5UDAwNCoQAKqWEHlX9WgzZM8aUdsuqZC1 sPVL8P7ihP4thyFiHnxfS527ASb8UxnpXFwZCnyEmtp103ons4jjrGIlB/YxoHxQ e7TuG6gN9wHn1UkW4eV1QG2v/99wV4aIl5qm8wtj5zhR+pkCUsHNYyfHzCzohA9L dWkvPm0+tz++GZG88LFauxPsztGupUMXVPSexdOYCHaz+i5xEjuisyTA3YQCqnAO rbekIMv2jDlE2VQVPrWXcYwqYfNtgSK3+lhMgS5bBtHVgWF94nJHBE8NcSkkv5UP yq6HxjM++LuI+bez3Yo5uhTi3dzTXIXtbvTrzaKJpoRM6gLY1GlK5r+c6zwlH2WL MgPVA3IG4b/1cPojeWKsV2iEt2bCymUGsMNtJJEPhANG+WMnHHzO6DXFBmeK4bSz R0Xa9y3jpC4aiiO1XvFxjqFaeQKrfnvvXHjHFc1bS1zRtkkPbFzlw8l3nx98tpgf CyfJZDlSu/IJxXzoFUgAwtGyqYQEnf3K3QiD5woIT7uBfboPdjl+nioKmsh3CIzW wdSTYt27GPrivLBUDttywfNOo+Xb38+nnDeyqCOViUkELVI2xn3/Rd+cofC6CFDu hosvMHJ/BOmEekDLHc1JTTJinXjtzeJk0d+yjUlb9q3QEOrNYqlV/IfgjFjv+Lqk 88ueF0ZB6/tiA/TmzoNN =bBsl -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/8cab6a37-18f5-8a9e-a9cd-dbd98468f39d%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Running qvm-create-default-dvm against fedora-24-minimal hangs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-02-11 04:25, qu...@posteo.de wrote: > Hi, > > On 31.01.2017 19:30, qu...@posteo.de wrote: >> I have tried to to create my own disposable vm based on the minimal >> Fedora 24 template and it always hangs during "Waiting for DVM >> fedora-24-minimal-dvm ...". The only difference to the original rpm >> template is sudo and the salt vm package. >> >> If I use the regular fedora-24 template it works fine. >> >> So which package or service am I missing? >> >> Thx in advance > > I have finally figured out the missing package. It is "perl-Encode". > With this the dvm creation process runs through. Can somebody add this > to the "Customize disposable vm Wiki"? > > Regards > Thanks. Added: https://github.com/QubesOS/qubes-doc/commit/308fa866e9533ccfb77b8c6c1b7b0f57446c7f85 - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYn8bXAAoJENtN07w5UDAwRnYQAK0NgJnnrqSE8+9ikoo6tm3T F+MTFmSFpct81nxoXR69X7ZnOeKpBEBtwoPZAQ/VoVOJo6VF1HrP/NytvisLM0Le H4ttA2mjFlNfx57Zk+apRViPjotwCfRpNCYTNLoWNPl1XC/uB4q3a+IW0+Hx5sVi tHlfNbLQ20x2JMVO5Ol6UuRWAbupNgDTagkPENqxA3P2ViOsVXR/5G809LFbBiuh o+yKlWoDDmXb8GkvhJ0YrO/SiA+W7fwYehTUuN7vjhYFMHv4NgAoUOiIiXgOdUyS J0C02irknM13aAtAGgOgNh8Uy8z5lRsU620dTxmHiFrToMd2p8GORU7a6wfOxbnh JfkoUjdBU7MgVt8bL2Q73Yu3EDAsT8jJs9+vzq1pYEYGQy6BRgNPXfb5FzTMupIV OBOl98biXbGsvq+2s7b1jZ97OmLuxv8dQMPIwJmdbA1xaYad9dNkz43f+CKy291b ZTjDGD05JOhAnlNTHobRh+MlcVl9eow2d2iJETM6+mD6qEs4x7kEK/R7akRYmEDf GHdfP9NDTExJArYF9JKu2XqMCmfhfZGMOlH7k4NfczIThgKOK0f++0867Zv5d1jZ M/N2ZrR9hOO5arfliFotmIu0WEcCwZST3cx5OVZs9Wq+LeXIT7YjxxFFUijWSr5D FymSXT865UQpaqKwoV6A =bgQJ -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/3d08a9ad-d5ba-f099-fe61-e931eb9062a3%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: I have a bank vm, how do you restrict
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-02-11 17:21, elsiebuck...@gmail.com wrote: > I tried tinyproxy, I'm fairly certain proxies in general willNOT > work with https. Am I right about this? Or have I not done > something right? > You should try to the method I described here: https://groups.google.com/d/topic/qubes-users/fSiFkQeoqGE/discussion - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYn8OnAAoJENtN07w5UDAwAG4QAM8LURn5Jt98VI1Q8HVMKfpA pCQ9zBg5NBA85rjPLXXhq1uLcmKloIHEnBTLqWboUQqDMtM5MToNzzs/fBNkjuUw HkAJfkpazjBNNvtS8E5XX77O7GTylJKtksk2iS6E0+RInyZAHrQs1c5tBLuss321 8hjgKQ75pQHQt/mqurV9YRfxJoxZOlCotzfXqWwoHEaRhsDBGxuius9DtHrs6Wqf FVeHUYAZxR4ZTsmBUAEgwMwRguldUwIXZWf8ueYt+nYcCYzADXIet4YwqyA1wbbl DZUxJn/J7CT1SReUBmlWzH+e45eTJxYAD5TDFJ5V8x39nTYSc/zJ1yTUPTPd6BgR boQ61/s2DECsN6gB8SXu1V/FpMOxK0YHaYyEJMxinH4Vph8AX6lcJR3CWD6L5hhk zsYG2OYtGbCq9sEUQrhmyFKR+sh5TBE0dzn+bFVh6jFazZx04nXaInowV3ivS/tG 3SLiWhW/vVJwad+tGI1oMzlIFqf9jjOnGsJnwzKaSXZLbzG6exbCXQ7s5cGB2rEv ZhAYDZd5krMkcGsJGrP0uz8JvbAlTPuORzwK+CPLYwPobSwt+1bobnK1AYVhX85f vI88PBNkK1BbS9oJtT3TACPtdZa4KGrY3ZO9edP07mKN2JM5OlDhjHSc6pQg3vyX fvAOQ9yVNBVNlVL7/PaI =dByr -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/10b6acc8-3317-62ed-99fa-d9a724522217%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: I have a bank vm, how do you restrict
I tried tinyproxy, I'm fairly certain proxies in general willNOT work with https. Am I right about this? Or have I not done something right? -- 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/bb43923c-e89d-46fd-9e2a-a501a93da4a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot install Qubes 3.2 - black screen of death
On Saturday, February 11, 2017 at 4:03:53 PM UTC-5, raah...@gmail.com wrote: > On Saturday, February 11, 2017 at 11:38:29 AM UTC-5, qubesn...@gmail.com > wrote: > > I am attempting to install Qubes, version 3.2, never having used any prior > > versions. > > > > My computer is custom-built with the following components: > > > > CPU: Intel Core i7-7700K Quad-core 4.2 GHz LGA 1151 Processor > > Motherboard: GIGABYTE Aorus GA-Z270X-Gaming 7 (rev 1.0) > > RAM: G.SKILL TridentZ Series 64GB > > Primary HDD: Samsung 850 EVO 2.5" 500GB 3-D Vertical Internal SSD > > CD-ROM: Pioneer 16x BD-R Blu-ray Burner (BDR-209DBK) > > > > I tried installing using the following types of media: > > > > -ISO burned to DVD > > -ISO burned to USB using Rufus in Windows and selecting dd mode > > -ISO burned to USB using dd in Debian > > > > When none of these worked, I started searching this newsgroup for similar > > problems. I found one suggestion that I tried, which was to add > > "GRUB_CMDLINUX_XEN_DEFAULT iommu-no-igfx" to grub.cfg - I could not do this > > one because I could not get the USB device out of read-only mode > > > > I removed the "quiet" option from the install, but still no success > > > > Afterward, I disabled VT-d in BIOS, but again, no success > > > > Every time, I get the splash screen with the options for installation. For > > any option I pick, it gets to the point where I believe Xen is launching > > the graphics for the installer. At that point, the screen goes completely > > black. In the case where I use the DVD, the drive stops spinning, and > > nothing else happens. > > > > I am at a loss, and any help would be greatly appreciated. > > hmm tried a diff usb stick, checked the signatures of the downloaded iso, > used only onboard gpu unplug pcie one. check gpu bios options,unplug all > other usb devices, check mobo for options, update mobo bios, does the > baremetal fedora 24 installer work? > > That board looks like it should work good with qubes, if I can think of > anything else I'll post back. > > Also I followed your advice on Fedora and was able to easily install Fedora Workstation 25. Not sure how to progress from here. Perhaps the disk needed to be formatted prior to installing Qubes? I am guessing at this point. -- 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/ec08a469-3c4f-4346-a102-fac42c37c2c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qvm-run fails silently with chromium
On Sat, Feb 11, 2017 at 09:59:36AM -0800, m...@lamarciana.com wrote: > > Yes, I know - that's why I said "using bash". > > You are using zsh, so you said, so you need to put the path in ~/.zprofile > > > > For example, with simple script 'logit' in home/user/newpath: > > > > qvm-run -a -p qube logit > > fails with "logit: not found" > > > > append path=('home/user/newpath' $path) to ~/.zprofile > > Then qvm-run succeeds > > Yeah, you are right, this works. Thank you very much. But I don't quite > understand. I guess that I'm opening an interactive non-login shell, but > ~/.zprofile is sourced while ~/.zshrc isn't, while, from > http://zsh.sourceforge.net/Intro/intro_3.html: > > > `.zshrc' is sourced in interactive shells > > > [...] > > > `.zlogin' is sourced in login shells. [...] `.zprofile' is similar to > > `.zlogin', except that it is sourced before `.zshrc' > try this: qvm-run -a -p qube "echo $0" and: qvm-run -a -p qube "ps aux" You may be surprised. -- 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/20170211233845.GC14849%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] VPN/Firewall Redundant?
On Sat, Feb 11, 2017 at 10:35:20AM -0800, jimmy.dack...@gmail.com wrote: > Assuming one wants to have all internet traffic go through a VPN, is having > both a VPN proxyVM and a firewall VM redundant? In other words, does the > proxyVM with the VPN running in it serve as a firewall just as well? Or is > there still some reason to have two separate VMs in this use case? > This will depend on what configuration you have on the VPN Proxy. It would be possible to combine firewall and VPN Proxy in one qube, particularly if you were always using the same downstream qubes attached to the proxy. This would be straightforward and could be done with a custom set of rules loaded in /rw/config/rc.local, either directly or using iptables-restore. imo a cleaner approach is to use "native" Qubes firewall capability - there isn't a great overhead in doing so, and it should minimise the risk of leaks. -- 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/20170211232613.GB14849%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: What? Can I access a windows USB drive?
Ok, did that. What I get is Computer TI10673200G /dev/sda4 Networks Windows Network When I left click TI106(...) I get nothing. When I right click, the menu says open, open in a new tab, open in a new window, and Mount. Nothing happened. What should I try now? -- 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/8bf12d18-1e7d-43e7-b01a-83402ec2ec57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: I have a bank vm, how do you restrict
Well I hate to beat a dead horse... Nether vm(s) will connect without refreshing several multiple times. This isn't acceptable. I prefer dnsmasq rather than some firefox addon. Actually, I'm pretty sure dnsmasq won't do in this case. Some other solution... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/4dc5ef44-268d-4392-bd76-9f4273ef3650%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ubuntu template
On Sat, Feb 11, 2017 at 01:38:15PM -0800, trul...@gmail.com wrote: > Thankx to all for the answers. It what i can do (some logs) > > > [user@test qubes-builder]$ sudo make vmm-xen-vm > Currently installed dependencies: > git-2.5.5-1.fc23.x86_64 > rpmdevtools-8.9-1.fc23.noarch > rpm-build-4.13.0-0.rc1.13.fc23.x86_64 > createrepo-0.10.3-3.fc21.noarch > debootstrap-1.0.87-1.fc23.noarch > dpkg-dev-1.17.27-1.fc23.noarch > python-sh-1.11-1.fc23.noarch > dialog-1.3-4.20160424.fc23.x86_64 > dpkg-dev-1.17.27-1.fc23.noarch > debootstrap-1.0.87-1.fc23.noarch > DEBUG > Repo Variables > ─── > SRC_DIR: qubes-src > CHROOT_DIR: /home/user/qubes-builder/chroot-xenial > CHROOT_REPO_DIR: chroot-qubuntu > CHROOT_DEBIAN_DIR: /home/user/qubes-builder/chroot-xenial//debian-vm/debian > BUILDER_REPO_DIR: > /home/user/qubes-builder/qubes-packages-mirror-repo/xenial > ─── > Chroot Variables > ─── > DIST_BUILD_DIR: /home/user > DIST_SRC: > DIST_SRC_DEBIAN_DIR: /debian-vm/debian > ─── > Build Variables > ─── > DEBIAN_PARSER: > /home/user/qubes-builder/qubes-src/builder-debian//scripts/debian-parser > DEBIAN_PLUGIN_DIR: /home/user/qubes-builder/qubes-src/builder-debian/ > OUTPUT_DIR: pkgs/xenial > PACKAGE_LIST:debian-vm/debian > DISTRIBUTION:qubuntu > DIST:xenial > DEBIANVERSION: xenial > UPDATE_REPO: > REPO_SUFFIX: > DISTRIBUTION_CAP:Qubuntu > REPO_PROXY: > APT_GET_OPTIONS: > CHROOT_ENV: BACKEND_VMM=xen > > # Make sure repo directory exists > -> Preparing xenial build environment > -> Installing qubuntu build chroot... > I: Retrieving InRelease > I: Checking Release signature > I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32) > I: Retrieving Packages > I: Validating Packages > I: Resolving dependencies of required packages... > I: Resolving dependencies of base packages... > I: Checking component main on http://archive.ubuntu.com/ubuntu... > I: Validating adduser 3.113+nmu3ubuntu4 > I: Validating apt 1.2.10ubuntu1 > I: Validating apt-utils 1.2.10ubuntu1 > I: Validating base-files 9.4ubuntu4 > I: Validating base-passwd 3.5.39 > I: Validating bash 4.3-14ubuntu1 > I: Validating bsdutils 1:2.27.1-6ubuntu3 > I: Validating busybox-initramfs 1:1.22.0-15ubuntu1 > I: Validating bzip2 1.0.6-8 > I: Validating console-setup 1.108ubuntu15 > I: Validating console-setup-linux 1.108ubuntu15 > I: Validating coreutils 8.25-2ubuntu2 > I: Validating cpio 2.11+dfsg-5ubuntu1 > I: Validating cron 3.0pl1-128ubuntu2 > I: Validating dash 0.5.8-2.1ubuntu2 > I: Validating debconf 1.5.58ubuntu1 > I: Validating debconf-i18n 1.5.58ubuntu1 > I: Validating debianutils 4.7 > I: Validating dh-python 2.20151103ubuntu1 > I: Validating diffutils 1:3.3-3 > I: Validating distro-info-data 0.28 > I: Validating dpkg 1.18.4ubuntu1 > I: Validating e2fslibs 1.42.13-1ubuntu1 > I: Validating e2fsprogs 1.42.13-1ubuntu1 > I: Validating eject 2.1.5+deb1+cvs20081104-13.1 > I: Validating file 1:5.25-2ubuntu1 > I: Validating findutils 4.6.0+git+20160126-2 > I: Validating gcc-5-base 5.3.1-14ubuntu2 > I: Validating gcc-6-base 6.0.1-0ubuntu1 > I: Validating gnupg 1.4.20-1ubuntu3 > I: Validating gpgv 1.4.20-1ubuntu3 > I: Validating grep 2.24-1 > I: Validating gzip 1.6-4ubuntu1 > I: Validating hostname 3.16ubuntu2 > I: Validating ifupdown 0.8.10ubuntu1 > I: Validating init 1.29ubuntu1 > I: Validating init-system-helpers 1.29ubuntu1 > I: Validating initramfs-tools 0.122ubuntu8 > I: Validating initramfs-tools-bin 0.122ubuntu8 > I: Validating initramfs-tools-core 0.122ubuntu8 > I: Validating initscripts 2.88dsf-59.3ubuntu2 > I: Validating insserv 1.14.0-5ubuntu3 > I: Validating iproute2 4.3.0-1ubuntu3 > I: Validating iputils-ping 3:20121221-5ubuntu2 > I: Validating isc-dhcp-client 4.3.3-5ubuntu12 > I: Validating isc-dhcp-common 4.3.3-5ubuntu12 > I: Validating kbd 1.15.5-1ubuntu4 > I: Validating keyboard-configuration 1.108ubuntu15 > I: Validating klibc-utils 2.0.4-8ubuntu1 > I: Validating kmod 22-1ubuntu4 > I: Validating less 481-2.1 > I: Validating libacl1 2.2.52-3 > I: Validating libapparmor1 2.10.95-0ubuntu2 > I: Validating libapt-inst2.0 1.2.10ubuntu1 > I: Validating libapt-pkg5.0 1.2.10ubuntu1 > I: Validating libatm1 1:2.5.1-1.5 > I: Validating libattr1 1:2.4.47-2 > I: Validating libaudit-common 1:2.4.5-1ubuntu2 > I: Validating libaudit1 1:2.4.5-1ubuntu2 > I: Validating libblkid1 2.27.1-6ubuntu3 > I: Validating libbsd0 0.8.2-1 > I: Validating libbz2-1.0 1.0.6-8 > I: Validating libc-bin 2.23-0ubuntu3 > I: Val
[qubes-users] Re: Cannot install Qubes 3.2 - black screen of death
On Saturday, February 11, 2017 at 4:03:53 PM UTC-5, raah...@gmail.com wrote: > On Saturday, February 11, 2017 at 11:38:29 AM UTC-5, qubesn...@gmail.com > wrote: > > I am attempting to install Qubes, version 3.2, never having used any prior > > versions. > > > > My computer is custom-built with the following components: > > > > CPU: Intel Core i7-7700K Quad-core 4.2 GHz LGA 1151 Processor > > Motherboard: GIGABYTE Aorus GA-Z270X-Gaming 7 (rev 1.0) > > RAM: G.SKILL TridentZ Series 64GB > > Primary HDD: Samsung 850 EVO 2.5" 500GB 3-D Vertical Internal SSD > > CD-ROM: Pioneer 16x BD-R Blu-ray Burner (BDR-209DBK) > > > > I tried installing using the following types of media: > > > > -ISO burned to DVD > > -ISO burned to USB using Rufus in Windows and selecting dd mode > > -ISO burned to USB using dd in Debian > > > > When none of these worked, I started searching this newsgroup for similar > > problems. I found one suggestion that I tried, which was to add > > "GRUB_CMDLINUX_XEN_DEFAULT iommu-no-igfx" to grub.cfg - I could not do this > > one because I could not get the USB device out of read-only mode > > > > I removed the "quiet" option from the install, but still no success > > > > Afterward, I disabled VT-d in BIOS, but again, no success > > > > Every time, I get the splash screen with the options for installation. For > > any option I pick, it gets to the point where I believe Xen is launching > > the graphics for the installer. At that point, the screen goes completely > > black. In the case where I use the DVD, the drive stops spinning, and > > nothing else happens. > > > > I am at a loss, and any help would be greatly appreciated. > > hmm tried a diff usb stick, checked the signatures of the downloaded iso, > used only onboard gpu unplug pcie one. check gpu bios options,unplug all > other usb devices, check mobo for options, update mobo bios, does the > baremetal fedora 24 installer work? > > That board looks like it should work good with qubes, if I can think of > anything else I'll post back. > > Also Hi, Thank you for writing back. I have not tried a different USB stick, as I don't have any others large enough for the image, however I have downloaded the ISO / checked all signatures & digests on two separate occasions. They checked out as good both times. I also burned the ISO to 2 different DVDs. I have only been using the on-board video, and don't have any separate PCI-E cards for the system. I only have the mouse & keyboard plugged in as USB when I am booting from the DVD. I will check on the GPU BIOS options again, but I couldn't really find much to change... As far as updating the BIOS, I went to the Gigabyte site and it looks like there's only 3 releases - the first release, and two beta releases, so I think I am good there. I am downloading Fedora now, but it looks like they're up to version 25. I'll let you know if that boots up and installs. I am trying to figure out how to boot into legacy mode, and will try that as well, and I didn't see much in the way of USB settings - I tinkered with a few of them and it didn't seem to help any. I'll keep trying... -- 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/a29532ae-9734-4b9d-8871-0188aec3fdcc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Linux StandaloneVM - Problems with X
I've "fixed it" by modifying the GDM config file and setting it to automatically login without entering credentials. Not entirely happy tho, this won't create a xorg.conf file, and when I try to generate 1 with X -configure :1 I get an error saying it failed as number of created screens do not match number of detected devices. This means I'm stuck with 640x480 for now... Any ideas are appreciated! -- 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/9779f796-7e56-4885-ac4e-ea5ba48da38a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: ubuntu template
Thankx to all for the answers. It what i can do (some logs) [user@test qubes-builder]$ sudo make vmm-xen-vm Currently installed dependencies: git-2.5.5-1.fc23.x86_64 rpmdevtools-8.9-1.fc23.noarch rpm-build-4.13.0-0.rc1.13.fc23.x86_64 createrepo-0.10.3-3.fc21.noarch debootstrap-1.0.87-1.fc23.noarch dpkg-dev-1.17.27-1.fc23.noarch python-sh-1.11-1.fc23.noarch dialog-1.3-4.20160424.fc23.x86_64 dpkg-dev-1.17.27-1.fc23.noarch debootstrap-1.0.87-1.fc23.noarch DEBUG Repo Variables ─── SRC_DIR: qubes-src CHROOT_DIR: /home/user/qubes-builder/chroot-xenial CHROOT_REPO_DIR: chroot-qubuntu CHROOT_DEBIAN_DIR: /home/user/qubes-builder/chroot-xenial//debian-vm/debian BUILDER_REPO_DIR:/home/user/qubes-builder/qubes-packages-mirror-repo/xenial ─── Chroot Variables ─── DIST_BUILD_DIR: /home/user DIST_SRC: DIST_SRC_DEBIAN_DIR: /debian-vm/debian ─── Build Variables ─── DEBIAN_PARSER: /home/user/qubes-builder/qubes-src/builder-debian//scripts/debian-parser DEBIAN_PLUGIN_DIR: /home/user/qubes-builder/qubes-src/builder-debian/ OUTPUT_DIR: pkgs/xenial PACKAGE_LIST:debian-vm/debian DISTRIBUTION:qubuntu DIST:xenial DEBIANVERSION: xenial UPDATE_REPO: REPO_SUFFIX: DISTRIBUTION_CAP:Qubuntu REPO_PROXY: APT_GET_OPTIONS: CHROOT_ENV: BACKEND_VMM=xen # Make sure repo directory exists -> Preparing xenial build environment -> Installing qubuntu build chroot... I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://archive.ubuntu.com/ubuntu... I: Validating adduser 3.113+nmu3ubuntu4 I: Validating apt 1.2.10ubuntu1 I: Validating apt-utils 1.2.10ubuntu1 I: Validating base-files 9.4ubuntu4 I: Validating base-passwd 3.5.39 I: Validating bash 4.3-14ubuntu1 I: Validating bsdutils 1:2.27.1-6ubuntu3 I: Validating busybox-initramfs 1:1.22.0-15ubuntu1 I: Validating bzip2 1.0.6-8 I: Validating console-setup 1.108ubuntu15 I: Validating console-setup-linux 1.108ubuntu15 I: Validating coreutils 8.25-2ubuntu2 I: Validating cpio 2.11+dfsg-5ubuntu1 I: Validating cron 3.0pl1-128ubuntu2 I: Validating dash 0.5.8-2.1ubuntu2 I: Validating debconf 1.5.58ubuntu1 I: Validating debconf-i18n 1.5.58ubuntu1 I: Validating debianutils 4.7 I: Validating dh-python 2.20151103ubuntu1 I: Validating diffutils 1:3.3-3 I: Validating distro-info-data 0.28 I: Validating dpkg 1.18.4ubuntu1 I: Validating e2fslibs 1.42.13-1ubuntu1 I: Validating e2fsprogs 1.42.13-1ubuntu1 I: Validating eject 2.1.5+deb1+cvs20081104-13.1 I: Validating file 1:5.25-2ubuntu1 I: Validating findutils 4.6.0+git+20160126-2 I: Validating gcc-5-base 5.3.1-14ubuntu2 I: Validating gcc-6-base 6.0.1-0ubuntu1 I: Validating gnupg 1.4.20-1ubuntu3 I: Validating gpgv 1.4.20-1ubuntu3 I: Validating grep 2.24-1 I: Validating gzip 1.6-4ubuntu1 I: Validating hostname 3.16ubuntu2 I: Validating ifupdown 0.8.10ubuntu1 I: Validating init 1.29ubuntu1 I: Validating init-system-helpers 1.29ubuntu1 I: Validating initramfs-tools 0.122ubuntu8 I: Validating initramfs-tools-bin 0.122ubuntu8 I: Validating initramfs-tools-core 0.122ubuntu8 I: Validating initscripts 2.88dsf-59.3ubuntu2 I: Validating insserv 1.14.0-5ubuntu3 I: Validating iproute2 4.3.0-1ubuntu3 I: Validating iputils-ping 3:20121221-5ubuntu2 I: Validating isc-dhcp-client 4.3.3-5ubuntu12 I: Validating isc-dhcp-common 4.3.3-5ubuntu12 I: Validating kbd 1.15.5-1ubuntu4 I: Validating keyboard-configuration 1.108ubuntu15 I: Validating klibc-utils 2.0.4-8ubuntu1 I: Validating kmod 22-1ubuntu4 I: Validating less 481-2.1 I: Validating libacl1 2.2.52-3 I: Validating libapparmor1 2.10.95-0ubuntu2 I: Validating libapt-inst2.0 1.2.10ubuntu1 I: Validating libapt-pkg5.0 1.2.10ubuntu1 I: Validating libatm1 1:2.5.1-1.5 I: Validating libattr1 1:2.4.47-2 I: Validating libaudit-common 1:2.4.5-1ubuntu2 I: Validating libaudit1 1:2.4.5-1ubuntu2 I: Validating libblkid1 2.27.1-6ubuntu3 I: Validating libbsd0 0.8.2-1 I: Validating libbz2-1.0 1.0.6-8 I: Validating libc-bin 2.23-0ubuntu3 I: Validating libc6 2.23-0ubuntu3 I: Validating libcap2 1:2.24-12 I: Validating libcap2-bin 1:2.24-12 I: Validating libcomerr2 1.42.13-1ubuntu1 I: Validating libcryptsetup4 2:1.6.6-5ubuntu2 I: Validating libdb5.3 5.3.28-11 I: Validating libdebconfclient0 0.198ubuntu1 I: Validating libdevmapper1.02.1 2:1.02.110-1ubuntu10 I:
[qubes-users] How install visual studio code on the template Fedora ?
How install visual studio code on the template Fedora ? I have follow this https://code.visualstudio.com/docs/setup/linux from my AppVM but I don't see vs-code in the list. I want install it into the template Fedora. -- 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/77eb6e9e-1925-4fcc-a0aa-13af6920eac1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Linux StandaloneVM - Problems with X
Hi, I'm installing a Debian based OS (Kali) as a StandaloneVM. If I boot in live mode all works perfectly fine, but when I install it, boot, and enter the credentials, the desktop loads out of place, so 80% of the VM screen is sort of grey, and on the bottom I see 20% of what should be the top of the VM, this includes the mouse. Any ideas? I can't even launch a terminal cause I'm not able to see where the menu is. -- 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/51b3e4cd-271e-4109-bdee-42ef7e4adcda%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot install Qubes 3.2 - black screen of death
On Saturday, February 11, 2017 at 4:03:53 PM UTC-5, raah...@gmail.com wrote: > On Saturday, February 11, 2017 at 11:38:29 AM UTC-5, qubesn...@gmail.com > wrote: > > I am attempting to install Qubes, version 3.2, never having used any prior > > versions. > > > > My computer is custom-built with the following components: > > > > CPU: Intel Core i7-7700K Quad-core 4.2 GHz LGA 1151 Processor > > Motherboard: GIGABYTE Aorus GA-Z270X-Gaming 7 (rev 1.0) > > RAM: G.SKILL TridentZ Series 64GB > > Primary HDD: Samsung 850 EVO 2.5" 500GB 3-D Vertical Internal SSD > > CD-ROM: Pioneer 16x BD-R Blu-ray Burner (BDR-209DBK) > > > > I tried installing using the following types of media: > > > > -ISO burned to DVD > > -ISO burned to USB using Rufus in Windows and selecting dd mode > > -ISO burned to USB using dd in Debian > > > > When none of these worked, I started searching this newsgroup for similar > > problems. I found one suggestion that I tried, which was to add > > "GRUB_CMDLINUX_XEN_DEFAULT iommu-no-igfx" to grub.cfg - I could not do this > > one because I could not get the USB device out of read-only mode > > > > I removed the "quiet" option from the install, but still no success > > > > Afterward, I disabled VT-d in BIOS, but again, no success > > > > Every time, I get the splash screen with the options for installation. For > > any option I pick, it gets to the point where I believe Xen is launching > > the graphics for the installer. At that point, the screen goes completely > > black. In the case where I use the DVD, the drive stops spinning, and > > nothing else happens. > > > > I am at a loss, and any help would be greatly appreciated. > > hmm tried a diff usb stick, checked the signatures of the downloaded iso, > used only onboard gpu unplug pcie one. check gpu bios options,unplug all > other usb devices, check mobo for options, update mobo bios, does the > baremetal fedora 24 installer work? > > That board looks like it should work good with qubes, if I can think of > anything else I'll post back. > > Also oh and legacy boot mode. check usb controller options too. -- 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/bb643148-619c-4125-beef-11141f1793b4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Cannot install Qubes 3.2 - black screen of death
On Saturday, February 11, 2017 at 11:38:29 AM UTC-5, qubesn...@gmail.com wrote: > I am attempting to install Qubes, version 3.2, never having used any prior > versions. > > My computer is custom-built with the following components: > > CPU: Intel Core i7-7700K Quad-core 4.2 GHz LGA 1151 Processor > Motherboard: GIGABYTE Aorus GA-Z270X-Gaming 7 (rev 1.0) > RAM: G.SKILL TridentZ Series 64GB > Primary HDD: Samsung 850 EVO 2.5" 500GB 3-D Vertical Internal SSD > CD-ROM: Pioneer 16x BD-R Blu-ray Burner (BDR-209DBK) > > I tried installing using the following types of media: > > -ISO burned to DVD > -ISO burned to USB using Rufus in Windows and selecting dd mode > -ISO burned to USB using dd in Debian > > When none of these worked, I started searching this newsgroup for similar > problems. I found one suggestion that I tried, which was to add > "GRUB_CMDLINUX_XEN_DEFAULT iommu-no-igfx" to grub.cfg - I could not do this > one because I could not get the USB device out of read-only mode > > I removed the "quiet" option from the install, but still no success > > Afterward, I disabled VT-d in BIOS, but again, no success > > Every time, I get the splash screen with the options for installation. For > any option I pick, it gets to the point where I believe Xen is launching the > graphics for the installer. At that point, the screen goes completely black. > In the case where I use the DVD, the drive stops spinning, and nothing else > happens. > > I am at a loss, and any help would be greatly appreciated. hmm tried a diff usb stick, checked the signatures of the downloaded iso, used only onboard gpu unplug pcie one. check gpu bios options,unplug all other usb devices, check mobo for options, update mobo bios, does the baremetal fedora 24 installer work? That board looks like it should work good with qubes, if I can think of anything else I'll post back. Also -- 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/0a77b599-8d73-497c-91b2-25028f688555%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Install Failing on Lenovo Yoya Pro 2
I am attempting to install Qubes from USB on a Lenvo Yoga Pro 2. GUI is not starting and only getting text message. When selecting the install option the screen only flashes and then returns to the menu Has anyone faced this issue before or have any suggestions? -- 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/c2bcca91-d93a-4551-832c-5a664941463f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to disable xfce login?
On Saturday, February 11, 2017 at 2:02:21 PM UTC-5, jimmy@gmail.com wrote: > The four items to comment out are: Or I should say, to un-comment. :-) -- 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/6fe3d5e6-88d8-46a3-be1a-3e04105b0b9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to disable xfce login?
On Saturday, February 11, 2017 at 1:37:22 PM UTC-5, 01v3g4n10 wrote: > Make sure that any instances of autologin in /etc/lightdm/lightdm.conf are > commmented out with a "#". The four items to comment out are: pam-service=lightdm pam-autologin-service=lightdm-autologin autologin-user= autologin-user-timeout=0 And be sure to put the username in for "autologin-user=" Works like a charm (for me at least, hopefully you too!) -- 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/85d05f85-b5a4-4559-834d-0d75e07d664f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to disable xfce login?
On Saturday, February 11, 2017 at 3:23:38 PM UTC, peter.p...@gmail.com wrote: > I enabled "login at boot" during installation (3.2). > How can i disable it again? > > Thanks, > Peter. Make sure that any instances of autologin in /etc/lightdm/lightdm.conf are commmented out with a "#". -- 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/a7319656-0ded-44b2-a038-25910587efe1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] VPN/Firewall Redundant?
Assuming one wants to have all internet traffic go through a VPN, is having both a VPN proxyVM and a firewall VM redundant? In other words, does the proxyVM with the VPN running in it serve as a firewall just as well? Or is there still some reason to have two separate VMs in this use case? -- 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/3d3ae77a-24d9-4eb3-9be0-18156d715d90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Fedora-minimal Based netVM Not Working
In case anyone else has a similar issue someday, for the record it was indeed missing firmware. I just copied the Marvell firmware from the regular Fedora template to my Fedora-minimal template and it worked. Note: just the files recommended by the official Qubes docs were needed. The several others suggested but Rudd-O (referenced in this thread by a third party) were not. -- 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/b99fb41f-4cb1-41da-9faa-4ff62eb2bbdc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qvm-run fails silently with chromium
> Yes, I know - that's why I said "using bash". > You are using zsh, so you said, so you need to put the path in ~/.zprofile > > For example, with simple script 'logit' in home/user/newpath: > > qvm-run -a -p qube logit > fails with "logit: not found" > > append path=('home/user/newpath' $path) to ~/.zprofile > Then qvm-run succeeds Yeah, you are right, this works. Thank you very much. But I don't quite understand. I guess that I'm opening an interactive non-login shell, but ~/.zprofile is sourced while ~/.zshrc isn't, while, from http://zsh.sourceforge.net/Intro/intro_3.html: > `.zshrc' is sourced in interactive shells > [...] > `.zlogin' is sourced in login shells. [...] `.zprofile' is similar to > `.zlogin', except that it is sourced before `.zshrc' -- 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/210bafbe-7d03-4752-a0ef-87162a6c6523%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Biostar MCP6P3
Slow at times, but seems to be working fine. -- 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/CANm%2BXpobRcEaPeqP5ORtbzvJbjCAEgJvKtP5UU8LgHrvm7YtCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-BIOSTAR_Group-MCP6P3-20170211-100639.cpio.gz Description: GNU Zip compressed data Qubes-HCL-BIOSTAR_Group-MCP6P3-20170211-100639.yml Description: application/yaml
[qubes-users] Cannot install Qubes 3.2 - black screen of death
I am attempting to install Qubes, version 3.2, never having used any prior versions. My computer is custom-built with the following components: CPU: Intel Core i7-7700K Quad-core 4.2 GHz LGA 1151 Processor Motherboard: GIGABYTE Aorus GA-Z270X-Gaming 7 (rev 1.0) RAM: G.SKILL TridentZ Series 64GB Primary HDD: Samsung 850 EVO 2.5" 500GB 3-D Vertical Internal SSD CD-ROM: Pioneer 16x BD-R Blu-ray Burner (BDR-209DBK) I tried installing using the following types of media: -ISO burned to DVD -ISO burned to USB using Rufus in Windows and selecting dd mode -ISO burned to USB using dd in Debian When none of these worked, I started searching this newsgroup for similar problems. I found one suggestion that I tried, which was to add "GRUB_CMDLINUX_XEN_DEFAULT iommu-no-igfx" to grub.cfg - I could not do this one because I could not get the USB device out of read-only mode I removed the "quiet" option from the install, but still no success Afterward, I disabled VT-d in BIOS, but again, no success Every time, I get the splash screen with the options for installation. For any option I pick, it gets to the point where I believe Xen is launching the graphics for the installer. At that point, the screen goes completely black. In the case where I use the DVD, the drive stops spinning, and nothing else happens. I am at a loss, and any help would be greatly appreciated. -- 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/a3643651-f9f8-4810-82e1-478565c1a8d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Convert live system to VM in Qube OS?
Thanks for all the responses! I finally cloned the drive using dd, after few attempts it worked. It took me another 2 days to boot into it and am currently rebuilding my windows environment into separate DOMs on QubeOS. -- 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/2526671d-6e06-4c84-b5c0-fa9bf8e2c71b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to disable xfce login?
I enabled "login at boot" during installation (3.2). How can i disable it again? Thanks, Peter. -- 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/fe4b1c43-ce0e-41a1-b9a4-e03d57acdc30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Nested virtualization
On 02/11/2017 08:35 AM, adonis28...@gmail.com wrote: On Saturday, February 11, 2017 at 2:35:15 AM UTC-5, pixel fairy wrote: On Friday, February 10, 2017 at 9:03:47 PM UTC-8, adoni...@gmail.com wrote: Hi guys, thanks for the responses, I will have a look at it. What I need in this case in particular requires VBox, it is Genymotion, an Android emulator. this might help. https://groups.google.com/d/msg/qubes-devel/5thjxcHcMFw/YQfiTZ4qDwAJ heres a quick guide to stand alone vms, https://www.qubes-os.org/doc/hvm/ H.. so Windows and then try to emulate android... I may give it a go, although I'd rather have a Linux VM with VBox in it Windows? no that's just the guide obviously you can use linux. I can't see any reason as to why virt wouldn't work on a HVM assuming the correct cpu flags are passed through. -- 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/410ce310-2b09-8a37-6eae-0e3ad8054df3%40gmx.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Nested virtualization
On Saturday, February 11, 2017 at 2:35:15 AM UTC-5, pixel fairy wrote: > On Friday, February 10, 2017 at 9:03:47 PM UTC-8, adoni...@gmail.com wrote: > > Hi guys, thanks for the responses, I will have a look at it. > > > > What I need in this case in particular requires VBox, it is Genymotion, an > > Android emulator. > > this might help. > > https://groups.google.com/d/msg/qubes-devel/5thjxcHcMFw/YQfiTZ4qDwAJ > > heres a quick guide to stand alone vms, https://www.qubes-os.org/doc/hvm/ H.. so Windows and then try to emulate android... I may give it a go, although I'd rather have a Linux VM with VBox in 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/e66d5b3e-80e1-48b7-904b-4bbf94eadce2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Two factor LUKS decryption
Hi, Is possible to obtain something like that: https://www.masarlabs.com/article/two-factor-luks-decription/ in Qubes Os and after that install Anti Evil Maid protection? Regards, Alex -- 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/trinity-7be6bc9e-527b-4895-9b1e-169d496c0b9f-1486818383071%403capp-mailcom-lxa07. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unable to install Qubes OS 3.2 on Dell Latitude E4310
Hi ! I have some problem to install Qubes OS with USB. When I boot on USB key with UEFI mode, Qubes OS install freeze after initrd.img. I have message like this : Xen 4.6.1 (c/s) EFI loader Using configuration file 'Xen.cfg' vmlinuz : 0x00... initrd.img : 0x00... 0x00... 0x00... I try to resolve this problem with solution 1 (add /mapbs /noexitboot) on this page : https://www.qubes-os.org/doc/uefi-troubleshooting/ but I have the same result. I try too solution 2 (add -- efi=attr=uc), it's not working but I have a different error message : [Image of pingus] efi: EFI_MEMMAP is not enable esrt: ESRT header is not in a memory map. If I boot my USB key with Legacy bios mode, I have a graphic bug, I can see nothing, the screen display distortion. A bit like that : http://image.shutterstock.com/z/stock-photo-colorful-abstract-background-texture-glitches-distortion-on-the-screen-broadcast-digital-tv-433387279.jpg Anyone has a solution? Thanks for your help, K. Configuration : Dell Latitude E4310 BIOS A14 Intel i5-520M Intel Graphics 4500 4Gb memory SSD 500Go TPM 1.2 -- 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/9ee89e63-bd6d-4af1-aac4-b1c1ae479fd2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Audio CD via USB drive
W dniu wtorek, 7 lutego 2017 12:08:56 UTC+1 użytkownik timo.ve...@googlemail.com napisał: > I tried it already with the same result. > > Is there no way to prevent Qubes from exposing a block device? This is a known problem in Qubes. I had similiar problem with data CDs with no solution. Gave up. -- 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/28276105-9173-4cde-ba07-79d6ecc67786%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Running qvm-create-default-dvm against fedora-24-minimal hangs
Hi, On 31.01.2017 19:30, qu...@posteo.de wrote: I have tried to to create my own disposable vm based on the minimal Fedora 24 template and it always hangs during "Waiting for DVM fedora-24-minimal-dvm ...". The only difference to the original rpm template is sudo and the salt vm package. If I use the regular fedora-24 template it works fine. So which package or service am I missing? Thx in advance I have finally figured out the missing package. It is "perl-Encode". With this the dvm creation process runs through. Can somebody add this to the "Customize disposable vm Wiki"? 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/1f65f7aec72bfe9d8b148cc7540f3df9%40posteo.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Long boot time for "Initialize and mount /rw and /home" unit
On 02/03/2017 06:52 PM, Chris Laprise wrote: > On 02/03/2017 10:30 AM, Alex wrote: >> Anyway, I've had this same problem today (Long time for that >> unit), and I had the logged proof that the diff does take less than >> one second to complete, but after the resize2fs pass, I have an >> error in the log, saying "Please run 'e2fsck -f /dev/xvdb' >> first.". >> >> I'll dig further to inspect why the volume was somehow marked as >> "not clean", because last shutdown was trouble-free (no fsck >> should be needed), and because the wait for this unit (the fsck >> took 1'40" to complete) caused a qrexec-not-connected error, that >> prevented the automated completion of the boot process and the >> launch of some programs. Same issue (long boot time) happening again today; a specific appVM (which has been resized multiple times in the last 2 years) took 2'40" to run an e2fsck pass. No errors reported from fsck (I added a couple rows in /usr/lib/qubes/init/setup-rwdev.sh). After it was run, resize2fs stopped complaining. I discovered that resize2fs seems to be extremely picky about date and time, particularly regarding the check about last fsck run: from http://blog.bastelhalde.de/?p=746 i see > After an hour of searching I found out that the time settings of your > system (hardware clock and software clock) have to be correct to let > rezise2fs check your last run of e2fsck. So this latency, and the fact that fsck seems to be run nearly on every boot, may have to do with time being inconsistent (actually, all VM environments are known for time issues). On 02/03/2017 06:52 PM, Chris Laprise wrote: > > Good luck. I have an opposite issue: VMs on newer templates (Debian > 9, Fedora 25) are taking up to 3min to shutdown. > > Chris I've had some problems in the past with shutdown because of some issues in pulseaudio; you can try to investigate with the last lines of a guest.log from the affected machines. Now I'm not having this situation anymore. -- Alex -- 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/e0af33d9-0053-3a9a-540e-f5fc7f839f69%40gmx.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] backup failes
haaber: > > Cannot create /media/user/hexstring/qubes-backup/2017-02... : permission > > denied. > > Try "sudo chown user:user /media/user/hexstring/qubes-backup". > > Rusty Thank you that worked! 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/24341d31-3953-b7d1-a67e-0e9eed76984f%40web.de. For more options, visit https://groups.google.com/d/optout.