bigrammy Update firmware is basic for any distro and should be bullet proof and newb friendly so If I was Solus I would ditch Discover and revert back or advance solseek.
I agree that updating firmware should, in an ideal world, "just work". As a software tester, I wish all core software would "just work", but software is complicated (and I therefore have a job). That isn't the cause of the Discover crash.
By "revert back" I assume you mean to Solus Software Center. We have no plans to do that, as sheepman explained in this other post, for technical reasons. Porting it from python2 to python3 and fixing the horrible old code would be a ton of work. We can more effectively use our time to improve other things in Solus and fix bugs in code we control.
There's something else I would like to share. The Solus team is unusual in the distro world for working with upstream. This means that we file bugs and merge requests with KDE, GNOME and other software we use in our distro. I learned this at the last Akademy from someone who works with multiple distros and desktop environment projects.
What this means for users of Solus is that we work harder for you than other distros - by bringing features and bugs to the attention of other projects, like bugs in Discover. In fact, we have been directly responsible for a couple of features in Discover. @EbonJaeger merged work to show the "Hardware Drivers" and @joebonrichie merged the work to show the "Fonts" section.
I'm going to get off my soapbox now and ask that this thread stay on topic of the original post. Feel free to post opinions in the Feedback topic.
