Bug 507828

Summary:	Screen numbers change after lock/unlock cycle
Product:	[Applications] yakuake	Reporter:	Nick W <nick>
Component:	general	Assignee:	Eike Hein <hein>
Status:	REPORTED ---
Severity:	normal	CC:	kde, nicolas.fella
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Nick W 2025-08-03 20:52:57 UTC

SUMMARY

This has been an issue for me since 5.x, on both Wayland & X11.

When I boot up, Yakuake launches on the last used screen (1  in my case). This is on the wrong screen, so I switch it to screen 3.

Then I leave my PC for a time, screens lock. I come back, and now have to move it back to screen 1. Subsequent locks don't affect it afterward, it stays on screen 1 until I reboot and the cycle repeats.

Hardware might matter?

I have 4 screens, all running off of 1 Radeon 6900XT. 1 screen runs off a USBC port on the same card. The one on the USB port is the one that registers as Screen 1 after screen lock. Screen arrangement remains correct, just the screen number changes.

Comment 1 David Edmundson 2025-08-04 16:27:13 UTC

yakuake just picks the screens randomly on wayland. 

This is not a kwin issue.

Comment 2 Nicolas Fella 2025-08-04 16:55:04 UTC

(In reply to David Edmundson from comment #1)
> yakuake just picks the screens randomly on wayland. 

It's not exactly random, and you know it.

https://invent.kde.org/utilities/yakuake/-/merge_requests/140 should improve this

Comment 3 Nick W 2025-12-30 17:26:16 UTC

This is 100% a kwin issue. Yakuake is actually following screen ordering as expected - it's screen ordering that changes.

I also have keyboard shortcuts to move windows to a specific screen, and the behavior is the same with all windows.

The issue is the screens are ordered differently when plasma starts after all screens are already on (boot up) vs when the screens start up after plasma is running (coming back from monitors off). Note my computer doesn't sleep - it's just turning monitors off & locking session.

Comment 4 Nick W 2026-01-02 16:28:34 UTC

I'm confused as to why this got reassigned to yakuake? It is happening with all of my windows.

Maybe I need to file a separate bug?

To further clarify:

I have shortcuts for "Move Window to screen [0123]" and the pattern is the same. If I use my shortcut to move to screen 0, screen 0 is always a different screen after reboot than after the screens coming back on from auto-off.

Despite my original message mentioning yakuake, it's not an app issue at all. It has to do with my screens getting enumerated inconsistently.

It would make no sense to go file this as a firefox bug - and makes the same amount of sense (zero) as a yakuake bug.

Comment 5 Nicolas Fella 2026-01-02 16:38:31 UTC

This report is tracking a problem with Yakuake. If you have issues with something else please file a separate report, thanks!