# Niri & (Dank Material | noctalia | ... ) - General thread, questions, tips & tricks **URL:** \ **Category:** All WMs\ **Created:** [July 17, 2026, 6:28am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655 "2026-07-17T06:28:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\ **Post date:** [July 17, 2026, 6:28am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/1 "2026-07-17T06:28:55Z")
Up so far, there is only sparse information available in terms of Niri and the Dank Material Shell. I’m currently migrating to it, essentially only due to a video from @joekamprad which he posted here : > [@Share your WM setup!](https://forum.endeavouros.com/t/share-your-wm-setup/78974/55): > > [[Dang !] ](https://www.youtube.com/watch?v=c5DgTD4UX3E) very easy And I really have to admit - getting started with Niri and DMS hasn’t been that challenging. I’ve tried to get started with the NWGShell using SWAY before, but that was a pretty rough experience from my side with too many hurdles in the initial configuration. For those not knowing : Niri does follows an different paradigm, with an emphasis on scrolling tiles. I just wanted to kickstart a dedicated thread here, in which questions could be asked and also setups / plugins and general tips for Niri itself, as well as the available shells based upon it such as the DMS or other candidates such as noctalia. ---
**Author:** ![erne.d.98](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/erne.d.98/32/95777_2.png) [@erne.d.98](https://forum.endeavouros.com/u/erne.d.98)\ **Post date:** [July 17, 2026, 8:15am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/2 "2026-07-17T08:15:52Z")
Niri is my preferred compositor. I’ve been using it for a month already and haven’t had an issue with it. I had experience with both most-known desktop shells and self-assembled desktop (waybar+rofi+dunst+swaylock). It turned out while Waybar’n’Stuff make the experience kinda old-fashioned, traditional WM way and DMS transforms Niri into (almost) full desktop environment, Noctalia is a sweet middle-ground. I’ve been using Noctalia v5 for already some time. Ditching Quickshell has been surprisingly good, shell is much lighter on resources, it is fairly stable and doesn’t change much of a workflow. ---
**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\ **Post date:** [July 17, 2026, 9:12am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/3 "2026-07-17T09:12:01Z")
+1 Noctalia, but on MangoWM here. NWG was too gnomeish for me 😃 ---
**Author:** ![ibarona](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/i/e0b2c6/32.png) [@ibarona](https://forum.endeavouros.com/u/ibarona)\ **Post date:** [July 17, 2026, 1:00pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/5 "2026-07-17T13:00:09Z")
Hi! I am using Noctalia V5 and I think it’s superb! It’s still in beta stage but can be daily driven without problems. Regards, Isaac ---
**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\ **Post date:** [July 17, 2026, 5:23pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/6 "2026-07-17T17:23:26Z")
Nice to see some replies, therefore there must be some interest 😉 Anyway, I’m on DMS 1.5 and I’ve spend some effort to recreate my design of a 3 column layout that consists of 2 static floating columns on the left (2 rows) and the right (3 rows), with a part in the middle that is almost 1800 px wide. As I’m using an ultra wide monitor in 3440x1440px resolution, that’s quite convenient and the scrolling behavior of the windows in the middle column (e.g. browser, mail client or other applications) work like a charm. The only issue is currently that some of the default keybinds are based upon english ISO keyboard layouts and certain key combinations are simply not feasible. That could be addressed by myself via software or by switching to an ISO keyboard. Nevertheless, simply by calling `dms ipc call keybinds toggle niri` the current declared key combinations (within the ~/.config/niri/dms/binds.kdl) would be displayed immediately in an overlay. And that’s quite handy at the moment. But a total of 135 keybinds might be overwhelming for some. ![Screenshot from 2026-07-17 19-17-06](https://forum.endeavouros.com/uploads/default/original/3X/9/b/9bc09b6b3d75ceea1e1b2ea96d0d54a053206fa5.jpeg) ---
**Author:** ![kagetora13](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/kagetora13/32/137235_2.png) [@kagetora13](https://forum.endeavouros.com/u/kagetora13)\ **Post date:** [July 17, 2026, 5:52pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/7 "2026-07-17T17:52:51Z")
I’m running Gnome and Niri on the same laptop as of 1 month ago. So working on my keybindings and learning the configuration file. I started with Noctalia V4 and transition to V5 which works great with Niri, and one weird bug with Hypraland. At the moment the little bit of grief are the way monitors are handled (e.g. I log out of Niri with computer docked and it suspends. It behaves as if it does not realize the external monitor has power). If I define my monitors in Niri, some games in Steams buttons do not line up (e.g. World of Tanks Blitz). So I commented out my monitors and let it auto detect. **Bugs I am monitoring:** > > > When log out action is executed (Thinkpad T450, Lenovo dock, external monitor at…tached and laptop screen closed) the laptop will suspend. When I press the power button on the docking station the laptop wakes up showing the GDM login screen. > > When the laptop is stand alone, you can log out and you are sent to the login screen (GDM). This is the expected outcome. > > I did try disabling Noctalia (tested with V4 and V5) and the outcome does not change. > > I can log out of Gnome 50 (stand alone or on dock) and I am returned to GDM. > > > > \*\*Steps to Reproduce:\*\* > > 1. Cold boot laptop on dock. > 2. Reach GDM. Sign into Niri. > 3. Log out of Niri \/ > > \*\*Expected Result:\*\* > > \- Return to GDM Login Manager. > > \*\*Actual Result\*\* > > \- The computer suspends. Must be woken up with power button. When computer wakes up you will see GDM login screen. > > \\Config\ > > \*\*kdl config file:\*\* > \`\`\` > // This config is in the KDL format: https://kdl.dev > // "/-" comments out the following node. > // Check the wiki for a full description of the configuration: > // https://niri-wm.github.io/niri/Configuration:-Introduction > > // Input device configuration. > // Find the full list of options on the wiki: > // https://niri-wm.github.io/niri/Configuration:-Input > input { > keyboard { > xkb { > // You can set rules, model, layout, variant and options. > // For more information, see xkeyboard-config(7). > > // For example: > // layout "us,ru" > // options "grp:win\_space\_toggle,compose:ralt,ctrl:nocaps" > > // If this section is empty, niri will fetch xkb settings > // from org.freedesktop.locale1. You can control these using > // localectl set-x11-keymap. > } > > // Enable numlock on startup, omitting this setting disables it. > numlock > } > > // Next sections include libinput settings. > // Omitting settings disables them, or leaves them at their default values. > // All commented-out settings here are examples, not defaults. > touchpad { > // off > tap > // dwt > // dwtp > // drag false > // drag-lock > natural-scroll > accel-speed 0.2 > // accel-profile "flat" > scroll-method "two-finger" > // disabled-on-external-mouse > } > > mouse { > // off > // natural-scroll > // accel-speed 0.2 > // accel-profile "flat" > // scroll-method "no-scroll" > } > > trackpoint { > // off > // natural-scroll > // accel-speed 0.2 > // accel-profile "flat" > // scroll-method "on-button-down" > // scroll-button 273 > // scroll-button-lock > // middle-emulation > } > > // Uncomment this to make the mouse warp to the center of newly focused windows. > // warp-mouse-to-focus > > // Focus windows and outputs automatically when moving the mouse into them. > // Setting max-scroll-amount="0%" makes it work only on windows already fully on screen. > // focus-follows-mouse max-scroll-amount="0%" > } > > // You can configure outputs by their name, which you can find > // by running \`niri msg outputs\` while inside a niri instance. > // The built-in laptop monitor is usually called "eDP-1". > // Find more information on the wiki: > // https://niri-wm.github.io/niri/Configuration:-Outputs > // Remember to uncomment the node by removing "/-"! > output "eDP-1" { > // Uncomment this line to disable this output. > // off > > // Resolution and, optionally, refresh rate of the output. > // The format is "\x\" or "\x\@\". > // If the refresh rate is omitted, niri will pick the highest refresh rate > // for the resolution. > // If the mode is omitted altogether or is invalid, niri will pick one automatically. > // Run \`niri msg outputs\` while inside a niri instance to list all outputs and their modes. > // mode "1920x1080@120.030" > mode "1920x1080@60.020" > > // You can use integer or fractional scale, for example use 1.5 for 150% scale. > scale 1.1 > > // Transform allows to rotate the output counter-clockwise, valid values are: > // normal, 90, 180, 270, flipped, flipped-90, flipped-180 and flipped-270. > transform "normal" > > // Position of the output in the global coordinate space. > // This affects directional monitor actions like "focus-monitor-left", and cursor movement. > // The cursor can only move between directly adjacent outputs. > // Output scale and rotation has to be taken into account for positioning: > // outputs are sized in logical, or scaled, pixels. > // For example, a 3840×2160 output with scale 2.0 will have a logical size of 1920×1080, > // so to put another output directly adjacent to it on the right, set its x to 1920. > // If the position is unset or results in an overlap, the output is instead placed > // automatically. > position x=1280 y=0 > } > > // Settings that influence how windows are positioned and sized. > // Find more information on the wiki: > // https://niri-wm.github.io/niri/Configuration:-Layout > layout { > // Set gaps around windows in logical pixels. > gaps 3 > > // When to center a column when changing focus, options are: > // - "never", default behavior, focusing an off-screen column will keep at the left > // or right edge of the screen. > // - "always", the focused column will always be centered. > // - "on-overflow", focusing a column will center it if it doesn't fit > // together with the previously focused column. > center-focused-column "never" > > // You can customize the widths that "switch-preset-column-width" (Mod+R) toggles between. > preset-column-widths { > // Proportion sets the width as a fraction of the output width, taking gaps into account. > // For example, you can perfectly fit four windows sized "proportion 0.25" on an output. > // The default preset widths are 1/3, 1/2 and 2/3 of the output. > proportion 0.33333 > proportion 0.5 > proportion 0.66667 > > // Fixed sets the width in logical pixels exactly. > // fixed 1920 > } > > // You can also customize the heights that "switch-preset-window-height" (Mod+Ctrl+Shift+R) toggles between. > // preset-window-heights { } > > // You can change the default width of the new windows. > default-column-width { proportion 0.5; } > // If you leave the brackets empty, the windows themselves will decide their initial width. > // default-column-width {} > > // By default focus ring and border are rendered as a solid background rectangle > // behind windows. That is, they will show up through semitransparent windows. > // This is because windows using client-side decorations can have an arbitrary shape. > // > // If you don't like that, you should uncomment \`prefer-no-csd\` below. > // Niri will draw focus ring and border \*around\* windows that agree to omit their > // client-side decorations. > // > // Alternatively, you can override it with a window rule called > // \`draw-border-with-background\`. > > // You can change how the focus ring looks. > focus-ring { > // Uncomment this line to disable the focus ring. > // off > > // How many logical pixels the ring extends out from the windows. > width 2 > > // Colors can be set in a variety of ways: > // - CSS named colors: "red" > // - RGB hex: "#rgb", "#rgba", "#rrggbb", "#rrggbbaa" > // - CSS-like notation: "rgb(255, 127, 0)", rgba(), hsl() and a few others. > > // Color of the ring on the active monitor. > active-color "#7fc8ff" > > // Color of the ring on inactive monitors. > // > // The focus ring only draws around the active window, so the only place > // where you can see its inactive-color is on other monitors. > inactive-color "#505050" > > // You can also use gradients. They take precedence over solid colors. > // Gradients are rendered the same as CSS linear-gradient(angle, from, to). > // The angle is the same as in linear-gradient, and is optional, > // defaulting to 180 (top-to-bottom gradient). > // You can use any CSS linear-gradient tool on the web to set these up. > // Changing the color space is also supported, check the wiki for more info. > // > // active-gradient from="#80c8ff" to="#c7ff7f" angle=45 > > // You can also color the gradient relative to the entire view > // of the workspace, rather than relative to just the window itself. > // To do that, set relative-to="workspace-view". > // > // inactive-gradient from="#505050" to="#808080" angle=45 relative-to="workspace-view" > } > > // You can also add a border. It's similar to the focus ring, but always visible. > border { > // The settings are the same as for the focus ring. > // If you enable the border, you probably want to disable the focus ring. > off > > width 4 > active-color "#ffc87f" > inactive-color "#505050" > > // Color of the border around windows that request your attention. > urgent-color "#9b0000" > > // Gradients can use a few different interpolation color spaces. > // For example, this is a pastel rainbow gradient via in="oklch longer hue". > // > // active-gradient from="#e5989b" to="#ffb4a2" angle=45 relative-to="workspace-view" in="oklch longer hue" > > // inactive-gradient from="#505050" to="#808080" angle=45 relative-to="workspace-view" > } > > // You can enable drop shadows for windows. > shadow { > // Uncomment the next line to enable shadows. > // on > > // By default, the shadow draws only around its window, and not behind it. > // Uncomment this setting to make the shadow draw behind its window. > // > // Note that niri has no way of knowing about the CSD window corner > // radius. It has to assume that windows have square corners, leading to > // shadow artifacts inside the CSD rounded corners. This setting fixes > // those artifacts. > // > // However, instead you may want to set prefer-no-csd and/or > // geometry-corner-radius. Then, niri will know the corner radius and > // draw the shadow correctly, without having to draw it behind the > // window. These will also remove client-side shadows if the window > // draws any. > // > // draw-behind-window true > > // You can change how shadows look. The values below are in logical > // pixels and match the CSS box-shadow properties. > > // Softness controls the shadow blur radius. > softness 30 > > // Spread expands the shadow. > spread 5 > > // Offset moves the shadow relative to the window. > offset x=0 y=5 > > // You can also change the shadow color and opacity. > color "#0007" > } > > // Struts shrink the area occupied by windows, similarly to layer-shell panels. > // You can think of them as a kind of outer gaps. They are set in logical pixels. > // Left and right struts will cause the next window to the side to always be visible. > // Top and bottom struts will simply add outer gaps in addition to the area occupied by > // layer-shell panels and regular gaps. > struts { > // left 64 > // right 64 > // top 64 > // bottom 64 > } > } > > // Add lines like this to spawn processes at startup. > // Note that running niri as a session supports xdg-desktop-autostart, > // which may be more convenient to use. > // See the binds section below for more spawn examples. > > // This line starts waybar, a commonly used bar for Wayland compositors. > // spawn-at-startup "waybar" > > // To run a shell command (with variables, pipes, etc.), use spawn-sh-at-startup: > // spawn-sh-at-startup "qs -c ~/source/qs/MyAwesomeShell" > > hotkey-overlay { > // Uncomment this line to disable the "Important Hotkeys" pop-up at startup. > skip-at-startup > } > > // Uncomment this line to ask the clients to omit their client-side decorations if possible. > // If the client will specifically ask for CSD, the request will be honored. > // Additionally, clients will be informed that they are tiled, removing some client-side rounded corners. > // This option will also fix border/focus ring drawing behind some semitransparent windows. > // After enabling or disabling this, you need to restart the apps for this to take effect. > // prefer-no-csd > > // You can change the path where screenshots are saved. > // A ~ at the front will be expanded to the home directory. > // The path is formatted with strftime(3) to give you the screenshot date and time. > screenshot-path "~/Pictures/Screenshots/Screenshot from %Y-%m-%d %H-%M-%S.png" > > // You can also set this to null to disable saving screenshots to disk. > // screenshot-path null > > // Animation settings. > // The wiki explains how to configure individual animations: > // https://niri-wm.github.io/niri/Configuration:-Animations > animations { > // Uncomment to turn off all animations. > // off > > // Slow down all animations by this factor. Values below 1 speed them up instead. > // slowdown 3.0 > } > > // Window rules let you adjust behavior for individual windows. > // Find more information on the wiki: > // https://niri-wm.github.io/niri/Configuration:-Window-Rules > > // Work around WezTerm's initial configure bug > // by setting an empty default-column-width. > window-rule { > // This regular expression is intentionally made as specific as possible, > // since this is the default config, and we want no false positives. > // You can get away with just app-id="wezterm" if you want. > match app-id=r#"^org\\.wezfurlong\\.wezterm$"# > default-column-width {} > } > > // Open the Firefox picture-in-picture player as floating by default. > window-rule { > // This app-id regular expression will work for both: > // - host Firefox (app-id is "firefox") > // - Flatpak Firefox (app-id is "org.mozilla.firefox") > match app-id=r#"firefox$"# title="^Picture-in-Picture$" > open-floating true > } > > // Example: block out two password managers from screen capture. > // (This example rule is commented out with a "/-" in front.) > window-rule { > match app-id=r#"^org\\.keepassxc\\.KeePassXC$"# > match app-id=r#"^org\\.gnome\\.World\\.Secrets$"# > > block-out-from "screen-capture" > > // Use this instead if you want them visible on third-party screenshot tools. > // block-out-from "screencast" > } > > // Example: enable rounded corners for all windows. > // (This example rule is commented out with a "/-" in front.) > > window-rule { > // Rounded corners for a modern look. > geometry-corner-radius 10 > > // Clips window contents to the rounded corner boundaries. > clip-to-geometry true > } > > // Floating Noctalia settings window. > window-rule { > match app-id="dev.noctalia.Noctalia.Settings" > open-floating true > default-column-width { fixed 1080; } > default-window-height { fixed 920; } > } > > debug { > // Allows notification actions and window activation from Noctalia. > honor-xdg-activation-with-invalid-serial > } > > binds { > // Keys consist of modifiers separated by + signs, followed by an XKB key name > // in the end. To find an XKB name for a particular key, you may use a program > // like wev. > // > // "Mod" is a special modifier equal to Super when running on a TTY, and to Alt > // when running as a winit window. > // > // Most actions that you can bind here can also be invoked programmatically with > // \`niri msg action do-something\`. > > // Mod-Shift-/, which is usually the same as Mod-?, > // shows a list of important hotkeys. > Mod+Shift+Slash { show-hotkey-overlay; } > > // Suggested binds for running programs: terminal, app launcher, screen locker. > Mod+T hotkey-overlay-title="Open a Terminal: alacritty" { spawn "alacritty"; } > // Mod+D hotkey-overlay-title="Run an Application: fuzzel" { spawn "fuzzel"; } > // Super+Alt+L hotkey-overlay-title="Lock the Screen: swaylock" { spawn "swaylock"; } > > // Core Noctalia binds > Mod+Space { spawn-sh "noctalia msg panel-toggle launcher"; } > // Mod+Comma { spawn-sh "noctalia msg panel-toggle control-center"; } > Mod+S { spawn-sh "noctalia msg settings-toggle"; } > > // Use spawn-sh to run a shell command. Do this if you need pipes, multiple commands, etc. > // Note: the entire command goes as a single argument. It's passed verbatim to \`sh -c\`. > // For example, this is a standard bind to toggle the screen reader (orca). > // Super+Alt+S allow-when-locked=true hotkey-overlay-title=null { spawn-sh "pkill orca || exec orca"; } > > // Audio & Brightness > XF86AudioRaiseVolume { spawn-sh "noctalia msg volume-up"; } > XF86AudioLowerVolume { spawn-sh "noctalia msg volume-down"; } > XF86AudioMute { spawn-sh "noctalia msg volume-mute"; } > XF86MonBrightnessUp { spawn-sh "noctalia msg brightness-up"; } > XF86MonBrightnessDown { spawn-sh "noctalia msg brightness-down"; } > > // Example volume keys mappings for PipeWire & WirePlumber. > // The allow-when-locked=true property makes them work even when the session is locked. > // Using spawn-sh allows to pass multiple arguments together with the command. > // "-l 1.0" limits the volume to 100%. > // XF86AudioRaiseVolume allow-when-locked=true { spawn-sh "wpctl set-volume @DEFAULT\_AUDIO\_SINK@ 0.1+ -l 1.0"; } > // XF86AudioLowerVolume allow-when-locked=true { spawn-sh "wpctl set-volume @DEFAULT\_AUDIO\_SINK@ 0.1-"; } > // XF86AudioMute allow-when-locked=true { spawn-sh "wpctl set-mute @DEFAULT\_AUDIO\_SINK@ toggle"; } > XF86AudioMicMute allow-when-locked=true { spawn-sh "wpctl set-mute @DEFAULT\_AUDIO\_SOURCE@ toggle"; } > > // Example media keys mapping using playerctl. > // This will work with any MPRIS-enabled media player. > XF86AudioPlay allow-when-locked=true { spawn-sh "playerctl play-pause"; } > XF86AudioStop allow-when-locked=true { spawn-sh "playerctl stop"; } > XF86AudioPrev allow-when-locked=true { spawn-sh "playerctl previous"; } > XF86AudioNext allow-when-locked=true { spawn-sh "playerctl next"; } > > // Example brightness key mappings for brightnessctl. > // You can use regular spawn with multiple arguments too (to avoid going through "sh"), > // but you need to manually put each argument in separate "" quotes. > // XF86MonBrightnessUp allow-when-locked=true { spawn "brightnessctl" "--class=backlight" "set" "+10%"; } > // XF86MonBrightnessDown allow-when-locked=true { spawn "brightnessctl" "--class=backlight" "set" "10%-"; } > > // Open/close the Overview: a zoomed-out view of workspaces and windows. > // You can also move the mouse into the top-left hot corner, > // or do a four-finger swipe up on a touchpad. > Mod+O repeat=false { toggle-overview; } > > Mod+Q repeat=false { close-window; } > > Mod+Left { focus-column-left; } > Mod+Down { focus-window-down; } > Mod+Up { focus-window-up; } > Mod+Right { focus-column-right; } > // Mod+H { focus-column-left; } > // Mod+J { focus-window-down; } > // Mod+K { focus-window-up; } > // Mod+L { focus-column-right; } > > Mod+Ctrl+Left { move-column-left; } > Mod+Ctrl+Down { move-window-down; } > Mod+Ctrl+Up { move-window-up; } > Mod+Ctrl+Right { move-column-right; } > // Mod+Ctrl+H { move-column-left; } > // Mod+Ctrl+J { move-window-down; } > // Mod+Ctrl+K { move-window-up; } > // Mod+Ctrl+L { move-column-right; } > > // Alternative commands that move across workspaces when reaching > // the first or last window in a column. > // Mod+J { focus-window-or-workspace-down; } > // Mod+K { focus-window-or-workspace-up; } > // Mod+Ctrl+J { move-window-down-or-to-workspace-down; } > // Mod+Ctrl+K { move-window-up-or-to-workspace-up; } > > Mod+Home { focus-column-first; } > Mod+End { focus-column-last; } > Mod+Ctrl+Home { move-column-to-first; } > Mod+Ctrl+End { move-column-to-last; } > > Mod+Shift+Left { focus-monitor-left; } > Mod+Shift+Down { focus-monitor-down; } > Mod+Shift+Up { focus-monitor-up; } > Mod+Shift+Right { focus-monitor-right; } > // Mod+Shift+H { focus-monitor-left; } > // Mod+Shift+J { focus-monitor-down; } > // Mod+Shift+K { focus-monitor-up; } > // Mod+Shift+L { focus-monitor-right; } > > Mod+Shift+Ctrl+Left { move-column-to-monitor-left; } > Mod+Shift+Ctrl+Down { move-column-to-monitor-down; } > Mod+Shift+Ctrl+Up { move-column-to-monitor-up; } > Mod+Shift+Ctrl+Right { move-column-to-monitor-right; } > // Mod+Shift+Ctrl+H { move-column-to-monitor-left; } > // Mod+Shift+Ctrl+J { move-column-to-monitor-down; } > // Mod+Shift+Ctrl+K { move-column-to-monitor-up; } > // Mod+Shift+Ctrl+L { move-column-to-monitor-right; } > > // Alternatively, there are commands to move just a single window: > // Mod+Shift+Ctrl+Left { move-window-to-monitor-left; } > // ... > > // And you can also move a whole workspace to another monitor: > // Mod+Shift+Ctrl+Left { move-workspace-to-monitor-left; } > // ... > > Mod+Page\_Down { focus-workspace-down; } > Mod+Page\_Up { focus-workspace-up; } > // Mod+U { focus-workspace-down; } > // Mod+I { focus-workspace-up; } > Mod+Ctrl+Page\_Down { move-column-to-workspace-down; } > Mod+Ctrl+Page\_Up { move-column-to-workspace-up; } > // Mod+Ctrl+U { move-column-to-workspace-down; } > // Mod+Ctrl+I { move-column-to-workspace-up; } > > // Alternatively, there are commands to move just a single window: > // Mod+Ctrl+Page\_Down { move-window-to-workspace-down; } > // ... > > Mod+Shift+Page\_Down { move-workspace-down; } > Mod+Shift+Page\_Up { move-workspace-up; } > // Mod+Shift+U { move-workspace-down; } > // Mod+Shift+I { move-workspace-up; } > > // You can bind mouse wheel scroll ticks using the following syntax. > // These binds will change direction based on the natural-scroll setting. > // > // To avoid scrolling through workspaces really fast, you can use > // the cooldown-ms property. The bind will be rate-limited to this value. > // You can set a cooldown on any bind, but it's most useful for the wheel. > Mod+WheelScrollDown cooldown-ms=150 { focus-workspace-down; } > Mod+WheelScrollUp cooldown-ms=150 { focus-workspace-up; } > Mod+Ctrl+WheelScrollDown cooldown-ms=150 { move-column-to-workspace-down; } > Mod+Ctrl+WheelScrollUp cooldown-ms=150 { move-column-to-workspace-up; } > > Mod+WheelScrollRight { focus-column-right; } > Mod+WheelScrollLeft { focus-column-left; } > Mod+Ctrl+WheelScrollRight { move-column-right; } > Mod+Ctrl+WheelScrollLeft { move-column-left; } > > // Usually scrolling up and down with Shift in applications results in > // horizontal scrolling; these binds replicate that. > Mod+Shift+WheelScrollDown { focus-column-right; } > Mod+Shift+WheelScrollUp { focus-column-left; } > Mod+Ctrl+Shift+WheelScrollDown { move-column-right; } > Mod+Ctrl+Shift+WheelScrollUp { move-column-left; } > > // Similarly, you can bind touchpad scroll "ticks". > // Touchpad scrolling is continuous, so for these binds it is split into > // discrete intervals. > // These binds are also affected by touchpad's natural-scroll, so these > // example binds are "inverted", since we have natural-scroll enabled for > // touchpads by default. > // Mod+TouchpadScrollDown { spawn-sh "wpctl set-volume @DEFAULT\_AUDIO\_SINK@ 0.02+"; } > // Mod+TouchpadScrollUp { spawn-sh "wpctl set-volume @DEFAULT\_AUDIO\_SINK@ 0.02-"; } > > // You can refer to workspaces by index. However, keep in mind that > // niri is a dynamic workspace system, so these commands are kind of > // "best effort". Trying to refer to a workspace index bigger than > // the current workspace count will instead refer to the bottommost > // (empty) workspace. > // > // For example, with 2 workspaces + 1 empty, indices 3, 4, 5 and so on > // will all refer to the 3rd workspace. > Mod+1 { focus-workspace 1; } > Mod+2 { focus-workspace 2; } > Mod+3 { focus-workspace 3; } > Mod+4 { focus-workspace 4; } > Mod+5 { focus-workspace 5; } > Mod+6 { focus-workspace 6; } > Mod+7 { focus-workspace 7; } > Mod+8 { focus-workspace 8; } > Mod+9 { focus-workspace 9; } > Mod+Ctrl+1 { move-column-to-workspace 1; } > Mod+Ctrl+2 { move-column-to-workspace 2; } > Mod+Ctrl+3 { move-column-to-workspace 3; } > Mod+Ctrl+4 { move-column-to-workspace 4; } > Mod+Ctrl+5 { move-column-to-workspace 5; } > Mod+Ctrl+6 { move-column-to-workspace 6; } > Mod+Ctrl+7 { move-column-to-workspace 7; } > Mod+Ctrl+8 { move-column-to-workspace 8; } > Mod+Ctrl+9 { move-column-to-workspace 9; } > > // Alternatively, there are commands to move just a single window: > // Mod+Ctrl+1 { move-window-to-workspace 1; } > > // Switches focus between the current and the previous workspace. > // Mod+Tab { focus-workspace-previous; } > > // The following binds move the focused window in and out of a column. > // If the window is alone, they will consume it into the nearby column to the side. > // If the window is already in a column, they will expel it out. > Mod+BracketLeft { consume-or-expel-window-left; } > Mod+BracketRight { consume-or-expel-window-right; } > > // Consume one window from the right to the bottom of the focused column. > Mod+Comma { consume-window-into-column; } > // Expel the bottom window from the focused column to the right. > Mod+Period { expel-window-from-column; } > > // Cycle through widths set in preset-column-widths. > Mod+R { switch-preset-column-width; } > // Cycling through the presets in reverse order is also possible. > Mod+Shift+R { switch-preset-column-width-back; } > > Mod+Ctrl+Shift+R { switch-preset-window-height; } > Mod+Ctrl+R { reset-window-height; } > > Mod+F { maximize-column; } > Mod+Shift+F { fullscreen-window; } > > // While maximize-column leaves gaps and borders around the window, > // maximize-window-to-edges doesn't: the window expands to the edges of the screen. > // This bind corresponds to normal window maximizing, > // e.g. by double-clicking on the titlebar. > Mod+M { maximize-window-to-edges; } > > // Expand the focused column to space not taken up by other fully visible columns. > // Makes the column "fill the rest of the space". > Mod+Ctrl+F { expand-column-to-available-width; } > > Mod+C { center-column; } > > // Center all fully visible columns on screen. > Mod+Ctrl+C { center-visible-columns; } > > // Finer width adjustments. > // This command can also: > // \* set width in pixels: "1000" > // \* adjust width in pixels: "-5" or "+5" > // \* set width as a percentage of screen width: "25%" > // \* adjust width as a percentage of screen width: "-10%" or "+10%" > // Pixel sizes use logical, or scaled, pixels. I.e. on an output with scale 2.0, > // set-column-width "100" will make the column occupy 200 physical screen pixels. > Mod+Minus { set-column-width "-10%"; } > Mod+Equal { set-column-width "+10%"; } > > // Finer height adjustments when in column with other windows. > Mod+Shift+Minus { set-window-height "-10%"; } > Mod+Shift+Equal { set-window-height "+10%"; } > > // Move the focused window between the floating and the tiling layout. > Mod+V { toggle-window-floating; } > Mod+Shift+V { switch-focus-between-floating-and-tiling; } > > // Toggle tabbed column display mode. > // Windows in this column will appear as vertical tabs, > // rather than stacked on top of each other. > Mod+W { toggle-column-tabbed-display; } > > // Actions to switch layouts. > // Note: if you uncomment these, make sure you do NOT have > // a matching layout switch hotkey configured in xkb options above. > // Having both at once on the same hotkey will break the switching, > // since it will switch twice upon pressing the hotkey (once by xkb, once by niri). > // Mod+Space { switch-layout "next"; } > // Mod+Shift+Space { switch-layout "prev"; } > > Print { screenshot; } > Ctrl+Print { screenshot-screen; } > Alt+Print { screenshot-window; } > > // Applications such as remote-desktop clients and softwNiri configuration file \`~/.config/niri/config.kdl\` are KVM switches may > // request that niri stops processing the keyboard shortcuts defined here > // so they may, for example, forward the key presses as-is to a remote machine. > // It's a good idea to bind an escape hatch to toggle the inhibitor, > // so a buggy application can't hold your session hostage. > // > // The allow-inhibiting=false property can be applied to other binds as well, > // which ensures niri always processes them, even when an inhibitor is active. > Mod+Escape allow-inhibiting=false { toggle-keyboard-shortcuts-inhibit; } > > // The quit action will show a confirmation dialog to avoid accidental exits. > Mod+Shift+E { quit; } > Ctrl+Alt+Delete { quit; } > > // Powers off the monitors. To turn them back on, do any input like > // moving the mouse or pressing any other key. > Mod+Shift+P { power-off-monitors; } > } > environment { > // This tells XDG portals to look for Niri-specific settings > "XDG\_CURRENT\_DESKTOP" "niri" > QT\_QPA\_PLATFORMTHEME "gtk3" > } > > //Launch Noctalia Shell > spawn-at-startup "noctalia" > > \`\`\` > > > \### System Information > > ❯ niri --version > niri 26.04 (8ed0da4) > > \* Distro: > > ❯ inxi -b > System: > Kernel: 7.0.14-zen1-1-zen arch: x86\_64 bits: 64 > > Desktop: niri v: N/A Distro: EndeavourOS > > Machine: > Type: Laptop System: LENOVO product: 20BV0064US v: ThinkPad T450 > LENOVO > v: JBET73WW (1.37 ) date: 08/14/2019 > Battery: > ID-1: BAT0 charge: 17.5 Wh (89.3%) condition: 19.6/23.2 Wh (84.4%) > > CPU: > Info: dual core Intel Core i5-5300U \[MT MCP\] speed (MHz): avg: 1491 > min/max: 500/2900 > > Graphics: > Device-1: Intel Broadwell-U GT2 \[HD Graphics 5500\] driver: i915 v: kernel > Device-2: Chicony Integrated Camera driver: uvcvideo type: USB > Display: wayland server: X.org v: 1.21.1.23 with: Xwayland v: 24.1.12 > compositor: niri driver: X: loaded: modesetting unloaded: fbdev,vesa > dri: iris gpu: i915 resolution: 1920x1200~60Hz > API: Vulkan v: 1.4.350 drivers: intel surfaces: N/A > API: EGL Message: EGL data requires eglinfo. Check --recommends. > Info: Tools: api: vulkaninfo x11: xprop,xrandr > Network: > Device-1: Intel Ethernet I218-LM driver: e1000e > Device-2: Intel Wireless 7265 driver: iwlwifi > Drives: > Local Storage: total: 465.76 GiB used: 247.48 GiB (53.1%) > Info: > Memory: total: 16 GiB available: 15.49 GiB used: 3.17 GiB (20.5%) > Processes: 195 Uptime: 7h 32m Shell: Zsh inxi: 3.3.40 > > > \### Submission checklist > > \- \[x\] I have searched existing issues and confirmed th…is is not a duplicate. > \- \[x\] I am using the latest available version of Noctalia. > > \### Bug description > > After logging into Noctalia V5 on Hyprland V 0.55 I notice I can start an item (e.g. Alacritty Terminal) from the Dock and I see the indicator on the dock light up that it is launched, but it does not show on the display. I will have to right click on the Alacritty icon to close it and re-launch it from the Dock to get the terminal window. > > If I repeat the test from a new login, but instead of using Dock I press \ to launch the Alacritty terminal it will launch right away. > > This issue is not re-producible when I use niri 26.04 (8ed0da4) + Noctalia v5. > > \### Steps to reproduce > > 1. Boot into Arch Linux and get to GDM boot manager. > 2. Select Hyprland and login. > 3. Click on Alacritty (or any other program on the Dock). > 4. Alacritty shows an indicator under the icon that it has launched. > > \### Expected behavior > > 5. Alacritty should show on the monitor/lcd > > Laptop display closed. > External display on. > Display is not defined in the hyprland.lua file. > > \### Actual behavior > > 5. Alacritty does not show on the monitor/lcd (even though the Alacritty icon launch indicator is lit) > 6. Close Alacritty with right \. > 7. Launch Alacritty a 2nd time from Dock and it shows on the display now. > > \*Note: After login, you can use hotkey \ and Alacritty will launch the first time. > > \### Logs / error output > > \`\`\`text > \- No errors found in the journals after re-producing the issue. > \`\`\` > > \### Noctalia version > > v5.0.0 (547ff8405682) > > \### Compositor > > Hyprland > > \### Distribution > > Arch-based > > \### Environment information > > \`\`\`text > arch: x86\_64 > Kernel: 7.1.3-zen1-3-zen > Distro: EndeavourOS > > Machine: > ThinkPad T450 > > CPU: > Info: dual core Intel Core i5-5300U \[MT MCP\] speed (MHz): avg: 1900 > min/max: 500/2900 > > Graphics: > Device-1: Intel Broadwell-U GT2 \[HD Graphics 5500\] driver: i915 v: kernel > Device-2: Chicony Integrated Camera driver: uvcvideo type: USB > Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13 > compositor: Hyprland v: 0.55.4 driver: X: loaded: modesetting > unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 1920x1200~60Hz > 2: 1280x720~60Hz > API: Vulkan v: 1.4.350 drivers: intel surfaces: N/A > API: EGL Message: EGL data requires eglinfo. Check --recommends. > Info: Tools: api: vulkaninfo x11: xprop,xrandr > > Network: > Device-1: Intel Ethernet I218-LM driver: e1000e > Device-2: Intel Wireless 7265 driver: iwlwifi > > Drives: > Local Storage: total: 465.76 GiB used: 246.13 GiB (52.8%) > > Info: > Memory: total: 16 GiB available: 15.49 GiB used: 2.88 GiB (18.6%) > Processes: 167 Uptime: 2h 43m Shell: Zsh inxi: 3.3.41 > > noctalia v5.0.0 (547ff8405682) > Hyprland 0.55.4 built from branch v0.55.4 at commit a0136d8c04687bb36eb8a28eb9d1ff92aea99704 clean (\[gha\] Nix: update inputs). > Date: Thu Jun 11 17:10:04 2026 > Tag: v0.55.4, commits: 7378 > > Libraries: > Hyprgraphics: built against 0.5.1, system has 0.5.1 > Hyprutils: built against 0.13.1, system has 0.13.1 > Hyprcursor: built against 0.1.13, system has 0.1.13 > Hyprlang: built against 0.6.8, system has 0.6.8 > Aquamarine: built against 0.12.0, system has 0.12.1 > > Version ABI string: a0136d8c04687bb36eb8a28eb9d1ff92aea99704\_aq\_0.12\_hu\_0.13\_hg\_0.5\_hc\_0.1\_hlg\_0.6 > no flags were set > \`\`\` > > \### Additional context > > \_No response\_ ---
**Author:** ![AlchemistCrafted](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/f6c823/32.png) [@AlchemistCrafted](https://forum.endeavouros.com/u/AlchemistCrafted)\ **Post date:** [July 24, 2026, 7:41am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/8 "2026-07-24T07:41:34Z")
Tip:- Niri + DMS When you press Win+Shift+N opens a notepad on the right side of the screen. You custom config to expand it with your keyboard shortcut. Handy & Functional 🙂 Notepad window stays top on other windows. You can use it also as a standalone notes app Search DNS Notes in Spotlight bar. You can get it ✌ Found from this yt vid [![](https://img.youtube.com/vi/NE_TZ4-OQEI/maxresdefault.jpg "Niri & DMS: Ein schöner, minimalistischer Linux-Desktop") ](https://www.youtube.com/watch?v=NE_TZ4-OQEI&t=329) Regards, Alchemist Crafted. ---
**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\ **Post date:** [July 25, 2026, 7:39am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/9 "2026-07-25T07:39:16Z")
Just a small tip, instead of the regular keybind to show the hotkeys, which is just a selection of commonly used keybinds, at least in the case of DMS you could change or add a new keybind that would execute `dms ipc call keybinds toggle niri` which shows a comprehensive list of all keybinds in a new dialog window that would include a search function as well. And this list is based upon the actual keybinds that are specified on the system on the configuration level. ![image](https://forum.endeavouros.com/uploads/default/original/3X/7/e/7e786ec55a5a3af7bb71b60244504fcc8d832aa1.jpeg) To map it to a key, simply add this line after the last entry inf front of the closing `}` of your `binds.kdl` that should reside within the path `~/.config/niri/dms` `Mod+Shift+Q { spawn "dms" "ipc" "call" "keybinds" "toggle" "niri"; }` It’s also feasible to map shell scripts to a key, e.g. I’m using a systemd time to shutdown my machine daily at a specific time and with `Mod+XF86Launch5 repeat=false allow-inhibiting=false { spawn "sh" "-c" "shutdown-time"; } ` A graphical dialog for the shell command would be created on the fly via zenity. If you wonder about the `XF86Launch5` that is just a function key. ![image](https://forum.endeavouros.com/uploads/default/original/3X/a/2/a291c895280347d9ef0fef19b2c7e87fe0cc8b70.png) If you’re not comfortable with editing the configuration files manually, the DMS settings do provide easy keyboard shortcut configuration options. ---
**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\ **Post date:** [July 27, 2026, 6:38am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/10 "2026-07-27T06:38:42Z")
I am typically using ghostty terminal but I wanted to play around with wezterm. Seems like wezterm is not easy to integrate into niri. I have a 2 column niri setup. So far I was not able to open a wezterm window so that it automatically fills a full column width, like any other app that I open. If I do not specify `initial_cols` in `~/.wezterm.lua` the opening width is always `initial_cols = 80`, which is not a full column width. I could specify the initial\_cols manually, but then the value is wrong on my second monitor. I need to have an automatism. It seems wezterm had issues with niri in the past. Therefore there is a specific window rule in `~/.config/niri/config.kdl` ```auto window-rule { // This regular expression is intentionally made as specific as possible, // since this is the default config, and we want no false positives. // You can get away with just app-id="wezterm" if you want. match app-id=r#"^org\.wezfurlong\.wezterm$"# default-column-width { } } ``` I found a suggestion to change the default-column-width to `default-column-width { proportion 0.5; }` But with that, the wezterm window is not showing up at all. Any idea how to open a wezterm window maximized to column width? ---
**Author:** ![erne.d.98](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/erne.d.98/32/95777_2.png) [@erne.d.98](https://forum.endeavouros.com/u/erne.d.98)\ **Post date:** [July 27, 2026, 10:16am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/11 "2026-07-27T10:16:19Z")
There are a few bug reports on Github, referring to Wezterm not launching at all or randomly failing to launch on Wayland. AFAIC the only way to make it work is to force XWayland in Wezterm’s config. * * * Just then, I would try checking app-id of Wezterm: `niri msg windows` to ensure it matches the value in Niri’s config. ---
**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\ **Post date:** [July 27, 2026, 1:34pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/12 "2026-07-27T13:34:53Z")
> [@erne.d.98](#): > > AFAIC the only way to make it work is to force XWayland in Wezterm’s config. That did the trick. Thank you. With `config.enable_wayland=false` in the wezterm config and `default-column-width { proportion 0.5; }` in the niri config, the wezterm window opens automatically in column width. But this is really weird from wezterm point of view. I guess I will keep ghostty for the long term. ---
**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\ **Post date:** [July 27, 2026, 2:04pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/13 "2026-07-27T14:04:57Z")
I couldn’t reproduce the issue. With an freshly installed [`wezterm`](https://archlinux.org/packages/extra/x86_64/wezterm/) out of the extra repository, without any configurations made at all, wezterm opens a new window in half the column width. Which actually doesn’t reflect the defaults within my single column design. My setup consists of permanently floating windows to the left and right of my screens middle section, I just tile / scroll the middle part of the workspace, which is almost 1900 in width. My `default-column-width { proportion 1.0; }`seems not to work properly in case of wezterm. But as you were able to tackle this by disabling wayland within wezterms config file, I guess there is no need to tinker around with it. I only can report that there aren’t any issues in relation to kitty. Everything works as it did under KDE Plasma, no need to reconfigure anything. The only feature which I miss is the option to exclude specific windows from the window pager / `Alt` + `Tab` overview. That was feasible with the window rules of KDE Plasma. Where you also could exclude specific windows to show up in the overview. Or within the panels currently running apps. So I may need to file a feature request. But all in all, I’m pretty happy up so far. My specific use case of mixed static and scrolling window tiles has only been introduce with the 1.5 release of DMS, if I’m not mistaken. But it solid and is working better than it did on KDE Plasma. ---
**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\ **Post date:** [July 27, 2026, 2:28pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/14 "2026-07-27T14:28:56Z")
> [@1093i3511](#): > > I couldn’t reproduce the issue. With an freshly installed [`wezterm`](https://archlinux.org/packages/extra/x86_64/wezterm/) out of the extra repository, without any configurations made at all, wezterm opens a new window in half the column width. But this is reproducing my initial issue. Your wezterm opens with width = only 1/2 column width. But it should open in column width as any other app window. wezterm under wayland always opens with `initial_cols = 80` if you do not specify otherwise. And when I set `default-column-width { proportion 0.5; }` in the niri conf, the wezterm window wont open at all. ---
**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\ **Post date:** [July 27, 2026, 4:14pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/15 "2026-07-27T16:14:27Z")
I can’t tell which presets you’ve got enabled within the `preset-column-widths` of niri. But it should ship by default with `1/3`, `1/2` and `2/3`. I’ve changed mine to `1/2`, `3/4` and `1`. And with a `default-column-width` set to a proportion of `0.5` a wezterm window does show up, but only in the size that is identical to the `initial_cols = 80` of characters per line of the terminal. ---
**Author:** ![PeterRies](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/peterries/32/119956_2.png) [@PeterRies](https://forum.endeavouros.com/u/PeterRies)\ **Post date:** [August 27, 2026, 6:30am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/16 "2026-08-27T06:30:18Z")
I gave dank linux a first try after having watched the video. It always looks so well designed when people are presenting their desktops. same for niri+dank. polished. simply goog looking. so I gave it a try on a fresh endeavour/gnome. that’s where inconsistency starts. the filemanager (nautilus) still looks libadwaita (gnomish) and just understands light/dark, but no touch of the accent color I choose in niri/dank. ghostty does not switch light/dark whenever i choose light/dark from top panel quick setting. same for firefox regarding color shades. I end up in my standard apps looking like a “stranger in town”. does it need more individual themeing? or better not start with gnome as desktop with all it’s default apps? better choose another basis (or none) with well picked standard apps for files, browsing, terminal, editing… Do you have a good reading recommendation for that? Otherwise it’s the most promising concept for me up to now, if one is willing to to switch over to a quick (floating?) tiling manager. ---
**Author:** ![ajgringo619](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ajgringo619/32/35599_2.png) [@ajgringo619](https://forum.endeavouros.com/u/ajgringo619)\ **Post date:** [August 27, 2026, 7:08am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/17 "2026-08-27T07:08:31Z")
DankLinux has Matugen templates (_Settings → Themes and Colors → Matugen Templates_), which can apply your main theme to main other programs; not sure about GNOME, though - don’t use it. You can always install another file manager. I use **Dolphin** with **Hyprland** , then theme with `QT 6 Settings`. ---
**Author:** ![ddnn](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/ddnn/32/126676_2.png) [@ddnn](https://forum.endeavouros.com/u/ddnn)\ **Post date:** [August 27, 2026, 7:26am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/18 "2026-08-27T07:26:21Z")
I’m a little confused about your post. Which DE/WC did you try it in? Gnome and libadwaita are notoriously anti-theming/ricing. ---
**Author:** ![PeterRies](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/peterries/32/119956_2.png) [@PeterRies](https://forum.endeavouros.com/u/PeterRies)\ **Post date:** [August 27, 2026, 8:29am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/19 "2026-08-27T08:29:17Z")
Installed fresh Endeavour with Gnome (as this is my current daily setup) to play around. May be a bad choice as libadwaita seems to be quite “resitant” to theming approaches. So I might need to start from scratch to have a consistant look. Question is to install Endeavour without DE and just use the Dank installer with niri. then choose a more flexible filemanager (thunar - to stay with GTK; Dolphin? get Qt dependencies??). Choose kitty over ghostty? Or start with another distro that already has a well chosen set of visually integrated apps? Sorry for questions. I might check internet, but would rely more on your opinions and experiences 🙂 ---
**Author:** ![smokey](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/smokey/32/133678_2.png) [@smokey](https://forum.endeavouros.com/u/smokey)\ **Post date:** [August 27, 2026, 8:45am UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/20 "2026-08-27T08:45:43Z")
Would really depend on how much time you want to invest and level of skill. While I am ok with understanding code or fragments of it I cannot write much and almost always have some sort of guide open so I can search and learn as I go and will google away to find more info and answrs as I need them. This process is fun for me but for others it could be very frustrating. TLDR - depends ---
**Author:** ![1093i3511](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/1093i3511/32/102376_2.png) [@1093i3511](https://forum.endeavouros.com/u/1093i3511)\ **Post date:** [August 27, 2026, 2:18pm UTC](https://forum.endeavouros.com/t/niri-dank-material-noctalia-general-thread-questions-tips-tricks/80655/21 "2026-08-27T14:18:32Z")
[Dms Theme Sync](https://github.com/arqueon/dms-theme-sync) is included in the [DMS plugin registry](https://github.com/AvengeMedia/dms-plugin-registry/) and would allow applying the different matugen themes for GTK, KDE & Qt Frontends and keep them in sync. It offers several approaches how the matugen theme would be enforced and I was able to achieve consistent themes relatively fast that way.