Making xset stick on a secondary X session

[Tony Mobily]

Hi,

I tried again. I am starting to doubt that xset works properly!

I did:

$ export DISPLAY=:1
$ sudo X :1 -noreset &
$ xeyes &
$ xterm &

I can then confirm that xset has no effect on the running X:

$ xset r rate 50 150

No difference in the repeat rate.
However, if you run the command on the terminal within :1, it will work (as
expected).

It really looks like xset will only work if run within the server itself...
but why? Should I report this as a bug? (it's really easy to reproduce)

Bye,

Merc.

On 14 October 2015 at 08:00, Tony Mobily <merc at mobily1.com> wrote:

> Hi,
>
> $ export DISPLAY=:1
>>> $ sudo X :1 &
>>> $ xterm &
>>>
>>> At this point, a new terminal is running and it's all dandy. But repeat
>>> is SLOW.
>>>
>>> Then, from the LAUNCHING terminal:
>>>
>>> $ xset r rate 50 150
>>>
>>> Back in the :1 server, the repeat has NOT changed. Input from xterm is
>>> still
>>> very slow.
>>>
>>
>> My best guess is either DISPLAY isn't set correctly for the xset process
>> or
>> that since you don't have -noreset in that X command line you're hitting a
>> race condition and the xset exits before the more complicated xterm begins
>> and thus the server resets between the two.
>
>
>
> I tried again.
>
> $ export DISPLAY=:1
> $ sudo X :1 -noreset &
> $ xeyes &
> $ xterm &
>
> I can then confirm that xset has no effect on the running X:
>
> $ xset r rate 50 150
>
> No difference in the repeat rate.
> However, if you run the command on the terminal within :1, it will work
> (as expected).
>
> It really looks like xset will only work if run within the server
> itself... but why? Should I report this as a bug? (it's really easy to
> reproduce)
>
> Bye,
>
> Merc.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20151014/2b5bedab/attachment.html>