From: Phillip Susi <psusi@cfl.rr.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: false udev event
Date: Sun, 21 Nov 2010 14:27:21 +0000 [thread overview]
Message-ID: <4CE92C49.4050600@cfl.rr.com> (raw)
In-Reply-To: <201011201810.oAKIAHxK019175@dcnode-02.unlimitedmail.net>
On 11/20/2010 01:10 PM, J. Bakshi wrote:
> ````````````````````````````````````
> ACTION="add", SUBSYSTEM="input", ENV{ID_CLASS}="mouse", ENV{DISPLAY}=":0.0", ENV{XAUTHORITY}="/home/joy/.Xauthority" RUN+="/usr/bin/synclient TouchpadOff=1", RUN+="/bin/su joy -c 'DISPLAY=:0.0 notify-send %k; killall syndaemon ' "
This rule is fundamentally broken. You are explicitly setting the
environment to point to your .Xauthority file and the first instance of
an X server, which of course, assumes that you are logged into that X
instance at the time. When this rule is processed, that is almost
certainly not going to be true.
It also will run repeatedly for every input device in the system. Maybe
you meant ENV{ID_CLASS}="mouse" instead of ENV{ID_CLASS}="mouse"?
next prev parent reply other threads:[~2010-11-21 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 18:22 false udev event J. Bakshi
2010-11-21 14:27 ` Phillip Susi [this message]
2010-11-21 15:53 ` J. Bakshi
2010-11-21 19:12 ` Phillip Susi
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=4CE92C49.4050600@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-hotplug@vger.kernel.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).