[qubes-users] Using 2 monitors in full screen mode with one application spanning both monitors

[Robin Green]

I am running VMWare Horizon in a trusted VM in order to WFH. It is able to 
detect and use both monitor geometries for what you might call a 
"double-full screen mode" - however, even though I have enabled full-screen 
mode for this trusted AppVM in /etc/qubes/guid.conf on dom0, Qubes 
unfortunately does not recognise what it's doing as "full-screen" and 
retains the title bar over the virtual window (which spans both screens) 
and over the Windows Remote Desktop widget (which appears as a separate 
window fully obscured by the Qubes window title bar, rather than a widget). 

Yes, I am running Remote Desktop, on a remote computer, that I am 
connecting to with VMWare Horizon, to connect to yet *another* computer! So 
many levels of desktop virtualisation here, hehe

If I right-click on the Qubes window title bar and choose Full screen, it 
of course goes to full screen on only the first display, and no second 
virtual monitor on the remote computer is accessible to me. If I leave it 
like it is, I can't see what's at the bottom of any maximised windows on 
the remote machine - and since I like to maximise all of my windows, this 
is pretty much unusable for me.

Gonna have to reboot my local machine into Windows for now so that I can 
use both screens with VMWare Horizon and Remote Desktop, but I would like 
to figure out a way to get this to work... that doesn't involve manually 
resizing all the windows on the remote computer!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a661398e-df6a-4270-ad43-d0017f5904bf%40googlegroups.com.

[qubes-users] Setting up IPv6 tunnel in netvm

[Robin Green]

This is my experience report after finally successfully setting up an IPv6
tunnel in sys-net in Qubes R4.0 and configuring things so that AppVMs could
use it. It was quite a struggle - some things did not work as I expected.

Steps I followed to make it work:

1. Put the commands from Hurricane Electric, my IPv6 over IPv4 tunnel
provider, into /rw/config/rc.local in sys-net.

2. As documented, in a dom0 terminal, enable the IPv6 feature:

qvm-features sys-net ipv6 1

The rest of the steps I did not find documented anywhere:

3. At this point, dnf stopped working. This turned out to be an MTU issue -
I had to add this line to my /rw/config/rc.local in sys-net:

ip link set he-ipv6 mtu 1472

I had discovered this 1472 value using:

tracepath6 mirrors.fedoraproject.org

Although I don't think this was a Qubes issue, the same MTU value that I
discovered also has to be used later as well.

Side note: at this point, qubes-dom0-update was able to download packages
but was not installing anything. However, I think that was because there
was nothing that needed to be installed, because the downloaded packages
were already up-to-date on dom0. So it wasn't a bug, or in any way related
to this change, just a bit confusing.

4. I still had no IPv6 access in my web browsers in my AppVMs, so I
investigated why. ipv6 NAT appeared to be set up in ip6tables as promised,
but it wasn't working. I then discovered that net-vm didn't have an IPv6
address, other than a locally-scoped IPv6 address, for its virtual network
interface. Is this a qubes bug?

I added an IPv6 address:

ip addr add fc00::10:8:8:71/7 dev vif9.0

and made it routable from sys-firewall:

sudo ip -6 route add fc00::10:8:8:71 dev eth0
sudo ip -6 route add default via fc00::10:8:8:71 dev eth0

At this point I could successfully execute

ping v6.ipv6-test.com

5. The web browsers still weren't able to use IPv6, and again it turned out
to be an MTU issue. I had to execute:

echo 1472 > /proc/sys/net/ipv6/conf/eth0/mtu

as root, in both sys-firewall and the AppVM. Again, this was based on the
MTU value I had discovered earlier.

This means that path MTU discovery within the Qubes internal network
doesn't work for IPv6 in Qubes. Though, based on something I have read
about that, I think that may be a good thing from a security point of view.

Can we simplify this process? It's quite complicated.

Perhaps the firewall could by default allow through IPv6 ICMP messages to
make MTU discovery work, only if they came from the internal network. Or
perhaps that's incompatible with NAT of IPv6. I'm new to IPv6 and I'm still
learning how it works.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CACVBcp51S2jHKkFbK9_jD5ThqMgg0Tp7A3bCMG35LY%2BVwwF1fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Dual boot Qubes R4.0 and Windows 10 on EFI system

[Robin Green]

I am trying to follow the instructions on 
https://www.qubes-os.org/doc/multiboot/ but grub is not even installed, so 
there is no such directory /etc/grub.d/

Does that page need to be updated?

-- 
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/2e544ab0-ef8e-4e32-a18d-253cca7b2dd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Windows 8.1 HVM - Windows mouse pointer moves at wrong speed

[Robin Green]

After my Windows 8.1 VM updated itself today, first the Windows mouse pointer 
disappeared entirely, and then when I rebooted it, it stopped moving as far as 
the Qubes mouse pointer, so the two mouse pointers became out of sync.

The solution was to go into the Control Panel in Windows and in Mouse Settings, 
disable "Enhance pointer precision" (which is a bit tricky to do while the 
mouse isn't working properly).

-- 
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/66a337c0-29b5-493d-8d6e-8ac82aacb733%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to set file association in disposable VMs?

[Robin Green]

On Wed, 4 Jan 2017 at 00:16 Unman  wrote:

> Did you actually read that bug report?


Yes.


> I'm amazed it's still open.
>
> I assume that you are using a Fedora template


Yes.


> since 'mimeopen'
> works for a vanilla Debian template.
>

I don't think the Fedora template uses mimeopen directly any more.


>
> 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?
>

No, it doesn't. I tried both ways of settings the file associations.
Neither works.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CACVBcp4mP%2BzuMmVajNTKSgnwsq81R-MN6Ecb_rDWU6KgFhU6ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to set file association in disposable VMs?

[Robin Green]

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] How to set file association in disposable VMs?

[Robin Green]

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.

-- 
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/2529376e-ef91-43c4-a12b-9204c71dbcde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.