Lucidv1.1.0
170
  1. Home
  2. Help
  3. Support

Support

Lucid is open source, and its issues and pull requests live on GitHub. Start with the Help Center. If your problem isn't there, a complete report is the fastest way to a fix.

Help Center

Searchable answers for the problems people hit most.

Search answers

Report a bug

Build the report below, then open it on GitHub.

Start a report

Suggest a feature

Tell us what Lucid should do, and why it would help.

Start an idea

Contribute

Send a pull request. Merged work is credited in the changelog.

How to contribute
Report builder

Write it once, open it on GitHub.

Fill in what you can. The preview becomes the body of a GitHub issue. Nothing is sent anywhere until you press Open on GitHub and submit it there yourself.

What is it?
One line that says what goes wrong, and where.
Run qs log right after the problem happens. Long logs are trimmed in the link; paste the rest into the issue.
Before you file

What to include, and how to find it.

These take a few seconds each and answer most of the first questions on any issue.

Your Lucid version. Also shown on Settings → About.

$ cat ~/.config/quickshell/VERSION

Your Hyprland version. Lucid tracks Hyprland's Lua config closely.

$ hyprctl version | head -n 1

The shell's log. QML errors land here. It is the single most useful thing in a report.

$ qs log

On NVIDIA, the render backend. Says which one Lucid picked and why.

$ ~/.config/lucid/launch-shell.sh --explain

Lucid is a personal open-source project, so there is no guaranteed reply time. A report with a log and steps to reproduce is much quicker to act on than one without.

Contribute

Pull requests welcome.

PRs go to Sn3akyy1/lucid. Merged work is credited by name in the changelog's Contributed section. v1.1.0 shipped a KDE Connect widget, a Sound page and installer fixes from the community.

Pull requests Open issues

House rules from the repo

  • Colours come from Theme roles, like Theme.accent, Theme.text and Theme.bg, never literals. That is what lets every palette and light mode work.
  • Radii and motion use the tokens: Theme.radiusSm through radiusLg, and durations durQuick, durShort, durMedium.
  • Features are scriptable through an IpcHandler with a clear target name.
  • Helper scripts print clean JSON to stdout and keep diagnostics on stderr.
  • Check the log after your change reloads. qs log catches what a linter misses.