a23 bugs in startup, mouse, & associations

Forum › Forums › Official Releases › antiX-23 “Arditi del Popolo › a23 bugs in startup, mouse, & associations

  • This topic has 32 replies, 9 voices, and was last updated Dec 22-4:03 am by Forto4nik.
Viewing 3 posts - 31 through 33 (of 33 total)
  • Author
    Posts
  • #192159
    Forto4nik
    Member

      Unfortunately I have antiX-pdm out of box and it’s not work properly. I update and upgrade after install antiX of course.

      #192172
      Robin
      Member

        it’s not work properly.

        What precisely reads the console output if you try?

        Where I find mouse layout config?

        The config file written by antiX-pdm is

        ~/.current_pointing_device_config

        containing a line

        xinput set-prop "Device_name_here" "libinput Left Handed Enabled" "1"

        and it should be hooked in

        ~/.desktop-session/startup

        therein again you should find a line reading:

        ## Uncomment to load device configurations set in antix poting device manager
        $HOME/.current_pointing_device_config &

        Windows is like a submarine. Open a window and serious problems will start.

        #192239
        Forto4nik
        Member

          I think that current antiX-pdm have an error with “Apply and close” button. It’s untouchable anyway – nor by mouse, nor by keyboard. Thus file “.current_pointing_device_config” not copied (I not see this file) from “.temporary_current_pointing_device_config” (I see this file). “startup” file not modified also.

          What precisely reads the console output if you try?

          Yep. I not try this way. See many errors:

          $ antiX-pdm
          ⎜ ↳ Logitech USB-PS/2 Optical Mouse id=9 [slave pointer (2)]
          /usr/local/bin/antiX-pdm: line 227: [: : wait integer equation
          /usr/local/bin/antiX-pdm: line 228: [: : wait integer equation
          Device Enabled (173): 1
          libinput Natural Scrolling Enabled (312): 0
          libinput Left Handed Enabled (328): 0
          argument could not be parsed
          libinput Accel Speed (323): 0.000000
          X Error of failed request: BadValue (integer parameter out of range for operation)
          Major opcode of failed request: 131 (XInputExtension)
          Minor opcode of failed request: 57 ()
          Value in failed request: 0xaf
          Serial number of failed request: 21
          Current serial number in output stream: 22
          Coordinate Transformation Matrix (175): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

          Just for your information, EVEN IF YOU CHANGED NOTHING, the current pointing device config is:

          xinput set-prop “Logitech USB-PS/2 Optical Mouse” “libinput Accel Speed” “”
          xinput set-prop “Logitech USB-PS/2 Optical Mouse” “Coordinate Transformation Matrix” 0 0 0 0 0 0 1
          libinput Middle Emulation Enabled (321): 0
          libinput Horizontal Scroll Enabled (331): 1

          23 dec: I’ll brute force this. Read /usr/local/bin/antiX-pdm and ~/.temporary_current_poiting_device_config, replay appropriate ~/.current_pointing_device_config with

          xinput set-prop "<Place_you_mouse>" "libinput Accel Speed" ""
          xinput set-prop "<Place_you_mouse>" "Coordinate Transformation Matrix" 0 0 0 0 0 0 1
          xinput set-prop "<Place_you_mouse>" "libinput Left Handed Enabled" "1"

          make them executable and paste this

          ## Uncomment to load device configurations set in antix pointing device manager
          ~/.current_pointing_device_config &

          into the ~/.desktop-session/startup
          Now mouse are left handed and I’d learn how to disable antiX-pdm update for a while.

          BTW: antiX-pdm have 3 typos (1 critical) with “poiting” instead of “pointing”.

          • This reply was modified 9 months ago by Forto4nik.
          • This reply was modified 9 months ago by Forto4nik.
        Viewing 3 posts - 31 through 33 (of 33 total)
        • You must be logged in to reply to this topic.