Hi,
Saw the news earlier today about the major dnsmasq vulnerabilities
(remote code execution), and already received the update for the
debian-8 template, but not for the fedora-23 template or dom0.
Anyone know of an ETA for this?
Thanks,
Ron
--
You received this message because you are
Hello,
after a lot of trial and error I found out that the following line in
~/.config/i3/config will auto-move the Qubes Manager window to another
workspace:
assign [class="Qubes-manager"] $workspace10
Using the 2nd value from the WM_CLASS(STRING) which I got using xprop and
clicking into
I'm experiencing a similar problem which I've reported a bug for at
https://github.com/QubesOS/qubes-issues/issues/3135
If you're still encountering the issue with the update proxy failing too, could
you check the output of "journalctl -u qubes-updates-proxy.service" when it
fails please?
Testing a CF-19 Panasonic toughbook with Qubes. Currently 3.2 but having issues
with getting touchpad to work.
I have seen from some research that the touchpad likely is connected via a
pci-usb device and one has to choose
between touchscreen with WWAN and touchpad.
Anyone have knowledge of how
After rebooting tow more times, the keyboard and mousepad became functional.
Ray
--
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
yuraei...@gmail.com:
> Heya,
>
> TL:DR
> Is there anything wrong with pushing VM partitions beyond the physical drive
> size, as long as data doesn't exceed the physical drive size (which it can't
> for obvious reasons). Corruption? Backup size? Privacy? or just no code
> available yet to
So i recently decided to try subgraph out as a hvm in qubes, first everything
went well, i choose lvm and everything installed fine, i could also boot up the
system, so i thought everything was alright, until i logged in, because after i
log in, the system starts acting weird. It seems like
On Tuesday, 3 October 2017 19:26:29 UTC+8, Foppe de Haan wrote:
> > When trying to start the VM using qvm-start, a window is opened with some
> > diagnostic information scrolling past (too fast to see what's going on),
> > and then the window disappears and the VM is shut down. Trying to go to
