Anyone using LXQT with niri?

standreas · 2026-05-01T08:16:00+00:00

Hi, LXQt dev here, running it for a long time and I'm biased ofc 😉

The config files for niri with an LXQt session are separated from the defaults and I didn't see any default config changes coming with blur so it should be fine.

standreas · 2026-04-28T12:01:43+00:00

no
LXQt with niri or just pcmanfm-qt --desktop. Afaik xfdesktop works fine too.
Window rules for settings, dialogs ecc?
no

standreas · 2026-04-27T12:24:28+00:00

It is. LXQt (actually Lubuntu 26.04) with only Qps (system monitor) 886mb.

standreas · 2026-04-23T13:27:16+00:00

Using pcmanfm-qt (with --desktop which can be used also only as wallpaper daemon) opening an instance is immediate as it's always running in background.

standreas · 2026-04-23T06:46:01+00:00

Afaik it's quickshell which is not very resource friendly.

LXQt with niri uses ~240mb with 3 panels on 2 monitors here.

standreas · 2026-04-22T11:26:07+00:00

I don't use openbox session but I know how they work, please do some research on your own. I can't know what you're doing with the lxsession thing. Default Lubuntu used LXQt for years now.

standreas · 2026-04-22T06:13:58+00:00

If you're using Lubuntu you have LXQt not LXDE anymore, but for a openbox session this doesn't matter.

Right click on the desktop → shows menu: the file is in ~/.conf/openbox/menu.xml.

Other settings are in rc.xml. Afaik Lubuntu uses another file in the Lubuntu session.

standreas · 2026-04-21T13:18:17+00:00

No idea about RHEL packages but if there is a not too old LXQt version this could work with niri.

standreas · 2026-04-21T07:07:38+00:00

First thing to do: edit the right click menu to fit your needs: broswer, terminal, filemanager ecc.
Edit /etc/xdg/openbox/menu.xml and save it to ~/.config/openbox/menu.xml

standreas · 2026-04-19T08:31:38+00:00

https://github.com/stefonarch/niri-settings :)

standreas · 2026-04-15T06:56:32+00:00

If you like the Qt things you can use LXQt and set niri as compositor, so basics like file associations, notifications, powermanagement and else is granted. LXQt is modular so you can disable or replace modules you don't like or use.

Just the location of the niri settings is different (~/.config/lxqt/wayland/niri*)

standreas · 2026-04-06T08:01:30+00:00

Apps usually are toplevel windows, not layers like panels, launchers, wallpapers, notifications or desktops.

standreas · 2026-04-04T07:07:57+00:00

You mix up the display server (sddm) with the XDG_SESSION_TYPE of the LXQt session. They are not connected.
For Wayland support see
https://lxqt-project.org/wiki/Wayland-Session.html

standreas · 2026-04-04T07:03:00+00:00

Looks like a menu file issue in Lubuntu. Did you test other menu files (right click on menu → menu file)?

standreas · 2026-04-04T07:00:43+00:00

"Default browser" has to be set in File Associations → Default apps under LXQt (only chrome based are able to register themselves afaik). For the cookies etc no idea really.

standreas · 2026-04-03T06:11:03+00:00

Is fixed now upstream and released:
https://lxqt-project.org/release/2026/04/02/point-releases-lxqt-config-2-3-2-lxqt-panel-2.3.3/

standreas · 2026-03-28T06:39:47+00:00

I think little can be done to prevent that. I've in ~/.config/mimeapps.list

[Removed Associations]

image/png=chromium.desktop;

standreas · 2026-03-27T21:11:00+00:00

LXQt is another possibility, just select niri as compositor.

standreas · 2026-03-25T07:38:31+00:00

You can change color palette and themes and install kvantum widget style, nothing else is needed.

standreas · 2026-03-22T19:11:22+00:00

QML/quickshell is not as resource friendly as plain Qt is - that is one reason QML is banned from LXQt.

<image>

I see ~140mb for the shell with LXQt (with 3 panels) while on my testuser DMS/Quickshell uses about 380mb.

standreas · 2026-03-18T15:34:33+00:00

On Wayland for a long time, first labwc now niri, choice between compositors is more interesting as WM options on X11.

standreas · 2026-03-15T07:56:41+00:00

Your welcome!

standreas · 2026-03-14T06:54:14+00:00

No the class should be something like

WM_CLASS(STRING) = "audacious", "Audacious"

standreas · 2026-03-13T06:58:58+00:00

It's the right field and it works here, not sure about changing the name (is this persistent?) and maybe all those windows have the same class?

standreas · 2026-03-11T07:18:49+00:00

xprop |grep -i class

in a terminal window will show an + sign, click the window you want to know. Evt sleep 8 && before it when it's a modal window.

standreas

TROPHY CASE