Re: udev rules behaves opposite when executing startx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



   Any clue please ??


On Thu, 4 Nov 2010 14:15:01 +0530
"J. Bakshi" <j.bakshi@xxxxxxxxxxxxxxxxx> wrote:

> On Thu, 4 Nov 2010 10:07:41 +0530
> "J. Bakshi" <j.bakshi@xxxxxxxxxxxxxxxxx> wrote:
> 
> > 
> > Hello list,
> > 
> > Here is my udev rules which disable touchpad when I plug my usb external mouse, and enable it again, when removing the mouse 
> > 
> > ```````````````````
> > ACTION=="add", SUBSYSTEM=="input", ENV{ID_CLASS}="mouse", ENV{DISPLAY}=":0.0", ENV{XAUTHORITY}="/home/user1/.Xauthority"  RUN+="/usr/bin/synclient TouchpadOff=1", RUN+="/bin/su user1 -c 'DISPLAY=:0.0 notify-send %k ' "
> > 
> > ACTION=="remove", SUBSYSTEM=="input", ENV{ID_CLASS}=="mouse"  RUN+="/usr/bin/synclient TouchpadOff=0", RUN+="/bin/su user1 -c 'DISPLAY=:0.0 notify-send %k ' "
> > ``````````````````````````````
> > 
> > The rules is running well within X. But only when I start my WM with startx , then the rules behaves opposite. With no mouse attached , the touchpad is still inactive. Though by pluging/unpluging the mouse, the rules start working normally. I don't understand why startx makes the rules behave so. Could anyone give me any clue please ? 
> > 
> > Thanks
> > --
> 
> I wonder, if there is any alternative to disable/enable the touchpad, irrespective of DISPLAY ( i.e. ENV{DISPLAY}=":0.0", ENV{XAUTHORITY}="/home/user1/.Xauthority" ). Hence the rules will work well whenever it detects the mouse, in X and in console.
> 
>


--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux