On Thu, Mar 05, 2020 at 11:24:03PM +0100, raingloom wrote:
> I tried sway and it's broken there too. Not sure if I started it up
> correctly though, as I just opened it on a separate virtual terminal.
I believe you started it correctly and your observation on udevadm is
what really is strang. I a
I tried sway and it's broken there too. Not sure if I started it up
correctly though, as I just opened it on a separate virtual terminal.
On Thu, Mar 5, 2020 at 18:27, raingloom wrote:
Well, udevadm shows it, but only as a single device instead of three.
On Thu, Mar 5, 2020 at 18:25, pelzflor
Well, udevadm shows it, but only as a single device instead of three.
On Thu, Mar 5, 2020 at 18:25, pelzflorian (Florian Pelz)
wrote:
On Thu, Mar 05, 2020 at 05:12:57PM +0100, raingloom wrote:
What about i3? Because that's what I used on all three distros.
(also GNOME
on Guix)
i3 is not
On Thu, Mar 05, 2020 at 05:12:57PM +0100, raingloom wrote:
> What about i3? Because that's what I used on all three distros. (also GNOME
> on Guix)
i3 is not Wayland. Note that I only remember GTK people say it works
differently. What I said about Wayland is a possible reason why Arch
behaves di
What about i3? Because that's what I used on all three distros. (also
GNOME on Guix)
On Thu, Mar 5, 2020 at 17:10, pelzflorian (Florian Pelz)
wrote:
Also note that GNOME on Wayland may work better than GNOME on Xorg
with regard to wacom/libinput/GTK. I presume on Arch you used
Wayland.
Rega
Also note that GNOME on Wayland may work better than GNOME on Xorg
with regard to wacom/libinput/GTK. I presume on Arch you used
Wayland.
Regards,
Florian
Maybe using a custom Xorg configuration service helps. Add to the
services field:
(set-xorg-configuration
(xorg-configuration
(modules
(list
xf86-video-fbdev
xf86-input-libinput
(or another xf86-video- driver depending on your GPU).
This would leave out evdev and other obsolet
I'm having trouble properly setting up my Wacom Intuos CTH-480 tablet.
It is recognized as a tablet and pressure sensitivity is working, but
the eraser is not recognized as a separate input device. I used it in
Arch, where it worked flawlessly, so it's not a driver bug.
`libwacom-list-local-de
