-
Notifications
You must be signed in to change notification settings - Fork 22
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
Hook scripts are not executed #31
Comments
I'm experiencing the same issue on X220. I made a quick and dirty fix (#33) and waiting for the maintainer's input. |
The scripts must be executable.
…________________________________
From: dkim286 <[email protected]>
Sent: Wednesday, April 8, 2020 11:02:35 PM
To: libthinkpad/dockd <[email protected]>
Cc: Subscribed <[email protected]>
Subject: Re: [libthinkpad/dockd] Hook scripts are not executed (#31)
I'm experiencing the same issue on X220. I made a quick and dirty fix (#33<#33>) and waiting for the maintainer's input.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#31 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADKRL6Z2ENLIEIV5UT7OWADRLTQ6XANCNFSM4J2LSCNA>.
|
Thanks for the reply. At least on my end, the hooks are already executable, but they're owned by the root user and it's preventing the script from being run:
I'm not sure how this can be avoided as |
Chown the config files to your user. If you need root apps use passwordless sudo.
…________________________________
From: dkim286 <[email protected]>
Sent: Wednesday, April 8, 2020 11:16 PM
To: libthinkpad/dockd <[email protected]>
Cc: Ognjen Galić <[email protected]>; Comment <[email protected]>
Subject: Re: [libthinkpad/dockd] Hook scripts are not executed (#31)
Thanks for the reply. At least on my end, the hooks are already executable, but they're owned by the root user and it's preventing the script from being run:
Apr 08 14:07:57 lateralus dockd[3694167]: Dock hook exited with non-zero value (32256)
I'm not sure how this can be avoided as dockd needs to be run with superuser permissions to write to /etc/dockd/ when configuring. The only workaround I can think of is running the hooks as file args for bash.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#31 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADKRL62O4CXH2QNKBO22S7TRLTSS3ANCNFSM4J2LSCNA>.
|
My local copy of dockd is from AUR fetched via auracle. I noticed that the original hook files in
...as opposed to what they're actually set to under In the meantime, I decided to just change my own hook files to match the intended permissions. No more hook problems. |
Hi,
I installed dockd according to the readme and have it running now.
Although, the dock and undock scripts are not working.
The scripts are executeable and work well when I call them manually, but don't work when I let them call automatically through dockd.
My dock.hook and undock.hook respectively look like this:
Alas, both don't work.
Lenovo T480s, Xubuntu 18.04
If there's anything you need, just ask.
The text was updated successfully, but these errors were encountered: