How to run (after make install)?

Open
#231 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ubuntu

Research direction

Start by reproducing the post-install behavior on Ubuntu plucky, checking whether liri-shell is available to lightdm and whether the referenced GLib schema is installed. Compare the liri-shell failure with the liri-notify command and verify that the shell launches successfully and can be started through lightdm.

Written by the indexing model from the issue text.

Description

It's not visible in my lightdm. The only related command that is available in my environment is liri-notify.
I also tried to run /usr/local/lib/x86_64-linux-gnu/libexec/liri-shell but got

(process:329179): GLib-GIO-ERROR **: 20:12:32.419: Settings schema 'io.liri.desktop.interface' is not installed
[1]    329179 trace trap (core dumped)  /usr/local/lib/x86_64-linux-gnu/libexec/liri-shell

I did run sudo glib-compile-schemas /usr/share/glib-2.0/schemas/ from https://github.com/lirios/shell/issues/63, but nothing changed.

Environment

Include as many relevant details about the environment you experienced the bug in.

  • Version used: git clone
  • Operating system and version: Ubuntu plucky (25.04 dev)
  • Device (phone, tablet, laptop, desktop, ...):
  • CPU, RAM, screen resolution:
Dominant language
C++
Stars
247
Forks
15
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from lirios/shell

All issues in lirios/shell

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.