• Support

  • Solus Budgie GUI useless after today's update

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.

    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.

    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 ❤️

    adurante Problem reported and solved in 2 hours

    Would have been faster, but I kept running upstairs and downstairs between the computer with the problem and a computer without the problem, so I could chat with the forum. 😁

      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!

        I'm currently on my laptop, today's update worked flawless on that. But on my desktop I end up getting booted in to emergency mode. I checked for the virtualbox-guest-common package and removed it. I rebooted the pc and I get returned to emergency mode again.

        JoshStrobl spacebar to get list of kernels worked. At least for signing in. Was able to get into the OS by selecting 'current' then changing to default and updating clt-boot-manager.

        however will keep the LTS since that was previously the only one that worked a few months back following another update

          Hi everyone, I'm having a very similar issue, however, removing the virtualbox-guest-common package didn't work. My laptop still cannot start the GUI. Any help?

          Here is my dmesg output: https://hastebin.com/oraleriqok

          24 days later

          JoshStrobl As of today I also have this problem on an ASUS laptop with Intel graphics. Switched to the terminal and ran an update with sudo eopkg up , which installed several packages. Then removed virtualbox-guest-common but this didn't resolve the problem. Only adding the srbds=off kernel parameter helped booting into the GUI.

          Note: the laptop was running fine yesterday and ran an automatic update. Today it rebooted the first time after the update.

              bolofar I have the same issue.
              When changing kernels from lts to current, it automatically switches bach to LTS.
              So in order to boot I have to switch manually every time from lts to current.

                I think removing LTS is a feasible solution.
                My desktop PC without an LTS Kernel runs flawlessly.