3 Second delay during startup

[maru-sama]

Compositor

Niri

Distribution

Ubuntu

If Other, please specify

No response

Select your Installation Method

DankInstaller

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: Ubuntu 25.10
  • ID: ubuntu, Version: 25.10, Arch: amd64
• [ok] Architecture: amd64
• [ok] Display Server: Wayland
  • WAYLAND_DISPLAY=wayland-1

Versions

• [ok] DMS CLI: dms v1.4.3
  • /usr/bin/dms
• [ok] Quickshell: quickshell 0.2.1, revision , distributed by: Unset
  • /usr/bin/qs
• [ok] DMS Shell: v1.4.3
  • /usr/share/quickshell/dms/quickshell

Installation

• [ok] DMS Configuration: Found
  • /usr/share/quickshell/dms/quickshell
• [ok] shell.qml: Present
  • /usr/share/quickshell/dms/quickshell/shell.qml
• [info] Install Type: System package
  • /usr/share/quickshell/dms/quickshell

Compositor

• [ok] Hyprland: usage: Hyprland [arg [...]].

Arguments:
--help -h - Show this message again
--config FILE -c FILE - Specify config file to use
--i-am-really-stupid - Omits root user privileges check (why would you do that?)

• /usr/local/bin/Hyprland
• [ok] niri: 25.11
  • /usr/bin/niri
• [ok] Sway: 1.10
  • /usr/bin/sway
• [info] Active: niri

Quickshell Features

• [ok] Polkit: Available
  • Authentication prompts
• [ok] IdleMonitor: Available
  • Idle detection
• [ok] IdleInhibitor: Available
  • Prevent idle/sleep
• [ok] ShortcutInhibitor: Available
  • Allow shortcut management (niri)

Optional Features

• [ok] accountsservice: Available
  • User accounts
• [ok] power-profiles-daemon: Available
  • Power profile management
• [ok] logind: Available
  • Session management
• [ok] cups-pk-helper: Available
  • Printer management
• [info] I2C/DDC: No monitors detected
  • External monitor brightness control
• [ok] qt6-imageformats: Installed (4 formats)
  • Formats: WebP, TIFF, GIF, ICNS (/usr/lib/x86_64-linux-gnu/qt6/plugins/imageformats)
• [warn] kimageformats: Not installed
  • AVIF, HEIF, JXL support
• [ok] Terminal: kitty
• [ok] Network: NetworkManager
  • NetworkManager present. Using NM API.
• [ok] matugen: Installed
  • Dynamic theming
• [ok] dgop: Installed
  • System monitoring
• [ok] cava: Installed
  • Audio visualizer
• [info] khal: Not installed
  • Calendar events
• [info] danksearch: Not installed
  • File search
• [ok] fprintd: Installed
  • Fingerprint auth

Config Files

• [ok] settings.json: Present
  • /home/maru/.config/DankMaterialShell/settings.json
• [info] clsettings.json: Not yet created
  • /home/maru/.config/DankMaterialShell/clsettings.json
• [ok] plugin_settings.json: Present
  • /home/maru/.config/DankMaterialShell/plugin_settings.json
• [ok] session.json: Present
  • /home/maru/.local/state/DankMaterialShell/session.json
• [ok] dms-colors.json: Present
  • /home/maru/.cache/DankMaterialShell/dms-colors.json

Services

• [ok] dms.service: enabled, active
• [ok] greetd: enabled

Environment

• [info] QT_QPA_PLATFORMTHEME: Not set
• [info] QS_ICON_THEME: Not set

---

Summary: 0 error(s), 1 warning(s), 32 ok

Description

Hi,

I am not sure when it started but during the login or restart there is a 3 second delay until the shell starts. During this time the niri shortcuts already work and you can open a temrinal window for example. but the shell is not there.

This was not always the case and the logs show no error at all

Expected Behavior

No response

Steps to Reproduce

1. Start or restart the shell
2. There is a 2 to 4 second delay until the shell is visible
3. Logs do not show errors

Error Messages/Logs

No response

Screenshots/Recordings

No response

[Purian23]

Hmm i'm not sure if I'd call this a bug but I did just push out a quickshell-git update to introduce a new crash handler from upstream commits. I'll see if I can reproduce this one a VM here later.

[maru-sama]

Hi, you are right it is not really a bug, since the application works fine, that said I am wondering where this delay is coming from since I do not remember seeing this before. Interestingly enough there are no error or warning messages when this delay happens. Is there a way to have a more verbose log to see where it is hanging/waiting?