[qubes-users] Re: Using USB device with Windows 7 HVM?

On 08/16/2017 02:53 PM, Yethal wrote: > 1. VT-d is not enabled on your machine. In this case go to bios and > enable it. It isn't. I am running Qubes 3.2 on a DELL Latitude E6410 ... which has the issue that he Intel Graphics stop working as soon as VT-d is enabled. At least that was the case

[qubes-users] libre motherboards

On Monday, August 14, 2017 at 8:50:20 PM UTC-4, tai...@gmx.com wrote: > As always I offer free tech support for libre motherboards if you > wish to buy one. For the next several months I am planing to use Qubes 3.2 with a DELL Latitude E6410 basically accepting that it is far from perfect. Also

[qubes-users] Using USB device with Windows 7 HVM?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I am new to Qubes OS and this group. Attached please find a PDF outlining how I organized my setup in general. Getting right to the point, here is what I have done so far: * setup and using all fedora-23 based qubes / qubes-split-gpg ... all

Re: [qubes-users] DELL | LATITUDE E6410 WITH QUBES OS

On 08/16/2017 01:55 PM, QubesOS-ML wrote: > there how i have done it - a bit tricky with the Bios Settings > http://wombat3.kozo.ch/j/gadgets/9720-laptop-dell-latitude-e6410-with-qubes-os I too have installed Qubes 3.2 on a DELL Latitude E6410. For me however it worked with the default BIOS

[qubes-users] Re: Using USB device with Windows 7 HVM?

On 08/17/2017 12:53 PM, Yethal wrote: > Issue might be resolved by adding iommu=no-igfx to GRUB config Thank you very much Yethal! Yes, it resolved my graphics issues. I am now able to run Qubes with VT-d enabled. :-) I am also able to assign the USB controller to the Windows HWM! :-) That

Re: [qubes-users] qvm-usb not functioning

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/13/2017 08:35 PM, Drew White wrote: > I try to do a qvm-usb attachment to pass a usb device through, but > it doesn't let me, it tells me it fails but provides no description > of error. Hi Drew, are you assigning the USB device to an AppVM

Re: [qubes-users] qvm-usb not functioning

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/20/2017 09:53 AM, Sven Semmler wrote: > are you assigning the USB device to an AppVM based on a Qubes > Fedora or Debian template? Or is it a HVM (e.g. Windows)? Sorry. Ignore me. I hadn't read the whole thread. -BEGIN PGP SIG

Re: [qubes-users] Re: secure hardware after purchase but before qubes installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/07/2017 10:00 PM, taii...@gmx.com wrote: > > Why do you guys use qubes anyways? (feel free to message me off > list) I can't understand why everyone is so paranoid 1) Qubes is an excellent networking lab / playground to learn about InfoSec.

[qubes-users] diagnose cause for lock up / black screen

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 In my post "[AMD/ATI] Carrizo (rev c5)" from today I make the assumption that the black screen / lock up is connected to the graphics driver, because that's what I have observed with other Linux distributions on that machine. However, I just

[qubes-users] Installing ssh / capturing dom0 output (was: [AMD/ATI] Carrizo (rev c5))

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/06/2017 04:59 PM, taii...@gmx.com wrote: > install ssh so you can get access then Ok, that'll keep me busy for a moment. My plan is: * install sshd in a dedicated qube on computer 1 * follow

Re: [qubes-users] Using UNISON between VMs... Is that possible?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/12/2017 02:15 AM, segu.sa...@gmail.com wrote: > I have a script that uses UNISON [...] The idea is to sync files > between two virtual machines that have no visibility between them. Can you be more specific? Will those two VMs have network

Re: [qubes-users] unable to start dvm

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/06/2017 04:53 PM, Sven Semmler wrote: > The computer does have iommu, however dmesg reports error > initializing iommuv2. All other AppVMs start and work. At this point I am giving up assuming that my particular AMD processor lacks a f

Re: [qubes-users] Installing ssh / capturing dom0 output

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/06/2017 11:44 PM, taii...@gmx.com wrote: > Just use another distro to do it, don't go to all that effort. Yeah, after 5+ hours of trying to get this to work, I'll have to cut my loses. While it might theoretically be possible to diagnose and

Re: [qubes-users] Re: Privacy in Qubes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/25/2017 09:10 PM, Drew White wrote: > Debian, Slackware, CentOS, Windows 3.11,95,98,2000,xp,7,8,10 (32 > and 64 bit versions of available). I run OSX, ESXi, PFSense, > Android 4, 5, 6, 7, Qubes 1,2,3, XEN, PASOS, COFFEE, OS/2, why? (just

Re: [qubes-users] libre motherboards

Thank you Taiidan, on 08/18/17 19:34, you wrote: > Lenovo G505S "AMD A10-Series A10-5750M (2.50 GHz) 6 GB Memory 1 TB HDD AMD Radeon HD 8650G" -> I do have an AMD based laptop and while Qubes installed, there are issues (DispVM doesn't work, after a while it won't even boot anymore). >From the

Re: [qubes-users] libre motherboards

On 08/24/17 17:34, taii...@gmx.com wrote: > That is a software error (which I of course would be pleased to help > with) not a hardware error. I will definitely try again. It has been my practice for over a decade to have a second computer fully installed and with the latest backups restored on

[qubes-users] set mimetypes in dispvm

Hi, I have a customized disposable vm template. It is based on fedora-25-minimal and instead of firefox I have icecat installed along with libreoffice and okular. When I now try qvm-open-in-dvm example.pdf I get a dialog with the following error message: Unable to handle mimetype of the

[qubes-users] how to cleanup the application menu?

Hi, this is probably documented somewhere but I seem to not find the right keywords to get to the answer. Issue: I have uninstalled the debian-8, fedora-23, fedora-25, whonix-* templates. All my VMs are based on fedora-25-minimal clones, a windows-7 or kali template. However the application menu

Re: [qubes-users] how to cleanup the application menu?

My apologies, as so often I found the answer right after I asked for help. Sorry! I missed https://www.qubes-os.org/doc/remove-vm-manually/ The missing step was rm ~/.local/share/applications/* /Sven -- You received this message because you are subscribed to the Google Groups "qubes-users"

Re: [qubes-users] set mimetypes in dispvm

On 09/02/17 08:06, Unman wrote: > There's been discussion of this with okular before, [...] Hi Unman, thank you for the hint. I found the discussion between Francesco and cooloutac on 2/7/16. In summary: > But it worked to use in template mimeopen -d So I installed perl-File-MimeInfo and then

Re: [qubes-users] Send Files to Windows 7 Qube

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/01/2017 07:38 AM, inval...@gmail.com wrote: > I can't send files to my Windows 7 Qube. Can someone tell me the > steps I should go through to set up my VM and Qubes so I can > transfer files to the Win7 Qube? Have you installed the Qubes

[qubes-users] cannot trim whonix-ws template anymore

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I regularly trim my templates after updating them. I don't recall this process ever being interrupted, but it appears that something got corrupted once when trimming whonix-ws. What I have already done: * deleted

Re: [qubes-users] Re: XEN)QUBES END POINT SECYRITY

On 10/19/2017 03:52 PM, yuraei...@gmail.com wrote: > If so, you can simply make good use of your AppVM firewall. For > example create a AppVM strictly and only for payments, then limit > all internet connections in the firewall to only talk with your > bank, and whichever additional services your

Re: [qubes-users] Re: cannot trim whonix-ws template anymore

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/20/2017 10:25 AM, Noor Christensen wrote: > $ virsh undefine 34bfb7d4-b96d-4d8d-9042-53e212761316 Thank you Noor! The above command did the trick. /Sven -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [qubes-users] Ethernet-to-USB Adapter

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/12/2017 05:27 AM, taii...@gmx.com wrote: > You can simply assign disable sys-usb then assign the USB > controllers to sys-net via the VM manager. Please note that any non > PCI-e network interface is going to be have terrible performance > and

[qubes-users] [HCL] Qubes OS R3.2 on a ThinkPad P51 (model 20HJS0BX00)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 With significant help from members of this mailing list, I was able to install R3.2 on my new ThinkPad P51 (model 20HJS0BX00). The starting point was the HCL linking to swami's post , which describes or links all the steps

[qubes-users] update dom0 offline?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 My problem: new computer (ThinkPad P51) comes with Intel networking hardware which requires kernel 4.9 to be detected. When installing Qubes 3.2 one starts of with kernel 4.4. I can see on my other computer that is already running Qubes 3.2 that

Re: [qubes-users] update dom0 offline?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/10/2017 07:06 PM, Unman wrote: > sudo qubes-dom0-update --action=download I *think* that > dnf will do the right thing and resolve dependencies for you. This > should download the packages to the current directory, then you > can transfer

Re: [qubes-users] update dom0 offline?

On Dec 7, 2017, at 6:37 PM, Unman wrote: > > You can always grab the files from yum.qubes-os.org on the old computer. You mean https://yum.qubes-os.org/r3.2/current/dom0/fc23/rpm/ ? All of them? There seem to be different versions. If I copy all of them, is there a

[qubes-users] Ethernet-to-USB Adapter

When installing R3.2 one is presented with the option to create sys-usb as sys-net. Is there a guide somewhere on how to achieve this after the fact? Is there an guide to bringing up an Ethernet-to-USB adapter? Context to my previous posts: I’m struggling too much with R4RC3. Really do need

[qubes-users] Constant pop-up from dom0 for qubes.gpg action

I just get started with R4 and restored my email vm. Everything works great, except that now everytime I am in the To: of Subject: line I get a pop-up from dom0 asking: [dom0] Operation execution Do you want to allow the following operation? Select the target domain and confirm with 'OK'

Re: [qubes-users] Trying to download new Whonix templates and fedora 23 gets updated?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/09/2017 08:38 PM, vel...@tutamail.com wrote: > Dependencies resolved. Nothing to do. Did you include the --enablerepo parameter as shown below? sudo qubes-dom0-update --enablerepo=qubes-community-templates qubes-template-whonix-ws

Re: [qubes-users] New HCL Entry: Lenovo ThinkPad T470 (20HDCTO1WW)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/15/2017 03:20 AM, kotot...@gmail.com wrote: > It does boot but the X server cannot start. Text installation did > not work. Based on swami's post from 9/15/17 I suspect you need kernel 4.9 in dom0 ...

Re: [qubes-users] Recommended wireless or Ethernet card / chipset

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/18/2017 11:07 PM, 'EW' via qubes-users wrote: > I tried a lot of things from various posts but to no avail, I'm > going to just assume for now that the HW is not compatible (they > are USB 3 adapters, some posts are at least opening the

Re: [qubes-users] rc04

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/09/2018 12:07 AM, Roy Bernat wrote: > What about release rc04? it should be release at 8/1 that was > yesterday . Delayed until the devs have a good workaround for SP1/SP2/Spectre. /Sven -BEGIN PGP SIGNATURE-

Re: [qubes-users] A question for the Qubes community: multiboot documentation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/12/2018 12:41 AM, Sven Semmler wrote: > I will try this next week ... I'll wait for "R3.3" and R4rc4 to be released. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlpesRQACgkQ2m

Re: [qubes-users] Change default usb qube

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/10/2018 04:10 AM, 'Blacklight447' via qubes-users wrote: > I recently installed qubes on my new laptop, but i think i > accidently ticked the box which configure qubes to use sysnet as > usb qube, does someone know i can revert this and usb a

Re: [qubes-users] A question for the Qubes community: multiboot documentation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/11/2018 07:15 AM, 'Blacklight447' via qubes-users wrote: > This issue described the lack of documentation how to multiboot > qubes. I have decided that i will be writing it, but as described > in the issue above, I need some user feedback.

Re: [qubes-users] A question for the Qubes community: multiboot documentation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/11/2018 06:48 PM, Unman wrote: > It's really easy to do this Sven. I will try this next week ... not sure though if grub is even used. I am booting via EFI. But I got the basic idea and will do some google-ing. And of course make backups of

Re: [qubes-users] Change default usb qube

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/11/2018 06:25 PM, Unman wrote: > If you are connected through sys-firewall or similar, then it is > sufficient to set the netvm of sys-firewall to none. Oh wow! Thank you! You just gave me back so much future time... /Sven -BEGIN PGP

[qubes-users] QWT has effect in Dom0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Let me describe my issue once more, maybe a bit easier: - -> I have a Windows 7 HVM and when I install QWT 4.0.1.3 I get the shared clipboard and the ability to send/receive files from other VMs - -> but something in Dom0 seems stuck...

Re: [qubes-users] Unable to reset PCI device....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/02/18 09:14, Patrick Bouldin wrote: > PCI device :02:00.0 is in use by driver xenlight > qvm-pci attach --persistent --option permissive=true --option > no-strict-reset=true sys-net dom0:00_XXX > "error : backend vm "dom0" doesn't

Re: [qubes-users] Unable to reset PCI device....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/05/18 18:05, Sven Semmler wrote: > Please run qvm-pci and post the output. Ignore. I see your problem was discussed and solved in another thread. /Sven -BEGIN PGP SIGNAT

Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/10/2018 07:47 AM, unman wrote: > Yes you can create win7 appVMs from a template. Unless you use QWT > to set home directory to /dev/xvdb you will have effectively a > disposableVM, which may throw you to start with. I am using a Win7 HVM as

[qubes-users] Update: HCL - LENOVO Thinkpad P51 (20hjs0bx00) for R4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Update to https://www.qubes-os.org/hcl/#lenovo_thinkpad-p51-20hjs0bx00_i7-7820hq_k aby-lake_nvidia Now running R4.0 (for several months actually) - -> still needs EFI boot fix - -> networking hardware now detected out of the box /Sven -BEGIN

Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/10/18 8:07 PM, Stumpy wrote: > Am i understanding this right? Can't answer for unman, but in general this is possible and in my opinion advisable: - -> https://www.qubes-os.org/doc/dispvm-customization/ If you go this route, it comes with

Re: [qubes-users] How to add Davmail (Launch Script) to the qubes menu

On Oct 23, 2018, at 10:52 PM, 799 wrote: > > qvm-run -q -a --service -- my-bizmail > qubes.StartApp+/home/user/davmail/davmail.sh qvm-run -a my-bizmail davmail/davmail.sh & ... will do the trick. I run a setup with DavMail and Thunderbird on a fedora-28-minimal based template. For some

[qubes-users] Re: Re: Qubes User Forum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Testing to post from the forum. First impressions: - - Pretty sure I want to post from my mail client, since I like my stuff to be signed. Faking an email address is way to easy. - - Following a discussion might be faster in the mail client too,

Re: [qubes-users] Costum qubes order in QVM

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/2/18 8:20 AM, pieter lems wrote: > How does one costumize the order in wich the qubes are displayed. If you want a solution without programming: use a naming convention. I use simple prefix: app-... for AppVMs dvm-... for DispVM templates

[qubes-users] Re: [qubes-devel] My farewell to Qubes OS!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Joanna, thank you for the vision and the hard work! You actually changed the world in a significant way for lots of people and to the better! /Sven -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlvk+sgACgkQ2m4We49U

[qubes-users] qubes-open fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since a day or two, I get the following error messages when attempting to open a file in a DVM... "Unable to handle mimetype of the requested file (exit status: 768)!" So I started the VM that is the template for the DVM qvm-run -a dvm-offline

Re: [qubes-users] Re: Open in Qube 3.0 beta released!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/16/18 9:28 AM, Ivan Mitev wrote: > Just curious - isn't it possible to open a link with > `qvm-open-in-dvm` in your ThunderbirdVM and tweak the > corresponding rpc service (qubes.OpenInVM) to open a whonix-dvm ? Yes it is, following the way

Re: [qubes-users] Re: Open in Qube 3.0 beta released!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/25/18 7:54 AM, Ivan Mitev wrote: > Is it working with whonix too ? (that was the part of the post > from John S.Recdep I was replying too - I was wondering if there > was a problem specific to whonix dispVMs) Works like a charm. Nothing

[qubes-users] signal-desktop?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I just installed signal-desktop (in the template) and now try to run it in the appVM. The app starts and I can see the window border, but nothing inside the window. Haven't done much diagnosis yet. Just wondering if someone here recently

[qubes-users] Qubes issue #3980 exists in Debian 9 template but not in Whonix 14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Patrick & qubes-users, the issue described in... - -> https://github.com/QubesOS/qubes-issues/issues/3980 ... exists with debian-9 templates but not with fedora or whonix-based templates (which to my knowledge are debian based). Any idea why?

Re: [qubes-users] Win7 HVM causes Qubes to hang

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/15/18 5:37 AM, 'Bjoern Christoph' via qubes-users wrote: > Once I shut down Win7 the Qubes I wanted to launch are started, the > Qube Manager also reacts as it should. > Ideas? Hi Bjoern, I reported this 4 months ago here:

Re: [qubes-users] i3 Tap to Click

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/13/18 10:35 AM, Todd Lasman wrote: > Just can't get it to work. Any thoughts? I'm on Qubes 4.0, using a > ThinkPad T430. I'm using Qubes R4 with I3 on a ThinkPad P51 and got it to work. Attached is my

Re: [qubes-users] Paste not working from one appvm to another appvm's bash (4.0)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/4/18 6:06 PM, s.w.i.m.on.qu...@gmail.com wrote: > I also do not have a middle mouse key, again, somewhere online > said that could be used as well. Yep, that's how I do it > Is there some way I can do this? Sure. 1) pipe the output of the

Re: [qubes-users] Possible to use WindowsVM as a NetVM?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/23/18 11:52 AM, Zrubi wrote: > I just wonder why would you do this? I suppose a Windows-only proprietary VPN client ... am I right? /Sven -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlv4RJgACgkQ2m4We49U

Re: [qubes-users] qubes-open fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/15/18 4:03 PM, Sven Semmler wrote: > What could cause this? I haven't actually changed anything other > than running regular updates on the template. As far as I can see > qubes-open is a wrapper script around xdg-open set

Re: [qubes-users] old version of xscreensaver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/4/19 9:08 AM, Stuart Perkins wrote: > GUI of choice is a very personal thing. I am more pragmatic and > don't like "dancing" icons and starting all of my application > names with K...or G for that matter...but to each his own. I am >

Re: [qubes-users] signal-desktop?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/7/19 9:24 AM, haaber wrote: > The "--disable-gpu" parameter works perfectly for the > debian-install and the signed package form the signal website. Yup. Thank you! /Sven -BEGIN PGP SIGNATURE-

[qubes-users] restoring dom0/Fedora baseline

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This is probably more a Fedora question then a Qubes question, but it's in the context of Qubes. I have installed i3, gnome-tweak-tools, qt5cl and redshift in dom0. Meanwhile I removed both gnome-tweak-tools and qt5cl but a lot of the dependencies

Re: [qubes-users] Re: [qubes-devel] [proposing new feature] Edit in VM: an idea that can improve security when managing documents

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/14/18 10:41 PM, airelemen...@tutanota.com wrote: > a) Documents that "link" other documents. [...] Yes, that's a corner case that needs manual steps (e.g. start dispvm, copy all files in, copy them back out before closing vm) > b) Can't save

Re: [qubes-users] syncing config across qubes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/14/18 4:31 PM, Daniel Allcock wrote: > But I feel like maybe they are all wrong and I am overlooking > something obvious. You could have one "work qube" with your vim/emacs environment and use qvm-open-in-vm in all other qubes to open

Re: [qubes-users] backup with debian-10-minimal based sys-usb fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/31/19 9:36 AM, unman wrote: > 1. The minimal template is minimal - it doenst have any GUI file > manager. When you click on the ... button it spawns a file manager > in the backup qube. Since you dont have one installed it cant be > opened.

[qubes-users] debian 10 minimal ... issue with update proxy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 My template tpl-deb-10-min was created by installing the debian-9-minimal from itl-testing then cloning and updating it and finally upgrading to it to buster. The template is the basis of an AppVM dvm-min, which in turn is a template for dispvms:

Re: [qubes-users] debian 10 minimal ... issue with update proxy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/29/19 2:34 PM, Sven Semmler wrote: > What did I mess up? user@tpl-deb-10:~$ sudo service qubes-updates-proxy status ● qubes-updates-proxy.service - Qubes updates proxy (tinyproxy) Loaded: loaded (/lib/systemd/system/qubes-upda

Re: [qubes-users] debian 10 minimal ... issue with update proxy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 3/29/19 8:58 PM, unman wrote: > There's another issue in that the service file refers to > /usr/sbin/tinyproxy but the exec is in /usr/bin Fix this by > editing /lib/systemd/system/qubes-updates-proxy.service to refer to > the correct path.

[qubes-users] backup with debian-10-minimal based sys-usb fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Very recently I migrated all my AppVMs to a debian-10 (buster) template, which itself was created by upgrading the debian-9 template. Equally my sys-net, sys-usb and sys-firewall dispvms are based on a debian-10-minimal, which was upgraded from the

Re: [qubes-users] coreboot on modern hardware?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 3/25/19 4:49 PM, jrsmi...@gmail.com wrote: > What does this say about the direction Joanna and Golem are > taking? I am severely confused about that. I'd have thought the direction to go is open hardware, more local, more decentralized, more

Re: [qubes-users] i3 support?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 3/23/19 3:11 PM, Stumpy wrote: > w/ v3 i was using kde then, as support seemed to wan, i switched > over to xfce which is admittedly lighter but doest seem to be as > feature rich. I too use i3 and couldn't be happier with it, however it is

Re: [qubes-users] Re: screen brightness

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/13/19 3:32 AM, haaber wrote: >> On Friday, December 21, 2018 at 2:44:36 PM UTC-8, haaber wrote: >>> [..] Especially in evening hours this is really a pain in the >>> eye >> >> [...] >> >> xrandr --output eDP1 --brightness .75 >> >> Use

[qubes-users] Re: [qubes-devel] Qubes 4.x Backup setting should not be set to save (replace) default settings by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This thread might be better located in qubes-users. On 2/13/19 9:49 AM, Teqleez Motley wrote: > a) Where exactly does qubes save this password/backup settings > (file+folder, please) /etc/qubes/backup/qubes-manager-backup.conf > b) It seems to

Re: [qubes-users] backup with debian-10-minimal based sys-usb fails

On 4/5/19 12:52 AM, Sven Semmler wrote: >> You could install a file manager but then you're getting closer to >> the normal Debian template which is pretty minimal. If you are >> committed to minimal service qubes, CLI backup . > You convinced me. My intermediate solution w

Re: [qubes-users] backup with debian-10-minimal based sys-usb fails

On 4/15/19 6:25 PM, unman wrote: > Why do you say this? Backup works fine with a buster qube. What is the > exact problem that you have? I apologize. The issue was between chair and keyboard. In Fedora external drives are mounted under /run/media/user and in Debian under /media/user ... sorry for

Re: [qubes-users] Kernel 4.14.103-1 dmenu is not working

On 5/2/19 1:16 PM, eduzw...@gmail.com wrote: > Hey guys I migrated from arch to qubes. But I am having some difficulties > with I3 windows manager I am fairly new to qubes. I like how I can still use > my favorite arch distro. and benefit from qubes' secured architecture. Great to see you join

Re: [qubes-users] Kernel 4.14.103-1 dmenu is not working

On 5/2/19 11:13 PM, eduzw...@gmail.com wrote: > But the problem with dmenu persists. Are you using the default i3 config that came with the -settings package or have you merged your preferences into it? Have you simply copied an old i3 config from another system? I am not an expert, but

Re: [qubes-users] Kernel 4.14.103-1 dmenu is not working

On 5/4/19 12:58 PM, eduzw...@gmail.com wrote: > Sorry for the late response. I am using the default config so far. What > version is your i3? I noticed that my version is 4.12 from 2016. The latest > release is i3-4.16 > > "sudo qubes-dom0-update i3 i3-settings-qubes" will install i3-4.12 4.16

Re: [qubes-users] Kernel 4.14.103-1 dmenu is not working

On 5/4/19 1:03 PM, eduzw...@gmail.com wrote: > Also I am running Qubes R3.2. > Kernel 4.14.103-1.pvops.qubes.x86_64 Ah, I am running R4 ... but when I used to run R3.2 I also used i3. Don't know which version though. R3.2 is no longer supported, so unless the hardware requirements forbid R4 I'd

Re: [qubes-users] Re: using static dispVM for sys-net

On 8/17/19 3:55 PM, rec wins wrote: > how to store the wifi credentials in custom-dvm-template ? assuming you created sys-net using the a dvm template named dvm-fed-30-min and know the PCI identifier of your wireless interface (the one you assigned to sys-net) 1) qvm-shutdown --all --wait 2)

Re: [qubes-users] How to change date and time format in Thunderbird

On 8/15/19 11:25 AM, galt...@gmail.com wrote: > I googled and found that thunderbird gets its setting from the OS. You want to google for the command line commands: locale and localectl as well as /etc/locale.conf /Sven -- You received this message because you are subscribed to the Google

[qubes-users] Re: Behaviour of qvm-open-in-(d)vm

On 8/16/19 8:37 AM, Phil Knüfer wrote: > qvm-open-in-vm still works like the older tools, that is, it takes two > parameters (VM name + file name or URL to be opened), but then still > shows the GUI prompt where the user needs to pick the destination VM. This depends on the contents of your

[qubes-users] Re: [QubesOS/qubes-issues] Support for HiDPI (#1951)

On 8/6/19 9:46 AM, Abdullah Alansari wrote: > 2. I will try to figure out how to use `xrandr` to add a 3840x2160 with 200% > zoom. I did some research before but I couldn't find any fast solutions and > will need to understand `xrandr` more to do what I need. xrandr knows nothing about "200%

Re: [qubes-users] Re: Confuse Update QUbes OS

On 7/25/19 10:48 AM, unman wrote: > Debian-10 is stuck in testing at the moment because it needs packages > from the *testing* repositories for updating. This could be confusing if > users install from current and don't want to use the testing > repositories. I'm sorry that confused me. My main

Re: [qubes-users] using two whonix-gw instances

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 My understanding is that TOR actually runs in the gateway and the the workstation(s) enable typical Qubes style compartmentalization. Meaning that if app-anon-1 is compromised, the sys-whonix and a potential app-anon-2 are not. When I create a

Re: [qubes-users] using two whonix-gw instances

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/25/19 8:31 PM, Claudia wrote: > One way to find out for sure. Open /etc/torrc (or ~/.config/tor/torrc, or > other torrc location), and look for stream isolation flags. Make sure you > understand exactly what each one means. Thank you! /Sven

Re: [qubes-users] using two whonix-gw instances

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/25/19 5:26 PM, 'Jackie' via qubes-users wrote: > Whonix vms have stream isolation so different whonix appvms, or even > different applications within the same vm, will use different tor circuits. Oh wow... that sounds great. I just discovered

Re: [qubes-users] using two whonix-gw instances

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/1/19 2:59 AM, tetrahe...@danwin1210.me wrote: > > A 2nd sys-whonix gateway for this situation would seem to reduce the > vulnerability. Or maybe I am just being paranoid? I agree and decided to go with two gateways for the following reason:

[qubes-users] Re: I just lost several days worth of email ... /var/spool/mail/user not mapped to /rw?

On Wed, Nov 6, 2019, at 10:32 AM, Sven Semmler wrote: > I assume this is because /var/spool/mail/user is not part of the VM but > the template? ... and I have to bind it to /rw like I did with the > postmail directory: mount --bind /usr/local/etc/postfix /etc/postfix ? > > If t

Re: [qubes-users] Turning a NetVM into an AppVM

On Fri, Nov 22, 2019 at 08:44:00AM +, 'awokd' via qubes-users wrote: > nanop...@tuta.io: > > Hello there, I realized that everytime I made a new Qubes VM, I have been > > checking the "provides network" option turning it into a NetVM. > > I mistakenly believed that the option of "provides

Re: [qubes-users] Re: redshift or brightness control?

On Wed, Dec 11, 2019 at 08:20:27PM -1000, rec wins wrote: > so $sudo dnf install redshift-gtk ? sudo qubes-dom0-update redshift /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- You received this

[qubes-users] need Qubes to forget a "--persistent" attached USB device

So I got myself into a corner: * Usually I attach the entire USB controller to my app-dev (debian 9) qube. But in that case this qube can only have 2048 MB of memory (for some reason that's the limit when the USB controller is attached; any more and things crash ... same with Windows qube and

Re: [qubes-users] need Qubes to forget a "--persistent" attached USB device

On Thu, Dec 05, 2019 at 04:35:57PM -0600, Sven Semmler wrote: > So ... now what? Where does Qubes keep a record of this. What can I do to > 'detach' this and the other USB devices from app-dev? qvm-clone app-dev app-dev2 qvm-remove app-dev qvm-clone app-dev2 app-dev qvm-remove app-dev2 .

Re: [qubes-users] Standalone VM (debian-9) doesn't boot anymore due to file system corruption

On Wed, Nov 27, 2019 at 05:59:07PM +, 'awokd' via qubes-users wrote: > Sven Semmler: > > > Since I have two full days of work in that VM that I haven't pushed to the > > git server yet, my first impulse is to get my source code out of there to a > > safe plac

[qubes-users] Standalone VM (debian-9) doesn't boot anymore due to file system corruption

Hi! This morning I shutdown my Debian 9 Standalone VM "app-dev" to change the amount of RAM allocated to it. When I tried to restart it, I get the following error: app-dev: Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-app-dev.log for details So I did and

Re: [qubes-users] Standalone VM (debian-9) doesn't boot anymore due to file system corruption

On Wed, Nov 27, 2019 at 12:40:26PM -0600, Sven Semmler wrote: > Once in the "emergency mode" I realized I got no skills here and wouldn't > know what to do. So I'll go an rebuild. *facepalm* ... I'll just restore my backup from Sunday. That'll be even faster. ;-) /Sven

[qubes-users] using two whonix-gw instances

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 In addition to my fairly standard dvm based on whonix-ws connected to sys-whonix based on whonix-ws I have now done the following: 1) cloned sys-whonix to sys-whonix-id 2) created app-signal based on whonix-ws 3) installed signal in whonix-ws 4)

Re: [qubes-users] Update: HCL - LENOVO Thinkpad P51 (20hjs0bx00) for R4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Reinstall with R4.0.1 ... this time everything worked out of the box! No workarounds, no change to 'discrete graphics' ... nothing. Just bliss! Awesome work! Thank you Qubes Team! HCL attached /Sven -BEGIN PGP SIGNATURE-

[qubes-users] Reinstall/Restore ... incredible speed up

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I remembered that after first installing R4 on my ThinkPad starting VMs took 1-2 seconds (super fast internal SSD). Over the last several months however things became slower and slower (factor 10 or more when starting VMs) even though I applied

  1   2   3   4   5   >