Please describe your issue in as much detail as possible:
Steam would not open its UI when launched from the KDE Application Launcher or from a pinned taskbar icon.
The splash/load process begins, steamwebhelper starts, and logs show normal initialization, but the Steam window never appears and the process silently exits.
Launching Steam from a terminal using the steam command works correctly every time, so this is not an issue with Steam's runtime, GPU drivers, or dependencies.
After investigation, the cause appears to be KDE Plasma caching an incorrect or invalid launch entry for Steam. The system Steam .desktop file contains multiple Exec= entries (used as URL handlers), and KDE sometimes caches the wrong Exec line as the primary launcher. The cached launcher continues to be used even after:
Removing and re-adding pinned icons
Deleting local .desktop overrides
Changing system themes
Reinstalling Steam
Even a manually created clean .desktop entry was ignored until KDE’s cached launcher database was cleared.
The issue was finally resolved by manually clearing KDE’s ksycoca application cache:
Hello @lazycooken, this issue should be reported to the maintainers of your desktop environment and/or your distro's package maintainer(s) for kservice.
Your system information
Steam client version (build number or date):
Build shown when launching Steam: 1763422420 (Nov 17 2025)
Distribution (e.g. Ubuntu):
Debian 13 (KDE Plasma desktop)
Opted into Steam client beta?:
No
Have you checked for system updates?:
Yes
Steam Logs:
steam-logs.tar.gz
GPU:
NVIDIA GeForce RTX 3050 (NVK GA106)
AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)
Mesa driver version: 25.0.7
Please describe your issue in as much detail as possible:
Steam would not open its UI when launched from the KDE Application Launcher or from a pinned taskbar icon.
The splash/load process begins, steamwebhelper starts, and logs show normal initialization, but the Steam window never appears and the process silently exits.
Launching Steam from a terminal using the steam command works correctly every time, so this is not an issue with Steam's runtime, GPU drivers, or dependencies.
After investigation, the cause appears to be KDE Plasma caching an incorrect or invalid launch entry for Steam. The system Steam .desktop file contains multiple Exec= entries (used as URL handlers), and KDE sometimes caches the wrong Exec line as the primary launcher. The cached launcher continues to be used even after:
Removing and re-adding pinned icons
Deleting local .desktop overrides
Changing system themes
Reinstalling Steam
Even a manually created clean .desktop entry was ignored until KDE’s cached launcher database was cleared.
The issue was finally resolved by manually clearing KDE’s ksycoca application cache:
rm -rf ~/.cache/ksycoca5*
rm -rf ~/.cache/ksycoca6*
kbuildsycoca5
After rebuilding the KDE application database, Steam launched normally from both the Application Launcher and pinned icons.
Expected behavior:
Steam should launch normally from KDE’s application menu or taskbar.
Actual behavior:
Steam UI appeared only when launched from a terminal, until KDE’s cache was manually rebuilt.
This issue appears specific to situations where the Steam .desktop file contains multiple Exec lines and KDE caches the wrong one.
Steps for reproducing this issue:
Install Steam on Debian 13 KDE Plasma
Launch Steam from the Application Launcher or pin it to the taskbar
Steam begins initialization but no UI appears
Attempt to run Steam again from the menu — same result
Run steam from a terminal → UI appears normally
Remove pinned icon, reinstall Steam, clear local .desktop files → issue persists
Run:
rm -rf ~/.cache/ksycoca5*
kbuildsycoca5
Launch Steam from KDE → now works normally