Compositor
Distribution
If Other, please specify
No response
dms doctor -vC
DMS Doctor Report
System
- [ok] Operating System: Arch Linux
- ID: arch, Version: rolling, Arch: amd64
- [ok] Architecture: amd64
- [ok] Display Server: Wayland
- WAYLAND_DISPLAY=wayland-1
Versions
- [ok] DMS CLI: dms v1.4.1
- [warn] Quickshell: quickshell 0.2.1, revision , distributed by: Arch Linux
- [ok] DMS Shell: v1.4.1
- /usr/share/quickshell/dms
Installation
- [ok] DMS Configuration: Found
- /usr/share/quickshell/dms
- [ok] shell.qml: Present
- /usr/share/quickshell/dms/shell.qml
- [info] Install Type: System package
- /usr/share/quickshell/dms
Compositor
- [ok] niri: 25.11
- [info] Active: niri
Quickshell Features
- [info] Polkit: Not available
- [info] IdleMonitor: Not available
- [info] IdleInhibitor: Not available
- [info] ShortcutInhibitor: Not available
- Allow shortcut management (niri)
Optional Features
- [ok] accountsservice: Available
- [ok] power-profiles-daemon: Available
- [ok] logind: Available
- [warn] cups-pk-helper: Not available (install cups-pk-helper)
- [info] I2C/DDC: No monitors detected
- External monitor brightness control
- [ok] qt6-imageformats: Installed (1 formats)
- Formats: GIF (/usr/lib/qt6/plugins/imageformats)
- [warn] kimageformats: Not installed
- [ok] Terminal: kitty
- [ok] Network: NetworkManager
- NetworkManager present; iwd also running (likely NM's Wi-Fi backend). Using NM API.
- [ok] matugen: Installed
- [ok] dgop: Installed
- [ok] cava: Installed
- [info] khal: Not installed
- [ok] danksearch: Installed
- [info] fprintd: Not installed
Config Files
- [ok] settings.json: Present
- /home/paglobal/.config/DankMaterialShell/settings.json
- [info] clsettings.json: Not yet created
- /home/paglobal/.config/DankMaterialShell/clsettings.json
- [ok] plugin_settings.json: Present
- /home/paglobal/.config/DankMaterialShell/plugin_settings.json
- [ok] session.json: Present
- /home/paglobal/.local/state/DankMaterialShell/session.json
- [ok] dms-colors.json: Present
- /home/paglobal/.cache/DankMaterialShell/dms-colors.json
Services
- [ok] dms.service: enabled, active
- [info] greetd: Not installed
Environment
- [info] QT_QPA_PLATFORMTHEME: qt6ct
- [info] QS_ICON_THEME: Not set
Summary: 0 error(s), 3 warning(s), 23 ok
Description
When file search is enabled using "/" in the launcher, the "/" character doesn't appear, just like it does with plugins. That's mostly not an issue though; the problem is that it seems like as a result of this, when the last file search character is deleted, the launcher reverts back to its default mode. For plugins, the special character has to be deleted first before the mode changes, but it can't happen here somewhat because the special character is not recorded in the launcher input in the first place
Expected Behavior
I guess I expect it to behave similarly to the way launcher plugins do with their special trigger characters
Steps to Reproduce & Installation Method
- Open the launcher
- Enter "/"
- In file search mode, type more than two characters to initiate a file search
- Delete the characters you've typed and watch the mode revert to the default (ideally, it should stay in file search mode until you do something else to exit)
Error Messages/Logs
No response
Screenshots/Recordings
No response
Compositor
Distribution
If Other, please specify
No response
dms doctor -vC
DMS Doctor Report
System
Versions
Installation
Compositor
Quickshell Features
Optional Features
Config Files
Services
Environment
Summary: 0 error(s), 3 warning(s), 23 ok
Description
When file search is enabled using "/" in the launcher, the "/" character doesn't appear, just like it does with plugins. That's mostly not an issue though; the problem is that it seems like as a result of this, when the last file search character is deleted, the launcher reverts back to its default mode. For plugins, the special character has to be deleted first before the mode changes, but it can't happen here somewhat because the special character is not recorded in the launcher input in the first place
Expected Behavior
I guess I expect it to behave similarly to the way launcher plugins do with their special trigger characters
Steps to Reproduce & Installation Method
Error Messages/Logs
No response
Screenshots/Recordings
No response