Sounds like a crash. There should be a message asking you to report the issue to launchpad on login. Please do so.
The file manager wonāt display properly with the mojave theme from budgie welcome. I was able to get an older cameo osx 3.38 theme to work, but the window title bar of the file manager still isnāt consistent with all the other applications.April 1st download and installation.
Cameo OSX Theme:
highly likely this is linked to the ādouble heightā issue at the end of the first post.
In this release of mutter GNOME has reworked displaying non-csd apps - and it is breaking all sorts of things- theming, focusing etc.
Yep confirmed
Bug fix is being worked on
The WhiteSur theme isnāt broken for some reason , but all the other 3rd party Mac themes Iāve tried are. This is only my second installation this cycle, my November installation died on March 31 with major package problems.
New version of mutter has been released. This should hopefully fix titlebar decoration theming issues.
No change after update and reboot .
ah well - thatās a shame. too many breakages this time from the GNOME devs. ho hum.
I have noted in the first post a curious observation I spotted with themes that end with ā-darkā such as Pocillo-dark and that have the Style āPrefer darkā the libadwaita dark styling is applied to window decorations by either mutter or GTK (not sure which) rather than the expected theme.
If you switch to Style āApplication Preferenceā the theme styling is applied.
This is a definite change by GNOME for 23.04 - I donāt know if its a bug or an intentional change but its annoying.
Hi all,
probably is my fault but I canāt see where the error could be ā¦
A couple of days ago Iāve customized Lunar original ISO (unsquashfs-ing, chroot-ing, customizing, ā¦ and so on); customization has been a ābaseā one: just changing hostname and username, installing vim and some base packages, then customizing grub.cfg and loopback.cfg (I hate try/install thing!).
A small set of packages because I donāt like too much waste my time: if it doesnāt work, it doesnāt work in a ābase customized versionā as in a āfully customized versionā.
Everything went at its best so I installed it on a Qemu VM; Iāve started it and, as Iām used to do, first thing I do, I change resolution from 1024x768 to 1440x900. Iāve launched budgie-control-center and ā¦ Iāve been ākicked offā!
I mean session brutally closed and I had to relog-in.
āOK, is your fault, girlā Iāve told to myself ā¦ Briefly, Iāve tried several other times without any result. Then decided to try to install without any customization, from livecd I freshly (re)downloaded, on a brand new Qemu VM but when Iāve launched budgie-control-center, ā¦ kicked off again!
Please, notice that being kicked off happens to me only in installed version and not on live one.
Thanks and cheers,
Sil
Yeah i have seen a report about kvm issues. Its likely a crash file would have been generated. It should be offered to report the issue to launchpad. Please do so and let me know the bug number
Your issue is probably this
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1965173
I.e. a kvm/qemu spice agent crash.
You probably cant see that report because its marked as private so only those of us who has the rights to see launchpad private data can view.
Do please still report your issue ā¦ if it is this issue then launchpad should mark it as a duplicate automatically
Hi fossfreedom,
Iām not sure is a kvm/qemu crash (btw, the link you provided gives a 404) because it happens both in qemu and in virtualbox (maybe they both use the same virtualization system, honestly Iām pretty illiterate about virtualization) and then, both in qemu and in virtualbox I can set screen resolution from terminal without a problem with xrandr --size 1440x900.
Third, it happens only when I try to get access to budgie-control-center and finally I get in /var/crash a Xorg-related crash notification, but without any chance to send it to anybody. Notive that reinstalling budgie-control-center is useless.
Cheers,
Sil
The 404 is because its a private bug that the public isnt privy too.
I am intrigued that you have reproduced this in virtualbox. So what was the last thing you were doing in virtualbox?
Iām not so sure what youāre meaning with your question but simply Iāve installed VB from Oracle deb and, on it, Iāve created three ācloneā VMs: 18Gb RAM, 100Gb HD partitioned into 4 slices: 512Mb EFI, 512 Mb bios-grub, 34Mb ext4 / and the rest ext4 /home.
On first VM Iāve installed my customized Budgie
on second VM Iāve installed a freshly downloaded Budgie
on third VM Iāve installed a freshly downloaded Ubuntu (Gnome, the āclassicalā)
On all three VMs, changing resolution from terminal with xrandr works w/o a problem while on Budgie only, changing resolution invoking displays via menu or invoking budgie-control-center via terminal kicks me off.
This doesnāt happen on āclassicalā Ubuntu, as if the problem were in budgie-control-center and not in gnome-control-center.
If needed, thereās half a ton of xorg-related logs in /var/log/apport, /var/log/lightdm ā¦
Same thing happened via Qemu: same brand new and clone VMs, same installation iso, same partitioning scheme.
Cheers,
Sil
PS āclassicalā ubuntu installer is horrible! 
Hmmā¦ sorry am using virtualbox also for a lunar vm and have changed the resolution several times ā¦ no issues
Hi, fossfreedom
today Iāve tested a bit on several pcs this way:
1A) on āfirstā linux machine (the one Iām using mostly at home, a desktop equipped by Ubuntu Budgie, i5 and 32 Gb ram) Iāve installed budgie-lunar on virtualbox
1B) same scenario described above, but lunar installed on a Qemu VM
1C/D) same scenarios described above, but kinetic installed instead of lunar
In cases 1A) and 1B) every time I invoke budgie-control-center Iām kicked off
In cases 1C/D) (both on Qemu and virtualbox) budgie-control-center opens without a problem.
Iāve changed PC, using my laptop (i7, 16 Gb RAM, Budgie) and executed tests 1A - 1D and nothing changed.
Thinking that it could be a host-PC fault (both desktop and laptop come from the same image), Iāve installed VBox on a windows machine (donāt remember processor, 16 Gb ram and win11) and tested both lunar and kinetic after having installed them: while on kinetic budgie-control-center works like a charm, on lunar Iām as usual kicked off ā¦
I donāt understand, sincerely: how are you able to install lunar, launch budgie-control-center and not be kicked off? Please, explain me, Master 
Finally, all easter afternoon spent in front of a pc ā¦ my husband and son thank! 
Cheers,
Sil
I am using virtualbox 7 and i just use 2cpu, 256Mb display ram with host acceleration. Standard lunar install with 25Gb disk and 4GB allocated ram
ok, I resign ā¦ anyway it will work before next LTS (thatās why I play with newest releases, for being prepared to next LTS 
)
last thing: if I run budgie-control-center from terminal and, after having been kicked off I give
journalctl -b -p 3
I get this:
apr 11 10:05:04 homardlunaire gnome-session-binary[3045]: Unrecoverable failure in required component org.buddiesofbudgie.BudgieWm.desktop
apr 11 10:05:04 homardlunaire gnome-session-binary[3045]: Unrecoverable failure in required component org.buddiesofbudgie.BudgiePanel.desktop
apr 11 10:05:05 homardlunaire lightdm[4086]: gkr-pam: couldnāt unlock the login keyring.
apr 11 10:05:11 homardlunaire lightdm[4197]: gkr-pam: unable to locate daemon control file
Cheers,
Sil
Appreciate that.
Your /var/crash should have a log file that can be analysed via apport-retrace
Since the crash is reported as āgnome-session-binaryā - I looked at errors.ubuntu.com for 23.04 issues - you mentioned this was specifically when you hit the ādisplaysā tab - so this would be a graphical issue hence the mention of budgiewm which is basically mutter.
The key graphical gnome-session issue for 23.04 over the last week is the gles-helper binary with multiple occurences ā¦ probably from yourself being reported automatically.
https://errors.ubuntu.com/problem/67a0e421dbe0476dee9022ce56bdc553755961b1
So if I was a betting person (ā¦!) this would an area to focus on in the absence of looking via apport-retrace with the log file. Its not budgie specific but would be part of the myriad of X11 issues that 23.04 is suffering with at the moment. Once more people hit the same issue this will be auto converted to a launchpad issue and Canonical will then look at this more closely.