Re: [qubes-users] kernel panic after upgrade
mai...@maiski.net: > Hello, > > Unfortunately after the last update of Qubes 4.0 I have a kernel panic: > "unable to mount root fa on unknown block" and would appreciate if > somebody here could give me a tip. > > I installed Qubes 4.0-RC1 and since then been only updating. That could be the problem. A reinstall was required between 4.0-RC1 and 4.0-RC2. See here: https://www.qubes-os.org/news/2017/10/23/qubes-40-rc2/ > After the next-to-last update I was not able to boot xen 4.8.3 and linux > 4.14.13-3. > With the following configuration: xen 4.8 and linux 4.9.56-21 there is > no problem. > My machine is Lenovo T470S. > > Does anyone have an idea? > > m -- 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/bf5d1c10-e2ab-0e06-1f8b-7cd2645cc94f%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] fw for network printer setup
yreb...@riseup.net: > per the network printing docs it says to : > > > > "Open an AppVM (make sure it’s based on the template where you just > installed the printer, normally all AppVMs are based on the default > template), and test if printing works. If it doesn’t then probably the > AppVM doesn’t have networking access to the printer – in that case > adjust the firewall settings for that AppVM in Qubes Manager." > > > How exactly do I do this ? in 3.2 use the tab for firewall in the VM > manager , hit the + sign and choose ? "any" and what IP ? neither the > GW nor the AppVM IP seems to work > > I did install the driver in a cloned template VM but it wouldn't print > from there , and I gave up , I also couldn't get anything to print > from my xubuntu HVM You're halfway there. It wouldn't print from the template because the templates don't normally have network access. See here: https://www.qubes-os.org/doc/software-update-vm/ Network printing can be done multiple ways, so it depends on your setup. For example, if you only want to print from a certain appvm, you would choose "Deny all except...", then add a firewall rule in the firewall tab to allow access to the IP of your printer. Assigning a static IP to the printer will make things much easier (which would be done on the printer itself if you're not sure). Alternatively, if you're trying to both print from a certain appvm and access the internet from that same appvm, you would choose "Allow all except..." and then simply make sure that the appvm in question is not behind a vpn or tor. No specific firewall rules for the printer would be needed in this case. Using a xubuntu HVM might be a little trickier, but if it already has networking set up, the same concepts would apply. -- 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/9c4cc164-5271-8f10-3725-e7c9d251a8d2%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Noob issues with DNS Failure in Debian-8 and Debian-9 after creating upgrade TemplateVM
chuckc...@gmail.com: > Hi, all. I apologize in advance that I'm totally new to Qubes and somewhat > new to the Linux environment in general. You do not need to apologize! No one is born knowing all these things. You just simply need to have a willingness to learn, that's it. Don't hesitate to continue asking questions as needed, and to echo Unman, welcome! > After following the Qubes documentation instructions to clone the stock > Debian-8 TVM to Debian-9 and perform the upgrade to 9, I find that I can't > resolve DNS in either Debian template. > > I'm running R3.2. > > Any help would be greatly appreciated. I've done a lot of searching and am > stumped. :/ > -- 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/0eefd45a-0481-7ae5-7bfc-8233ce20c80a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Start VMs on boot before user login (Qubes OS 4.0rc4)
msgh...@gmail.com: > Hello, > > Is it possible to start all VMs marked as "Start qube automatically on boot" > on Qubes OS boot and not on user login in Qubes OS? > Is it possible to do it without Qubes OS autologin? > I want to have a working server application on VM on Qubes OS boot without > the need to login in Qubes OS. > Your question made me curious so I ran a quick test on 4 RC4. In dom0, run: [user@dom0 ~]$ sudo systemctl enable qubes-vm@serverVM (replace serverVM with the actual name of the VM running the server) Restart the machine, then after entering your LUKS passphrase hit escape, and you should see the serverVM being autostarted before login the same way that sys-net, sys-usb, and sys-firewall do. This successfully started a testVM for me before login. -- 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/2d278cde-e9d5-cf8a-c84e-77e87f22fcfe%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4
'awokd' via qubes-users: > On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote: >> What do you mean it is easy to do? Where do you get a compatible wireless >> card, that is definitely supported by Qubes anyway? You can purchase them many places online, even Amazon, for example, for about $12 USD. >> I somehow imagined that getting appropriate driver should be simpler :/ > > It's not necessarily a driver issue; more of a Xen (on which Qubes is > based) pass-through issue. Of the subset of wireless NICs that work > problem-free on Linux, there's a smaller subset that Xen can pass-through > problem-free and an even smaller subset that can be passed through a > QEMU/Xen stub-domain (which is what Qubes uses). I think it comes down to > how virtualization friendly the hardware manufacturer laid out their BARs > and MSI pages and whether MSI interrupts work (and who knows, maybe > there's a QEMU or some other bug somewhere in there too). Broadcom wireless in linux has always been a pain. That is because of Broadcom. > I have success with an AR9565 on R4.0 but not an AR928x. If you're going > to be shopping for another wireless card, maybe pick one then search this > mailing list for problem/success reports, or identify which laptops come > with it then search https://www.qubes-os.org/hcl/ and see if those laptops > are reported problem free with R4.0? I can confirm that an Atheros AR9462 works great on 3.2 and 4.0. If you're open to considering replacing the wifi card, you can email me off-list and I can walk you through it step by step. It really is easy to do, even the first time. > Longer term, I wonder if a section should be added to > https://www.qubes-os.org/hcl/ specifically to list known > compatible/incompatible network cards under Qubes R4.0? Could be painful > to maintain if we expand it to cover PCI devices in general... -- 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/b1ba1ef0-c15f-7562-1c04-0387197c6d05%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] how to show menu bar in qubes VM Manager
jerr...@disroot.org: > i clicked view and hide something i think > Right click inside the window, click "show menu bar" at the bottom of the list. -- 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/f7885424-acc9-22d1-2ab3-8bb8dc9dc1db%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0-rc3 not installing on Lenovo P71
Yuraeitha: > On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com > wrote: >> I burned the ISO to USB stick then started to install Qubes but got >> the following: >> >> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace >> lookup failure, AE_NOT_FOUND (20170531/dswload-210) [0.093383] >> ACPI Exception: AE_NOT_FOUND, During name lookup/catalog >> (20170531/psobject-252) [0.093539] ACPI Exception: >> AE_NOT_FOUND, (SSDT:ProjSsdt) while loading table >> (20170531/tbxfload-220) [0.098243] ACPI Error: 1 table load >> failures, 12 successful (20170531/tbxfload-246) [2.376031] >> Couldn't get size: 0x800e [ 137.216201] >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting >> timeout scripts [ 137.779207] dracut-initqueue[566]: Warning: >> Dracut-initqueue timeout - starting timeout scripts [ 138.324711] >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting >> timeout scripts [ 138.852226] dracut-initqueue[566]: Warning: >> Dracut-initqueue timeout - starting timeout scripts [ 139.395971] >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting >> timeout scripts . . . >> >> This went on for some time, so I switched off and wrote this >> message. I hope there are no serious typos coz I typed this off of >> a picture taken of the screen. >> >> Any hints? Thanks > > I'm by no means an expert on the kernel, but dracut "looks" like > kernel errors, and "ACPI" (Advanced Configuration and Power > Interface) looks like a firmware/kernel support mismatch, either by a > lack of features, lack of development, firmware-bug, kernel-bug, or > possibly an un-updated firmware. The firmware should be the > motherboard (BIOS/UEFI). > > You could start looking in your BIOS/UEFI after settings that may be > wrong and require adjustments. Is VT-d enabled? Is there a second > "Virtualization" that needs enabling, for exaple under "Advanced --> > CPU" UEFI settings? There can be other settings too, it's hard to > mention them all, but those two are the most important ones, which is > sometimes only 1 merged setting. > > Does your hardware support VT-d and other Qubes hardware > requirements? Does Qubes 3.2. run on this hardware? Qubes 4 is known > to be more strict to hardware requirements and may not work smoothly > or may not even install if the hardware requirements or security is > not correct. Qubes 3.2. is less an issue when missing VT-d and > similar. This might also be a place to look and confirm. If you got > Qubes 3.2. running on the machine, then try run in dom0 > "qubes-hcl-report" to see if you meet the requirements. > > However, dracut/ACPI errors doesn't strike me as errors that appear > if there are issues with the Qubes 4 specific requirements. > > You may want to try install with LegacyBIOS/Grub if you tried > UEFI/EFI, or vice versa, whichever you did not try yet. You can also > update your BIOS/UEFI to the newest version, however be sure you > don't brick your machine. Make sure you know any pitfalls as it may > make your motherboard break and become useless. > > The kernel contains drivers too, the most essential ones, while the > modules contain extra drivers for the kernel. These errors could also > be driver issues, for example you may have to edit the EFI or the > Grub to pick a different driver before starting. Unfortunately I > believe you need to edit the /boot/efi/EFI.cfg file on the install > media, but you can more easily change it live on Grub by hovering > over the install menu, and thne press "E" key to edit the install > menu in grub. Here you can change ACPI settings, drivers, > virtulization states, hide/unhide hardware, and so on. Maybe try this: hit e at this point as directed, then add: acpi=off to the end of the long line that begins with: module /vmlinuz-4... then boot in to the installer from there. > I'm not sure if it even is a driver issue, I can't see that from the > logs, whether it can be found there or not. But it's some clues to go > with, and maybe you can google some up to trial and error. Just be > careful, for example few of the ACPI settings can be dangerous to > your hardwaree, so double-check any recommendations you find on the > internet. > > Also it may be worth if you can find any ACPI settings in your > UEFI/BIOS too. > > At any rate, I usually solve these kind of problems with trial and > errors through experiments. Someone more knowledgeable might drop by > with a better advice. For now though, some clues you can try start > with if you did not do them already. > -- 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
Re: [qubes-users] Help :: Disposable VMs start without a NetVM (can't use DVMs currently )
Qubed One: > 'P R' via qubes-users: >> Hello, >> >> I have spend several hours to built new Template VMs from scratch (more >> precise: the fedora-24-minimal templates). >> >> Now I have the problem, that my new disposable VMs all start without an >> attaches Net-VM. >> >> sys-usb, sys-firewall, sys-net are now all based on the >> fedora-24-minimal template, with some additional packages, as suggested >> in the documentation. >> >> I have also built a new dvm which is based on the fedora-24 template: >> >> My default fedora-24 template is named "my-fedora-24-apps" and is a >> Template VM without a NetVM attached. >> >> I created a new dvm in dom0: >> >> [user@dom0 ~] qvm-create-default-dvm my-fedora-24-apps >> >> In preferences of the new dvm template which is named >> "my-fedora-24-apps-dvm" I have attached the firewall Proxy VM as NetVM. > > > After this step, you needed to run qvm-create-default-dvm again as > above. Not doing this step after changing anything about the > my-fedora-24-apps-dvm template is why the change did not take effect in > the dispvms created after that (assuming vanilla dispvm from the > application menu of course). Woops, I just realized that this step isn't necessary for me now, although I thought this was for me at some point. Only if you change something *inside* the -dvm template do you need to regenerate. Sorry list, I'll check first next time before I post... > >> But when I launch a program in the disposable VM there is no Net-VM >> attached. >> I have also set the "NetVM for DispVM" unter "Other" in the "Advanced" >> Settings Tab of Qubes Manager for the dvm template to sys-firewall. >> >> Still all my disposable AppVM start with an empty NetVM. >> If I edit a disposable App VM and add the sys-firewall as NetVM, >> everything works fine. >> >> >> QUESTION: >> Where and how am I supposed to set the correct information which NetVM >> should be used for my DVMs? >> >> - P R >> > -- 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/adfec551-56af-cfec-e226-8999329648bf%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Help :: Disposable VMs start without a NetVM (can't use DVMs currently )
'P R' via qubes-users: > Hello, > > I have spend several hours to built new Template VMs from scratch (more > precise: the fedora-24-minimal templates). > > Now I have the problem, that my new disposable VMs all start without an > attaches Net-VM. > > sys-usb, sys-firewall, sys-net are now all based on the > fedora-24-minimal template, with some additional packages, as suggested > in the documentation. > > I have also built a new dvm which is based on the fedora-24 template: > > My default fedora-24 template is named "my-fedora-24-apps" and is a > Template VM without a NetVM attached. > > I created a new dvm in dom0: > > [user@dom0 ~] qvm-create-default-dvm my-fedora-24-apps > > In preferences of the new dvm template which is named > "my-fedora-24-apps-dvm" I have attached the firewall Proxy VM as NetVM. After this step, you needed to run qvm-create-default-dvm again as above. Not doing this step after changing anything about the my-fedora-24-apps-dvm template is why the change did not take effect in the dispvms created after that (assuming vanilla dispvm from the application menu of course). > But when I launch a program in the disposable VM there is no Net-VM > attached. > I have also set the "NetVM for DispVM" unter "Other" in the "Advanced" > Settings Tab of Qubes Manager for the dvm template to sys-firewall. > > Still all my disposable AppVM start with an empty NetVM. > If I edit a disposable App VM and add the sys-firewall as NetVM, > everything works fine. > > > QUESTION: > Where and how am I supposed to set the correct information which NetVM > should be used for my DVMs? > > - P R > -- 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/175d50aa-892e-4c3a-b4bf-80401a2d467c%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Request for feedback: 4.9 Kernel
Reg Tiangha: > On 06/15/2017 01:53 PM, Zrubi wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 06/15/2017 06:34 PM, Reg Tiangha wrote: >> >>> Curious: For those apps that exhibit that behavior, are they >>> running on Debian 9 or Fedora 25 templates? >> Nope. >> Fedora 24 mainly, and Debian 8 >> The later is only for sys-net, so all my taskbar icons coming from a >> F24 based template. >> > Thanks. I don't really use Fedora, but I'll set up a test VM once my > laptop is finished converting this Debian 8 template to 9. Can you list > some apps that this happens with so I can test across a variety of > templates? I'm still leaning towards an X issue, but maybe it's always > been there since Fedora 24, even under kernel 4.9. But I would assume if > that was the case, then more people would have spoken up by now. >>> Since it works fine in Debian 8 (I haven't tested much with any >>> Fedoras), I'm wondering if it's less a kernel issue and more of an >>> issue with newer X or how Qubes integrates with newer X (but I >>> guess if it works properly on 4.4, it may be a combination of the >>> three; don't know how to fix it though). >> Maybe it is a know issue, but: >> online netvm change on a disposable VM is also broken on the latest >> 4.9 VM kernel. (Qubes Manager shows it is changed, but not working in >> practice) >> > I've *never* ever had this work for me (although it might have worked > once in R3.0 or something old like that); I've always had to shut down > the Disp VM first, alter the dvm template, and then start up a new one > in order to change NetVMs. I have no problem with this myself. 3.2, kernels 4.4, 4.9, 4.10. The difference I think is that my dvm templates net-vm is set to none, so each dispvm I start which requires net access is set manually. Is it common for you or others to change a given dispvms net-vm more than once? Im just curious. >>> I can't play around with this until later today, but in the >>> meantime, what graphics hardware are you running, Zrubi? And which >>> version of 4.4 are you running where things work fine? And finally >>> if you can, if it's an Intel card, can you try booting with this >>> kernel option to see if it makes a difference? >>> >>> i915.preliminary_hw_support=0 >> I believe this setting will not affect this chipset. But will try if I >> have a chance. (This is my only Qubes Laptop atm and using it for >> production) >> >> HW details: >> >> Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz >> Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) >> Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 >> >> SW versions: >> Qubes 3.2 >> xen: 4.6.5 >> kernel: 4.4.62-12 >> > It might; if you could try it in both dom0 and vm (and maybe different > combinations if you have the time), that'd be useful to help rule things > out. It's toggled on by default to work around this: > > https://www.phoronix.com/scan.php?page=news_item=intel-skl-prelim-support > > but maybe it's no longer an issue with 4.9. > > > -- 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/b40cbfad-5eb1-3c2d-802f-6b62e5521f45%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Question(s) regarding Qubes minimal templates
'Tomei Ningen' via qubes-users: >> I'm a strong advocate of using minimal (or smaller) templates, >> customised for specific use cases. Some people HATE this approach. >> >> unman > > Really? Coming from the sort of people with the patience for an OS > like Qubes? I'd think anyone who's involved enough to have an opinion > would be in favor of that -- that's kind of the idea here, isn't it? > One thing I wish I could change would be the visual clutter it > produces; anybody know of a means to flag these VMs as internal so I > can hide the ones I'm not interested in seeing regularly? In dom0, type this from the command line: qvm-prefs -s internal True > That being > said, I'm definitely in agreement with you, unman. Would you > recommend any particular setup for a more granular approach? My > current arrangement of VMs [work in progress; suggestions welcome!] > is structured like this as of now: > > - dom0 - fedora-24 > > - dispVM(s) - fedora-24-minimal ( ... > derivative templates > appVM > > packages*) > > - fedora-24-min-net > > - sys-net** > > - General-purpose: gnome-keyring, less, man, pciutils, psmisc, sudo, > vim-minimal, xterm - Template-specific: dbus-x11, dejavu-sans-fonts, > NetworkManager, NetworkManager-wifi, network-manager-applet, > notification-daemon, tinyproxy - fedora-24-min-frwll > > - sys-firewall > > - No additional packages; effectively a clone of the > Fedora-24-minimal template. - fedora-24-min-vpn > > - sys-vpn > > - G.P.: sudo, xterm - T.S.: [TBD; trying out some different VPNs > atm] - fedora-24-min-usb > > - sys-usb > > - G.P.: sudo, xterm - T.S.: qubes-input-proxy-sender - > fedora-24-min-pen > > - pentest > > - G.P.: sudo, xterm - T.S.: aircrack-ng, ettercap, kismet, nmap, > nmap-telcat, tcpdump, wireshark***, [remaining packages TBD] > > * The concomitant dependencies aren't included in these lists (n.b. > packages are installed in the respective templateVM) ** Can't quite > get this one to run properly yet; I presume I need to install a > proprietary driver in the template to make this work for my > machine(?) *** Very interested in trying out v6ak's split-wireshark" > idea but haven't found the time yet. Thanks for sharing that idea, > v6ak! > > - TN > > Sent with [ProtonMail](https://protonmail.com) Secure Email. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/a32d0613-2e00-33db-33f3-7740ed820949%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Window VM disappear when dont use
phongxuan1...@gmail.com: > hi every one, i'm using Win7 64 bit in Quebe, I have a case that when i dont > use the VM in 15-20 min, window VM disappear and i cant find this vm anymore, > i have to restart vm or kill it to reuse it. Any one have solution for my > problem? Thank you > IIRC, that happens when win7 goes to sleep (by default). Changing that setting should solve your problem. I think its under power management or something similiar. -- 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/6de9f251-43ff-aa03-a436-0ac37f9cd9e9%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Upgraded to 3.2 - now my desktop is wrong
galt...@gmail.com: > I upgraded to 3.2 by backing up in 3.1 and restoring in 3.2. Did you back up dom0 in 3.1? That is where such configs are. > I was using xfce in 3.1 and had 4 workspaces (or activities) and each had its > own background image and I had different icons placed on each one. Now in 3.2 > there are 4 workspaces but no icons and the same background. If I add an icon > it gets added to all four workspaces. > > Also, under the system tools menu is a menu item for every shortcut in every > VM. For example Systemm Tools->work: Files > > Other than this, everything seems to work as before and I cant see anything > new. > > I've done the install and restore twice and it was the same both times. > > Have I done something wrong in the restore? Should I go back to 3.1? > -- 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/3a3d9603-8936-d472-07b2-3f93c3747cb6%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Tool to record Whonix / Tor browsing history..?
Manuel Amador (Rudd-O): > On 08/12/2016 01:39 PM, neilhard...@gmail.com wrote: >> I would like to be able to do something like: >> >> 1. Use Whonix/Tor as a disposable VM >> >> 2. Record browsing history using an external software >> >> One of the reasons I don't use Tor that much (other than slow speed, >> captchas etc) is because I actually want to have a record of the websites I >> have visited. >> >> We know that it could be risky to have the Tor browser itself record >> history, if it gets hacked. >> >> But to have some tool running outside of the VM would be useful.. > > For the same reason that attackers outside the VM can't see what you're > visiting, you yourself won't be able to see it either. > > What you want is not doable. > > If you want to have a record of sites you visit, then tell the Tor > Browser to record your browsing history, and hope that works for you. > You could also simply fire up a text editor (gedit etc) in another VM and record what you want that way. Trying to automate the process would be a bad idea for security, especially if using Whonix as a dispVM. -- 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/28f04dba-7a03-9468-cf85-ba68ea502216%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Configuring OpenDNS in Qubes
m...@lamarciana.com: >> eth0 is an uplink to sys-net. And /etc/resolv.conf there indeed is >> generated, so manual changes will be lost. There is a way to avoid this >> using /etc/qubes/protected-files.d/, but I think it isn't the way to go. >> Better adjust NetworkManager settings in sys-net, using standard >> connection editor GUI. The DNS servers in any other VM are in the end >> pointing to what you have in sys-net(*) (using DNAT redirections). >> >> (*) unless you use Tor/Whonix - in which case those are redirected to >> tor process. > > Thanks for your answer. > > Does it mean that all VM have to share the same DNS settings (except > Tor/Whonix)? What I was trying to do is routing only one of them through > OpenDNS, while keeping the rest with my ISP DNS server (and I would like to > avoid an HVM just for that). > > I see I can create a new "NetVM" but I'm not sure if it is full supported. If > I create a new one, is the GUI adapted so that I can configure both (sys-net > and my custom one)? I prefer to ask before trying it and risking leaving > something in an inconsistent state. > I would suggest trying to completely disable or get rid of NetworkManager in that ProxyVM (you shouldn't need it, especially just to redirect DNS), then see if /etc/resolv.conf changes become persistent. If not, you could still use /rw/config/rc.local to replace /etc/resolv.conf on boot. -- 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/a038a41c-61c1-da76-225e-68600908de45%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Configuring OpenDNS in Qubes
m...@lamarciana.com: >> If I understand correctly, permanently changing /etc/resolv.conf in the >> ProxyVM to show: >> >> nameserver 208.67.222.222 >> nameserver 208.67.220.220 >> >> should achieve that in a standalone ProxyVM. > > Thanks for your answer. I thought that changing /etc/resolv.conf by hand was > not recommended because some other programs can overwrite it. Anyway, I tried > it and changes in /etc/resolv.conf in my standalone ProxyVM are lost once I > reboot... > Are you using NetworkManager in that ProxyVM? -- 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/46da2e66-4687-886f-2250-43067e021d91%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: [qubes-devel] Window border colors
> Jeremy Rand: >> Marek Marczykowski-Górecki: >> Try this: >> >> Go to system settings -> Application Style -> Window Decorations. It >> should be set to "Breeze". If it is set to "Plastik", it may be the >> cause of the problems. >> >> If this is the case, I think this may be related to KDE update done by >> Fedora recently (a lot of kf5-* packages), so unrelated to >> qubes-gui-dom0 version. > > Yes! It was set to Plastik. Changing it to Breeze and clicking Apply > instantly fixed the issues. (Well, I can't test whether it fixed the > icon of the launcher, because I've already done the workaround that I > described previously. But everything else is fixed now.) > > Thank you Marek! > > -Jeremy > This also instantly fixed the same problem for me, and I can confirm that it began at about the same time as the kf5-* updates from Fedora. 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/243b1d95-2d10-7786-c7fd-4fcc3ce05a97%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2 rc2 has been released!
Iestyn Best: > Thank you guys, great work. > > Just a little side note, yesterday when I updated it seemed to break my > window borders in KDE. I am now using XFCE and all seems fine. > > I have not tried KDE again today, just trying to get use to XFCE now as that > is your focus now. > I can't link to the exact message right now (qubes-devel, Marek, thread named "Window Borders", fifth message in the thread), but these instructions fix that issue in KDE: "Try this: Go to system settings -> Application Style -> Window Decorations. It should be set to "Breeze". If it is set to "Plastik", it may be the cause of the problems. If this is the case, I think this may be related to KDE update done by Fedora recently (a lot of kf5-* packages), so unrelated to qubes-gui-dom0 version." -- 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/3b1026c0-664a-5945-b6d8-0814ef247010%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2 rc1 has been released!
raahe...@gmail.com: > On Friday, July 22, 2016 at 7:24:16 PM UTC-4, raah...@gmail.com > wrote: >> On Friday, July 1, 2016 at 6:03:23 PM UTC-4, Qubed One wrote: >>> Marek Marczykowski-Górecki: >>>> On Tue, Jun 28, 2016 at 10:36:42AM -0700, raahe...@gmail.com >>>> wrote: >>>>> Will we be able to upgrade to 3.2 from dom0 update >>>>> eventually? Or if we choose not to reinstall is there >>>>> security implications? >>>> >>>> Yes. Experimental instruction already online: >>>> https://www.qubes-os.org/doc/upgrade-to-r3.2/ >>>> >>>> >>> >>> >>> Thanks! >>> >>> Upgrading from 3.1 to 3.2 worked perfectly for me. >> >> trying to update qubes on a machine after doing the command sudo >> qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2 >> qubes-release shows lots of updates to be installed, but I get >> errors. >> >> Package: xfce4-panel-4.12.0-4.fc23 requires libgarcon-gtk2-1.so.0 >> Package: kde-style-plastik-for-qubes-1.1-1.fc20 requires >> libkdecorations.so.4 Package: 1000:garcon-0.2.0-3.fc20 requires >> libxfce4util.so.6 Package: qubes-kde-dom0-4.12.3-1.fc20 requires >> kde-workspace-libs Obsoleted by: >> 1:kde-workspace-common-4.11.22-7.fc23 Not found package: >> qubes-kde-dom0-4.12.3-1.fc20 requies kde workspace Obsoleted By: >> Plasma-desktop-5.6.5-1.fc23 Not found You could try using >> --skip-broken to worka round the problem You could try running:rpm- >> Va--nofiles --nodigest > > I tried sudo qubes-dom0-update --skip-broken and I got error at end > about Multilib version problems found. Protected multilib versions: > unbound-libs-1.5.5-1.fc23 != unbound-libs-1.5.4-4.fc20 > gnupb-1.4.19-3.fc23 != gnupb-1.4.19-2.fc20 libdrm-2.4.65-1.fc23 != > libdrm-2.4.58-1.fc20 > Was this machine fully updated before running the update command containing qubes-release? Do you normally use updates-testing or security-testing? You might try getting all updates from qubes*testing first, then reboot and run the command containing qubes-release. -- 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/9d0b3215-f0d0-846a-c7bc-01934d952674%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Can someone help me out DRM failed to create kernal channel 22
randallrba...@gmail.com: > I just freshly installed the os and now with every boot it hangs on > the message nouveau DRM failed to create kernal channel 22. What does > this mean and how to I get past that error? My computer is running > with an Asus x99 delux, an Intel core i7 5960x extreme cpu, 4 4gig > sticks of ddr4 corsair ram and 2evga geforce gtx 970 graphics cards. > yes I know its over the top for cubes but whatever it worked fine > before. Will someone please give me some answers or link me to a post > with the answer? I see questions receiving multiple answers but for > people like me who are new with linux are recieveing no answers and > with the direction windows went I only prefer cubes os. > You need to do this: when the computer first boots, at the grub menu, hit esc to stop the timer, then hit e to edit the first entry on the list. go to the line that begins with /vmlinuz-4... and at the end of that line add:rd.driver.blacklist=nouveau nouveau.modeset=0 then hit f10 to boot. Let me know if that works. -- 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/3f871ae5-7486-dc80-be09-d1eab66153c5%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] [newbie] Memory settings
Gustavo Lapido Loureiro: > I changed my personal vm max memory to 8 GB since this will be the vm > where I plan to run most of my applications, most of them memory > consuming (Firefox with hundreds of opened tabs, video playing, image > processing...). Initial memory was automatically adjusted to 800 MB. > Memory balancing is turned on. > > I have 12 GB of ram installed on my laptop. > > Is this an acceptable procedure? Yes. All you've done is increased the maximum, which seems reasonable. If memory balancing were turned off, it would mean setting aside all 8 GB any time the personal vm was running. > Before posting this I read this post > > https://groups.google.com/forum/#!searchin/qubes-users/memory$20appvm/qubes-users/lxcMPl01hMM/uCe3PXhlJyEJ > > and, although the final conclusion seems to be "Don't touch default > settings, let automatic memory balancing take care of it", it is from > 2014, so I wonder if things could have changed since then? > > If it's still effective, then I wonder when it would be necessary to > change those settings? In my own experience, I have reduced the RAM and disabled memory balancing for vms like sys-net, sys-firewall, VPNs etc. I have also increased the fixed (non memory balanced) RAM in win7 standalone vms. > Thanks in advance > -- 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/cf06b1cb-90bc-3c8a-fde9-63a3b18435ad%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Networking Disabled - cannot enable NetworkManager Applet [sys-firewall]
Qubed One: > jefferson_pla...@hotmail.com: >> Hello Andrew >> >>> This is the NetworkManager applet running in sys-firewall. Normally, >>> sys-firewall is connected to sys-net for network access, and the >>> NetworkManager applet only runs in sys-net. (The situation can be >>> different if you're running things like VPN VMs, but we'll set those >>> aside here.) >>> >>> In short: the NetworkManager applet shouldn't be visible in >>> sys-firewall in the first place, but it's not a big problem (just a >>> confusing one). There's normally a script that hides it, but in your >>> case, that's not working for some reason. >> >> My set up is standard with the only change from fresh installation being the >> updating of templates and dom0. Is this difference of NetworkManager >> appearing an indication of any loss of function or security? >> >>> So, are you still having problems updating dom0 and your templates? If >>> so, can you explain the problems? >> >> There were issues with dom0. The link below give the solution: >> https://groups.google.com/forum/#!searchin/qubes-users/errno$2014$20curl$2337/qubes-users/zMETrlPMqng/GcwIPcZ8BQAJ >> >> The whonix templates were difficult. I was able to update them however I >> still get a whonixcheck error for the whonix gateway. It reads "WARNING: >> Whonix Meta Packages Test Result: Whonix-Gateway detected, but the meta >> package qubes-whonix-gateway is not installed. Did you accidentally >> uninstall it?" >> >> I followed the steps from this discussion: >> https://groups.google.com/forum/#!searchin/qubes-users/meta$20package$20qubes-whonix-gateway$20is$20not$20installed/qubes-users/P2BTCOPcTnU/xHXxMEzLPwAJ >> >> This did not work: >> "sudo apt-get install qubes-whonix-workstation" on WS template >> "sudo apt-get install qubes-whonix-gateway" on GW template. >> >> Another similar command to the two above worked. However the autoremove >> command did not work. I was root and met the requirements it seemed to need. >> >> The sanity check from here did not work, returning 1 instead of 0. The >> command was not recognised: >> https://www.google.com/url?q=https%3A%2F%2Fwww.whonix.org%2Fwiki%2FUpgrading_Whonix_12_to_Whonix_13=D=1=AFQjCNGFl1_nVVp9x0MIL9am3BnI9-vOlA >> >> I would like to learn how to fix this meta package error. From what I have >> read here it would be a risk to my security to bypass this issue. >> https://www.whonix.org/wiki/Whonix_Debian_Packages#What_is_the_disadvantage_of_removing_a_meta_package.3F > > > These steps worked for me (sorry, can't find the source that directed me > here. It mentioned something about upgrading Whonix from 12 to 13 > without realizing it.): > > https://www.whonix.org/wiki/Upgrading_Whonix_12_to_Whonix_13 Sorry again, it appears you've already tried that. I need to read more thoroughly before replying... >> Thank you for providing some sources. Are there any that I can learn to >> better navigate qubes and use basic code? I will keep looking through the >> documentation. Aside for running an update on a VM is there anyway to check >> if the VM (or dom0) is up to date? >> > -- 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/37148fc2-d147-96b7-a9cd-f295e14fe44d%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Networking Disabled - cannot enable NetworkManager Applet [sys-firewall]
jefferson_pla...@hotmail.com: > Hello Andrew > >> This is the NetworkManager applet running in sys-firewall. Normally, >> sys-firewall is connected to sys-net for network access, and the >> NetworkManager applet only runs in sys-net. (The situation can be >> different if you're running things like VPN VMs, but we'll set those >> aside here.) >> >> In short: the NetworkManager applet shouldn't be visible in >> sys-firewall in the first place, but it's not a big problem (just a >> confusing one). There's normally a script that hides it, but in your >> case, that's not working for some reason. > > My set up is standard with the only change from fresh installation being the > updating of templates and dom0. Is this difference of NetworkManager > appearing an indication of any loss of function or security? > >> So, are you still having problems updating dom0 and your templates? If >> so, can you explain the problems? > > There were issues with dom0. The link below give the solution: > https://groups.google.com/forum/#!searchin/qubes-users/errno$2014$20curl$2337/qubes-users/zMETrlPMqng/GcwIPcZ8BQAJ > > The whonix templates were difficult. I was able to update them however I > still get a whonixcheck error for the whonix gateway. It reads "WARNING: > Whonix Meta Packages Test Result: Whonix-Gateway detected, but the meta > package qubes-whonix-gateway is not installed. Did you accidentally uninstall > it?" > > I followed the steps from this discussion: > https://groups.google.com/forum/#!searchin/qubes-users/meta$20package$20qubes-whonix-gateway$20is$20not$20installed/qubes-users/P2BTCOPcTnU/xHXxMEzLPwAJ > > This did not work: > "sudo apt-get install qubes-whonix-workstation" on WS template > "sudo apt-get install qubes-whonix-gateway" on GW template. > > Another similar command to the two above worked. However the autoremove > command did not work. I was root and met the requirements it seemed to need. > > The sanity check from here did not work, returning 1 instead of 0. The > command was not recognised: > https://www.google.com/url?q=https%3A%2F%2Fwww.whonix.org%2Fwiki%2FUpgrading_Whonix_12_to_Whonix_13=D=1=AFQjCNGFl1_nVVp9x0MIL9am3BnI9-vOlA > > I would like to learn how to fix this meta package error. From what I have > read here it would be a risk to my security to bypass this issue. > https://www.whonix.org/wiki/Whonix_Debian_Packages#What_is_the_disadvantage_of_removing_a_meta_package.3F These steps worked for me (sorry, can't find the source that directed me here. It mentioned something about upgrading Whonix from 12 to 13 without realizing it.): https://www.whonix.org/wiki/Upgrading_Whonix_12_to_Whonix_13 > Thank you for providing some sources. Are there any that I can learn to > better navigate qubes and use basic code? I will keep looking through the > documentation. Aside for running an update on a VM is there anyway to check > if the VM (or dom0) is up to date? > -- 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/7448bbb6-f675-ba08-d008-48073bb2c5cd%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 3.2 rc1 has been released!
Marek Marczykowski-Górecki: > On Tue, Jun 28, 2016 at 10:36:42AM -0700, raahe...@gmail.com wrote: >> Will we be able to upgrade to 3.2 from dom0 update eventually? Or if we >> choose not to reinstall is there security implications? > > Yes. Experimental instruction already online: > https://www.qubes-os.org/doc/upgrade-to-r3.2/ > > Thanks! Upgrading from 3.1 to 3.2 worked perfectly for me. -- 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/2ea11550-6378-bf95-3ee9-0b9ab650f2bb%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes-usb-proxy in 3.2?
Niels Kobschätzki: > Hi, > > I am trying to install qubes-usb-proxy in my Fedora-23-template in > 3.2RC1 but dnf cannot find it. When I do a "dnf search qubes" I get > listed several qubes-packages but nothing like qubes-usb-proxy. > Do I need to enable an extra repo, is the problem once again the > interface between chair and keyboard or is something else broken? > > Niels > The package you're looking for is called qubes-input-proxy-sender. You can see if it's already installed in the template with: $ rpm -qi qubes-input-proxy-sender -- 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/e8ab2af9-20f8-a902-b600-582685f06ebd%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
Andrew David Wong: > On 2016-06-19 00:09, CANNON NATHANIEL CIOTA wrote: > >>> On 2016-06-17 23:17, CANNON NATHANIEL CIOTA wrote: Hello thank you for the reply... > What is the output when you run this command in a dom0 > terminal? > > $ qvm-create-default-dvm --default-template I have already tried this before re-installing Qubes which made no difference. >>> >>> Can you be more specific when you say it "made no difference"? >>> For example, can you tell us the exact output when you attempted >>> to run that command? (Even if there was no output at all, that >>> would be helpful to know.) > >> Here is output (I am manually typing this output, so there might >> be slight typos): [...] > > > Ok, that looks normal. When you say DispVMs "do not launch," does that > just mean that nothing happens when you click the DispVM shortcuts in > the KDE launcher? > > Is your default template fedora-23? Have you made any modifications to > it? > > What happens if you execute this command in dom0? > > $ sh -c 'echo xterm | /usr/lib/qubes/qfile-daemon-dvm \ > qubes.VMShell dom0 DEFAULT red' > Also try removing the pre-existing fedora-23-dvm first, then recreate it with the above command. I've had issues before that were solved by removing the old *-dvm first, then creating a new one. -- 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/052bbbd0-32aa-a8bf-d3df-5a1cd88eea3c%40riseup.net. For more options, visit https://groups.google.com/d/optout.
