input-remapper icon indicating copy to clipboard operation
input-remapper copied to clipboard

Not loading on boot using Open SUSE Tumbleweed

Open danielrosehill opened this issue 1 year ago • 8 comments

Hello there!

Before assuming anything, I thought I would check first whether Open SUSE is a supported distro.

The behavior I'm experiencing is that the applied presets won't automatically load. If I manually run the GUI providing my sudo permissions as requested then it works including if I exit the GUI.

I guess it's got something to do with it not loading as a boot service.

Before I go ahead and build from source, I wanted to ask whether there's any known workaround for just getting this running.

Many thanks for creating the tool.

danielrosehill avatar Jan 03 '25 15:01 danielrosehill

Hi. There is an issue template for autoload issues: https://github.com/sezanzeb/input-remapper/blob/main/.github/ISSUE_TEMPLATE/autoloading-not-working.md

sezanzeb avatar Jan 03 '25 17:01 sezanzeb

(I think step 3 in Testing the setup is outdated, you can skip over that)

sezanzeb avatar Jan 03 '25 17:01 sezanzeb

Same here, but Slowroll.

Did you install as user, using su and thus installed for root, but expect it to be active for regular users? Or, if you have copied files manually and not chown -Red /root/.config/input-remapper-2 for root or the user, respectively, that may be another cause.

The documentation lacks some crucial info that you have to extract from the script files. Try this:

  • Clone or copy the repo, if you have not already.
  • Make sure your local repo directory is named input-remapper. The script is picky about it.
  • Run .../input-remapper/scripts/build.sh.
  • Run .../input-remapper/scripts/setup.sh ***usage*** (without the *s!) to see your options.
  • Run .../input-remapper/scripts/setup.sh local-install. Repeat from a login of every user who shall use input-remapper.

HTH, I hope I have understood your problem and the installation procedure right.

Only why after every boot, authentication as root is asked to read the devices, that beats me.

noyannus avatar Jan 04 '25 19:01 noyannus

Only why after every boot, authentication as root is asked to read the devices, that beats me.

Shouldn't happen. Do you have input-remapper in your autostart entries (you shouldn't)?

sezanzeb avatar Jan 05 '25 00:01 sezanzeb

In setup.py you can see where your files should go to: https://github.com/sezanzeb/input-remapper/blob/main/setup.py#L112

There is no need to create or manage /root/.config/input-remapper-2. It reads config files from your users home directory.

Using sudo python3 setup.py install is probably sufficient in most cases.

sezanzeb avatar Jan 05 '25 00:01 sezanzeb

I just pushed something to the main branch that might fix autoloading for some people.

sezanzeb avatar Jan 05 '25 00:01 sezanzeb

Only why after every boot, authentication as root is asked to read the devices, that beats me.

Shouldn't happen. Do you have input-remapper in your autostart entries (you shouldn't)?

That was it. Thank you.

noyannus avatar Jan 05 '25 16:01 noyannus

For those in debian/ubuntu:

The systemd service should be kept as a root-owned service (no need to install the service as user) but to make it autoload mappings for a user (upon loging) you must add an autostart entry with the following command /usr/bin/input-remapper-control --command autoload

Also, make sure your device mapping has the autoload flag/config enabled.

layoaster avatar Mar 06 '25 12:03 layoaster