Search Criteria
Package Details: msiklm-git 20180823.a284db0-1
Git Clone URL: | https://aur.archlinux.org/msiklm-git.git (read-only, click to copy) |
---|---|
Package Base: | msiklm-git |
Description: | A simple backlighting manager for MSI steelseries keyboards |
Upstream URL: | https://github.com/Gibtnix/MSIKLM |
Keywords: | keyboard msi steelseries |
Licenses: | |
Conflicts: | |
Provides: | |
Submitter: | lhark |
Maintainer: | lhark |
Last Packager: | lhark |
Votes: | 2 |
Popularity: | 0.000004 |
First Submitted: | 2016-04-17 21:12 |
Last Updated: | 2018-12-08 22:37 |
Latest Comments
lhark commented on 2018-12-08 22:38
The issue with these kind of unit files (which otherwise work great), is that the user needs to hardcode their color settings in each of them.
petrusenus commented on 2018-09-03 17:46
I've had a problem as well with the autostart-script. My solution is using the systemd service daemons. Here are them:
/etc/systemd/system/msiklm-afterSleep.service
[Unit] Description=Change Keyboard lights color after Sleep After=suspend.target multi-user.target
[Service] User=root Type=simple ExecStart=/usr/bin/msiklm 0x1793d1 Restart=on-failure
[Install] WantedBy=suspend.target
/etc/systemd/system/msiklm-afterSuspend.service
[Unit] Description=Change Keyboard lights color after Suspend After=hibernate.target multi-user.target
[Service] User=root Type=simple ExecStart=/usr/bin/msiklm 0x1793d1 Restart=on-failure
[Install] WantedBy=hibernate.target
/etc/systemd/system/msiklm-afterBoot.service
[Unit] Description=Change Keyboard lights color after Sleep After=multi-user.target
[Service] User=root Type=simple ExecStart=/usr/bin/msiklm 0x1793d1 Restart=on-failure
[Install] WantedBy=multi-user.target
Make them executeable: sudo chmod 777 msiklm-afterBoot.service sudo chmod 777 msiklm-afterSuspend.service sudo chmod 777 msiklm-afterSleep.service
Then execute: sudo systemctl daemon-reload sudo systemctl enable msiklm-afterBoot.service sudo systemctl enable msiklm-afterSuspend.service sudo systemctl enable msiklm-afterSleep.service
Then it should work.
PS: thanks for msiklm-git @ the developer
lhark commented on 2017-02-04 19:58
There are a few problems with the autostart script which in my mind make it unsuitable for the automated process of a PKGBUILD.
First, this script takes your personal customisation as arguments, so i don't think it is a good idea to run it during install with a default configuration that you will have to update by hand anyway.
Second, the executable path is hardcoded in the script (and it is not the one used in archlinux)
Finaly, i'm not sure everyone wants to handle autostart the udev way.
miguelangellv commented on 2017-02-04 14:07
Maybe you could add autostart script?
zezinand0 commented on 2016-10-26 17:15
well, i reinstalled the package and it works... Thanks for the fast reply !
lhark commented on 2016-10-25 20:11
Is /usr/bin in your $PATH ?
use `echo $PATH' to check and if not you can add `export PATH=$PATH:/usr/bin' to your ~/.bashrc (or .zshrc)
Also, msiklm must be run as root.
zezinand0 commented on 2016-10-25 18:52
Installed with success. Triyng the command msiklm but "command not found". Im new to archlinux. Sorry if im in the bad place to ask for help. Thanks in advance