Open joseon-penggwin opened 4 years ago
I'm experiencing the same issue on X220. I made a quick and dirty fix (https://github.com/libthinkpad/dockd/pull/33) and waiting for the maintainer's input.
The scripts must be executable.
From: dkim286 notifications@github.com Sent: Wednesday, April 8, 2020 11:02:35 PM To: libthinkpad/dockd dockd@noreply.github.com Cc: Subscribed subscribed@noreply.github.com 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 (#33https://github.com/libthinkpad/dockd/pull/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 GitHubhttps://github.com/libthinkpad/dockd/issues/31#issuecomment-611192864, or unsubscribehttps://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:
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 or manually marking them as executable for all users, the latter being less than ideal.
Chown the config files to your user. If you need root apps use passwordless sudo.
From: dkim286 notifications@github.com Sent: Wednesday, April 8, 2020 11:16 PM To: libthinkpad/dockd dockd@noreply.github.com Cc: Ognjen Galić smclt30p@gmail.com; Comment comment@noreply.github.com 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 GitHubhttps://github.com/libthinkpad/dockd/issues/31#issuecomment-611198937, or unsubscribehttps://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 dockd-1.21.tar.gz
have their permissions set as "intended":
-rwxr-xr-x 1 username username 222 Jan 19 2018 dock.hook
-rwxr-xr-x 1 username username 224 Jan 19 2018 undock.hook
...as opposed to what they're actually set to under /etc/dockd
, which matches the original post's.
I suspect this is caused by permissions not being preserved at installation time and probably outside dockd's control.
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.