Bug 515933

Summary:	KDE Connect window does not get drawn after removing monitor
Product:	[Applications] kdeconnect	Reporter:	Riven Skaye <riven>
Component:	windows-application	Assignee:	brute4s99 <piyushaggarwal002>
Status:	REPORTED ---
Severity:	minor
Priority:	NOR
Version First Reported In:	25.12.1
Target Milestone:	---
Platform:	Other
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Riven Skaye 2026-02-13 08:03:34 UTC

SUMMARY
If the last screen KDE Connect was placed on is not attached before booting, the window will never render, and its coordinates will place it beyond the far edge on the other side of the screen. Hovering the taskbar icon will show a flat white rectangle as the preview, and allows focusing the application but it's never displayed. The window will also not respond to the usual Super+arrow key combinations to reposition it, nor can it be moved or resized by right-clicking the window preview when hovering the taskbar icon. Maximizing the window from this context menu does force a redraw on whatever screen it gets sent to by the OS, making it usable again.

Reinstalling the application seems to not remove known connections and preferences, and this also includes the last used coordinates to draw on. This causes updating or reinstalling to _not_ solve the issue.

STEPS TO REPRODUCE
1. Attach an extra monitor to a system with KDE Connect installed
2. Boot the system, log on to windows and open the KDE Connect application (kdeconnect-app.exe)
3. Move the KDE Connect window to the new monitor and shut down
4. Detach the monitor from the PC
5. Power the system back on, sign in, and attempt to open the KDE Connect window
6. Observe the aforementioned behavior.

OBSERVED RESULT
No functional window gets drawn, the application does get focus, but cannot be normally moved to another display. The daemon does run in the background, and its functions seem unimpaired.

EXPECTED RESULT
KDE Connect draws on the primary display as fallback and functions as normal.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Pro 22H2 build 19045.6937 with Extended Support Updates

ADDITIONAL INFORMATION
A workaround is available, and it's a weird edge case to even run into. It would be valid to mark this `wontfix`, but in that case it might be worthwhile to add an entry to the wiki's Troubleshooting section. I will try to see if the same behavior is exhibited on a laptop running Windows 11 over the weekend, and update this report accordingly.