Kraken 2023 Elite: set lcd screen orientation applies a consistent +90 degree offset from the requested value
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start at the liquidctl set lcd screen orientation <degrees> entry point and inspect the Kraken 2023 Elite driver and its device-table handling. Reproduce the four reported commands on the affected USB device, then verify that requested and displayed orientations match without regressing other LCD controls.
Written by the indexing model from the issue text.
Description
Describe the bug
liquidctl set lcd screen orientation <degrees> succeeds (exit code 0, no error) but the LCD ends up rotated 90 degrees further than the value requested, consistently and reproducibly. Brightness (set lcd screen brightness <0-100>) works correctly on the same device, so this looks specific to the orientation command rather than a general communication problem.
Confirmed across 4 data points by visually checking the physical screen after each command, starting from upright (0):
| Requested | Actual result on screen |
|---|---|
| 180 | 90° left (i.e. 270, not 180) |
| 0 | 90° right (i.e. 90, not 0) |
| 90 | upside down (i.e. 180, not 90) |
| 270 | upright (i.e. 0, not 270) |
Every result is exactly (requested + 90) mod 360. Workaround for anyone hitting this: request (desired - 90) mod 360 to get the orientation you actually want (e.g. request 270 to get upright/0).
Commands executed
liquidctl --match kraken set lcd screen orientation 180
liquidctl --match kraken set lcd screen orientation 0
liquidctl --match kraken set lcd screen orientation 90
liquidctl --match kraken set lcd screen orientation 270
Affected device
NZXT Kraken 2023 Elite (USB PID 1e71:300c) - noting the driver already flags this exact model "(broken)" in its own device table, and separately confirmed the known image/gif upload failure (#657 / AssertionError('Cannot find bulk out device')) on the same unit, so this may be part of the same general firmware/protocol gap for this specific model rather than a new discovery, but didn't see it reported anywhere as its own issue.
Operating system and version
Windows 11
Version of liquidctl
1.16.0
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 295
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from liquidctl/liquidctl
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug external
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in liquidctl/liquidctl
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·