[qubes-users] Re: usb keyboard not working on debian 11 template

2021-10-07 Thread 'qtpie' via qubes-users
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 documentation. Please let me know.


--
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/fdddae23-40df-6fe6-23f8-99b78d06bbc6%40disroot.org.


[qubes-users] usb keyboard not working on debian 11 template

2021-08-25 Thread 'qtpie' via qubes-users

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 before or after startup, tried both)
3. I get the 'Device X is available' notification
4. I can use the device both inside the sys-usb qube and in other qubes 
and in dom0



When I switch the sys-usb to a debian 11 template:
(same)
4. I can use the keyboard inside the sys-usb qube, not in other qubes. 
The mousepointer does not respond at all.


How can I troubleshoot this? thanks for your suggestions.


---

fyi, this is my only problem with debian 11 as the default template, 
multiple applications seem to work smoother when compared to debian 10.


--
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/6ab45cb8-2d62-c3fe-fd6a-66e8c5db083a%40disroot.org.


[qubes-users] DNS issues: servfail on selected subdomains, Qubes modifying DNS replies by stripping IPv6?

2021-05-11 Thread 'qtpie' via qubes-users
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 my side.


Selected domainnames (all subdomains, eg www.qubes.org, so not 
qubes.org) get a SERVFAIL when trying to resolve them within 
applications, and on the commandline with 'host' and 'nslookup'. 
Strangely enough, 'dig' has no issues, (querying the same default 
resolver ip of course). At times, the domainname will resolve inside 
sys-net and certain app-vm's, and not in another app-vm. At other times, 
it resolves nowhere. When quering resolvers directly (like my isp's 
resolvers or 1.1.1.1) the issue does not occur.


What can be happening here? One of the only consistent hints I found is 
that Qubes does not seem to pass the full nslookup response from sys-net 
to the appvm (compare nslookup examples below). My router gives a 
servfail when quering it via ipv4, nslookup then tries it's ipv6 
address, where it does get a reply, but this reply is not passed to the 
appvm. The servfail might be an ipv6 issue or an issue with my router, 
but I think still Qubes should pass the full response, right?



some affected domainnames:
www.duckduckgo.com
www.startpage.com
textsecure-service.whispersystems.org



user@chat-1:~$ host -v www.startpage.com
Trying "www.startpage.com"
Host www.startpage.com not found: 2(SERVFAIL)
Received 35 bytes from 10.139.1.2#53 in 2 ms

-

user@chat-1:~$ nslookup  www.startpage.com
;; Got SERVFAIL reply from 10.139.1.1, trying next server
Server:        10.139.1.2
Address:    10.139.1.2#53

** server can't find www.startpage.com: SERVFAIL



user@sys-net:~$ host -v www.startpage.com
Trying "www.startpage.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22135
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.startpage.com.        IN    A

;; ANSWER SECTION:
www.startpage.com.    2393    IN    CNAME    startpage.com.
startpage.com.        10    IN    A    145.131.132.72

Received 65 bytes from 192.168.0.1#53 in 4 ms
Trying "startpage.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8508
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;startpage.com.            IN    

;; AUTHORITY SECTION:
startpage.com.        2598    
IN    SOA    dns1.p01.nsone.net. 
hostmaster.nsone.net. 1619470914 3600 600 1209600 3600


Received 96 bytes from 192.168.0.1#53 in 3 ms
Trying "startpage.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;startpage.com.            IN    MX

;; ANSWER SECTION:
startpage.com.        2598    
IN    MX    10 mx2.startmail.com.
startpage.com.        2598    
IN    MX    10 mx1.startmail.com.


Received 81 bytes from 192.168.0.1#53 in 1 ms




user@sys-net:~$ nslookup  www.startpage.com
;; Got SERVFAIL reply from 192.168.0.1, trying next server
Server:        fd00::(redacted):ee5e
Address:    fd00::(redacted):ee5e#53

Non-authoritative answer:
www.startpage.com    canonical name = startpage.com.
Name:    startpage.com
Address: 37.0.87.39



--
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/cf58fe9c-c3f8-be3c-42be-1e40fd64b135%40disroot.org.


Re: [qubes-users] Replacing the wpa_supplicant wifi daemon with iwd

2021-03-18 Thread 'qtpie' via qubes-users


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 "[device] \nwifi.backend=iwd" | tee -a
>> /etc/NetworkManager/NetworkManager.conf
>> $ systemctl enable iwd.service
>> $ systemctl start iwd.service
>
> interesting. I tried that in my debian-minimal-net but I cannot start
> iwd with systemctl. Errors similar to here
>
>   https://bbs.archlinux.org/viewtopic.php?id=250220
>
> but the proposed "solution" does not work. The thread suggests
>
>   sudo cp /usr/lib/systemd/system/iwd.service /etc/systemd/system/
>
> but that file does simply not exist, so I cannot copy it. So I stopped
> that experiment for the moment. Maybe @unman has a suggestion for a
> well-working debian-based 'minimal' solution without  networkmanager
> and/or   wpa_applicant ?  Best,
>
>

For those who want to stick to NetworkManager, II found out that the

$ systemctl enable iwd.service
$ systemctl start iwd.service

from my initial post, should not be necessary and can cause conflict.
Because NetworkManager is supposed to handle starting iwd, after iwd is
added to the NetworkManager config file.

That networkmanager does not handle iwd correctly, is a known issue with
NetworkManager. We can only wait for it to get updated with future
Fedora releases I guess.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/101

I am now also curious about non-networkmanager alternatives and their
usability though.

-- 
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/73c466a3-2c9e-6227-343b-be8197d2b618%40disroot.org.


[qubes-users] Replacing the wpa_supplicant wifi daemon with iwd

2021-03-03 Thread 'qtpie' via qubes-users
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 wpa_supplicant
$ echo -e "[device] \nwifi.backend=iwd" | tee -a
/etc/NetworkManager/NetworkManager.conf
$ systemctl enable iwd.service
$ systemctl start iwd.service
$ systemctl restart NetworkManager

There are just two integration issues remaining that I hope people can
help me with. I am using the standard Qubes Fedora template, and want to
stay as close to it as possible, so I'm not interested in ditching
NetworkManager unless it is unavoidable.

1. /etc/dbus-1/system.d/org.freedesktop.GeoClue2.conf: this is the only
other file in /etc/ that mentions wpa_supplicant. It contains policy to
allow wpa_supplicant to be used for geolocation. Since I don't care for
geolocation, I just removed it (don't comment it out. But if someone
cares to adapt this to iwd, it would be nice.

2. Occasionally, NetworkManager says 'device not ready' under wifi, and
wifi stops working. It is solved temporarily by ``$ systemctl restart
iwd.service && systemctl restart NetworkManager.service`` in sys-net. I
don't get from the log what the exact issue is though.

--

Resources:
- I used this howto from Josh Stoik as a starter:
https://blobfolio.com/2019/replacing-wpa-supplicant-with-iwd-in-ubuntu-eoan/
- https://wiki.archlinux.org/index.php/Iwd

GeoClue2 policy:

  
    
    

    
    

    

    

    

    
  


-- 
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/a92da205-6c3d-5ae7-3a9e-78ad19cefaaa%40disroot.org.


[qubes-users] Re: issues with i3, xrandr and keyboard

2021-01-29 Thread 'qtpie' via qubes-users



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 remains used to open menu's
> (altgr+f for File, altgr+e for Edit, etc.) If I could use altgr-intl and
> retain that functionality that would actually be great.

To answer my own question for other peoples reference: in i3 the way to
change the keyboard layout is basically suggested in the qubes faq, but
you really have to dig into the workings of localectl and keyboard
configuration in general. I ended up doing in dom0:

$ localectl set-x11-keymap us pc105 altgr-intl compose:ralt
$ localeclt status


localectl howto:
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/basic-system-configuration/System_Locale_and_Keyboard_Configuration/#s2-Setting_the_Keymap

List of possible keyboard options. This page is about setxkbmap, do not
actually use setxkbmap (I've tried), but these options are generic:
https://gist.github.com/jatcwang/ae3b7019f219b8cdc6798329108c9aee

https://www.qubes-os.org/faq/#my-keyboard-layout-settings-are-not-behaving-correctly-what-should-i-do

-- 
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/e4197a36-2fcf-a5f7-369a-00933864877d%40disroot.org.


Re: [qubes-users] issues with i3, xrandr and keyboard

2021-01-21 Thread 'qtpie' via qubes-users


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.
>>
>> The issue I keep running in to is that about half of the time, my mouse
>> will not work on the the external monitor on the rightmost quarter and
>> lowest quarter (approximately). The pointer will move there, but clicks
>> are not registered. It is as if the mousedriver sees the second monitor
>> as 1920x1080 instead of its actual resolution. The status bar is
>> displayed on both monitors.
>
> Hi,
>
> This can be fixed by increasing the dom0 Qubes GUI video memory [1].
>
> [1]
> https://www.qubes-os.org/doc/gui-configuration/#video-ram-adjustment-for-high-resolution-displays
>
>
> Cheers,
> Patrik
>
Patrik,

Thanks for this excellent answer, an immediate fix! Dual monitors now
seem to work flawlessly withouth having to use any fancy xrandr options.

I will at some point propose an update to the qubes-i3 documentation
with this addition among others.



-- 
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/611f5eda-a594-0de7-2e9f-6644e4fe0ef4%40disroot.org.


[qubes-users] issues with i3, xrandr and keyboard

2021-01-19 Thread 'qtpie' via qubes-users
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 second monitor I do $ xrandr  --output eDP1 --auto --right-of
DP1 --output DP1 --auto.

The issue I keep running in to is that about half of the time, my mouse
will not work on the the external monitor on the rightmost quarter and
lowest quarter (approximately). The pointer will move there, but clicks
are not registered. It is as if the mousedriver sees the second monitor
as 1920x1080 instead of its actual resolution. The status bar is
displayed on both monitors.

I have read much of what there is to read on xrandr and tried many
options, like switching monitor postitions, scaling, panning,
positioning, but to to avail, the issue keeps returning. I have tried
comparing the output of $ xrandr -q, but there is no difference between
working and error situations.

- Does anyone have a comparable setup and what xrandr command do you use?
- Is there an alternative to using xrandr under i3?


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 remains used to open menu's
(altgr+f for File, altgr+e for Edit, etc.) If I could use altgr-intl and
retain that functionality that would actually be great.

thanks!

qtpie



-- 
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/8705a851-50ff-3cb2-bc2f-bf53d07ef7a2%40disroot.org.