From: sardior <sardior@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ratbagd starts too early?
Date: Tue, 24 Nov 2020 16:58:31 +0100 [thread overview]
Message-ID: <20201124155831._wl8yzv0A0zwAahghZg5yLlhQDpwO6dAloCc9wevJXg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26430@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
New comment by sardior on void-packages repository
https://github.com/void-linux/void-packages/issues/26430#issuecomment-733067186
Comment:
I need the daemon because the MX master 3 mouse I'm using does not retain settings after poweroff, so after some research I constructed the following udev rule to remedy that when I turn on the mouse:
```
$ cat /etc/udev/rules.d/70-logitec-mouse.rules
ACTION=="change"\
, SUBSYSTEM=="power_supply"\
, ENV{POWER_SUPPLY_MODEL_NAME}=="Wireless Mouse MX Master 3"\
, ENV{POWER_SUPPLY_ONLINE}=="1"\
, ENV{POWER_SUPPLY_STATUS}=="Discharging"\
, RUN+="/usr/bin/su root -c 'ratbagctl Logitech\ MX\ Master\ 3000 dpi set 4000'"
```
However for ratbagctl to work I need the daemon properly running and seeing the device, e.g. `ratbagctl list ` outputting the device list : `singing-gundi: Logitech MX Master 3000` , which is not happening for some reason unless I restart the service manually.
I changed i3 startup in my xinit from `exec i3` to `exec dbus-run-session i3` but it didn't help in this case.
Also I know the conditions are bad, they aren't meant to stay there :D
next prev parent reply other threads:[~2020-11-24 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:05 [ISSUE] ratbgagd " sardior
2020-11-16 15:16 ` ratbagd " ericonr
2020-11-17 13:16 ` sardior
2020-11-22 12:15 ` ahesford
2020-11-22 13:50 ` Duncaen
2020-11-24 15:58 ` sardior [this message]
2020-11-24 16:02 ` ericonr
2020-11-24 16:03 ` 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=20201124155831._wl8yzv0A0zwAahghZg5yLlhQDpwO6dAloCc9wevJXg@z \
--to=sardior@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).