Bug 510417

Summary:	External screen used as primary at first launch
Product:	[I don't know] kde	Reporter:	Gergely HORVÁTH <horvathg.1988>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED LATER
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Gergely HORVÁTH 2025-10-09 07:53:37 UTC

Hi,
this is not actually my bug, but the blog author may not have opened an issue for it.
Source: [blogpost](https://kokada.dev/blog/kde-is-now-my-favorite-desktop/)
As such, I will not be able to provide any more details than that, but what is described seems like a typical 15min bug.
Description (verbatim from the blogpost):

"
At the first launch I got one issue where it started without the task bar because I connected this PC to both my monitor and TV, but the TV is used exclusively for gaming. However, KDE considered my TV the primary desktop and put the task bar only in that monitor, and even disabling the TV didn't add the task bar to my monitor. Easily fixed by manually adding a task bar, but an annoying problem (especially when you're not used to the desktop). There were also a few other minor issues that I don't remember right now.
"

Thanks if you look into this!

Comment 1 Nate Graham 2025-10-09 16:04:32 UTC

I appreciate you filing a bug report on behalf of someone else, but unfortunately this usually makes the bug report un-actionable if its cause is not immediately, 100% obvious. And I'm afraid this is probably one of those cases.

Based on the symptoms, I *suspect* when the author disabled the TV, what they actually did was turn it off via the remote/button on the TV, which does not actually disable it due to the funny way that TVs work.

If they had disabled it from System Settings > Display Configuration, then the panel should definitely have moved to the other screen. And if that's what they did do and this didn't work, we would need a bunch of debug logging to figure out what went wrong — debug logging that you won't be able to get, because it's not your own system.