Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

numlock state always remembered when changed

Open
#328 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
c
Domain
desktop

Research direction

Read plugins/keyboard/csd-keyboard-manager.c around line 162 and inspect how the remember-numlock-state dconf option is accessed. Reproduce the NumLock press while watching /home/user/.config/dconf with inotifywait; done means the setting is respected and unnecessary writes no longer occur.

Written by the indexing model from the issue text.

Description

 * csd version: 4.8.4+ulyssa
 * Distribution: Linux Mint 20.1
 * 64 bit

Issue

CSD writes to disk on every press of NumLock.

Steps to reproduce

Press the NumLock and watch the disk operation indicator.

Use sudo inotifywait -m -e modify -r /home/user/.config/dconf to watch the realtime modifications:

/home/user/.config/dconf/ MODIFY user.FRBRZ0
/home/user/.config/dconf/ MODIFY user.FRBRZ0

Expected behaviour

There is an option in dconf: '/org/cinnamon/settings-daemon/peripherals/keyboard/remember-numlock-state', which should be checked before writing to dconf. I can't see any change of CSD behaviour when this option is enabled or disabled.

The actual code from the source file csd-keyboard-manager.c Line: 162 is:

	if (numlock_state != manager->priv->old_state) {
		g_settings_set_enum (manager->priv->settings,
				     KEY_NUMLOCK_STATE,
				     numlock_state);
		manager->priv->old_state = numlock_state;
	}

Other information

The same behavior can be seen on previous versions of Linux Mint / Cinnamon.

Dominant language
C
Stars
70
Forks
78
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/cinnamon-settings-daemon

All issues in linuxmint/cinnamon-settings-daemon

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.