well - I’ve connected my 4k monitor to my laptop - monitor to the right.
I’ve set my monitor to DPI 1.25. I’ve then grabbed via screenshot the logo area on the laptop and separately the monitor resolute logo. Both worked successfully.
So I’m interested in what is different with your setup.
so just one monitor?
Yes, I only have a laptop.
Damn. So I’ve tried that - and still no problems. This is amd ryzen 4 graphics BTW. Dunno if that snippet makes a difference.
lspci | grep VGA
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 03)
small detail I note that your dpi settings use a comma in the value so I’m wondering if this is a locale formatting issue.
Please attach your ~/.config/budgie-desktop/*.toml file here - its a text file so you might need to copy it and rename it with a .txt extension to attach here.
Here it is:
display-config-shim.toml.txt (458 Bytes)
OK. The key here is not to test with just the wdisplays setting. Logout and login and then redo the screenshot and you will notice the bug. Will need to think. I have a sneaking suspicion but will need to confirm
The key thing is understanding how to reproduce. This allows the investigation to take place.
So good news. Now have fixed it and posted this to upstream. Assuming that upstream are happy we will then patch budgie-desktop on ubuntu because a new release of upstream budgie will likely be after final freeze in April.
On the other hand, Budgie Screencast works fine. 
Just a reminder folks - beta freeze date is this coming Monday. So any help testing or raising issues sooner than later would be welcome.
Incoming will be a budgie-desktop update later this week resolving 3 matters:
Incoming to the slicksddm-customizer option to toggle the lock-screen “press any key” on and off
Incoming to the live ISO to hopefully launch the installer on boot
Unless I’m mistaken, you can’t copy a file to system directories using Nemo in administrator mode.
I had to use sudo cp to copy a wallpaper to /usr/share/backgrounds.
yep - known. Nemo isn’t fully wayland compatible. That will be for 26.10 hopefully.
<keyboard>
<numlock>on</numlock>
Adding this tag to .config/budgie-desktop/labwc/rc.xml enables the numeric keypad at startup.
However, it then takes between five and ten seconds for this to take effect.
Noted - since you’ve dropped this here it is useful as a reminder - will be included in the release notes.
nicely found. As an aside - since using xhost it shows the app is still X based rather than wayland - so it is running under XWayland at the moment.
Again - all good stuff - think we should have a “that’s something to be aware of - here is a workaround” type section in the release notes.
