AprilNEA / AprilNEA/OpenLogi

[Bug]: G309 LIGHTSPEED buttons tab not showing

Open
#877 0 comments 0 reactions 0 assignees View on GitHub
needs: triage type: bug
Dominant language
Rust
Stars
21k
Forks
675
Avg merge
1d 6h
Merged PRs (30d)
180

Description

### Pre-flight checklist

- [x] I searched [existing issues](https://github.com/AprilNEA/OpenLogi/issues?q=is%3Aissue) and this is not a duplicate.
- [x] I am on the [latest release](https://github.com/AprilNEA/OpenLogi/releases/latest) or a recent `master` build.
- [x] I quit **Logi Options+** before running OpenLogi (the two apps fight over HID++ access and only one can own a receiver at a time).

### Which part of OpenLogi?

GUI (desktop app)

### OpenLogi version

0.7.10

### Operating system

Windows

### OS version & architecture

11 25H2

### Device model

G309 + LIGHTSPEED receiver

### How is the device connected?

Other / not sure

### Affected area(s)

- [ ] Device discovery / detection
- [x] Button remapping
- [ ] DPI control
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Battery status
- [ ] Settings / configuration (TOML)
- [ ] Auto-update
- [ ] Menu bar / tray
- [x] Other

### What happened?

The G309 buttons tab only shows on new installs and then when turning the mouse on it's gone and doesn't come back. Also the mouse doesn't show a picture in the UI.

### OpenLogi Diagnostics

**App**
- OpenLogi (GUI): v0.7.10 (release)
- Agent: v0.7.10 (connected)
- IPC protocol: GUI 26 / agent 26
- Inventory: ready
- OS: Windows (x86_64)
- Locale: en-US (UI: follow system)
- Accessibility: granted · Input hook: installed
- Launch at login: no · Menu bar: yes · Update check: on
- Running from: source build (dev)
- Config: schema 4 · 3 configured device(s) · thumbwheel 14

**Assets**
- Source: user cache · Index: loaded (210 models) · User cache: present
- Cache path: C:\Users\InterClaw\.local/share/openlogi\assets · Bundle assets: absent

**Devices (3)**
- G309 — mouse (codename: G309)
- Connection: Logi Unifying receiver · Online: yes · Battery: 100% (discharging, full)
- Capabilities: buttons=no, pointer=yes, lighting=no
- DPI: 400 dpi (range 100–25600, 383 steps)
- Model: 0b03c (wpid: 40b1, model-ids: b03c/40b1/0000, ext-model: 00)
- Transports: eQuad, BTLE
- Render: ⚠️ none (silhouette) · Slot 1
- MX Keys S — keyboard (codename: MX KEYS S)
- Connection: Logi Bolt receiver · Online: yes · Battery: 55% (charging, full)
- Capabilities: buttons=yes, pointer=no, lighting=no
- Model: 0b378 (wpid: b378, model-ids: b378/0000/0000, ext-model: 00)
- Transports: BTLE
- Render: mx_keys_s · Slot 1
- M585/M590 — mouse (codename: M585/M590)
- Connection: Logi Unifying receiver · Online: yes · Battery: 90% (discharging, full)
- Capabilities: buttons=yes, pointer=no, lighting=no
- Model: 5b01b (wpid: 406b, model-ids: b01b/406b/0000, ext-model: 05)
- Transports: eQuad, BTLE
- Render: m585 · Slot 1

**Receivers (3)**
- Logi Bolt Receiver (VID 046d / PID c548)
- Lightspeed Receiver (VID 046d / PID c547)
- Unifying Receiver (VID 046d / PID c52b)

Image

Image

### Steps to reproduce

1. Plug in the USB dongle.
2. Install OpenLogi.
3. Turn on the mouse.

### Diagnostics report

```markdown

```

### `openlogi list` output

```text

```

### Logs

```shell

```

### macOS permissions (if applicable)

- [ ] OpenLogi has **Accessibility** permission (needed to remap buttons via the event tap).
- [ ] OpenLogi has **Input Monitoring** permission (needed for Bluetooth-direct devices and capture).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the OpenLogi GUI device view and the G309 capability and asset data reported by Diagnostics, then reproduce the issue using the three listed steps. Check why the G309 is reported with buttons=no and Render: none after the mouse is turned on. Done means the buttons tab remains available and the G309 image appears consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.