Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not loading on boot using Open SUSE Tumbleweed #1031

Open
danielrosehill opened this issue Jan 3, 2025 · 7 comments
Open

Not loading on boot using Open SUSE Tumbleweed #1031

danielrosehill opened this issue Jan 3, 2025 · 7 comments

Comments

@danielrosehill
Copy link

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.

@sezanzeb
Copy link
Owner

sezanzeb commented Jan 3, 2025

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
Copy link
Owner

sezanzeb commented Jan 3, 2025

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

@noyannus
Copy link

noyannus commented Jan 4, 2025

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.

@sezanzeb
Copy link
Owner

sezanzeb commented Jan 5, 2025

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
Copy link
Owner

sezanzeb commented Jan 5, 2025

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
Copy link
Owner

sezanzeb commented Jan 5, 2025

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

@noyannus
Copy link

noyannus commented Jan 5, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants