LiveSplit / LiveSplit/LiveSplitOne

(Desktop) Hotkey settings partially resetting upon program start

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

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
301
Forks
55
Avg merge
8m
Merged PRs (30d)
1

Description

I'm using Livesplit One's desktop version on Gentoo Linux.

When I open the program for the first time, I unbind all hotkeys, and then set my hotkeys to the following:
Start/stop: Down Arrow
Reset: Numpad 2
Undo: Numpad 4
Skip: Numpad 6
Pause: Numpad 8

This works as expected while the program is running. But the next time I open the program, my hotkeys will change to:
Start/stop: Down Arrow
Reset: Numpad 2
Undo: Numpad 8
Skip: Numpad 2
Pause: Numpad 5
Previous Comparison: Numpad 4
Next Comparison: Numpad 6

And unlike before, this time even if I change the settings here, they will not be saved when I hit "OK."
Other settings, such as disabling "always on top," seem to be saved correctly.
Splits and layout are also mostly remembered on reopening the program (window size is not saved.)

I located what seems to be Livesplit One's config file location (~/.local/share/org.livesplit.one/databases/indexeddb/v1/tauri_localhost_0/[numbers]/
If I delete all files in this directory, then the settings (and splits/layout) will reset and I will be able to temporarily have the correct keybindings until I next close the program, but since I'll have to resize the layout and such every time, this is obviously not ideal.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Reproduce the hotkey persistence problem in the desktop version on Gentoo Linux, using the listed keybindings and reopening the program. Inspect the hotkey settings persistence in the IndexedDB location mentioned in the report. Done means bindings remain unchanged after restarting and subsequent edits are saved without resetting other settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
tauri, typescript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.