Why XInput can't work in X-terminal?Xinput device disable doesn't work for all mousesWhy does “xinput...

Is this photo showing a woman standing in the nude before teenagers real?

What would the United Kingdom's "optimal" Brexit deal look like?

(3 of 11: Akari) What is Pyramid Cult's Favorite Car?

What language is Raven using for her attack in the new 52?

Why force the nose of 737 Max down in the first place?

What are the cons of stateless password generators?

Is there a way to know the composition of a Team GO Rocket before going into the fight?

How can I kill my goat?

Why do they sell Cat 5 Ethernet splitters if you can’t split the signal?

Filter search results by multiple filters in one operation

Why didn’t Christianity spread southwards from Ethiopia in the Middle Ages?

How does one get an animal off of the Altar surreptitiously?

How did the SysRq key get onto modern keyboards if it's rarely used?

Did Vladimir Lenin have a cat?

Does Wolfram Mathworld make a mistake describing a discrete probability distribution with a probability density function?

8086 stack segment and avoiding overflow in interrupts

Should I accept an invitation to give a talk from someone who might review my proposal?

How can Paypal know my card is being used in another account?

Does dual boot harm a laptop battery or reduce its life?

Struggling with cyclical dependancies in unit tests

How could Nomadic scholars effectively memorize libraries worth of information

What is more environmentally friendly? An A320 or a car?

What happens when a flying sword is killed?

2 weeks and a tight budget to prepare for Z-day. How long can I hunker down?



Why XInput can't work in X-terminal?


Xinput device disable doesn't work for all mousesWhy does “xinput list” work just like “xinput --list”?Disable scroll wheel horizontal buttons (back/forward)Remapping keycode generated by a mouseX: alt/ctrl/f1 doesn't work any more after turning the display off and on again with xrandrIncrease mouse speed (xinput)Evdev Wheel Emulation by keyboardWhy does not Anaconda's question box appear during system startup?confusions on xinput query-state outputsdisable touchpad through xinput






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I am trying to show keyboard event by app xinput. I tried on three workstations. On the first two workstations (in local X-session), all is good:



Get device list:



$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HID 1241:1177 id=8 [slave pointer (2)]
⎜ ↳ SIGMACH1P USB Keykoard id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ SIGMACH1P USB Keykoard id=9 [slave keyboard (3)]


Device event:



$ xinput test 9
key release 36
key press 48
key press 47
key release 48
key press 46
lkey release 47
key release 46
key press 41
key press 36
key release 41
key release 36
key press 62
key release 62
key press 37


But on the third workstation, I connect from X-terminal x2go (connect from Windows 7). And in this workstation xinput does not fulfill its function. Xinput does not find devices and segfaults.



$ xinput
"pointer" id=0 [XPointer]
"keyboard" id=1 [XKeyboard]

$ xinput test 1
unable to find device '1'

$ xinput test-xi2 1
"keyboard" id=1 [XKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
Segmentation fault


Question 1: The xinput principial does not work if connection to X-server stable from X-terminal? Or it is bug in standart X11 application?



Question 2: How to alternative get global keyboard event (push and release key) if connect from X-terminal (x2go)?



Environment:

From connect: Windows 7 Pro, official X2GO client from site x2go.org.

To connect: Debian 7.8, LXDE, official server X2GO from site x2go.org.










share|improve this question

















bumped to the homepage by Community 52 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.























    2















    I am trying to show keyboard event by app xinput. I tried on three workstations. On the first two workstations (in local X-session), all is good:



    Get device list:



    $ xinput
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ HID 1241:1177 id=8 [slave pointer (2)]
    ⎜ ↳ SIGMACH1P USB Keykoard id=10 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ SIGMACH1P USB Keykoard id=9 [slave keyboard (3)]


    Device event:



    $ xinput test 9
    key release 36
    key press 48
    key press 47
    key release 48
    key press 46
    lkey release 47
    key release 46
    key press 41
    key press 36
    key release 41
    key release 36
    key press 62
    key release 62
    key press 37


    But on the third workstation, I connect from X-terminal x2go (connect from Windows 7). And in this workstation xinput does not fulfill its function. Xinput does not find devices and segfaults.



    $ xinput
    "pointer" id=0 [XPointer]
    "keyboard" id=1 [XKeyboard]

    $ xinput test 1
    unable to find device '1'

    $ xinput test-xi2 1
    "keyboard" id=1 [XKeyboard]
    Num_keys is 248
    Min_keycode is 8
    Max_keycode is 255
    Segmentation fault


    Question 1: The xinput principial does not work if connection to X-server stable from X-terminal? Or it is bug in standart X11 application?



    Question 2: How to alternative get global keyboard event (push and release key) if connect from X-terminal (x2go)?



    Environment:

    From connect: Windows 7 Pro, official X2GO client from site x2go.org.

    To connect: Debian 7.8, LXDE, official server X2GO from site x2go.org.










    share|improve this question

















    bumped to the homepage by Community 52 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.



















      2












      2








      2








      I am trying to show keyboard event by app xinput. I tried on three workstations. On the first two workstations (in local X-session), all is good:



      Get device list:



      $ xinput
      ⎡ Virtual core pointer id=2 [master pointer (3)]
      ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
      ⎜ ↳ HID 1241:1177 id=8 [slave pointer (2)]
      ⎜ ↳ SIGMACH1P USB Keykoard id=10 [slave pointer (2)]
      ⎣ Virtual core keyboard id=3 [master keyboard (2)]
      ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
      ↳ Power Button id=6 [slave keyboard (3)]
      ↳ Power Button id=7 [slave keyboard (3)]
      ↳ SIGMACH1P USB Keykoard id=9 [slave keyboard (3)]


      Device event:



      $ xinput test 9
      key release 36
      key press 48
      key press 47
      key release 48
      key press 46
      lkey release 47
      key release 46
      key press 41
      key press 36
      key release 41
      key release 36
      key press 62
      key release 62
      key press 37


      But on the third workstation, I connect from X-terminal x2go (connect from Windows 7). And in this workstation xinput does not fulfill its function. Xinput does not find devices and segfaults.



      $ xinput
      "pointer" id=0 [XPointer]
      "keyboard" id=1 [XKeyboard]

      $ xinput test 1
      unable to find device '1'

      $ xinput test-xi2 1
      "keyboard" id=1 [XKeyboard]
      Num_keys is 248
      Min_keycode is 8
      Max_keycode is 255
      Segmentation fault


      Question 1: The xinput principial does not work if connection to X-server stable from X-terminal? Or it is bug in standart X11 application?



      Question 2: How to alternative get global keyboard event (push and release key) if connect from X-terminal (x2go)?



      Environment:

      From connect: Windows 7 Pro, official X2GO client from site x2go.org.

      To connect: Debian 7.8, LXDE, official server X2GO from site x2go.org.










      share|improve this question
















      I am trying to show keyboard event by app xinput. I tried on three workstations. On the first two workstations (in local X-session), all is good:



      Get device list:



      $ xinput
      ⎡ Virtual core pointer id=2 [master pointer (3)]
      ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
      ⎜ ↳ HID 1241:1177 id=8 [slave pointer (2)]
      ⎜ ↳ SIGMACH1P USB Keykoard id=10 [slave pointer (2)]
      ⎣ Virtual core keyboard id=3 [master keyboard (2)]
      ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
      ↳ Power Button id=6 [slave keyboard (3)]
      ↳ Power Button id=7 [slave keyboard (3)]
      ↳ SIGMACH1P USB Keykoard id=9 [slave keyboard (3)]


      Device event:



      $ xinput test 9
      key release 36
      key press 48
      key press 47
      key release 48
      key press 46
      lkey release 47
      key release 46
      key press 41
      key press 36
      key release 41
      key release 36
      key press 62
      key release 62
      key press 37


      But on the third workstation, I connect from X-terminal x2go (connect from Windows 7). And in this workstation xinput does not fulfill its function. Xinput does not find devices and segfaults.



      $ xinput
      "pointer" id=0 [XPointer]
      "keyboard" id=1 [XKeyboard]

      $ xinput test 1
      unable to find device '1'

      $ xinput test-xi2 1
      "keyboard" id=1 [XKeyboard]
      Num_keys is 248
      Min_keycode is 8
      Max_keycode is 255
      Segmentation fault


      Question 1: The xinput principial does not work if connection to X-server stable from X-terminal? Or it is bug in standart X11 application?



      Question 2: How to alternative get global keyboard event (push and release key) if connect from X-terminal (x2go)?



      Environment:

      From connect: Windows 7 Pro, official X2GO client from site x2go.org.

      To connect: Debian 7.8, LXDE, official server X2GO from site x2go.org.







      linux x11 xinput x2go






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 10 '16 at 5:46







      Xintrea

















      asked Jun 9 '16 at 19:20









      XintreaXintrea

      113 bronze badges




      113 bronze badges






      bumped to the homepage by Community 52 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.









      bumped to the homepage by Community 52 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 52 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The segmentation fault is a bug in the xinput program.



          The limited set of devices and missing X Input functionality looks like a lack of support for the newer versions of the X Input extension from the x2go X server.






          share|improve this answer




























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f288780%2fwhy-xinput-cant-work-in-x-terminal%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The segmentation fault is a bug in the xinput program.



            The limited set of devices and missing X Input functionality looks like a lack of support for the newer versions of the X Input extension from the x2go X server.






            share|improve this answer






























              0














              The segmentation fault is a bug in the xinput program.



              The limited set of devices and missing X Input functionality looks like a lack of support for the newer versions of the X Input extension from the x2go X server.






              share|improve this answer




























                0












                0








                0







                The segmentation fault is a bug in the xinput program.



                The limited set of devices and missing X Input functionality looks like a lack of support for the newer versions of the X Input extension from the x2go X server.






                share|improve this answer













                The segmentation fault is a bug in the xinput program.



                The limited set of devices and missing X Input functionality looks like a lack of support for the newer versions of the X Input extension from the x2go X server.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 30 '16 at 6:44









                alancalanc

                2,68811 silver badges23 bronze badges




                2,68811 silver badges23 bronze badges

































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f288780%2fwhy-xinput-cant-work-in-x-terminal%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                    Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                    Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...