Download the latest .flatpak bundle from the Releases page:

flatpak install --user logitune.flatpak
flatpak run com.logitune.Logitune

See Building for full instructions. The short version:

git clone https://github.com/logitune/logitune.git
cd logitune
make build
make run

Logitune needs read/write access to hidraw devices and uinput for keystroke injection. A udev rules file is included at data/71-logitune.rules:

SUBSYSTEM=="hidraw", ATTRS{idVendor}=="046d", TAG+="uaccess"
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess"

Install it:

sudo cp data/71-logitune.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules
sudo udevadm trigger

If Logitune starts but shows "No device connected":

1. Check hidraw access: ls -la /dev/hidraw* — your user should have rw access to Logitech devices
2. Check uinput access: ls -la /dev/uinput — needed for keystroke injection
3. Check the device is detected: Run with --debug flag to see device scanning logs

./build/src/app/logitune --debug

Logitune uses a lock file at $TMPDIR/logitune.lock to prevent two instances from fighting over the device. If a previous instance crashed without cleanup, delete the lock file manually:

rm /tmp/logitune.lock

The application window is organized into four main areas:

Logitune Settings page
_{Settings page with debug logging toggle and bug report button}

Point & Scroll page
_{Point & Scroll page showing DPI slider, SmartShift, scroll, and thumb wheel controls}

A vertical navigation bar on the left with icons for each page:

The Buttons page shows a rendered image of the device (front view by default, side view available). Interactive hotspots are overlaid at positions defined by the device descriptor — clicking a hotspot opens the action picker for that button.

A horizontal tab bar at the bottom of the window:

• Default tab is always present — this profile is used for applications without a specific binding
• App profiles appear as additional tabs with the application's icon
• The hardware-active profile (the one currently applied to the device) is indicated with a highlight
• The display profile (the one you're currently viewing/editing) may differ from the hardware-active profile
• Click the + button to add a new app profile from the list of installed applications

Profiles are stored per-device under:

~/.config/Logitune/devices/<device-serial>/profiles/

Each profile is a .conf file (QSettings INI format). App bindings are stored in app-bindings.conf in the same directory.

Logitune runs as a tray application — closing the window hides it to the tray rather than quitting. The tray menu shows:

• 🔋 Battery level — e.g., "Battery: 85%"
• 👁️ Show — brings the window back
• ❌ Quit — exits the application

Debug logging can also be toggled at runtime from the Settings page.

1. 🔒 Single-instance check — attempts to acquire logitune.lock
2. 📝 Log manager init — sets up Qt logging categories, optional file output
3. 🛠️ Crash recovery — checks for previous unclean shutdown, offers to file a bug report
4. 🎛️ AppController init — creates DeviceManager, ProfileEngine, models, wires signals
5. 🖼️ QML engine load — registers model singletons, loads Main.qml
6. 📡 Start monitoring — DeviceManager begins udev scanning and KDE desktop starts focus tracking
7. 🔌 Device connect — on first hidraw match, enumerates HID++ features, reads state, creates command queue
8. 📂 Profile load — loads or seeds the default profile, applies settings to hardware
9. 🔔 Tray icon — system tray icon appears with battery info