all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raingloom <raingloom@riseup.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel@gnu.org
Subject: Re: Wacom tablet issues
Date: Thu, 05 Mar 2020 23:24:03 +0100	[thread overview]
Message-ID: <1583447043.1586.4@riseup.net> (raw)
In-Reply-To: <1583429235.1586.3@riseup.net>

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 <raingloom@riseup.net> wrote:
> Well, udevadm shows it, but only as a single device instead of three.
> 
> On Thu, Mar 5, 2020 at 18:25, pelzflorian (Florian Pelz) 
> <pelzflorian@pelzflorian.de> 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. 
>>> \x7f\x7f(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 differently if you used Wayland on Arch.  In theory it should
>> be possible to make old xf86-input-wacom work too, I do not know how
>> and have no wacom tablet at hand.  Then again, I do not know why
>> udevadm does not show the device.
>> 
>> Regards,
>> Florian
> 
> 
> 

  reply	other threads:[~2020-03-05 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 14:53 Wacom tablet issues raingloom
2020-03-05 15:52 ` pelzflorian (Florian Pelz)
2020-03-05 16:10   ` pelzflorian (Florian Pelz)
2020-03-05 16:12     ` raingloom
2020-03-05 17:25       ` pelzflorian (Florian Pelz)
2020-03-05 17:27         ` raingloom
2020-03-05 22:24           ` raingloom [this message]
2020-03-06  6:31             ` pelzflorian (Florian Pelz)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1583447043.1586.4@riseup.net \
    --to=raingloom@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.