On 6/10/22 23:45, Demi Marie Obenour wrote:
On Fri, Jun 03, 2022 at 04:00:20PM +0200, Qubes OS Users Mailing List wrote:
So, apparently, this is not a sys-firewall, but a clocksync issue. To root
out any causes, I moved the clocksync service to a separate, brand new qube
(named sys-clock).
Yes, it!
https://github.com/QubesOS/qubes-issues/issues/7510#issuecomment-1146258366_
On 6/10/22 23:49, Demi Marie Obenour wrote:
On Fri, Jun 03, 2022 at 04:00:20PM +0200, Qubes OS Users Mailing List wrote:
So, apparently, this is not a sys-firewall, but a clocksync issue. To root
out any
On 6/4/22 11:56, tetrahe...@danwin1210.de wrote:
On Fri, Jun 03, 2022 at 04:00:20PM +0200, 'qtpie' via qubes-users wrote:
So, apparently, this is not a sys-firewall, but a clocksync issue. To
root out any causes, I moved the clocksync service to a separate,
brand new qube (named sys-clock
So, apparently, this is not a sys-firewall, but a clocksync issue. To
root out any causes, I moved the clocksync service to a separate, brand
new qube (named sys-clock). And voila: sys-firewall no longer 'crashes'
on resume from suspend, now it's sys-clock.
The cause is probably somewhere in
Hi,
I have a really annoying issue with resume from suspend. On resume,
sys-firewall is crashed/freezed/unresponsive. So on every resume from
suspend, I need to kill and restart this VM if I want to use networking.
Other qubes are fine, except that sys-whonix also freezes, but this is
Installing qubes-input-proxy-sender in the template it was. Problem
solved. Thanks awokd!
Note: to avoid this problem, these should either be default installed
packages in all templates, or be documented in
https://www.qubes-os.org/doc/usb-qubes/. If the latter is preferred, I
can adapt the
Hi,
Question: does a template qube need some kind of modification to let a
sys-usb qube based on that template work with usb keyboards?
Issue: On a debian 10 template, my usb keyboard/mouse combo 'just
worked'(tm):
1. I have a default sys-usb qube
2. I attach the keyboard device (either
I have a very annoying issue with DNS recently. I'm using the standard
DNS device and servers provided by my internetprovider which runs a full
dual-stack IPv4/6. Other non-qubes devices have no issues. I think this
might be a Qubes bug but I want to ask for help first to rule out an
error on
On 3/18/21 12:46 PM, haaber wrote:
> On 3/3/21 5:19 PM, 'qtpie' via qubes-users wrote:
>> Due to mysterious, unsolvable Wifi issues, I decided to replace the
>> wpa_supplicant wifi daemon with iwd.
> -- snip --
>> $ dnf remove wpa_supplicant
>> $ echo -e "
Hi,
Due to mysterious, unsolvable Wifi issues, I decided to replace the
wpa_supplicant wifi daemon with iwd. iwd itself is excellent and a
definite improvement over wpa_supplicant. I can't find Fedora working on
this though. In the Fedora 33 template, it currently comes down to:
$ dnf remove
On 1/19/21 6:27 PM, qtpie wrote:
> Also, how do you change your keyboard settings under i3/Fedora/Qubes? I
> want to use the us-altgr-intl keymap. Under i3 when I do $ localectl
> set-keymap us-altgr-intl in a qube vm terminal, this has no effect in
> applications. The right alt key instead
On 1/20/21 12:32 PM, Patrik Hagara wrote:
>> I'm using the i3 window manager with Qubes in a multi-monitor setup. The
>> laptop monitor is 1920x1080, the external monitor is 2560x1440. To
>> enable the second monitor I do $ xrandr --output eDP1 --auto --right-of
>> DP1 --output DP1 --auto.
>>
Hi,
A few questions about using Qubes with i3. I think the idea behind i3 is
great, but getting everything to work is a bit of a struggle.
I'm using the i3 window manager with Qubes in a multi-monitor setup. The
laptop monitor is 1920x1080, the external monitor is 2560x1440. To
enable the
13 matches
Mail list logo
