From: dashezup <dashezup@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: ydotool-0.1.8
Date: Sun, 04 Oct 2020 21:28:10 +0200 [thread overview]
Message-ID: <20201004192810.dMb5eBS9QVGM248Sr-2jwd7y1aLCRTw53n52p0nye1Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25341@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
New comment by dashezup on void-packages repository
https://github.com/void-linux/void-packages/pull/25341#issuecomment-703303848
Comment:
1. `/dev/input`
If I recall correctly, ydotool need to access /dev/uinput to work.
normal user can't access `/dev/uinput`, so you need to run ydotool with root, or add your user to a group and then add udev rules to allow the group to access it
https://github.com/ReimuNotMoe/ydotool/issues/25#issuecomment-535842993
2. `/tmp/.ydotool_socket`
In this case, ydotoold is run by the service (with root), it creates /tmp/.ydotool_socket` with permission 600 (in this case, only the user root can access to it)
So even if you have that udev rules and added the user to that group, another condition to meet to be able to use ydotool with normal user is **having ydotoold and ydotool run with the same user**.
I mentioned it here: https://github.com/ReimuNotMoe/ydotool/issues/73
Basically if you want to use ydotool directly, you must run it with root. Do you use ydotool by always run it with root user or sudo ? I wonder how do people use it, it's barely usable/useful to me if I need to run it with sudo.
If we want to solve this on our side, we can include the udev rules in this package, notice user to add himself to the specific group (maybe we should use `input` group?). If the user want to use ydotoold as service, then he need to change the uid/gid which runs ydotoold in the runit service.
> exec chpst -u root:input /usr/bin/ydotoold
you can add ", works on Wayland" to short description, so people can search it with keyword "wayland".
You can check [my template](https://ezup.dev/git/void-packages/files.html) (search srcpkgs/ydotool there)
```
srcpkgs/ydotool/INSTALL.msg
srcpkgs/ydotool/files/80-uinput.rules
srcpkgs/ydotool/files/ydotoold/log/run (log is not necessary and idk much about it)
srcpkgs/ydotool/files/ydotoold/run
srcpkgs/ydotool/template
```
next prev parent reply other threads:[~2020-10-04 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 15:45 [PR PATCH] " petrvelicka
2020-10-04 19:28 ` dashezup [this message]
2021-03-30 18:56 ` lelgenio
2021-07-21 3:47 ` ericonr
2021-07-21 3:47 ` [PR PATCH] [Closed]: " ericonr
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=20201004192810.dMb5eBS9QVGM248Sr-2jwd7y1aLCRTw53n52p0nye1Q@z \
--to=dashezup@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).