- User Since
- Jan 6 2017, 4:52 AM (280 w, 6 d)
May 13 2020
@kyrios123 I've been having the same issues and attempted all of the solutions above (reinstall and config/cache/share files deletion). I don't know if it worked for @lavadrop but it didn't solve the problem for me. Do you have any suggestions on how I can provide better diagnostic data?
May 22 2018
May 18 2018
Please pardon me if this is regarded as a duplicate.
Hey thanks @kyrios123!
Feb 19 2018
@DataDrake Does that offer to help someone build this from source still stand? If not, anyone else have any tips?
Nov 30 2017
Sep 6 2017
Jul 17 2017
@kyrios123 What you're describing, in terms of hiding non-GUI applications and categories, is what I was proposing with the "Advanced" toggle on the bottom right. I think that would really make the Software Center more user friendly, even for advanced users who are just browsing. I wouldn't default to sorting by most downloaded, but probably alphabetically, for the reasons you've described.
These are the noteworthy changes, plus some brief explanation:
- Font to Roboto and other typographical tweaks. It sounds like Roboto will be one of the defaults on the next release, and it just renders better, so I changed that out;
- Added package sorting. It would be nice to not only sort alphabetically, but by the most downloaded, newest, etc. I know there are some privacy concerns about counting downloads, but I'm sure this can be done in a way that respects the privacy of users, while also providing a mechanism to see what is most popular. This view will probably not be so useful when libraries end up rising to the top, but perhaps in conjunction with the prior suggested advanced view toggle that would hide such packages;
- Added number bubbles to Updates and Queued. Just seemed like a good indicator add, and a way to make it more intuitively understood that all of the items in the queue can be found in one place, rather than just nested in their categories;
- Added global refresh button. Placed this in a relatively prominent location, for hopefully obvious reasons;
- Simplified "Community Pick" styling/behavior. Consistency is good. In this case clicking on the icon/text will go to the package, and the download button displays and animates as do list items;
- Removed payment related elements. Mainly to remove confusion. Prior mockup demonstrated that it would fit without too much trouble in this layout if added later;
- Moved search icon. Tough call, because this whole thing started with search being super prominent, however placing it where it was introduced some interface collisions. Placing it at the top will bring it inline with Nautilus, with its behavior mirroring that as well;
- Other minor color tweaks. Added a different default package icon that is square. Made the installation status bar a little more obvious.
Jul 14 2017
@dan_ I think what will end up being the most efficient method is to immediately begin installing (or uninstalling) upon the click of the first item, and automatically queuing subsequent operations. Upon thinking about it harder I could not come up with any reason to batch an operation (i.e. click a bunch of checkboxes and initiate it with another click). If you have a use case for doing so for which that is preferable, I'm interested to hear more about it.
Jul 6 2017
@kyrios123 What @JoshStrobl said. Just a placeholder for a possible inclusion at some point. I'm just presenting ideas. Eventually Solus will be popular enough people will want to sell their software on it, right!? ;)
Brief explanation found here: https://plus.google.com/u/0/105767379162162441315/posts/67gR1NYG56m
Jun 30 2017
@sunnyflunk Just installed from unstable and no more crashes. Looks like you've fixed it. Thanks!
Jun 29 2017
Jun 15 2017
Just FYI, I posted a modest update on Google Plus here: https://plus.google.com/105767379162162441315/posts/59jpvtVw3Jy
Jun 14 2017
@ikey I think I've isolated the issue. If I add the intel_iommu=off kernel boot parameter in GRUB I am able to boot on the current kernel without any errors or wireless issues. There is an unresolved Ubuntu bug report for the same problem with the same hardware: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634108
Jun 12 2017
@GrisuProjects As a part of this task please review the additional concept and comments found here: https://plus.google.com/105767379162162441315/posts/D4PFU8rzLeg
Jun 7 2017
@sunnyflunk Same error after reinstall.
Jun 4 2017
Jun 2 2017
@Barksten I am able to switch in the GRUB menu during boot. I have to be careful not to update when connected over ethernet on the bad kernel, otherwise the older kernel that works would get deleted. If yours is already deleted I don't know how to install a prior kernel manually.
By the way, I attempted to boot with the irqpoll option. It cleared up some of the errors, but did not remedy the wifi problem.
@ikey I haven't added one, nor are there any files in that directory (just the install.d directory)
May 30 2017
May 17 2017
Feb 23 2017
Feb 18 2017
@DataDrake Just wondering what would need to happen in order for something like this, designated as a "Wishlist" item, to end up in the repository. I know there is limited capacity doing this work, and I'm grateful for the donated time put into this stuff. But since it is has been over 5 months without any movement, and I'm not capable of doing the work myself, I'm trying to figure out what can be done so I can put my machine into production use. Will flatpack integration solve the problem? I'm donating to Solus, and I would be willing to donate more if I knew these important elements would be added. Or is a better avenue to find someone I can employ specifically to work on it?
Feb 5 2017
Found this solution on the forum to solve a similar problem I was having, which was to install xbacklight:
Jan 25 2017
Nevermind. Confirmed elsewhere (https://plus.google.com/105767379162162441315/posts/QNc8rLTsuxN). +1 for CUDA support in Solus.
Prior information (https://plus.google.com/+Solus-Project/posts/HZq9fjHEWgJ) made it sound as if CUDA was included as part of the packaged Nvidia drivers. It sounds like that is no longer correct. Will someone be kind enough to confirm that so I know whether this is the end of the road for solving my Blender GPU issue?