Compositor
Niri
Distribution
Fedora
If Other, please specify
No response
Select your Installation Method
Distro Packaging
Was this your original Installation method?
Yes
If no, specify
No response
dms doctor -vC
Click to expand
## DMS Doctor Report
System
- [ok] Operating System: Fedora Linux 44.20260801.0 (Forty Four)
- ID: fedora, Version: 44, Arch: amd64
- [ok] Architecture: amd64
- [ok] Display Server: Wayland
- WAYLAND_DISPLAY=wayland-1
Versions
- [ok] DMS CLI: dms v1.5.3
- [ok] Quickshell: Quickshell 0.3.0 (revision 43d4fa9e883cb03239b3d578c9c57070f4fbd281, distributed by Fedora COPR (avengemedia/quickshell))
- [ok] DMS Shell: 1.5.3
- /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: 26.04
- [info] Active: niri
- [ok] Background Blur: Supported
- Compositor supports ext-background-effect-v1
Quickshell Features
- [ok] Polkit: Available
- [ok] IdleMonitor: Available
- [ok] IdleInhibitor: Available
- [ok] ShortcutInhibitor: Available
- Allow shortcut management (niri)
- [ok] BackgroundBlur: Available
- Background blur API support in Quickshell
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/lib64/qt6/plugins/imageformats)
- [warn] kimageformats: Not installed
- [ok] Terminal: kitty, alacritty
- [ok] Network: NetworkManager
- NetworkManager present. Using NM API.
- [ok] matugen: Installed
- [ok] dgop: Installed
- [ok] cava: Installed
- [info] khal: Not installed
- [ok] danksearch: Installed
- [info] dankcalendar: Not installed
- [info] fprintd: Not installed
Config Files
- [ok] settings.json: Present
- /var/home/jaswinder/.config/DankMaterialShell/settings.json
- [info] clsettings.json: Not yet created
- /var/home/jaswinder/.config/DankMaterialShell/clsettings.json
- [ok] plugin_settings.json: Present
- /var/home/jaswinder/.config/DankMaterialShell/plugin_settings.json
- [ok] session.json: Present
- /var/home/jaswinder/.local/state/DankMaterialShell/session.json
- [ok] dms-colors.json: Present
- /var/home/jaswinder/.cache/DankMaterialShell/dms-colors.json
Services
- [ok] dms.service: enabled, active
- [ok] greetd: enabled
Environment
- [info] QT_QPA_PLATFORMTHEME: gtk3
- [info] QS_ICON_THEME: Not set
- [info] XDG_MENU_PREFIX: Not set
Fonts
- [warn] Normal Font: 'Inter Variable' not found
- Font is not registered. Try running 'fc-cache -fv' or install the font.
- [warn] Monospace Font: 'Fira Code' not found
- Font is not registered. Try running 'fc-cache -fv' or install the font.
Summary: 0 error(s), 4 warning(s), 31 ok
Description
I've got enableU2f: true and u2fMode: "or" set, expecting the lock screen to accept either password or security key, like GDM does, where hitting Enter on an empty password field lights up the key for a touch, no other input needed.
On the dms lock screen that doesn't happen. Enter always starts the password flow. The only way to trigger security key auth is clicking the little passkey icon with the mouse. There's no keyboard equivalent, and no dms ipc command for it either.
This is extra annoying since my key is a biometric FIDO2 (no PIN), auth is just a touch, so the mouse click is the only manual step in what should be a one-touch unlock, same as it already is in GDM.
Looked through the source a bit: LockScreenContent.qml's password field onAccepted only calls pam.passwd.start(), and pam.u2f.startForAlternativeAuth() is wired up only to the button's onClicked. So it's not a config issue on my end, seems like the "or" mode just doesn't have an Enter/keyboard path wired up yet.
dms 1.5.3, quickshell-git 0.3.1^834.git43d4fa9, niri 26.04, Fedora 44.
Expected Behavior
Like gdm, pressing enter or another keyboard shortcut should trigger yubikey, without having to use mouse or touchpad and clicking that super small yubikey button.
Steps to Reproduce
No specific steps.
Error Messages/Logs
No response
Screenshots/Recordings
No response
Compositor
Niri
Distribution
Fedora
If Other, please specify
No response
Select your Installation Method
Distro Packaging
Was this your original Installation method?
Yes
If no, specify
No response
dms doctor -vC
Click to expand
## DMS Doctor ReportSystem
Versions
Installation
Compositor
Quickshell Features
Optional Features
Config Files
Services
Environment
Fonts
Summary: 0 error(s), 4 warning(s), 31 ok
Description
I've got enableU2f: true and u2fMode: "or" set, expecting the lock screen to accept either password or security key, like GDM does, where hitting Enter on an empty password field lights up the key for a touch, no other input needed.
On the dms lock screen that doesn't happen. Enter always starts the password flow. The only way to trigger security key auth is clicking the little passkey icon with the mouse. There's no keyboard equivalent, and no dms ipc command for it either.
This is extra annoying since my key is a biometric FIDO2 (no PIN), auth is just a touch, so the mouse click is the only manual step in what should be a one-touch unlock, same as it already is in GDM.
Looked through the source a bit: LockScreenContent.qml's password field onAccepted only calls pam.passwd.start(), and pam.u2f.startForAlternativeAuth() is wired up only to the button's onClicked. So it's not a config issue on my end, seems like the "or" mode just doesn't have an Enter/keyboard path wired up yet.
dms 1.5.3, quickshell-git 0.3.1^834.git43d4fa9, niri 26.04, Fedora 44.
Expected Behavior
Like gdm, pressing enter or another keyboard shortcut should trigger yubikey, without having to use mouse or touchpad and clicking that super small yubikey button.
Steps to Reproduce
No specific steps.
Error Messages/Logs
No response
Screenshots/Recordings
No response