This project is to enable issues to report issues or specific feature enablement for existing software in the Solus repository.
Round of applause for @joebonrichie! 👏 👏 👏 👏 👏
@Jacalz no worries. Keep up the good work with Brave :P
Back from the dead. Everything is rebased and rebuilt. Plan is to push it next next Sunday (touches wood). Will re-validate everything over the coming week.
How do we get this updates ?
They are available now where you normally get the Solus iso: https://getsol.us/download/
How do we get this updates ? Do we have to install the OS again or we can run a command that upgrades everything ?
Pushed to shannon.
Alrighty, I'll get this fixed and pushed out to stable repo. Thanks for the report!
@Schykle Could you try installing alsa-plugins and restarting your system? Seems I might need to add alsa-plugins as an explicit rundep of audacity if that turns out to be the issue.
@Girtablulu Can you take a look at this please?
Solus 4.1 Released and now with a Solus Plasma Edition 🎉
Okay just changed the date, guess that works.
I can't stop this countdown help xD
WE WERE EARLY OMG
Fri, Jan 24
@Timalex Not a problem, thank you for the additional test results with it written in dd mode. Interesting that you're specifically having issues on NVIDIA + 144hz. I'm going to guess this is either a nouveau issue, Xorg itself, or something in the kernel. At least we can safely rule out it being Mutter, given you had the issues on Budgie, GNOME, and MATE (which doesn't use Mutter).
I installed Solus from new Budgie ISO on the laptop with Ryzen 7 3700U and integrated Vega 10. Laptop utilizes UEFI, OS was installed on the whole SSD using default partition settings (no dual boot), Secure Boot was disabled. ISO was flashed on the USB drive using dd.
If it helps to know, my Navi setup was tested with GPT, UEFI, 120 Hz monitor, CSM disabled.
What a fool I am. I haven't used Windows for years and apparently forgot that little crucial step.
Sorry about that. Trust me it's more than a little frustrating.
Rufus was used to simulate a user coming from Windows. Written in ISO Image mode (Default).
The data is in
|GPT||UEFI||144||Corrupted boot log||Disabled|
|GPT||UEFI||120||Corrupted boot log||Disabled|
Thu, Jan 23
@rjurga Thank you for testing the other ISOs. Much appreciated.
Booted all the ISOs successfully on my Ryzen 5 3600 and RX 5700 setup. I didn't test installation with Gnome and Mate. Everything seems to run fine in the live environment, not much to report compared to Budgie.
Seeded out GNOME and MATE testing ISOs. Thanks again to everyone that has tested and provided feedback. For those that emailed and have not seen a reply, I do appreciate you all reaching out and fortunately much of the hardware that you all have generously volunteered is already receiving test coverage either by existing testers or Core Team / Global Maintainers. If I see anything that sticks out of course, I'll send out an email.
Known issue with the Spotify server, nothing we can do about it. Issues in Third Party mechanism are also known and won't be addressed until the Software Center rewrite.
Can you check if you have them installed and maybe reinstall them?
@paracetamol We have heard and understood your argument and will take it under advisement for the next development cycle for the installer.
! In T8592#163570, @JoshStrobl wrote:
It's not even stupidity. Those are extremely likely to be the most popular languages. The UX in that section makes sense. I have absolutely no reason to desire for it to be changed.
"Never attribute to malice that which can be adequately explained by stupidity." - Hanlon's razor
Wed, Jan 22
Because Ikey borrowed it from gnome-initial-setup ages ago and never changed it. They still do it the same way:
First, I strongly suggest the next release to be called Solus 4.0.9999.
On Dell XPS L421x (2012) with i5-3517U, GT630 and 2 hard drives:
- Installation alongside Windows 10 went fine and super fast (3minutes excluding partitioning),
- Udisks was the only broken package (I know it isn't actually broken, but eopkg's derp)
- Swap was not created. The space for Solus was tiny (15GB), but was this really on purpose? I wouldn't use a system without swap
- The installer only saw 1 ESP, which was on the other drive to which it automagically suggested to install the system (suggested automatic install on Windows drive, but bootloader in Solus 4.0's ESP). I know you know about it but is no less problematic, especially in laptops where you can't just take the drive out.
- In CLR-Boot-Manager the system name is still Solus 4.0 Fortitude, don't forget to change it for the final ISO.