Solus 4.8 Opportunity Released

BuzzPCSOS

Lucien_Lachance Looks like it is in the pipeline but not there yet. Link

Solarmass

BuzzPCSOS Looks like it is in the pipeline but not there yet. Link

I hope it won't be enabled by default. I dislike offline updates very much.

mdst77125

excelent is a amazing new version, gnome look very good

LNC

alfisya I tried it, it shows a blank screen and won't proceed to login. How can I fix it ?

AlphaElwedritsch

German Press
https://gnulinux.ch/solus-4-8-opportunity

banger

Plasma boots on both my machines with Nvidia cards, interesting to note that if you select nomodeset it gets stuck at flashing cursor.

Harvey

I would expect nomodeset to always work but the option only exists for users with a video card that does not play nice with the open source driver. Hopefully getting them installed so they can reboot, drop to a tty, install the proprietary driver for their card, reboot once more and have a working system.

Its been awhile since I used a nvidia video card, but I never needed this option.

banger

Harvey drop to a tty

What's the login and password for the live tty?

TraceyC

jmdennis After that discover would not longer launch.

This is a known issue - see our list of Known Issues for the workaround.. This will need to be solved more permanently by KDE.

Harvey

banger
username live, no password.

penny-farthing

alfisya

For me (and apparently for @LNC ), it's... GAME OVER! 😰

Indeed, after reading @EbonJaeger 's post announcing the release of the ISO images for the new Solus version 4.8, I learned from @Harvey that the Solus logo can be displayed during boot by installing the plymouth package.

Unfortunately for me. so, I installed it, then I restarted my computer.

I briefly glimpsed the Solus logo below the Gigabyte logo, my motherboard's logo. Then the boot process stops with the message "Broadcast message from administrateur@solus-pc on pts/1 (Mon 2025-12-041 00:41:10 The system will reboot now!"), which never happens.
When I turn the computer off and then back on, the boot process stops, sometimes on a frozen screen (either white or black, in both cases with colored dots, or large, distorted blue, gray, and black stripes).
This means that, as of today, I can no longer access Solus. I am writing to you on the forum from a live USB of version (Budgie) 4.6.
I should also add that I created a bootable USB drive of version 4.8 of Budgie using Rufus under Windows.
The result is the same as described above. It seems to stop just before displaying the login screen.

This has been going on for over 5 and a half years now, I've been using Solus as my daily operating system, and I really don't want to switch anytime soon.

What can I do? Is it still possible to restore my Solus configuration without having to reinstall it? And if so, how do I do it?

Thank you in advance for any help and advice you can offer.
Best regards.

banger

penny-farthing What can I do? Is it still possible to restore my Solus configuration without having to reinstall it? And if so, how do I do it?

Drop to tty when the blank screen appears (ctrl+alt+F3), login at the prompt with your username and password then run sudo eopkg rm plymouth and reboot

penny-farthing

banger

Thank you for the suggestion.

I also tried that (like Ctrl+Alt+F2 or Ctrl+Alt+F4, for example), and each time I end up on a black screen that doesn't give me the option to log in. What bad luck...

I can see my partitions in GParted: /dev/sdb1 contains my personal data (I can access to it with Nemo on the live USB), and /dev/sda6 contains Solus, but I don't see how to access it.

pomon

penny-farthing At system startup, when the boot menu appears, press e, and at the end of the line add a space followed by systemd.unit=rescue.target
Then press Enter.
When it finishes loading, enter the root password.
Uninstall Plymouth with: eopkg rm plymouth and reboot

On my Dell, pressing the spacebar a few times shows the boot menu.

penny-farthing

pomon
LNC

Thanks to both. It's reassuring to know that by posting on this forum, you'll find one or more people who will offer a solution (or even more) to your problem. 😃

However, having been unable to achieve the desired result with your suggestions, I finally found what I was looking for with a help page on Solus titled "My system doesn't start after an update":
https://help.getsol.us/docs/user/troubleshooting/boot-rescue/system-not-working-after-update/
and here is the result:
https://0.0g.gg/?9cc4cb27e03e0e3c#7zFh1zQUSUmXJCJtfWEWwXk3Jj3c4etHPeNLYLNy4M6:~:text=https%3A%2F%2F0%2E0g%2Egg%2F%3F9cc4cb27e03e0e3c%237zFh1zQUSUmXJCJtfWEWwXk3Jj3c4etHPeNLYLNy4M6

It's still amazing that such a package could disrupt a computer's restart to this extent.

LNC

Dropping to tty didn't work in my case so I solved my issue by uninstalling plymouth through a live USB key:

fdisk -l
mount /dev/[solus_partition_id] /mnt
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --rbind /dev /mnt/dev
chroot /mnt
eopkg rm plymouth
reboot

TraceyC

Could I ask penny-farthing or @LNC to create an issue on the tracker for the bug caused by plymouth so we can look into it? Thanks.

Moltes34

New Solus Plasma pour moi ..... merci beaucoup

penny-farthing

TraceyC

That's done:
https://github.com/getsolus/packages/issues/7234

irondave

It would be great if after installing on a dual boot system I could choose between the different systems without having to mess with anything.

TraceyC

irondave It would be great if after installing on a dual boot system I could choose between the different systems without having to mess with anything.

It's unfortunate that sometimes, installing Solus after another OS / distro results in all of them being in the boot menu, and sometimes it doesn't. In order for us to improve anything, we need an issue created on the dev tracker.

I had created one to Improve installing Solus as dual boot with Windows system using a separate drive. If you have a different problem, please create a new bug report. Thanks.

« Previous Page