Re: [qubes-users] How to set file association in disposable VMs?
On Tue, 3 Jan 2017 at 03:14 Unman wrote: > > > Original Message > > > Subject: [qubes-users] How to set file association in disposable VMs? > > > Local Time: December 29, 2016 7:48 PM > > > UTC Time: December 29, 2016 11:48 AM > > > From: gree...@gmail.com > > > To: qubes-users > > > > > > I have configured Nautilus in an AppVM to open PDF files with Okular, > and > > > I've then done the same configuration (as user "user") in the > TemplateVM > > > that the disposable VMs are also based on. However, when I choose > "Open in > > > disposable VM" from that reconfigured AppVM, even though the dispvm > > > savefile is updated before launching the dispvm, it still uses the > default > > > PDF viewer instead of Okular. > > > > > > > > > Sounds similar to this: > > > > > > > https://groups.google.com/forum/#!searchin/qubes-users/open$20in$20dvm|sort:relevance/qubes-users/GZ2zWcoMuwc/vwAzmYS5DgAJ > > > > > > --WillyPillow > > > > > You don't say *how* you have changed the association. > I changed it using Nautilus, by right-clicking on the file, Properties. > Try changing the file association in the template: > mimeopen -d file.pdf will allow you to set the default application. > Close down the template. > Then make sure the dvm file is regenerated before opening the dispVM, > as you have done. > That didn't work either. Please note, as noted already in this thread, this is a known bug. -- 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/CACVBcp4j5ufmszR-mJe-BDv%3DOnLMs_CJXZphS0GxtMMNRtnQBQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL + Lenovo ThinkPad T430
BIG thanks to all Qubes Developers. Works fine. Problem with four penguins solved by https://www.qubes-os.org/doc/uefi-troubleshooting/ Proof - http://imgur.com/oQXIpjH -- 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/a5eb8df6-f88a-48ee-a12e-0d71e501405d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL + Lenovo ThinkPad T430
вторник, 3 января 2017 г., 12:15:19 UTC+3 пользователь jimmyo...@gmail.com написал: > BIG thanks to all Qubes Developers. Works fine. > > Problem with four penguins solved by > https://www.qubes-os.org/doc/uefi-troubleshooting/ > > Proof - http://imgur.com/oQXIpjH Qubes ver. Qubes-R3.2-x86_64 -- 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/a691502e-837f-499e-9411-d4dbb6c27daa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] [solved] installing vlc media player in FC24 template vm
Folks, I've just had a small fight to install vlc. Here is what solved my issue: http://unix.stackexchange.com/a/333775/189220 (rpmfusion was installed, but not enabled so dependencies had been being not resolved) PD -- 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/196b3a10-d870-42d3-8126-32c1e61d8f51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
On 03/01/2017 04:35, Otto Kratik wrote: > I am using Qubes R3.2. Suddenly almost all of the KDE shortcuts > usually found under applications-> system tools have completely > vanished. I have no konsole, file manager, system settings etc. Only > four remain: I can't help but I had this happen once using Xfce as the desktop. All my 'start menu' disappeared bar a few. I re-installed. Possibly a bug then in this 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/94a635b3-9e5f-9f12-97e8-b311c90e19d8%40gmsl.co.uk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] botched 3.1 -> 3.2 upgrade: reset dom0 password
On 01/02/2017 08:51 PM, Unman wrote: On Thu, Dec 29, 2016 at 02:52:12PM -0600, Jake wrote: hello list, i have taken a R3.1 system installed from the ISO and attempted to upgrade it to R3.2 by following the instructions from the docs ( https://www.qubes-os.org/doc/upgrade-to-r3.2/ ), but i have encountered an unusually irritating problem in the process: after getting to step 7 of the dom0 upgrade, the machine was rebooted and i cannot log into dom0 using the password that worked fine with R3.1. i am 100% certain that this is not a PEBCAK error and that my previously working password for dom0 is no longer working. that said, this is typically an easy enough problem to fix on most *nix systems: drop to single user mode during boot and reset the password for root or whatever user. i have searched the qubes-users archives, found no advice on how to do this and had no luck trying this myself. i have used the install ISO to boot into "rescue mode", manually mounted the LUKS volume and attempted to reset the password to no avail. it would appear that the passwd installed in dom0 does not support the -R option, nor does passwd work properly inside a chroot, e.g. mount / filesystem on /mnt, run 'chroot /mnt' and run 'chroot '. if there is a trick to interrupting the qubes boot process to drop into single user mode, i would greatly appreciate someone sharing that information. it seems the issue is that this must occur between unlocking the LUKS volume and arriving at the password prompt for dom0. regards, jake Hi Jake Sorry to hear of your problem. I havent encountered this in a number of upgrades. unman, thanks for the feedback on the upgrade process. i'll try to repro the issue on identical hardware. the extra steps to make passwd work are appreciated, i'll give them a try if i can reproduce this failure. regards, jake If you want to use a chroot, then you need to do something like this: Mount the decrypted disk to /mnt $ sudo mount ‐‐bind /dev /mnt/dev $ sudo mount ‐‐bind /proc /mnt/proc $ sudo mount ‐‐bind /sys /mnt/sys Then chroot, and the passwd command should work within the chroot. (If you've already tried this, apologies - it isnt clear from your post.) unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d54b8fb2-7885-1326-3114-c22a2a70cf3d%40companyzero.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Synaptic touchpad not working through usbVM
On 28/12/2016 21:33, Marek Marczykowski-Górecki wrote: > Interesting, do you have that touchpad really as a USB device? If so, > it's probably not supported by InputMouse service - probably we need > InputTouchpad, or sth like this. That's a good question. It's an Acer laptop. The usbVM shows it in lsusb as a USB device but it's not listed in /dev/input. I'll install that tool and report back here with the results. -- 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/3df36252-e897-a6aa-7878-b3cc808e7afe%40gmsl.co.uk. For more options, visit https://groups.google.com/d/optout.
[qubes-users] lemur7 Unable to reset PCI device
I have a similar issue on a modern laptop with a workaround for you which may help. My acer f5 573 55lv will also only work properly with either the wireless in the devices for sys-net or the wired (collectively or separately - as you have the same bridging as i do with a card reader plus ethernet arrangement - that i use so infrequently i forget if have just the ethernet & not the reader is ok). It's all down to the conflicts caused by the necessary evil of bridging & the demands of dealing with how xen currently copes (due to current capabilities & security). Give a try like this - boot laptop up, shutdown sys vms if they ever got started & then enter the device list of qubes vm qui specific to the sys-net & make sure that only either bdf 03:00.1 is listed or both 03 devices if you want wired access to work, bdf 02:00.0 if you want wireless to be possible. Then try to start sys-net & if it starts ok then try sys-firewall. I have noticed also issues where if you could get both wired & wireless devices assigned (different hardware) the nm solution seemed to only cope with the wireless from the gui if you disabled the wired from the sys-net devicelist (or i am misremembering something). -- 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/e849f81b-805a-4f3e-888d-b3580c4479ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] lemur7 Unable to reset PCI device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-02 22:27, pixel fairy wrote: > used a working desktop to install and update to qubes-unstable. > this time the lemur was able to boot, but sys-net could not run. > heres an hcl-report followed by a typescript session showing pci > devices and the error. adding pci devices to sys-net in the > qubes-manager gave the same result. > > [...] Sounds like you might have the same device assigned to more than one VM. When you try to start sys-net, is there already a VM running (e.g., autostarting) with one or more of the same devices as those assigned to sys-net? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYa7dIAAoJENtN07w5UDAwWjsP/Av7m3ts3Bb7LMcuancJptZC WOm2hHlDY52dxjVtVc3OC8dEtmNCUTaVnEpf6RmDu0WUdT3ejMIduMe7+jOnp9dK ee9R7kuqlBJPBRJvvHSLteWPk/+SSZ+ZzsH1LeSYdg/F3v6Yzy9KoaE5Pia5+aUI 4MKBrpt9TFXvPmFGEyHnDWxx1SxG/AORPTFf/GQVIJI2/NMkPYKeP9uc8lwbnZRc tPBznNWYbTtxlSTFOfXgAgMET7coqNYhO53F3rzSccViGoj9p/M4nIX+D9tzNWX+ 0S/qzGveMoagmgt97rFjf+h/rkEinEHBravkiW54Nu8PHUwGbgIBwQknTt3PoAPU IwEGwPCMoinZAOwTAe5WLuKoBjZKORlm7rqYmty0zJGeFXcXMhS9E8IYHojetcwy Z+99ULnsH1ZbwP+Bc/neuhnE1PHvzZr8b/YKZ2+jU5DG/DQuQSyq4K4ujGhI/Ur2 hjABiuIN6DlpOj+dQO+CuvcVv1CYtUTSzwhsqTlNsbPyKfojcQmrjbfUTy/8ScYu wqmVUtNuMNsiqn9HCj+fNc5TyX8jRlMhfrR1WIZWxe8VAQwzc6RjyVdG3W3I3Jhh NtkixpjjH5LvLJqgG1zSRks+TWMfo+5NnfxhNcpQq6SAwJKhMLhwQFOy7CA++BrZ x7zjbQ3uBZwQXqalNGVn =9gJh -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/52e055f1-7c93-1b3f-6630-da8251f977b0%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] SSD cache breaks Anti Evil Maid completely
Hi, I added an SSD cache to my Qubes installation, following Eric Shelton's instructions : https://groups.google.com/forum/#!msg/qubes-users/ArHTEeQAH8A/r9zzY0DLBQAJ It worked smoothly and well, and I can immediately see that my system became much faster and responsive. On the other hand, it completely broke my Anti-Evil-Maid installation. Once the SSD cache is configured per instructions, if I try to boot with AEM, it exits immediately to an emergency shell in initramfs, complaining that it has found the root FS to be unexpectedly unencrypted - most probably because AEM is unable to figure out the LVM cache setup properly. Uninstalling an reinstalling AEM after the cache is setup, unfortunately doesn't help. So I had to trade AEM for an SSD cache (which, in my own use case, is not dramatically critical, anyway AEM didn't work properly on my HP system...) But I wanted to document this to the list : SSD cache works plain good, but breaks AEM. ॐ -- Swâmi Petaramesh PGP 9076E32E -- 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/70021590-fb3a-4f95-9ce5-4b340530ddbf%40petaramesh.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Is Fedora Really A Good Choice For QubeOS?
This thread just sprung to life again. I had a quick look at https://www.qubes-os.org/doc/templates/ And along with Debian which is installed by default both Arch and Ubuntu Are available... My personal preference in Ubuntu because it generally just works, and Arch because it has the latest version of everything when every you have the problem that xyz does not work because it needs the latest version. That the distribution maintainer has not yet made available in your favourite distro. I have not yet tried these templates. Since I am a xfce fan I love qubes UI along with all the other parts. Only gripe is no Win10 template ( and the various issues getting Windows to work - no password ). Regards Ronald -- 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/99bf19f6-e364-4c03-917a-fc15ced62787%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Best way to install qubes on mixed ssd and sata disks
Looking to reinstall qubes from scratch and would like to optimise the use of the ssd so I execute as much as possible on the ssd and use the sata for storage. I have a 500gig ssd and 1 tb sata. Thoughts appreciated At the moment I installed qubes on the sata drive to test out and experiment on. Regards Ronald -- 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/2ad0b6e3-5586-436e-aed6-29f6d2eb6e99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to install sabnzb+ in qubes
Hi folks, I installed sabnzb+ inside a appvm with debian-8 as template. the problem is that sabnzbd van't connect with a usenet server on port 5563 and the serveroption for ssl connection is greyed out. Does anyone use sabnzb+ succesfully? Help would be 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/0dd86915-5c0a-4f26-93f1-bc91ab0b0c70%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
On Tuesday, January 3, 2017 at 6:54:24 AM UTC-5, Fred wrote: > I can't help but I had this happen once using Xfce as the desktop. All > my 'start menu' disappeared bar a few. It happened to me at least once before under R3.1 as well, also randomly with no obvious or apparent cause. The System Tools menu items stayed gone for several weeks, then one day after new Dom0 updates they magically re-appeared again, with no explanation. I can also confirm that at the login screen if I choose xfce as the desktop environment, the missing shortcut issue still persists, so it isn't an intrinsic KDE thing indeed, as surmised. On a related note, I'm not even sure whether entries like "DispVM: Web Browser" are meant to appear under System Tools in R3.2, or if that is a menu glitch as well. Previously DispVM had its own top-level menu entry like any other AppVM, under which different app shortcuts appeared, so I don't know if something else has gone wrong. Is there a text file somewhere in Dom0, from which the System Tools menu obtains its default list of items? And if so, is it possible for someone with a functioning menu to "dump" the contents of that file here in this thread, so that I can copy and paste them into my presumably broken source file here, if such a thing is even possible? > I re-installed. Possibly a bug then in this case? I would really, really, really like to avoid having to re-install my entire operating system just to fix some missing menu entries, especially since it could presumably happen again at any given time thereafter. No other template or app vm's are affected, only Dom0. Surely there must be some alternative way to fix this issue, without resorting to ssuch drastic measures. Anyone? -- 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/4224ce3a-0cf9-4b11-abd9-824ee30f88b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Dom0 (System tools) shortcuts suddenly disappeared
As one approach, is there any command that will force a re-download and re-install of ALL dom0 packages and components, despite cache showing them as already up to date? If one or more elements are broken or corrupted, a refresh update might do the trick. Similar to if I'd made a dom0 backup and wanted to restore it completely. But since I don't have such a backup, can dom0 be effectively restored with a terminal command that will force-refresh everything from the repository? -- 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/8ada30a0-635b-4f0d-a0b6-1efea184a708%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] removing of f23 template did not go as planned
Has anyone else run into this. I was attempting to remove the Fedora 23 template as I no longer use it. I removed my cloned F23 templates with the gui manager and that went OK but when I did a dnf remove from terminal in dom0 for the main template I got a bunch of file not found errors and even though it says it removed the template and can't be found with dnf list or in qubes manager, the template entry is still in my application menu. Any suggestions on how to clean this up properly would be appreciated Below if the output of dnf remove $ sudo dnf remove qubes-template-fedora-23 Dependencies resolved. Package Arch Version Repository Size Removing: qubes-template-fedora-23 noarch 3.0.6-201608081228 @qubes-dom0-cached 3.3 G Transaction Summary Remove 1 Package Installed size: 3.3 G Is this ok [y/N]: y Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction A VM with the name 'fedora-23-dvm' does not exist in the system. --> Removing menu shortcuts... Erasing : qubes-template-fedora-23-3.0.6-201608081228.noarch 1/1 warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.03: remove failed: No such file or directory warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.02: remove failed: No such file or directory warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.01: remove failed: No such file or directory warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.00: remove failed: No such file or directory warning: file /var/lib/qubes/vm-templates/fedora-23/apps.templates: remove failed: No such file or directory warning: file /var/lib/qubes/vm-templates/fedora-23/apps.tempicons: remove failed: No such file or directory warning: file /var/lib/qubes/vm-templates/fedora-23/apps: remove failed: No such file or directory Verifying : qubes-template-fedora-23-3.0.6-201608081228.noarch 1/1 Removed: qubes-template-fedora-23.noarch 3.0.6-201608081228 Complete! -- 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/K__s8p3--3-0%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] QTW status in Qubes 3.2
I'm looking to find out the status of Qubes tools for Windows in Qubes 3.2. Is it stable enough that I could run a Windows VM for things like Quicken? Does it support audio devices yet? -- 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/145da196-c243-4548-85b7-bc4cf8833e8d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Computer Models Guaranteed to work with Qubes 4.0?
I would like to start saving up for a desktop that will run 4.0 out of the box. Price isn't really an issue; what's important is that I have a computer that meets all the standards necessary for running 4.0. I have looked at the HCL list, but none of the machines have been tested with 4.0 (which I understand, given that it is still in alpha). Would it be sufficient to just get a machine with one of the processors listed in the ark.intel link on your site's "Minimum requirements for 4.x" page? Or could I even just replace my current processor with one of those listed there? Otherwise, if anyone can point me toward a machine (or better yet, a few different machines) that will meet all the necessary requirements, run the OS with sufficient hardware isolation, etc., I would be most grateful. Thanks in advance for your time. -- 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/cYX4B2e7z_zFKlAp5kUSuy0HIUAwQfdwR6Y5XwayCbhjbQkAMEU4javhYhGW_QTIj_n4GioIQkZhaYBo8bAtagFzlZKIXLZiXZXgK97oT48%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] removing of f23 template did not go as planned
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 11:48, cubit wrote: > Has anyone else run into this. I was attempting to remove the Fedora 23 > template as I no longer use it. > > I removed my cloned F23 templates with the gui manager and that went OK but > when I did a dnf remove from terminal in dom0 for the main template I got a > bunch of file not found errors and even though it says it removed the > template and can't be found with dnf list or in qubes manager, the template > entry is still in my application menu. > > Any suggestions on how to clean this up properly would be appreciated > > Below if the output of dnf remove > > $ sudo dnf remove qubes-template-fedora-23 > Dependencies resolved. > > Package Arch Version Repository > Size > > Removing: > qubes-template-fedora-23 noarch 3.0.6-201608081228@qubes-dom0-cached 3.3 > G > > Transaction Summary > > Remove 1 Package > > Installed size: 3.3 G > Is this ok [y/N]: y > Running transaction check > Transaction check succeeded. > Running transaction test > Transaction test succeeded. > Running transaction > A VM with the name 'fedora-23-dvm' does not exist in the system. > --> Removing menu shortcuts... > Erasing : qubes-template-fedora-23-3.0.6-201608081228.noarch > 1/1 > warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.03: remove > failed: No such file or directory > warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.02: remove > failed: No such file or directory > warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.01: remove > failed: No such file or directory > warning: file /var/lib/qubes/vm-templates/fedora-23/root.img.part.00: remove > failed: No such file or directory > warning: file /var/lib/qubes/vm-templates/fedora-23/apps.templates: remove > failed: No such file or directory > warning: file /var/lib/qubes/vm-templates/fedora-23/apps.tempicons: remove > failed: No such file or directory > warning: file /var/lib/qubes/vm-templates/fedora-23/apps: remove failed: No > such file or directory > Verifying : qubes-template-fedora-23-3.0.6-201608081228.noarch > 1/1 > > Removed: > qubes-template-fedora-23.noarch 3.0.6-201608081228 > > > Complete! > Not sure why the removal failed, but you can clean up any remnants by following these instructions: https://www.qubes-os.org/doc/remove-vm-manually/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbBIxAAoJENtN07w5UDAw4nAP/0B5uG/PS602aAvIdOuXM+Cb c7HFlQL+n+08p7JwTRYnlOifPj3+MLSpPFBB6db9T2l/zwMWvKyKKk4CtS0t6ady ftCTUjMWnaql35/YeJ2qZQzfaw3ihkHDvy4pPsrFpmHOSMFmSChRIeqA+AjxYgge NZgPgbHvComjtq4++RuJan+FJ/LmtX8ahG5EVN3KszVvqULOHYunpznqovDIT371 4bHfD7OH3Nb1J8Ee8U/SnlPkEfOp6V4/0nRqku2xiZ13GgBtTrWXZ4XJwP16Og94 bS5Tr1K5Rsw7ZmiJWAazTfwoHhOc0fWdyhaa+f2siuYiBTKTByy0qwXVWkLKWvXz 6NwukOAKIe2zSrPPQ2vTypi+lybCZQIDjeOx2DXHMHSN3EfyBAlyiD4vrTCiom6t oW5Boyr1hUoXRtaL1r7jCz0wQ3Dxm3cq2N2lVz8xqGJWqWU0uU+kqL8T1Aq1bZUk NXeuIgDou1nDL3MOKM2H5nX7pCVVr6H32RIUkj9EuOxkH6RZuFYnrS1Js4xwRdrR OtnI5yu6OQV29HUmagunkPdCEAgpQnKMfR7iwVbxmmukCzcmNtBgRoRuCPeF6P8A mnkFMhjQoQAwDG3za1kcX5fk+wt4b31ODdvN5L8qR2I+2HHwS8hrqCMSDa1KotTk ujjQi9DTStRpJ7v6Zk67 =9s6J -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/80f8884f-df7b-8652-8512-21eb993305ec%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Computer Models Guaranteed to work with Qubes 4.0?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 13:01, 'James Funkhauser' via qubes-users wrote: > I would like to start saving up for a desktop that will run 4.0 out > of the box. Price isn't really an issue; what's important is that I > have a computer that meets all the standards necessary for running > 4.0. I have looked at the HCL list, but none of the machines have > been tested with 4.0 (which I understand, given that it is still in > alpha). Would it be sufficient to just get a machine with one of the > processors listed in the ark.intel link on your site's "Minimum > requirements for 4.x" page? Or could I even just replace my current > processor with one of those listed there? > > Otherwise, if anyone can point me toward a machine (or better yet, a > few different machines) that will meet all the necessary > requirements, run the OS with sufficient hardware isolation, etc., I > would be most grateful. Thanks in advance for your time. There are a few different levels of compatibility. The highest is Qubes-certified hardware. Unfortunately, I'm not aware of any machines that meet all the certification requirements for Qubes 4.x.[1] But this shouldn't be too surprising, given that those requirements are exceptionally stringent and intentionally aspirational. The second level is the recommended requirements.[2] The fast SSD and Intel IGP requirements are mainly about convenience and compatibility (e.g., avoiding the troubleshooting hassles of discrete graphics cards). A TPM is required for AEM, but if you don't plan on using AEM, then it's not necessary. A non-USB keyboard or multiple USB controllers is required if you wish to have a dedicated USB qube and to use it safely, since otherwise it would control your keyboard (and either your keyboard controls dom0, or you don't control dom0). The lowest bar is the minimal requirements.[2] Even the minimal requirements for 4.x are quite secure, since they now include VT-d and VT-x (which weren't minimally required in previous Qubes releases). VT-d is required for isolating devices (e.g., networking, USB),[3] and VT-x is required for running certain kinds of VMs (e.g., Windows).[4] This should be relatively easy to achieve, but you have to attend to more than just the CPU's properties. For example, it's not enough that the CPU alone supports VT-d. The motherboard has to support it also. [1] https://www.qubes-os.org/news/2016/07/21/new-hw-certification-for-q4/ [2] https://www.qubes-os.org/doc/system-requirements/#qubes-release-4x [3] https://www.qubes-os.org/doc/user-faq/#can-i-install-qubes-on-a-system-without-vt-d [4] https://www.qubes-os.org/doc/user-faq/#can-i-install-qubes-on-a-system-without-vt-x - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbBZAAAoJENtN07w5UDAwqCcP/2A1mBh+EuUzNJYyF30xmj6D 5Kbt18QBw3jXf1wD9qJQtaio2eEgoskeMPU7eWvHbrr1/xFIe974oXda25ZmDj0T lCrVBtCuomnZH82A+lA7ckVH/i4K4X1Wf73KNENFhpYd62i95HwZNSuQgU9MpsB3 makuaAg9mfmnlxrsz0k9rK2XQERaeZlToq1vvW1os85O9H6XQxOYYR9cOvg0EqdJ VScVcPVuUCqQtElNuwAIiNKKGqS0kijuCA53HbhvnST8HGy83cdz2T9Ag0wyPB8L y/2KxEBVlPGwEFIeMfYSNfVZF97ZKmOSMFGVD5rQO+A4pHBpBgvzV3/aM1+OH4BE iIR/ecudmGMvoRQVQ9aA7reQO5qSU4oeVgMOTuMs81VNHMzIeCap9G5GUSU6Lshk UPM9Y8gGAXlno5pYEoBPz94A1d3j/op0vtI+huSlV8KMbepHU84z8fz9xgh2zRkc /EsNkHwjqfs8dZ+GAiG6xeuVaOmlhib6YR+75/0zIJ/bZklH+VWK3K5z59M3uoCb AuXHf72uuRWVaGJa3l+ShrHiCAotcQVeop1c9OYPPbo3TWcJXbs0A9NNmXfWGd3I 1cnzxISw6PoDQcGpH4Tmdb9jPujfT4EybLkUGZ0Xgtbb17Y3qvE4RWoE1aHy0j+0 5KUVQgEh/ZwZBW9IZGN+ =m5/i -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/55e1d319-12ba-977f-3901-bcaa34179d3f%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 09:55, Otto Kratik wrote: > On Tuesday, January 3, 2017 at 6:54:24 AM UTC-5, Fred wrote: > >> I can't help but I had this happen once using Xfce as the >> desktop. All my 'start menu' disappeared bar a few. > > It happened to me at least once before under R3.1 as well, also > randomly with no obvious or apparent cause. The System Tools menu > items stayed gone for several weeks, then one day after new Dom0 > updates they magically re-appeared again, with no explanation. > > I can also confirm that at the login screen if I choose xfce as > the desktop environment, the missing shortcut issue still persists, > so it isn't an intrinsic KDE thing indeed, as surmised. > > On a related note, I'm not even sure whether entries like "DispVM: > Web Browser" are meant to appear under System Tools in R3.2, or if > that is a menu glitch as well. Previously DispVM had its own > top-level menu entry like any other AppVM, under which different > app shortcuts appeared, so I don't know if something else has gone > wrong. > > Is there a text file somewhere in Dom0, from which the System > Tools menu obtains its default list of items? And if so, is it > possible for someone with a functioning menu to "dump" the contents > of that file here in this thread, so that I can copy and paste them > into my presumably broken source file here, if such a thing is > even possible? > > >> I re-installed. Possibly a bug then in this case? > > I would really, really, really like to avoid having to re-install > my entire operating system just to fix some missing menu entries, > especially since it could presumably happen again at any given > time thereafter. No other template or app vm's are affected, only > Dom0. Surely there must be some alternative way to fix this issue, > without resorting to ssuch drastic measures. Anyone? > I'm afraid I don't have any special insight into this problem. (I vaguely recall that it happened to me once on 3.1, then I think I ignored the problem and it eventually reverted itself somehow.) However, it occurs to me that what you're asking about is primarily a KDE issue, and the information you seek should, in principle, be available from a KDE source (docs, devs) or even Fedora or another distro that uses KDE. To clarify: The *cause* may be Qubes-related (I have no idea), but the default file/list for KDE System Tools should probably be the same as in non-Qubes KDE installations. At least, it's worth checking. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbBhQAAoJENtN07w5UDAweV4P/j8BRWWWX6JA8mA7G01dNfiQ LInayfOESqSI3Y+sU405Ci3hJVVNyzi2SB+IRbrtSvTXKYnPY1kIZ5YrtC88RZvf yxhYqzvgTCNiZxr4TTxxQGiFF0uC/b04xIS3+1WFgnb86D/DATMPPdHaSOA2xtCQ OzYOondRueTvuq1yZLZxBwYAXM7LUqAL5gHqammFAyWve7r4L/RFta4JKp/FFwV4 YP6XPuu0KvgxgYUxF1+cM2+D2pvi/4CEO321Zwh2DtOFx2kzNBF/6XOL78akWtt0 D6aTcKfhIENs8ho2oB1MfxeBPQeQFKhC5Xcf/1V4oYrHmUdw6D8L2ecqCSyPkmXY aHRwZm6ASktYvsNgdKd8aGeaerLZv40XJ6bOwHMXOKiAAmbDQvEDkw2Ni0MQCQxv VBIoBAjfjmn8ms6/kULWUdOpWmun+Oz2Qtm6BYAWppos2hjBtoZI23B9MWOMRQVE HzFUWbtU2aynkHh1H5i17N/Ow469MwGJxGzKPj01Yuzz81tRJi5h7YvVcWUts354 k1SIjLUXHPeVVnurDv/Iux6ebqXDxris1AicR1pEfzMtJKGnckfq6/QvL+2wZeMd KBgiF3I3aVFqr7zgr293YGrJS/lqydVPtYylMemPOd/4uDwHeWrpTCd929TaRC0T zx+c5ZySRav/6gd0DIH2 =aXp6 -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/d498e413-0bac-a9b0-6c47-b83041adf85b%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Best way to install qubes on mixed ssd and sata disks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 08:38, Ronald Duncan wrote: > Looking to reinstall qubes from scratch and would like to optimise > the use of the ssd so I execute as much as possible on the ssd and > use the sata for storage. > > I have a 500gig ssd and 1 tb sata. > > Thoughts appreciated > > At the moment I installed qubes on the sata drive to test out and > experiment on. > > Regards Ronald > Personally, I install Qubes on an SSD and leave all of my frequently-accessed VMs on there. For infrequently-accessed, bulk-storage VMs, I use this method: https://www.qubes-os.org/doc/secondary-storage/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbBivAAoJENtN07w5UDAwceQP/0QX1OmJb3/i14ZEWETi0bYA 725uoQfPcBuTHAAhT/Kis6QhJXvXE7BYNXdHoPOVZI5IHTb3ctQeAMPv6k0BS9AE bDjex0z9xrH551/QeuE/KC/vkdywobGncardL19AfFHpSSxuAQ04erhWb95D0nrz tRbp8wRBHU+bqnodH0q4Ik8dHeKzkT0T8gE3GS5MzwksZ6xJoIJOyjrIfa3Y5g9F 2VhzYIhYfLEeDQHLTizPS5HXl8nTQnE4j2pzd7qcHCv/sijN4gK0rWvhTeCHe9S9 kVB7tI5pljBbJOydtQ/zL/Ne6cCE8CNr+DqONa+Q/o91vR2N51M/1+qWFfG5dc9D vmaJhlDtsyDUYTtoMUmLrtjT6pSILG+0M/ZN08cVUv6Q5mQ5comF1G7DC3FLB0mg CLLRGpqAs6scxAkDGJePKubT/yR90aJPjY/TK/7Ys+RjIXJL092oR4ttZxDx6JNe gbJzyQRAlStnWVmDQoKa/mw0Kw6ajNvPif41eTcqszez0t+eXuLBdr9ZZr5/C4i1 w8F8U/q6qyR9VMEymEw/7uc0OWerxeqSIvxbe9YsOA5oaN2GNEObS0cVNim28gTx XKoj3vkrAbQ8NFXAKoepf2ckudDvs6Owy+1PBsZbsM34YGeHEP+a2mrd3ygjL/N0 Cf8aEwwAxmiN5Ohzoley =OxIo -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/0d219517-bb6a-37ba-e5b5-6d15398f0744%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] QTW status in Qubes 3.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 12:22, Raymond Rizzuto wrote: > I'm looking to find out the status of Qubes tools for Windows in > Qubes 3.2. Is it stable enough that I could run a Windows VM for > things like Quicken? Does it support audio devices yet? > Still in testing/development, but might be stable enough for your usage. (Consider testing it if you can.) No audio yet, AFAIK. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbBkCAAoJENtN07w5UDAw7w8P/151/Z7xZ5IwrGP2b14Dpeil 9zKnlOCZr5bkcza/9hPIhIJ0pf3mqdxigTCXuTmExA9LXMp9UIA4WWP19XGmsX4B qYvQPnU6XWO3uAeGN3vpVhPXyxg0NG3xOVZCE/jFdyEWrp4iw2Ah0K1YXSHm3Q+X QbgEFvtvcICdEm9WGSDhELhMH4yiqzajphd3OCELjk/APnfEKDzaYkaU+FkiSk40 ObheN/xqAiL6GjTS6Oa7azV93WZEY20PywhbYd1rwiNTsi5YLdG/o/t5xfhKQGmT aGTYy0r6boxNBLYkJMlih5jpOfUuwk3VJWXXJcxZx9VLM05xqOUUGA93XDIiLjes 8ZtP1JG2P/u1PjsEEAtaXGEtu4gzIEkBAR7e0ldrY2UCcMHcrfc7ApvuyL3+HrQY 3JQrQ/bwTbiTqWVkPlNl0nJTmMB8hDsSY626CMVSV1/xjBJhUx0Ze41WvEMsikFU dx9JoP/t9I8q9WfNihHNrGwQyHEFbxpn0SbV+Pw7kc3Wbh6lRIU2qO4dtgmATQwg R+24pemhWP6Mp96ld2ZfsKDUot47HQef/sF0qSgD0w6csLj1ZWhQScVgajdUqw7e afVnqWc4owiILmDVMuee+BrAn4EFCicBWwjPlfLf+Tlwdnbhaq/tsIYMJceuxAed gz/5P4A9n0WTWDM+UfxH =7wXs -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/e62cd9b2-68b2-448b-e6b8-43084ab7451d%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] SSD cache breaks Anti Evil Maid completely
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 07:03, Swâmi Petaramesh wrote: > Hi, > > I added an SSD cache to my Qubes installation, following Eric Shelton's > instructions : > > https://groups.google.com/forum/#!msg/qubes-users/ArHTEeQAH8A/r9zzY0DLBQAJ > > It worked smoothly and well, and I can immediately see that my system > became much faster and responsive. > > On the other hand, it completely broke my Anti-Evil-Maid installation. > Once the SSD cache is configured per instructions, if I try to boot with > AEM, it exits immediately to an emergency shell in initramfs, > complaining that it has found the root FS to be unexpectedly unencrypted > - most probably because AEM is unable to figure out the LVM cache setup > properly. > > Uninstalling an reinstalling AEM after the cache is setup, unfortunately > doesn't help. > > So I had to trade AEM for an SSD cache (which, in my own use case, is > not dramatically critical, anyway AEM didn't work properly on my HP > system...) > > But I wanted to document this to the list : SSD cache works plain good, > but breaks AEM. > > ॐ > Thanks for the report! Added: https://www.qubes-os.org/doc/anti-evil-maid/#known-issues - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbBpLAAoJENtN07w5UDAwwakP/1lk5JU3mI5G35I4m+Df1MV6 XJmh0BndXXT/okyKRQVqCj0A/8whU9zZ7dEddKhGa9njJuEIn3gLlG7DiknxAKtf P+wa2OlhKeY5+y2v3fMqxZvjgdOlJIEsOdSc40tJXLxidqY9huE2vlkRvxrj+6Zp 4rcn932Qg+22GMjdor/e+cRAaVAhebdzoTtYDbo3OokXMF0rze6B1NpRsyzKW7iF uBSqMt6Xxmm4cVBbnXtehdubFDETJvxdZ+oRVOwir7hPK+xhc4bCv6EbZDL9BmZA 5hYJ5sHkcGR7BT5f1ShDZWk5hrvSNk5JmiCZTxXxeEGOrDcd/H/DtcCp2/0Xpc7n ZZBQyXunfnIx/kmFCudzpgOwWV01hl6FXzjQFb17TT918/66U2Z+ZIO8H/qAzF83 sibHRJtQ9uR22tT0ZLios7Kx+p0TKGAGjC+pApf2MXunFsVTaCzFi8NQTyvTR87B cnlagAdo+6hsInBo37VAZOo8AzP8+L5TntOOsLiPp8T+6DvYmmYr+0P2y7C/Mg42 NOB6xOHVk1dQzkpPIW50bZWkpX8uCWFQKLFK8fp59TXPdYdYU1lLhDkhjaqnK1sD xKjKQ53Tiqb6ALJt3fa1YOUwD7Fez3pC7gXx5DPQhHQTfrHj5rJdbMr0BGAAH1xJ aBkr+BVJPo3hb1Lv97rG =uxnl -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/253f6fab-fc8d-2e9d-da01-fe8074a96ccf%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] removing of f23 template did not go as planned
3. Jan 2017 21:05 by a...@qubes-os.org: > Not sure why the removal failed, but you can clean up any remnants by > following these instructions: > > https://www.qubes-os.org/doc/remove-vm-manually > Fixed, the dnf remove cleaned up everything but the .desktop files. rm'ing those got rid of the app menu entries -- 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/K_aI0Cg--7-0%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
On Tuesday, January 3, 2017 at 4:32:11 PM UTC-5, Andrew David Wong wrote: > I'm afraid I don't have any special insight into this problem. (I > vaguely recall that it happened to me once on 3.1, then I think I > ignored the problem and it eventually reverted itself somehow.) > > However, it occurs to me that what you're asking about is primarily a > KDE issue, and the information you seek should, in principle, be > available from a KDE source (docs, devs) or even Fedora or another > distro that uses KDE. To clarify: The *cause* may be Qubes-related (I > have no idea), but the default file/list for KDE System Tools should > probably be the same as in non-Qubes KDE installations. At least, it's > worth checking. The file may possibly be in the same place, but of course in the case of Qubes it is a customized one containing entries like "Qubes VM Manager" etc, so I would need that specific one. I don't know the default location. Also as noted however, it makes no difference whether I use Xfce or KDE. In either case I have no menu item available anywhere for "Qubes VM Manager" which I normally would, so it is a pan-desktop-environment issue, likely related to Qubes itself rather than one of the DE's. So far I have not found any solution to this, and am looking at a complete system re-install in order to fix one single interface issue. -- 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/c49af7bb-2d47-4783-85c5-a9d1b72205ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, Jan 02, 2017 at 08:35:14PM -0800, Otto Kratik wrote: > I am using Qubes R3.2. Suddenly almost all of the KDE shortcuts usually found > under applications-> system tools have completely vanished. I have no > konsole, file manager, system settings etc. Only four remain: > > DispVM: Terminal > DispVM: Web Browser > Screen Capture Program > Software Management > > Everything else is gone. They were there one minute, and then gone the next. > I have performed Dom0 updates and rebooted afterward to see if it fixed the > issue, without success. > > What is the recommended course of action? Try running `xdg-desktop-menu forceupdate`. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYbC1rAAoJENuP0xzK19csMXkIAIs1PHY7V62dpSzxl2JfqWTC swLK8RSqJmj6uqWzLJoSRkTkErS4gEClZmcas49GIaPnxKnusWjFOpGSPXzH7bIC zBKV8JLGOgG5819CS116HTJW52LLw6rx1ps13NvQUmf6xikgVy5ABqG57q8SfKl9 1U0dDXi+GEyeghvpTcm5MYmWnjAhKfuU/TxPbuWy1SUZBF7VeFGwhXFEjyRs7RaD O/IvXWTCzQI5GNq7vE5+H3Oc3PhgOv1bUIqY7V/MHPGrH5oRmkBPKuo9gCSEyZpW a5lwNtDrTpVHemRoO3jatZ70CZJadTHnw9Tz4Z5dYUYnN8kyPBxddS4T1lA1lmc= =6x9c -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/20170103230203.GD5268%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Is Fedora Really A Good Choice For QubeOS?
On Wednesday, 4 January 2017 02:19:20 UTC+11, Ronald Duncan wrote: > This thread just sprung to life again. > > I had a quick look at > > https://www.qubes-os.org/doc/templates/ > > And along with Debian which is installed by default both > > Arch and > Ubuntu > > Are available... But not for Dom0... that is the main issue for me. Need a Slackware build. At least then there will be no SystemD crap. > My personal preference in Ubuntu because it generally just works, and Arch > because it has the latest version of everything when every you have the > problem that xyz does not work because it needs the latest version. That the > distribution maintainer has not yet made available in your favourite distro. > I have not yet tried these templates. > > Since I am a xfce fan I love qubes UI along with all the other parts. I am an xFCE fan as well. It's a simple interface and just works smoothly, unlike KDE and Gnome which are so bloated. > Only gripe is no Win10 template ( and the various issues getting Windows to > work - no password ). I have found no issues getting windows to work with no password. I just set the auto Login, and done. There are no tools for Win10, so until then, all good. But if you want to use the tools, stick to version 3.2.1.3 until they fix them, because the tools got broken in version 3.2.2.3, and I have not seen a version that is fixed yet. -- 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/42d41a16--4cb7-b106-b815841d5d38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Computer Models Guaranteed to work with Qubes 4.0?
The lowest bar is the minimal requirements.[2] Even the minimal requirements for 4.x are quite secure, since they now include VT-d and VT-x (which weren't minimally required in previous Qubes releases). VT-d is required for isolating devices (e.g., networking, USB),[3] and VT-x is required for running certain kinds of VMs (e.g., Windows).[4] This should be relatively easy to achieve, but you have to attend to more than just the CPU's properties. For example, it's not enough that the CPU alone supports VT-d. The motherboard has to support it also. I see. I can then shop around for devices that have one of the CPUs listed as being compatible. But what about motherboards? Is there a compatibility list for those? -- 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/NFxdUlBeNwXu8EJh5WZB3WTYOPoRQVCUBG0V-_USoSxri19StS4t4dQIIuXSUwQoLhk4ZKivgxx7N1r9A-GEtpYh77r_oDDkAUUwAZ5zgAI%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Shading doesn't work as it's meant to.
Hi folks, I've been shading for a long time, and I've found that it's glitchy and buggy, and doesn't work the way that it's supposed to in Qubes. This needs to be fixed. One VM, I shade the window, click on the window behind that's in the same VM, and all I do is click on the content of the window I just shaded. In linux, shading normally works fine, but it seems that the shading may not actually be transferring to the guests either. This really needs to be resolved ASAP. It's the most annoying thing when using Linux the way it's able to be used. Well, maybe not the MOST annoying, because there are other things that I've mentioned in the past that have yet to be resolved that are annoying issues too. But they will eventually get fixed in 3.2 or even when 3.3 comes out. -- 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/b28fa59c-f903-44af-9a15-6876a0889664%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
On Tuesday, January 3, 2017 at 6:02:09 PM UTC-5, Marek Marczykowski-Górecki > > Try running `xdg-desktop-menu forceupdate`. Ran it as su from dom0 terminal. Command was accepted, but no noticeable effect or change, or output. -- 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/d9ecc53c-b93d-4dfb-ba42-b5146d6ef987%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to set file association in disposable VMs?
On Tue, Jan 03, 2017 at 08:57:58AM +, Robin Green wrote: > On Tue, 3 Jan 2017 at 03:14 Unman wrote: > > > > > Original Message > > > > Subject: [qubes-users] How to set file association in disposable VMs? > > > > Local Time: December 29, 2016 7:48 PM > > > > UTC Time: December 29, 2016 11:48 AM > > > > From: gree...@gmail.com > > > > To: qubes-users > > > > > > > > I have configured Nautilus in an AppVM to open PDF files with Okular, > > and > > > > I've then done the same configuration (as user "user") in the > > TemplateVM > > > > that the disposable VMs are also based on. However, when I choose > > "Open in > > > > disposable VM" from that reconfigured AppVM, even though the dispvm > > > > savefile is updated before launching the dispvm, it still uses the > > default > > > > PDF viewer instead of Okular. > > > > > > > > > > > > Sounds similar to this: > > > > > > > > > > https://groups.google.com/forum/#!searchin/qubes-users/open$20in$20dvm|sort:relevance/qubes-users/GZ2zWcoMuwc/vwAzmYS5DgAJ > > > > > > > > --WillyPillow > > > > > > > > You don't say *how* you have changed the association. > > > > I changed it using Nautilus, by right-clicking on the file, Properties. > > > > Try changing the file association in the template: > > mimeopen -d file.pdf will allow you to set the default application. > > Close down the template. > > Then make sure the dvm file is regenerated before opening the dispVM, > > as you have done. > > > > That didn't work either. Please note, as noted already in this thread, this > is a known bug. > Did you actually read that bug report? I'm amazed it's still open. I assume that you are using a Fedora template since 'mimeopen' works for a vanilla Debian template. For Fedora based dvms, the dvm does NOT pick up the association from the template. It's therefore necessary to customize the DispVM: there are instructions for doing this in the docs. In brief, for a fedora-24-dvm: qvm-run -a fedora-24-dvm xterm In the dvm: mimeopen -d test.pdf touch /home/user/.qubes-dispvm-customized sudo halt Regenerate DispVM template using qvm-create-default-dvm: qvm-create-default-dvm fedora-24 I haven't tested this with Okular, but it works for setting other default applications. Can you confirm it with Okular? -- 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/20170104001653.GA27422%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] OnionShare
> On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: >> Does OnionShare work safely in Qubes? >> >> Gave it a try with an AppVm based on a qubes-debian template but wasn't >> able to get it working. >> >> Haven't been able to find any posts in the qubes users or devel forums >> about this. Did see some discussion on the whonix forum but that looks >> to >> still be in the development stage. >> >> Would it be possible using a non-qubes debian or fedora hvm? >> >> > > You don't say why you weren't able to get it working, or what steps you > took to troubleshoot the problem. > I can confirm that it works fine on a standard Debian appVM. > > From your reference to whonix, I suspect that that is your problem. I > don't use whonix so cant check this but I believe that onionshare relies > on access to a tor control port opened with Tor Browser. I think that > the whonix design would preclude this. > > You can try with a normal qube connected to sys-firewall. You can't use > the normal qubes torVM because that doesn't have the control port open, > but with some minor modifications you can fix this, and then try to run > onionshare there. > > I don't believe there are any "safety" issues. > > unman @ unman: Thanks and you are right. I should have included the steps taken to troubleshoot. Steps taken: 1. Using a cloned qubes-debian template created an AppVM. 2. Installed onionshare via debian apt-get. 3. Was able to open onionshare but not able to connect using sys-firewall as the Net-VM. 4. Deleted the AppVM, created new AppVM and reinstalled via debian apt-get. Although onionshare appeared to install properly, onionshare was not accessable via konsole nor visible in file manager. 5. Installed in the cloned template with the same results. unman quote: I can confirm that it works fine on a standard Debian appVM. As I'm unsure, are you referring to an AppVM based on the included qubes debian template? Maybe a problem with the debian repo? Did you install via debian repo or do a build? -- 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/d9cee31f9b667534fd695f3ec64c487e.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: How do I get Qubes 4.0 pre-release/dev build?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Dec 30, 2016 at 05:29:05PM -0800, HiringQubesExperts wrote: > On Wednesday, 30 November 2016 17:49:06 UTC+1, bent...@cloudctrl.nl wrote: > > Hi, > > > > I've been using Qubes-OS since R2, and I would like to start using the > > development build so I can try and do some testing for some unikernel and > > mirage-based security stuff I want to implement. > > > > Can someone tell me where I can get the files? Any tips or hints when it > > comes to running the latest build? > > > > Hope someon can help me get it. > > > > P.S. > > How long before the first rc will be released? This shouldnt be much longer > > right? > > Hello? Can someone please give me an update on this topic? I would really > like to build 4.0 ... Have you seen this message: https://groups.google.com/d/topic/qubes-devel/2DMBT2eBbyw/discussion ? - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJYbEWGAAoJENuP0xzK19cs3h4H/3gh2Bfkfm3fuO46zlkICGo+ uYk1MnjELy7/u4+YaBLWA9bmC9+s3xmGbMR0KmjmgeCnw9DFPVJe8LdAN6MvYmNy XQJW4wqnE7QhvlzZkQpiIoRxg8qCcATFPCXEzAuNCpTXnVGMvlGFgswc6bbZ3TjE hPhdDUCNF5KikXUFSxNjchozlirVQ1htHwjnzi3VS2yXVRN9KA4VNgx8nVxx5qT2 epmf5nqd+j3wQOtk0aYsCuYpuJUgwtheK4Oev7uFjBH6hnsUfguVJK89MsiJZ7Bi RZvP8o7JdHKJ2AfNeDEJhrFo3+9EQyAKzvXKjSD/8aIMm6SULe+QOpESJyj5qDE= =bAWY -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/20170104004453.GF5268%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] OnionShare
Another thought not related to the inability to access onionshare the second time... Could using TBB hardened vice stable version make the connection fail? -- 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/63a7fc2b8cd911bb078e5aa8fe3feee8.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
On Tue, Jan 03, 2017 at 04:12:28PM -0800, Otto Kratik wrote: > On Tuesday, January 3, 2017 at 6:02:09 PM UTC-5, Marek Marczykowski-Górecki > > > > Try running `xdg-desktop-menu forceupdate`. > > Ran it as su from dom0 terminal. Command was accepted, but no noticeable > effect or change, or output. > Have you checked the menu files? For xfce, in /etc/xdg/menus/xfce-applications.menu you should have a section with System that references qubes-System-Tools.directory There should be an section containing and Excludes for X-Qubes_VM and X-Xfce-Toplevel The actual desktop files should be in /usr/share/applications: check that they are there. Confirm the Categories of a sample desktop file. I can't imagine that these have been deleted - if they have then you don't need to reinstall, just replace the missing files. let us know what you find (or not, as the case may be). -- 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/20170104015557.GA28071%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] OnionShare
On Wed, Jan 04, 2017 at 12:39:39AM -, haxy wrote: > > On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: > >> Does OnionShare work safely in Qubes? > >> > >> Gave it a try with an AppVm based on a qubes-debian template but wasn't > >> able to get it working. > >> > >> Haven't been able to find any posts in the qubes users or devel forums > >> about this. Did see some discussion on the whonix forum but that looks > >> to > >> still be in the development stage. > >> > >> Would it be possible using a non-qubes debian or fedora hvm? > >> > >> > > > > You don't say why you weren't able to get it working, or what steps you > > took to troubleshoot the problem. > > I can confirm that it works fine on a standard Debian appVM. > > > > From your reference to whonix, I suspect that that is your problem. I > > don't use whonix so cant check this but I believe that onionshare relies > > on access to a tor control port opened with Tor Browser. I think that > > the whonix design would preclude this. > > > > You can try with a normal qube connected to sys-firewall. You can't use > > the normal qubes torVM because that doesn't have the control port open, > > but with some minor modifications you can fix this, and then try to run > > onionshare there. > > > > I don't believe there are any "safety" issues. > > > > unman > > @ unman: Thanks and you are right. I should have included the steps > taken to troubleshoot. > > Steps taken: > > 1. Using a cloned qubes-debian template created an AppVM. > 2. Installed onionshare via debian apt-get. > 3. Was able to open onionshare but not able to connect using sys-firewall > as the Net-VM. > 4. Deleted the AppVM, created new AppVM and reinstalled via debian > apt-get. Although onionshare appeared to install properly, onionshare was > not accessable via konsole nor visible in file manager. > 5. Installed in the cloned template with the same results. > > unman quote: I can confirm that it works fine on a standard Debian appVM. > > As I'm unsure, are you referring to an AppVM based on the included qubes > debian template? > > Maybe a problem with the debian repo? Did you install via debian repo or > do a build? > I used a qube based on the standard Debian template. Cloned with git and installed the dependencies, and the TBB. Started the TorBrowser. Ran the onionshare-gui script. Tested the connection to TorBrowser from File-Settings. Shared a file. I'll check using the Debian package. -- 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/20170104030248.GB28071%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Wifi Issues Atheros QCA9377
Hello Qubes World. I have spent the better part of 5-6 hours trying to figure out why my wifi will not show up in sys-net, it has never worked. I have read through every forum/post I could find and wasn't able to figure out the exact issue. I feel as if this is my last resort, I have to travel in a few weeks and if I can't get it working I'll have to abandon my 3 week qubes exerience. I'll provide as much information as possible to aid in troubleshooting. Appreciate any help given, thanks. Laptop: Acer Aspire E 15 E5-575G-76YK When I first start sys-net I typically have to kill it a couple times before it will even recognize my ethernet..what a pain. As for the Wifi I run dmesg and dont see any errors regarding that the device has failedbut i'm not really sure what to look for... I will post the output below ...can't figure out how to make a link to it yet so sorry for the expanded output. I've attempted to manually add the Wifi SSID and crap through the Network Manager and that didn't work either. It appears that it just isn't loading when sys-net starts up even though I've added the device in the devices tab. A lot of the ubuntu forums say to install "linux-headers-generic" and "build-essential" but those aren't listed in the repo The output of lspci shows the wireless adapter but one thing that I noticed is that it doesn't say "Kernel driver in use" like the others say (part of the problem?) 00:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 30) Subsystem: Lite-On Communications Inc Device [11ad:0806] Kernel modules: ath10k_pci The drivers are installed as listed in /lib/firmware/ath10k/QCA9377/hw1.0 sudo modprobe -D ath10k_pci insmod /lib/modules/4.4.31-11.pvops.qubes.x86_64/kernel/net/rfkill/rfkill.ko insmod /lib/modules/ 4.4.31-11.pvops.qubes.x86_64/kernel/net/wireless/cfg80211.ko insmod /lib/modules/4.4.31-11.pvops.qubes.x86_64/kernel/net/mac80211/mac80211.ko insmod/lib/modules/4.4.31-11.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath.ko insmod /lib/modules/4.4.31-11.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath10k/ath10k_core.ko insmod /lib/modules/4.4.31-11.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko Current linux firmware is 20160923-68.git42ad5367.fc24.noarch When I run the command "nmcli g" it shows the wifi enabled and wwan enabled. STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled ifconfig output: enp0s1f1: flags=4163 mtu 1500 inet 192.168.1.60 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::b353:2725:5528:1f78 prefixlen 64 scopeid 0x20 ether 54:ab:3a:81:38:24 txqueuelen 1000 (Ethernet) RX packets 25634 bytes 32481540 (30.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13396 bytes 1586775 (1.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Local Loopback) RX packets 84 bytes 8028 (7.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 84 bytes 8028 (7.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vif5.0: flags=4163 mtu 1500 inet 10.137.1.1 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::fcff::feff: prefixlen 64 scopeid 0x20 ether fe:ff:ff:ff:ff:ff txqueuelen 32 (Ethernet) RX packets 13246 bytes 1385694 (1.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 24267 bytes 32251590 (30.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I've attempted to install the kvalo ath10k firmware listed on github but it did no good. md5sums of the files were the same as what I had anyways modinfo ath10k_pci produces the following output filename: /lib/modules/4.4.31- 11.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath10k/ ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2
Re: [qubes-users] OnionShare
On Wed, Jan 04, 2017 at 03:02:48AM +, Unman wrote: > On Wed, Jan 04, 2017 at 12:39:39AM -, haxy wrote: > > > On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: > > >> Does OnionShare work safely in Qubes? > > >> > > >> Gave it a try with an AppVm based on a qubes-debian template but wasn't > > >> able to get it working. > > >> > > >> Haven't been able to find any posts in the qubes users or devel forums > > >> about this. Did see some discussion on the whonix forum but that looks > > >> to > > >> still be in the development stage. > > >> > > >> Would it be possible using a non-qubes debian or fedora hvm? > > >> > > >> > > > > > > You don't say why you weren't able to get it working, or what steps you > > > took to troubleshoot the problem. > > > I can confirm that it works fine on a standard Debian appVM. > > > > > > From your reference to whonix, I suspect that that is your problem. I > > > don't use whonix so cant check this but I believe that onionshare relies > > > on access to a tor control port opened with Tor Browser. I think that > > > the whonix design would preclude this. > > > > > > You can try with a normal qube connected to sys-firewall. You can't use > > > the normal qubes torVM because that doesn't have the control port open, > > > but with some minor modifications you can fix this, and then try to run > > > onionshare there. > > > > > > I don't believe there are any "safety" issues. > > > > > > unman > > > > @ unman: Thanks and you are right. I should have included the steps > > taken to troubleshoot. > > > > Steps taken: > > > > 1. Using a cloned qubes-debian template created an AppVM. > > 2. Installed onionshare via debian apt-get. > > 3. Was able to open onionshare but not able to connect using sys-firewall > > as the Net-VM. > > 4. Deleted the AppVM, created new AppVM and reinstalled via debian > > apt-get. Although onionshare appeared to install properly, onionshare was > > not accessable via konsole nor visible in file manager. > > 5. Installed in the cloned template with the same results. > > > > unman quote: I can confirm that it works fine on a standard Debian appVM. > > > > As I'm unsure, are you referring to an AppVM based on the included qubes > > debian template? > > > > Maybe a problem with the debian repo? Did you install via debian repo or > > do a build? > > > > I used a qube based on the standard Debian template. > Cloned with git and installed the dependencies, and the TBB. > Started the TorBrowser. > Ran the onionshare-gui script. > Tested the connection to TorBrowser from File-Settings. > Shared a file. > > I'll check using the Debian package. > OK, well apart from the huge dependencies pulled in, everything seemed to work. Created qube based on standard Debian template. Installed the onionshare package with apt-get. Started onionshare-gui from xterm. I had to start TBB - why? The install pulled in tor and started it. Once TBB running and checked, I could share files. In view of your later email I'd suggest testing with a standard TBB. You can follow progress from the term where you started onionshare, and you should see the connection established to the control port and then the HS being set up. Obviously you will need to test the TBB is working. unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20170104033109.GC28071%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Dom0 (System tools) shortcuts suddenly disappeared
On Tuesday, January 3, 2017 at 8:55:58 PM UTC-5, Unman wrote: > On Tue, Jan 03, 2017 at 04:12:28PM -0800, Otto Kratik wrote: > > On Tuesday, January 3, 2017 at 6:02:09 PM UTC-5, Marek Marczykowski-Górecki > > > > > > > > Try running `xdg-desktop-menu forceupdate`. > > > > Ran it as su from dom0 terminal. Command was accepted, but no noticeable > > effect or change, or output. > > > > Have you checked the menu files? > > For xfce, in /etc/xdg/menus/xfce-applications.menu you should have a > section with System that references > qubes-System-Tools.directory > There should be an section containing > and Excludes for X-Qubes_VM and X-Xfce-Toplevel > > The actual desktop files should be in /usr/share/applications: check > that they are there. > Confirm the Categories of a sample desktop file. > > I can't imagine that these have been deleted - if they have then you don't > need to reinstall, just replace the missing files. > > let us know what you find (or not, as the case may be). Here are the contents of the xfce-applications.menu file: ** http://www.freedesktop.org/standards/menu-spec/1.0/menu.dtd";> Xfce X-Xfce-Toplevel exo-file-manager.desktop exo-mail-reader.desktop exo-web-browser.desktop /usr/local/share/applications xfce4-run.desktop exo-terminal-emulator.desktop System xfce4-about.desktop xfce4-session-logout.desktop System qubes-System-Tools.directory X-Xfce-Toplevel X-Qubes-VM xfce-settings-manager.desktop *** In /usr/share/applications I see: kde (folfer) kde4 (folder) screensavers (folder) gnome-mimeapps.list kde-mimeapps.list mimeapps.list mineinfo.cache xfce-mimeapps.list Does that reveal anything? What should I be looking for within this location further? Thanks... -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4caa2ffd-447d-491d-afe6-f20adf77114e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Computer Models Guaranteed to work with Qubes 4.0?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 15:41, James Funkhauser wrote: > The lowest bar is the minimal requirements.[2] Even the minimal > requirements for 4.x are quite secure, since they now include VT-d > and VT-x (which weren't minimally required in previous Qubes > releases). VT-d is required for isolating devices (e.g., > networking, USB),[3] and VT-x is required for running certain > kinds of VMs (e.g., Windows).[4] This should be relatively easy to > achieve, but you have to attend to more than just the CPU's > properties. For example, it's not enough that the CPU alone > supports VT-d. The motherboard has to support it also. > > I see. I can then shop around for devices that have one of the > CPUs listed as being compatible. But what about motherboards? Is > there a compatibility list for those? > Not one that I'm aware of. Typically, you have to check the specs for the motherboard you're considering purchasing. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbHxhAAoJENtN07w5UDAwuSkP/1bcHUiX5JIXpaJXVMewmMM8 x8l9TqhGcnubnYRgjoLzdxBjCvzeEX9RJ73mDo4cTRZJtIM+6urN7hHaA9mpgoi7 3MVDcp5a+Zl+1AgRPsgcBcR/guKBdS5FJo21tY1f4vl/aZbXAkyaM0FFNlM6XW19 Zpmw8TU3Cdk38puNdCdVV1l9LyL+hRfdeZHJGc2xamx4Yo//9S8Vnw6E127+X4LC nd9TBE4CLJ6XHm0P8Z7ilbsgdoi3bFXuC5j93315myfJyKv8ToQGuox94KJNclHn 3feyTJL8IVOFsvMdU9DZxfx4rYT2VKhEN9w8UsWwP6Za8s5IDA+Yj9xwPtA8xAm0 dpey4/SqwSl7mZh4G57I61WrPXh4TJFVmldauu8kYzO6c/7uPFdg0pxq+dcv1tg9 b7W5F5bqsqsIaOMzup8qDaVdQAvv1lzny/j+iGmP9xD5qFUVq6N9xQsI1yEUSEUB O7Fb4kayoT+uWv5Ce10S9iyTbNQ7vYOLQ0AjXJ9Hev+Lhzw0Z+NHB+XbDYc9+aZ8 6vjdxcZH9ca9E+XB9Mukoflv71o4oyBkpa5EA7rh1lJn+m7qZWW4v/YfU5lJ9AES 0IMToCWA5WNSf7Ae3/tjFtwyp1XTPzapGqaZT9QvAAt1Upea/vT25QaEffeQUhZJ W7P2x7EKP6AU71NK6g7m =huBa -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/684a49cf-ead9-205f-1ba2-9b333d72498b%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to set file association in disposable VMs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-03 16:16, Unman wrote: > On Tue, Jan 03, 2017 at 08:57:58AM +, Robin Green wrote: >> On Tue, 3 Jan 2017 at 03:14 Unman wrote: >> > Original Message > Subject: [qubes-users] How to set file association in disposable VMs? > Local Time: December 29, 2016 7:48 PM > UTC Time: December 29, 2016 11:48 AM > From: gree...@gmail.com > To: qubes-users > > I have configured Nautilus in an AppVM to open PDF files with Okular, >>> and > I've then done the same configuration (as user "user") in the >>> TemplateVM > that the disposable VMs are also based on. However, when I choose >>> "Open in > disposable VM" from that reconfigured AppVM, even though the dispvm > savefile is updated before launching the dispvm, it still uses the >>> default > PDF viewer instead of Okular. > > > Sounds similar to this: > > >>> https://groups.google.com/forum/#!searchin/qubes-users/open$20in$20dvm|sort:relevance/qubes-users/GZ2zWcoMuwc/vwAzmYS5DgAJ > > --WillyPillow > >>> >>> You don't say *how* you have changed the association. >>> >> >> I changed it using Nautilus, by right-clicking on the file, Properties. >> >> >>> Try changing the file association in the template: >>> mimeopen -d file.pdf will allow you to set the default application. >>> Close down the template. >>> Then make sure the dvm file is regenerated before opening the dispVM, >>> as you have done. >>> >> >> That didn't work either. Please note, as noted already in this thread, this >> is a known bug. >> > > Did you actually read that bug report? I'm amazed it's still open. > Would you mind explaining why you think it should be closed? > I assume that you are using a Fedora template since 'mimeopen' > works for a vanilla Debian template. > > For Fedora based dvms, the dvm does NOT pick up the association from the > template. It's therefore necessary to customize the DispVM: there are > instructions for doing this in the docs. > > In brief, for a fedora-24-dvm: > qvm-run -a fedora-24-dvm xterm > > In the dvm: > mimeopen -d test.pdf > touch /home/user/.qubes-dispvm-customized > sudo halt > > Regenerate DispVM template using qvm-create-default-dvm: > qvm-create-default-dvm fedora-24 > If this solves the problem in the aforementioned issue, we can add this to the documentation (as a way of closing that issue). > > I haven't tested this with Okular, but it works for setting other default > applications. Can you confirm it with Okular? > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYbH01AAoJENtN07w5UDAwBqoP+wZmMw2YtKRloYd6uS042NGM nKrp1BmPYyDsjiGscEiH8k2xsoteltstm/dV+AO5NiJdhqiC588SjIFuwZXzxZxI tyW7OjOH/2QAc9lVGgagfDM3JYABfgBRzyyyB2D9Ehy3UVTTsvM/wKmIfD41Qppj P4Xo3S44ns2mDl/IFggGgDt4mX7lJiAnrBDbOpBQpASmxfetcqcn5PifPMG/T3wc iLG0XyCsAzRLozYLBah4fMg0XrjP3ZE95wLf8iKtW9ftL8bSnmYpeFqPm/MR6CSS s8tvxWQtBBEhBGf3IhSphMM96rPYQsgrG2681Oa2S5nULEcVfYYCEH4HjKLOOv35 dtqWGTZ4UN5nj2i7ois3ob+Dccgid05FyLAMKcQ8EqNq90vQV4/xCWy80KeAqxXd Spqno1VUR/Gztux/o3o6g18aiiNVWg37IEPGFg3BAGdzq2cn/kYzFkykO/pa0QSE 5bMVX8FJ6FtSZ3jHnITliO9NTgobzElkxeCKlqT59beubCn77t7wCtY4nbIj7qKe Fa1hQG2stN8kWGnc1q/aBymq1JMRbsxYWSqkrAlM02t2Fd7WYMPCitKP8LzYDalN p7IA/s3eaY4sHuiIRZD4Q4u6QZbMo9LngYSzz9N7ow/Si+Ys3xFSH1mzCcg09e4e /zJHMzlEATJTY1nK+rPX =dhsc -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/bf597435-73eb-c0dc-d71e-1a512ca4848c%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Kali VM is unusable
I have a Kali VM (installed in a new vm via iso). 90% of the screen is gray. The Kali top bar appears at the bottom of the screen, and most of the desktop is not even onscreen. Has anyone else encountered this? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d664c4db39dd7fd16ff5b2ff079ba8d5%40airmail.cc. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Best way to install qubes on mixed ssd and sata disks
Le 03/01/2017 à 17:38, Ronald Duncan a écrit : > Looking to reinstall qubes from scratch and would like to optimise the use of > the ssd so I execute as much as possible on the ssd and use the sata for > storage. > > I have a 500gig ssd and 1 tb sata. > > Thoughts appreciated > > At the moment I installed qubes on the sata drive to test out and experiment > on. Yo can go on from there by following this : https://groups.google.com/forum/#!msg/qubes-users/ArHTEeQAH8A/r9zzY0DLBQAJ ॐ -- Swâmi Petaramesh PGP 9076E32E -- 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/dd6a9a9a-866e-52e0-40dd-4f0ee449064e%40petaramesh.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: lemur7 Unable to reset PCI device
For Wifi, in sys-net keep 02:00.0, but remove (03:00.0 and) 03:00.1. If you need Ethernet, good luck. I have been unable to get the Realtek Ethernet devices to function reliably -- barely at all -- on my Lemur, but Wifi works great. For the error that you're getting, you need to add 03:00.0 to sys-net. However, even with that change, I was only sometimes able to get Ethernet connectivity. Similar: https://groups.google.com/forum/#!topic/qubes-users/Fs94QAc3vQI https://github.com/QubesOS/qubes-issues/issues/1393 I played around with permissive settings but ultimately it is unneeded for Wifi and did not seem to impact the reliability of the Ethernet. My experience: Sometimes Ethernet would work only to not work upon reboot, regardless of the kernel version or configurations I attempted; although, my Linux troubleshooting skills are minimal so maybe I missed something in the kernel/xen and other logs. Yet, it seemed strange that it would work during one session but not after a VM and/or system reboot. Something about the 03:00.0/1 device does not play well with Xen/Qubes. So, unless you really need Ethernet, I recommend only connecting your Wifi device to sys-net. The 8260 works great when on its own. On Monday, January 2, 2017 at 10:27:27 PM UTC-8, pixel fairy wrote: > used a working desktop to install and update to qubes-unstable. this time the > lemur was able to boot, but sys-net could not run. heres an hcl-report > followed by a typescript session showing pci devices and the error. adding > pci devices to sys-net in the qubes-manager gave the same result. > > --- > layout: > 'hcl' > type: > 'notebook' > hvm: > 'yes' > iommu: > 'yes' > slat: > 'yes' > tpm: > 'unknown' > brand: | > System76, Inc > model: | > Lemur > bios: | > 5.12 > cpu: | > Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz > cpu-short: | > FIXME > chipset: | > Intel Corporation Device [8086:5904] (rev 02) > chipset-short: | > FIXME > gpu: | > Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) > gpu-short: | > FIXME > network: | > Intel Corporation Wireless 8260 (rev 3a) > Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit > Ethernet Controller (rev 12) > memory: | > 32655 > scsi: | > Samsung SSD 850 Rev: 1B6Q > CT750MX300SSD1 Rev: 0100 > > versions: > > - works: > 'FIXME:yes|no|partial' > qubes: | > R3.2 > xen: | > 4.6.3 > kernel: | > 4.8.12-12 > remark: | > FIXME > credit: | > FIXAUTHOR > link: | > FIXLINK > > --- > > Script started on Mon 02 Jan 2017 09:33:34 PM PST > ]0;user@dom0:~ [user@dom0 ~]$ lspci > 00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02) > 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) > 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model > 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI > Controller (rev 21) > 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP > Thermal subsystem (rev 21) > 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME > HECI #1 (rev 21) > 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller > [AHCI mode] (rev 21) > 00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1) > 00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1) > 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port > #6 (rev f1) > 00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21) > 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) > 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) > 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) > 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) > 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI > Express Card Reader (rev 01) > 03:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) > ]0;user@dom0:~ [user@dom0 ~]$ qvm-start sys-net > --> Creating volatile image: /var/lib/qubes/servicevms/sys-net/volatile.img... > --> Loading the VM (type = NetVM)... > Traceback (most recent call last): > File "/usr/bin/qvm-start", line 136, in > main() > File "/usr/bin/qvm-start", line 120, in main > xid = vm.start(verbose=options.verbose, > preparing_dvm=options.preparing_dvm, start_guid=not options.noguid, > notify_function=tray_notify_generic if options.tray else None) > File "/usr/lib64/python2.7/site-packages/qubes/modules/005QubesNetVm.py", > line 122, in start > xid=super(QubesNetVm, self).start(**kwargs) > File "/usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py", line > 1966, in start > self.libvirt_domain.createWithFlags(libvirt.VIR_DOMAIN_START_PAUSED) > File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1059, in
