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

allow autoload command to execute if config_dir is provided #219

Closed
wants to merge 2 commits into from

Conversation

tmclane
Copy link

@tmclane tmclane commented Nov 30, 2021

I have a Linux machine that does not show any logged in users with the who command even when I am using the machine.
It is perhaps a specialized use-case but I don't see why you need a logged in user in order to activate the mapping IF a config directory has been provided which contains the relevant configuration for key-mapper.

The machine in question is a JingPad A1.

tmclane@JingOS:/media/tmclane/data/key-mapper$ who
tmclane@JingOS:/media/tmclane/data/key-mapper$ whoami
tmclane

@sezanzeb
Copy link
Owner

sezanzeb commented Nov 30, 2021

You are absolutely right!

But that won't fix autoloading at login (data/key-mapper-autoload.desktop) or device plugging (data/99-key-mapper.rules) on your system. An alternative to who would be a check if the system booted up completely, until that happened it should ignore calls from udev. Any ideas?

sezanzeb added a commit that referenced this pull request Dec 7, 2021
@sezanzeb
Copy link
Owner

sezanzeb commented Dec 7, 2021

I have pushed a change to main that uses systemd-analyze, does that work for you?

@tmclane
Copy link
Author

tmclane commented Dec 7, 2021

Let me give your changes a try.

FYI: I found another solution which was to put a script in: /usr/lib/pm-utils/sleep.d that calls the key-mapper-control command on sleep / wake to disable and reenable it.

Specifically this one: https://github.com/tmclane/jingpad/blob/main/99_jingpad_wakeup

@sezanzeb
Copy link
Owner

I think this can be closed, the change with systemd-analyze probably fixed this

@sezanzeb sezanzeb closed this Oct 23, 2022
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

Successfully merging this pull request may close these issues.

2 participants