Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S Solaar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pwr-Solaar
  • Solaar
  • Issues
  • #418
Closed
Open
Issue created Mar 23, 2018 by Administrator@rootContributor

solaar (CLI) doesn't persist settings on K400+

Created by: rhester72

If I use solaar from master to toggle the Fn state on my K400+, it works, up until keyboard inactivity causes the keyboard to sleep - and once I wake it with a keypress, the setting is lost until I manually re-run solaar to set it again.

Is there any way to have solaar run in some sort of daemon mode where it will do this automatically, short of cronning it (and likely causing it to never sleep, which would 'fix' the problem at the expense of much-reduced battery life)?

Assignee
Assign to
Time tracking