Solus Budgie GUI useless after today's update
WetGeek Save it on hastebin and paste the link here. https://hastebin.com/
WetGeek When you paste some text on hastebin and then save by clicking the floppy icon or pressing CTRL+S you should get a link like https://hastebin.com/isinuzituc which links directly to the pasted text
Thanks. That's a pretty cool service.
Another suggestion for testing if it is Intel SRBDS mitigation related, boot your system then spam the spacebar until you see the kernels listed. Press e and you'll see a input at the bottom of your screen. Type srbds=off then press Enter.
sebastian-brandt Any chance I can see your dmesg as well?
JoshStrobl you'll see a input at the bottom of your screen
Done. Not sure what you meant by "input at the bottom" but what I saw there was initrd. I didn't know whether I should enter srbds=off before or after that content, so I tried it both ways.
Neither attempt apparently did anything. Reboot and login the same as before, then the bottom panel displayed and the screen went blank.
DataDrake https://hastebin.com/giqutayula.coffeescript
Noticed it doesn't happen all the time I restart but about 7 out of 10 times for me.
- Edited
DataDrake Please remove virtualbox-guest-common. You don't need it
YES! Rebooted and logged in normally. A long time ago, I tried to run a Win10VM on that machine, but not since.
EDIT: I'll make sure that it isn't on any of the other Budgie computers here, before attempting the updates.
Here my dmesg output on my laptop after I installed virtualbox-guest-common and thus caused the same failure: https://hastebin.com/libibetoru.md
@WetGeek You don't need the guest-package when you host a VM on that machine, just when Solus itself is inside the VM
sebastian-brandt Can you try removing virtualbox-guest-common as well? Independent testing points to it as a culprit.
DataDrake After removing virtualbox-guest-common it works again. Thank you!
- Edited
Staudey You don't need the guest-package when you host a VM on that machine
Thanks for all your help. 99.9% of my experience with VirtualBox (years of it) has been on Windows. I was accustomed to updating the guest additions every time I updated VirtualBox. That's probably why I installed it in the first place, in case it was needed.
Other than using it at work, most of what I did with VMs was distro-hopping. I'm done with that, now that I have Solus.
EDIT: And that thanks goes to everyone who helped with this.
- Edited
Hi there, I just thought I have the same problem. I have installed solus on an external USB SSD. I boot it on a notebook with an Intel GPU as well as on a PC with an AMD GPU. On both devices I had no GUI.
Then looked into lsmod and saw there's no amdgpu loaded. After that I saw it bootet an old kernel 4.9.210 although I don't have linux-lts installed. I tried clr-boot-manager update but It still booted kernel 4.9. I had to manually select 5.6 on the boot menu. Now I removed the old kernel from /boot/EFI/com.solus-project. Now it's working fine.
I don't know why there was still this old kernel in the boot folder. Just in case someone has the same problem.
- Edited
Just a follow-up: A regression in VirtualBox crept back in and it appears to be what is causing the issue. @DataDrake is removing that applicable code from VirtualBox and will be pushing the update to stable as soon as possible. Thank you all for being so quick to report the issue and provide information that helped us narrow it down (including all the folks in IRC). You're all amazing 
Problem reported and solved in 2 hours. BestOS continues business as usual
- Edited
Fix deployed to stable. If you come across this issue, please just run sudo eopkg up after logging in to a TTY. This can be accessed using Ctrl+Alt+F1-F7 (pick one, shouldn't matter unless you hit the graphical TTY).
If you are unsure if you're affected, double check for virtualbox-guest-common after doing an upgrade. You can check if you have it installed by running sudo eopkg info virtualbox-guest-common. If you have it installed, will show "Installed package:" then list the details.
If you have it installed and it is 6.1.10-159 then you should be fine and no intervention should be necessary (you can safely reboot). If you don't have that version and you haven't rebooted yet, just check for updates again and you should see some virtualbox ones. If you don't have any virtualbox guest driver bits installed, you should be able to safely ignore all the things and reboot as usual.
If you have no need for anything related to virtualbox, you can remove virtualbox-guest-common as well!
If you have any further issues related to booting / reaching the graphical session after getting all your updates, please report it so we can take a look as soon as possible. Thanks!