Cleanroom Full screen issues with wayland
Your CleanroomMC Discord Username
kurama
Cleanroom Version
0.3.0-alpha
Java Version
Java 21
Graphics Card Vendor
NVidia
Bug Report
Issues with Wayland when full screening, keeps jumping to my second display and stretching the screen rather than resizing also when exiting full screen seems to be minimized in corner of window
only occurs on alpha 3.0 seems to be on 0.2.4
recorded behavior you can view here https://nextcloud.lunar-stack.co.uk/s/44dFbCdp2fMZSBM
Logs https://mclo.gs/S5NWYol
note preview window wont load you need to click 3 dots top right and click download
Mod List
no mods
Final Checklist
- [x] I have searched the issues and haven't found a similar issue.
- [x] I have read the readme and know that what is action build and non-MMC based launcher are unsupported.
- [x] I have installed Fugue and it does not fix this issue.
- [x] I have installed Scalar and it does not fix this issue.
- [x] I have switched my Forgelin and LibrarianLib to continuous versions(check readme for more detail).
- [x] I am running a test build from Cleanroom Github Actions. (Or, if I've compiled it myself I plan to fix the issue)
Is this happen on 0.2.4 too?
No this does not occur on 0.2.4
Probably another problem introduced by using official LWJGL Did you try to reproduce this with only 1 display?
No I have not will try and let you know may be a little difficult due to my pc setup being fiber cables in another room but il get back to you on that one let you know
Yeah, exact same problem here on 0.3.0 doesn't happen on 0.2.4a, it makes mc go full screen on my secondary display, (left side)
But it works perfectly when using ALT+ENTER Reproduced with only one display and problem doesn't happen.
.-/+oossssoo+/-. egg@OBELIX
`:+ssssssssssssssssss+:` -----------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 24.10 x86_64
.ossssssssssssssssssdMMMNysssso. Kernel: 6.11.0-19-generic
/ssssssssssshdmmNNmmyNMMMMhssssss/ Uptime: 1 hour, 23 mins
+ssssssssshmydMMMMMMMNddddyssssssss+ Packages: 3442 (dpkg), 24 (flatpak), 17 (snap)
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Shell: bash 5.2.32
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Resolution: 2560x1440
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ DE: Plasma 6.1.5
ossyNMMMNyMMhsssssssssssssshmmmhssssssso WM: kwin
ossyNMMMNyMMhsssssssssssssshmmmhssssssso Theme: cdetheme [GTK2/3]
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Icons: Win2kSVG-plasma5up-scalable-icontheme-blackysgate.de [GTK2/3]
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Terminal: konsole
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ CPU: AMD Ryzen 9 3900X (24) @ 5.163GHz
+sssssssssdmydMMMMMMMMddddyssssssss+ GPU: NVIDIA GeForce RTX 4090
/ssssssssssshdmNNNNmyNMMMMhssssss/ Memory: 29989MiB / 31996MiB
.ossssssssssssssssssdMMMNysssso.
-+sssssssssssssssssyyyssss+-
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
Demo : https://github.com/user-attachments/assets/05efec3a-8ad0-47eb-98ea-6ff7bfe2669d
seems you also have the resize issue when you exit out of full screen (from F11) im not sure what you use for Alt enter my does not do anything when i do alt enter so wonder if thats a ububtu thing, im using arch plasma
The glitches caused by F11 while exiting seems to be due to the fact that I launch cleanroom in a custom resolution in Prism. I also noticed that when I hold backspace key it removes only one character, i now have to press 6x backspace to delete 6 characters... But I'm not sure if that happens since 0.3 or if it's simply a spooky mod. CTRL + C or V doesn't The glitches caused by f11 while exiting are due to the fact that I launch cleanroom in a custom resolution in prism.
I also noticed that when I hold backspace key it removes only one character, i now have to press 6x backspace to delete 6 characters... But I'm not sure if that happens since 0.3 or if it's simply a spooky mod. Also when doing CTRL+V, it seems that it pastes only the clipboard content that was here while loading the game. In simple words, it does not paste the actual content of my clipboard but an old content that copied before the game...
I have to try that on 0.2.4 and open an issue about it if its caused by CR.