Inputattach does nothing on elo touchscreen ubuntu 18.04Configuring touchscreenUbuntu 11.10 Dual Screen, Configuration of 1 Touchscreen MonitorUbuntu 12.10 not working with Samsung ME40B/CY-TM40Nexio USB IR touchscreen issuesTouchscreen ELO(touch) not recognized on Lubuntu at startupHow to rotate touch screen input on Ubuntu 16.04?How can I disable the multitouch functionality of a touchscreen?Touch screen stops working occationallyEGalax touchscreen no input on Ubuntu 18.04How to calibrate multiple touchscreen connected on 2 different graphic cards?

I am the person who abides by rules, but breaks the rules. Who am I?

Can I negotiate a patent idea for a raise, under French law?

Smooth vector fields on a surface modulo diffeomorphisms

The preposition for the verb (avenge) - avenge sb/sth (on OR from) sb

How can a demon take control of a human body during REM sleep?

How do I increase the number of TTY consoles?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

Why do we say 'Pairwise Disjoint', rather than 'Disjoint'?

What was so special about The Piano that Ada was willing to do anything to have it?

Is divide-by-zero a security vulnerability?

How can I wire a Raspberry Pi to an 8-relay board in a tidy professional manner?

Are all players supposed to be able to see each others' character sheets?

How to open new window on center of screen

Can one live in the U.S. and not use a credit card?

Strange opamp's output impedance in spice

Why does Central Limit Theorem break down in my simulation?

What do you call someone who likes to pick fights?

Writing text next to a table

Too soon for a plot twist?

How exactly does an Ethernet collision happen in the cable, since nodes use different circuits for Tx and Rx?

Was it really inappropriate to write a pull request for the company I interviewed with?

What to do if my university does not offer any advanced math courses?

What is better: yes / no radio, or simple checkbox?

What is this tube in a jet engine's air intake?



Inputattach does nothing on elo touchscreen ubuntu 18.04


Configuring touchscreenUbuntu 11.10 Dual Screen, Configuration of 1 Touchscreen MonitorUbuntu 12.10 not working with Samsung ME40B/CY-TM40Nexio USB IR touchscreen issuesTouchscreen ELO(touch) not recognized on Lubuntu at startupHow to rotate touch screen input on Ubuntu 16.04?How can I disable the multitouch functionality of a touchscreen?Touch screen stops working occationallyEGalax touchscreen no input on Ubuntu 18.04How to calibrate multiple touchscreen connected on 2 different graphic cards?













0















I have been stuck on making ubuntu to recognize an old Elo TouchScreen. After a lot of reading/testing i managed to detect the touchscreen using screen:



sudo screen /dev/ttyS4 


ttyS4 = COM5 where the touchscreen is connected. After executing this command i get to touch the screen and it draws weird characters on the screen, which in my understanding is that ubuntu recognize the device.
Then i'm suppossed to attach the touchscreen with inputattach:



inputattach -elo /dev/ttyS4


But nothing happens. Either i get not action at all or it just get stuck without any result, and i even can't draw anymore when touching the screen again. Before it was even telling me:



inputattach: can't set line discipline


Which according to https://forums.gentoo.org/viewtopic-p-6406944.html is fixed by going into my kernel config and make sure the serial line discipline is enabled.



Sounds easy but i 'm not an experimented user so can you tell me how do i do that or if there is any suggestion or alternative solution that i could take?



Specs:
Ubuntu 18.04.
Device: Point Of Sale Model 430/435 with B55/B75 M/B wich according to user manual has an elotouch monitor.
Video driver only doing 640X480 resolution and it suppossed to do at least 800X600.



I have also tried to install several linux drivers from elo website without any luck. Originally this device was running WinXp SP2 but a friend brought me and ask me to update the device to a better OS. So it's been a kind of long but fun journey :)



Any help will be appreciated.



Update #1
I didn't know i could add 2 options at the same time to the inputattach command.
So i tried: --daemon --always like this:



sudo inputattach --daemon --always -elo /dev/ttyS4


And it started to work, it recognized each touch. So i went to edit the inputattach file located at /lib/udev/rules.d/60-inputattach.rules in order to save the configuration for every boot, and added the line:



SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elo /dev/%k" I rebooted, the line is still there but not effects at all, just not working and i can't manage to make it work again :(



Tried to add several lines to that file:



SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k"

SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"

SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/modprobe elo" RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"


Still no luck.
I keep getting response with screen command, but apart from that nothing happens :( I'm close to the solution and sure i'm missing something basic here...
Thanks again




UPDATE #2
Reason why it stopped to give me response: I mixed the commands variations. The one that recognize when touching the screen was another.
Summing it up:



I went ahead and tried several combinations of inputattach first entering modprobe elo and then tested again without it. And my conclusion is that modprobe elo //does nothing on my end



So, the only combination when i get response is: (no need of modprobe or screen commands before. Since modprobe does nothing and screen is only for detecting the right port COM4 = ttyS4 in my case)



sudo inputattach --daemon --always --mtouch /dev/ttyS4 


--mtouch = MicroTouch (3M) touchscreen. (you can find all the inputattach compatible devices typing: inputattach --help.



The response is not good enough. Each time i touch the screen it seems like if i'm using a normal mouse and left cliking and selecting some area. (I guess this is what the mtouch device does), so it isn't good enough for me.



However, I tried to calibrate the screen using:



sudo apt-get install xinput-calibrator
sudo xinput_calibrator


I see the 4 points in each corner but is impossible to touch it in the right place in order to calibrate it. So what i did is connected a normal usb mouse and calibrated the screen clicking with it. After that, each touch isn't accurate yet but i least i have values for X and Y Max/Min.



So after more research my second solution was trying to calibrate it myself calculating the TransformationMatrix but I have no idea how. So far:



xinput --list


//Gives me the device name and the id MicroTouch Serial Touch Screen | ID=12



Then xinput --list-props 12 gives me the TransformationMatrix that i'm supposed to add to the file: /etc/X11/xorg.conf.f/99-calibration.conf like this:



Section "InputCalls"
Identifier "calibration
MatchProduct "MicroTouch Serial Touch Screen"
Option "TransformationMatrix" "1 0 0 0 1 0 0 0 1" #Got this values after calibrating the screen clicking with my mouse on each corner point (xinput_calibrator)
Option "MinX" "299"
Option MaxX" "65492"
Option "MinY" "705
Option "MinX" "66058"
EndSection


Problems:



  • Even though i don't mind, this is not my device driver and maybe is
    just not going to work properly.

    • I'm not sure how to re-calculate that TransformationMatrix to the proper calibration axis.

    • Even if i managed to recalculate that Matrix, I don't know where the xorg config file is, since is not in /user/share/X11/xorg.conf.d
      neither and i'm not sure that the file i created is actually doing
      something.


  • -

If i can figure out this last problems, next step will be to add the final configuration to my //lib/udev/rules.d/60-inputattach.rules so it can be loaded every boot by default.



But it seems i'm stuck.
I'm gonna try doing more research and in the mean time the other idea i have is to just test with each device listed in inputattach --help and see if i get any different response.
Otherwise will be back to winxp :(
Hope this journey could be useful for anyone since i have been talking to my own LOL :p










share|improve this question




























    0















    I have been stuck on making ubuntu to recognize an old Elo TouchScreen. After a lot of reading/testing i managed to detect the touchscreen using screen:



    sudo screen /dev/ttyS4 


    ttyS4 = COM5 where the touchscreen is connected. After executing this command i get to touch the screen and it draws weird characters on the screen, which in my understanding is that ubuntu recognize the device.
    Then i'm suppossed to attach the touchscreen with inputattach:



    inputattach -elo /dev/ttyS4


    But nothing happens. Either i get not action at all or it just get stuck without any result, and i even can't draw anymore when touching the screen again. Before it was even telling me:



    inputattach: can't set line discipline


    Which according to https://forums.gentoo.org/viewtopic-p-6406944.html is fixed by going into my kernel config and make sure the serial line discipline is enabled.



    Sounds easy but i 'm not an experimented user so can you tell me how do i do that or if there is any suggestion or alternative solution that i could take?



    Specs:
    Ubuntu 18.04.
    Device: Point Of Sale Model 430/435 with B55/B75 M/B wich according to user manual has an elotouch monitor.
    Video driver only doing 640X480 resolution and it suppossed to do at least 800X600.



    I have also tried to install several linux drivers from elo website without any luck. Originally this device was running WinXp SP2 but a friend brought me and ask me to update the device to a better OS. So it's been a kind of long but fun journey :)



    Any help will be appreciated.



    Update #1
    I didn't know i could add 2 options at the same time to the inputattach command.
    So i tried: --daemon --always like this:



    sudo inputattach --daemon --always -elo /dev/ttyS4


    And it started to work, it recognized each touch. So i went to edit the inputattach file located at /lib/udev/rules.d/60-inputattach.rules in order to save the configuration for every boot, and added the line:



    SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elo /dev/%k" I rebooted, the line is still there but not effects at all, just not working and i can't manage to make it work again :(



    Tried to add several lines to that file:



    SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k"

    SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"

    SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/modprobe elo" RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"


    Still no luck.
    I keep getting response with screen command, but apart from that nothing happens :( I'm close to the solution and sure i'm missing something basic here...
    Thanks again




    UPDATE #2
    Reason why it stopped to give me response: I mixed the commands variations. The one that recognize when touching the screen was another.
    Summing it up:



    I went ahead and tried several combinations of inputattach first entering modprobe elo and then tested again without it. And my conclusion is that modprobe elo //does nothing on my end



    So, the only combination when i get response is: (no need of modprobe or screen commands before. Since modprobe does nothing and screen is only for detecting the right port COM4 = ttyS4 in my case)



    sudo inputattach --daemon --always --mtouch /dev/ttyS4 


    --mtouch = MicroTouch (3M) touchscreen. (you can find all the inputattach compatible devices typing: inputattach --help.



    The response is not good enough. Each time i touch the screen it seems like if i'm using a normal mouse and left cliking and selecting some area. (I guess this is what the mtouch device does), so it isn't good enough for me.



    However, I tried to calibrate the screen using:



    sudo apt-get install xinput-calibrator
    sudo xinput_calibrator


    I see the 4 points in each corner but is impossible to touch it in the right place in order to calibrate it. So what i did is connected a normal usb mouse and calibrated the screen clicking with it. After that, each touch isn't accurate yet but i least i have values for X and Y Max/Min.



    So after more research my second solution was trying to calibrate it myself calculating the TransformationMatrix but I have no idea how. So far:



    xinput --list


    //Gives me the device name and the id MicroTouch Serial Touch Screen | ID=12



    Then xinput --list-props 12 gives me the TransformationMatrix that i'm supposed to add to the file: /etc/X11/xorg.conf.f/99-calibration.conf like this:



    Section "InputCalls"
    Identifier "calibration
    MatchProduct "MicroTouch Serial Touch Screen"
    Option "TransformationMatrix" "1 0 0 0 1 0 0 0 1" #Got this values after calibrating the screen clicking with my mouse on each corner point (xinput_calibrator)
    Option "MinX" "299"
    Option MaxX" "65492"
    Option "MinY" "705
    Option "MinX" "66058"
    EndSection


    Problems:



    • Even though i don't mind, this is not my device driver and maybe is
      just not going to work properly.

      • I'm not sure how to re-calculate that TransformationMatrix to the proper calibration axis.

      • Even if i managed to recalculate that Matrix, I don't know where the xorg config file is, since is not in /user/share/X11/xorg.conf.d
        neither and i'm not sure that the file i created is actually doing
        something.


    • -

    If i can figure out this last problems, next step will be to add the final configuration to my //lib/udev/rules.d/60-inputattach.rules so it can be loaded every boot by default.



    But it seems i'm stuck.
    I'm gonna try doing more research and in the mean time the other idea i have is to just test with each device listed in inputattach --help and see if i get any different response.
    Otherwise will be back to winxp :(
    Hope this journey could be useful for anyone since i have been talking to my own LOL :p










    share|improve this question


























      0












      0








      0








      I have been stuck on making ubuntu to recognize an old Elo TouchScreen. After a lot of reading/testing i managed to detect the touchscreen using screen:



      sudo screen /dev/ttyS4 


      ttyS4 = COM5 where the touchscreen is connected. After executing this command i get to touch the screen and it draws weird characters on the screen, which in my understanding is that ubuntu recognize the device.
      Then i'm suppossed to attach the touchscreen with inputattach:



      inputattach -elo /dev/ttyS4


      But nothing happens. Either i get not action at all or it just get stuck without any result, and i even can't draw anymore when touching the screen again. Before it was even telling me:



      inputattach: can't set line discipline


      Which according to https://forums.gentoo.org/viewtopic-p-6406944.html is fixed by going into my kernel config and make sure the serial line discipline is enabled.



      Sounds easy but i 'm not an experimented user so can you tell me how do i do that or if there is any suggestion or alternative solution that i could take?



      Specs:
      Ubuntu 18.04.
      Device: Point Of Sale Model 430/435 with B55/B75 M/B wich according to user manual has an elotouch monitor.
      Video driver only doing 640X480 resolution and it suppossed to do at least 800X600.



      I have also tried to install several linux drivers from elo website without any luck. Originally this device was running WinXp SP2 but a friend brought me and ask me to update the device to a better OS. So it's been a kind of long but fun journey :)



      Any help will be appreciated.



      Update #1
      I didn't know i could add 2 options at the same time to the inputattach command.
      So i tried: --daemon --always like this:



      sudo inputattach --daemon --always -elo /dev/ttyS4


      And it started to work, it recognized each touch. So i went to edit the inputattach file located at /lib/udev/rules.d/60-inputattach.rules in order to save the configuration for every boot, and added the line:



      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elo /dev/%k" I rebooted, the line is still there but not effects at all, just not working and i can't manage to make it work again :(



      Tried to add several lines to that file:



      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k"

      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"

      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/modprobe elo" RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"


      Still no luck.
      I keep getting response with screen command, but apart from that nothing happens :( I'm close to the solution and sure i'm missing something basic here...
      Thanks again




      UPDATE #2
      Reason why it stopped to give me response: I mixed the commands variations. The one that recognize when touching the screen was another.
      Summing it up:



      I went ahead and tried several combinations of inputattach first entering modprobe elo and then tested again without it. And my conclusion is that modprobe elo //does nothing on my end



      So, the only combination when i get response is: (no need of modprobe or screen commands before. Since modprobe does nothing and screen is only for detecting the right port COM4 = ttyS4 in my case)



      sudo inputattach --daemon --always --mtouch /dev/ttyS4 


      --mtouch = MicroTouch (3M) touchscreen. (you can find all the inputattach compatible devices typing: inputattach --help.



      The response is not good enough. Each time i touch the screen it seems like if i'm using a normal mouse and left cliking and selecting some area. (I guess this is what the mtouch device does), so it isn't good enough for me.



      However, I tried to calibrate the screen using:



      sudo apt-get install xinput-calibrator
      sudo xinput_calibrator


      I see the 4 points in each corner but is impossible to touch it in the right place in order to calibrate it. So what i did is connected a normal usb mouse and calibrated the screen clicking with it. After that, each touch isn't accurate yet but i least i have values for X and Y Max/Min.



      So after more research my second solution was trying to calibrate it myself calculating the TransformationMatrix but I have no idea how. So far:



      xinput --list


      //Gives me the device name and the id MicroTouch Serial Touch Screen | ID=12



      Then xinput --list-props 12 gives me the TransformationMatrix that i'm supposed to add to the file: /etc/X11/xorg.conf.f/99-calibration.conf like this:



      Section "InputCalls"
      Identifier "calibration
      MatchProduct "MicroTouch Serial Touch Screen"
      Option "TransformationMatrix" "1 0 0 0 1 0 0 0 1" #Got this values after calibrating the screen clicking with my mouse on each corner point (xinput_calibrator)
      Option "MinX" "299"
      Option MaxX" "65492"
      Option "MinY" "705
      Option "MinX" "66058"
      EndSection


      Problems:



      • Even though i don't mind, this is not my device driver and maybe is
        just not going to work properly.

        • I'm not sure how to re-calculate that TransformationMatrix to the proper calibration axis.

        • Even if i managed to recalculate that Matrix, I don't know where the xorg config file is, since is not in /user/share/X11/xorg.conf.d
          neither and i'm not sure that the file i created is actually doing
          something.


      • -

      If i can figure out this last problems, next step will be to add the final configuration to my //lib/udev/rules.d/60-inputattach.rules so it can be loaded every boot by default.



      But it seems i'm stuck.
      I'm gonna try doing more research and in the mean time the other idea i have is to just test with each device listed in inputattach --help and see if i get any different response.
      Otherwise will be back to winxp :(
      Hope this journey could be useful for anyone since i have been talking to my own LOL :p










      share|improve this question
















      I have been stuck on making ubuntu to recognize an old Elo TouchScreen. After a lot of reading/testing i managed to detect the touchscreen using screen:



      sudo screen /dev/ttyS4 


      ttyS4 = COM5 where the touchscreen is connected. After executing this command i get to touch the screen and it draws weird characters on the screen, which in my understanding is that ubuntu recognize the device.
      Then i'm suppossed to attach the touchscreen with inputattach:



      inputattach -elo /dev/ttyS4


      But nothing happens. Either i get not action at all or it just get stuck without any result, and i even can't draw anymore when touching the screen again. Before it was even telling me:



      inputattach: can't set line discipline


      Which according to https://forums.gentoo.org/viewtopic-p-6406944.html is fixed by going into my kernel config and make sure the serial line discipline is enabled.



      Sounds easy but i 'm not an experimented user so can you tell me how do i do that or if there is any suggestion or alternative solution that i could take?



      Specs:
      Ubuntu 18.04.
      Device: Point Of Sale Model 430/435 with B55/B75 M/B wich according to user manual has an elotouch monitor.
      Video driver only doing 640X480 resolution and it suppossed to do at least 800X600.



      I have also tried to install several linux drivers from elo website without any luck. Originally this device was running WinXp SP2 but a friend brought me and ask me to update the device to a better OS. So it's been a kind of long but fun journey :)



      Any help will be appreciated.



      Update #1
      I didn't know i could add 2 options at the same time to the inputattach command.
      So i tried: --daemon --always like this:



      sudo inputattach --daemon --always -elo /dev/ttyS4


      And it started to work, it recognized each touch. So i went to edit the inputattach file located at /lib/udev/rules.d/60-inputattach.rules in order to save the configuration for every boot, and added the line:



      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elo /dev/%k" I rebooted, the line is still there but not effects at all, just not working and i can't manage to make it work again :(



      Tried to add several lines to that file:



      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k"

      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"

      SUBSYSTEM=="tty", KERNEL=="ttyS4", ACTION=="add|change", RUN+="/lib/udev/modprobe elo" RUN+="/lib/udev/inputattach --elotouch /dev/%k --daemon --always"


      Still no luck.
      I keep getting response with screen command, but apart from that nothing happens :( I'm close to the solution and sure i'm missing something basic here...
      Thanks again




      UPDATE #2
      Reason why it stopped to give me response: I mixed the commands variations. The one that recognize when touching the screen was another.
      Summing it up:



      I went ahead and tried several combinations of inputattach first entering modprobe elo and then tested again without it. And my conclusion is that modprobe elo //does nothing on my end



      So, the only combination when i get response is: (no need of modprobe or screen commands before. Since modprobe does nothing and screen is only for detecting the right port COM4 = ttyS4 in my case)



      sudo inputattach --daemon --always --mtouch /dev/ttyS4 


      --mtouch = MicroTouch (3M) touchscreen. (you can find all the inputattach compatible devices typing: inputattach --help.



      The response is not good enough. Each time i touch the screen it seems like if i'm using a normal mouse and left cliking and selecting some area. (I guess this is what the mtouch device does), so it isn't good enough for me.



      However, I tried to calibrate the screen using:



      sudo apt-get install xinput-calibrator
      sudo xinput_calibrator


      I see the 4 points in each corner but is impossible to touch it in the right place in order to calibrate it. So what i did is connected a normal usb mouse and calibrated the screen clicking with it. After that, each touch isn't accurate yet but i least i have values for X and Y Max/Min.



      So after more research my second solution was trying to calibrate it myself calculating the TransformationMatrix but I have no idea how. So far:



      xinput --list


      //Gives me the device name and the id MicroTouch Serial Touch Screen | ID=12



      Then xinput --list-props 12 gives me the TransformationMatrix that i'm supposed to add to the file: /etc/X11/xorg.conf.f/99-calibration.conf like this:



      Section "InputCalls"
      Identifier "calibration
      MatchProduct "MicroTouch Serial Touch Screen"
      Option "TransformationMatrix" "1 0 0 0 1 0 0 0 1" #Got this values after calibrating the screen clicking with my mouse on each corner point (xinput_calibrator)
      Option "MinX" "299"
      Option MaxX" "65492"
      Option "MinY" "705
      Option "MinX" "66058"
      EndSection


      Problems:



      • Even though i don't mind, this is not my device driver and maybe is
        just not going to work properly.

        • I'm not sure how to re-calculate that TransformationMatrix to the proper calibration axis.

        • Even if i managed to recalculate that Matrix, I don't know where the xorg config file is, since is not in /user/share/X11/xorg.conf.d
          neither and i'm not sure that the file i created is actually doing
          something.


      • -

      If i can figure out this last problems, next step will be to add the final configuration to my //lib/udev/rules.d/60-inputattach.rules so it can be loaded every boot by default.



      But it seems i'm stuck.
      I'm gonna try doing more research and in the mean time the other idea i have is to just test with each device listed in inputattach --help and see if i get any different response.
      Otherwise will be back to winxp :(
      Hope this journey could be useful for anyone since i have been talking to my own LOL :p







      ubuntu-touch display-resolution touchscreen ubuntu-drivers xinput






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 19 '18 at 3:35







      gallo2000sv

















      asked Dec 13 '18 at 16:02









      gallo2000svgallo2000sv

      14




      14




















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2faskubuntu.com%2fquestions%2f1100647%2finputattach-does-nothing-on-elo-touchscreen-ubuntu-18-04%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Ask Ubuntu!


          • 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%2faskubuntu.com%2fquestions%2f1100647%2finputattach-does-nothing-on-elo-touchscreen-ubuntu-18-04%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

          Are there any comparative studies done between Ashtavakra Gita and Buddhim?How is it wrong to believe that a self exists, or that it doesn't?Can you criticise or improve Ven. Bodhi's description of MahayanaWas the doctrine of 'Anatta', accepted as doctrine by modern Buddhism, actually taught by the Buddha?Relationship between Buddhism, Hinduism and Yoga?Comparison of Nirvana, Tao and Brahman/AtmaIs there a distinction between “ego identity” and “craving/hating”?Are there many differences between Taoism and Buddhism?Loss of “faith” in buddhismSimilarity between creation in Abrahamic religions and beginning of life in Earth mentioned Agganna Sutta?Are there studies about the difference between meditating in the morning versus in the evening?Can one follow Hinduism and Buddhism at the same time?Are there any prohibitions on participating in other religion's practices?Psychology of 'flow'

          Where else does the Shulchan Aruch quote an authority by name?Parashat Metzora+HagadolPesach/PassoverShulchan Aruch UTF-8Anonymous glosses in the Shulchan AruchWhy is the Shulchan Aruch definitive?Siman 32, Kitzur Shulchan Aruch: UntranslatedLitvaks/Yeshivish and Shulchan AruchBuying a Shulchan AruchEnglish version of SHULCHAN ARUCHIs there any place where Shulchan Aruch rules with the Rosh against the Rif and Rambam?Are there practices where Sepharadim do not hold by Shulchan Aruch?5th part of the shulchan aruch

          fallocate: fallocate failed: Text file busy in Ubuntu 17.04? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)defragmenting and increasing performance of old lubuntu system with swap partitionIssue with increasing the root partition from the swapthis /usr/bin/dpkg returned error || ubuntu-16.04, 64bitDefault 17.04 swap file locationHow to Resize Ubuntu 17.04 Zesty Swap file size?Ubuntu freezes from online formsMy Laptop is not starting after upgrade ubuntu 16.04 (Kernel 4.8.0-38 to 04.10.0-36)hcp: ERROR: FALLOCATE FAILED!Not sure my swap is being usedWine 3.0 asking for more virtual free swap