Skip to content

Detect modern KWin process names (kwin_x11, kwin_wayland) - #826

Open
GeoPakas wants to merge 1 commit into
KittyKatt:masterfrom
GeoPakas:fix-kwin-wm-detection
Open

GeoPakas wants to merge 1 commit into
KittyKatt:masterfrom
GeoPakas:fix-kwin-wm-detection

Conversation

@GeoPakas

Copy link
Copy Markdown

Problem

WM detection only matched a process named exactly kwin (the KDE 4 /
early-Plasma name). Modern KDE Plasma runs kwin_x11 on X11 and
kwin_wayland on Wayland, so screenFetch reported WM: Not Found on
current KDE.

Fix

  • Add kwin_x11 and kwin_wayland to the wmnames list and map both to
    the KWin label (bare kwin kept for older setups).
  • Widen the detectwm session guard from [[ -n $DISPLAY ]] to
    [[ -n $DISPLAY || -n $WAYLAND_DISPLAY ]] so detection isn't skipped on
    Wayland-only sessions without XWayland.

Notes

Testing

Validated the matching logic for kwin, kwin_x11, and kwin_wayland
(all resolve to KWin). I'm on Xfwm4/X11, so I verified the KWin paths by
isolating the detection logic rather than a live KDE run.

screenFetch only matched a process named exactly 'kwin' (KDE 4 era). Modern KDE Plasma runs 'kwin_x11' or 'kwin_wayland', so WM detection returned 'Not Found' on current KDE. Add both names to the detection list (keeping 'kwin' for legacy) and let the detection block run on Wayland-only sessions via WAYLAND_DISPLAY.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant