SethStorm666 I too want that model and number of graphics card. I am shopping for a new Mobo to put it on that will handle all the info being evenly distributed across the board. I have been using a AMD RX-580 card for the system for two reasons: it matches the data speeds of the board overall well, and it has many output ports on the back for multiple monitors. When using Linux and streaming with OBS, its very light on the mobo resources and I rest assured their will be no hotspots on the board 🙂

      brent Hey Brent, in Temporary blocking updates thread you write also: windows barely move, runs like poop. Are you referring here to gedit or in general?
      Because I remember that after the week 17 sync you wrote some apps sluggish out of the gate. So I wonder if this is still the case. If so, maybe you are also like me affected from this new GTK renderer introduced in week 17 that might lead to some sluggishnes and graphic glitches on older hardware. You might check this by adding GSK_RENDERER=gl to file /etc/environment and reboot.
      If this has no effect, you can revert changes easily.

          Sebastian
          thanks for checking up on me. here's the extent of my poop: runs like poop, glitchy, sometimes out of the gate but never lasts. I.E. not chronic.
          My lamebrain has a hard time interpreting this behavior---
          hardware? software? ram? all in my head? could barely move librewolf when updating today. but its a flatpak. so should not apply? once in a while choke points where mouse barely moves, processes probably being mega-spawned, sluggish, clock skips time....but 20 seconds? 30? not every day at all.

          all that jibberish ^^ smells like hardware but it also resembles software...certainly started (I think) around the gtkrenderer--great observation.
          It's not aggravating enough or occurring enough for a bug, but I know the poop sometimes is there.
          I will try your:

          Sebastian You might check this by adding GSK_RENDERER=gl to file /etc/environment and reboot.

          and report back. thank you.

              brent No, you can just in terminal do sudo nano /etc/environment and add GSK_RENDERER=gl there.

                  brent Might be that the file /etc/environment didn't exist yet and you had to create it.

                    brent eh didn't see it in /etc

                    As Sebastian said it probably didn't exist yet. /etc is for configuration files supplied by the user, while /usr/share/defaults/etc is where the default configurations sit. One shouldn't modify the latter, as they are managed by the packaging system. That way one can simply delete their custom configs in /etc and the system will fall back to the default configuration. That's the (or one of the ideas) behind stateless configuration.

                        Staudey That's the (or one of the ideas) behind stateless configuration.

                        Thanks for the explanation. I really have to read (any articles the forum would recommend?) about how stateless works. Word of mouth stuff makes me think there are pros/cons and customization would be limited. Same with immutable but that's another thing I haven't read enough about.

                        When budgie/lightdm can accept Wayland I'd love to run Sway over Budgie. I have bspwm experience (muy poquito).
                        the linux future:
                        wayland
                        immutable
                        stateless
                        I have to be proactive methinks.
                        Solus future: All the above ^^ and Moss and we are overdue to retire eopkg. Dear Devs: love the SC the way it is. All the education it gives someone about the package is important. I don't use it for installing anything...so maybe there's that. ALSO within a year or two Solus will reach the decade mark.
                        For you maintainers I'll bet it's been a long strange trip. 😀 ---I'm rambling obviously!

                            brent I really have to read (any articles the forum would recommend?) about how stateless works.

                            https://www.clearlinux.org/clear-linux-documentation/reference/manpages/stateless.7.html
                            https://www.clearlinux.org/clear-linux-documentation/guides/clear/stateless.html#stateless (this one is a bit more dry/technical though)

                            brent Word of mouth stuff makes me think there are pros/cons and customization would be limited.

                            The only con I can think of is that the user would have to create/copy config files on first use. I don't see how customization is limited. In fact it allows freedom of customization with an easy way to roll things back (deleting the user config in /etc) when stuff goes wrong.

                                  Staudey
                                  "The goal of “stateless” is to provide a system OS that functions without user configuration. A system should not require editing of configuration files by the end user before it is functional, nor should it place lengthy and confusing configuration files automatically in user-maintained file system areas (/etc/) by default."

                                  I cannot imagine such a creature until you read the fine print: "before it is functional." I agree. User should not config to make an app work--they can config til their heart's content after its up an running.
                                  Here's the part that confused me:

                                  "The user should create configuration files as needed and avoid modifying distribution provided defaults. The filesystem folders and all content under /etc/ and /var/ may be modified as needed, but the content under /usr/, /lib/, /lib64/, /bin/, /sbin/ should never be modified, and will be overwritten by swupd(1) as needed."

                                  Don't we already have user & sys separation? What's new about this concept? My icons, themes, configs all exist in /home and in/root. Are they just saying that elevated privileges will be restricted for sys files?
                                  because?"
                                  "To modify system service configuration (systemd(1) service units), the user should not touch or modify unit files under the /usr/ file structure directly, as changes in those files will be lost after a system software update with swupd(1)."
                                  anything reckless you do in /root will be reset next rolling sync?
                                  Great reading. Over my head a little but I'm a fast learner.

                                      brent Don't we already have user & sys separation? What's new about this concept? My icons, themes, configs all exist in /home and in/root. Are they just saying that elevated privileges will be restricted for sys files?

                                      Not everything supports per user configurations in a /home/$USER directory. Services like samba, ssh, mdlna etc you can not set per user configurations of the service, it makes no sense for this to be an option. The administrator controls the config in /etc/ that is you on your system but that is not how it works on other multi-user systems.

                                      The problem is if system wide configurations are in /etc/ and default configurations shipped by the distribution which I think we can all agree are a good idea are in the same location what happens when the package is updated?

                                      The config file is part of the package so it is going to overwrite it or the package manager must have added logic to prompt the user to make a decision about which configuration file should be authoritative and if the user choses the wrong one or like most computer users lose the ability to read when an error appears, they're in for a bad day.

                                      Since those options suck we ship our "sane" defaults to /usr/share/defaults/* which users should not touch and leave /etc/ to the administrators of the system (For the most part, still 162 packages installing files here).

                                      Samba is somewhat unique among other stateless configurations on Solus and has other benefits that allow Solus to ship sane, more secure defaults and combine it with user provided changes at the same time, but no one asked and I'm rambling so... moving on.

                                      brent anything reckless you do in /root will be reset next rolling sync?

                                      No. /root is the root users home directory a user that is disabled by default on Solus and most modern Linux distributions.

                                      Contrary to popular beleif /usr/ does not stand for User it stands for Unix System Resources. If you want to be strict, users should not be messing with /usr/ - I don't follow this strict seperation of user and system space, its okay~ but you need to be careful. If in doubt and want to add something to /usr/bin/ that you have manually downloaded, add it to ~/.local/bin/ instead, that is actually all yours and will be added to $PATH when the directory exists.

                                            Harvey Contrary to popular beleif /usr/ does not stand for User it stands for Unix System Resources.

                                            If I remember correctly that's a backronym and it originally actually stood for "User", but I can't find a good source for either claim atm.

                                            edit: Still haven't found a source that says it directly, but:

                                            "In particular, in our own version of the system, there is a directory "/usr" which contains all user's directories, and which is stored on a relatively large, but slow moving head disk, while the othe files are on the fast but small fixed-head disk. "
                                            https://www.bell-labs.com/usr/dmr/www/notes.html

                                            "A person is either the name of an entry in the directory
                                            /usr, in which case the mail is sent to
                                            /usr/person/mailbox, or the path name of a directory, in
                                            which case mailbox in that directory is used."
                                            https://www.bell-labs.com/usr/dmr/www/man12.pdf

                                            All the entries in the "User-managed Software" part of the Unix 7th Edition manual have a /usr path
                                            https://www.bell-labs.com/usr/dmr/www/man61.pdf

                                                Staudey

                                                Yeah. FreeBSD held on to this for a very long time.

                                                The pw(8) and bsdinstall(8) programs now create home directories for users in /home by default rather than /usr/home.

                                                Source: https://www.freebsd.org/releases/14.0R/relnotes/

                                                The Filesystem Hierarchy Standard frustratingly never states what /usr stands for but it probably was User at some point. It still is mixed usage because /usr/local is still part of the standard.

                                                The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated.

                                                Source: https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#usrlocalLocalHierarchy

                                                EDIT:
                                                History of why home was moved out of /usr https://www.pixelstech.net/article/1477109665-Unix-directory-hierarchy-history

                                                  @Harvey @Staudey

                                                  Wow I've spent some time with this reading---I'm becoming a student of unix history!
                                                  "Ken Thompson and Dennis Ritchie created Unix on a PDP-7 in 1969? Well around 1971 they upgraded to a PDP-11 with a pair of RK05 disk packs (1.5 megabytes each) for storage."

                                                  good god it basically stayed that way thru the 80s-90s didn't it? I mean a handful of MBs always got the job done.
                                                  The hierarchy reading fascinating too

                                                  The following is also a nice resource with some background information that describes the FSSTND ("Filesystem Standard", precursor to the Filesystem Hierarchy Standard or FHS)

                                                  https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/index.html

                                                  /usr usually contains by far the largest share of data on a system. Hence, this is one of the most important directories in the system as it contains all the user binaries, their documentation, libraries, header files, etc.... X and its supporting libraries can be found here. User programs like telnet, ftp, etc.... are also placed here. In the original Unix implementations, /usr was where the home directories of the users were placed (that is to say, /usr/someone was then the directory now known as /home/someone). In current Unices, /usr is where user-land programs and data (as opposed to 'system land' programs and data) are. The name hasn't changed, but it's meaning has narrowed and lengthened from "everything user related" to "user usable programs and data". As such, some people may now refer to this directory as meaning 'User System Resources' and not 'user' as was originally intended.
                                                  https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/usr.html

                                                  But it gives no additional source for that claim.

                                                  One more thing I could find is this: https://marc.info/?l=openbsd-misc&m=127276011001745&w=2

                                                  But that mostly just says what we already know (that user directories were located in /usr). Once again only circumstantial evidence for the origin of the abbreviation.

                                                  Then there is that one Rob Landley mail, which is also mention in the "Unix directory hierarchy history" article Harvey linked, which confidently claims:

                                                  When the operating system grew too big to fit on the first RK05 disk pack (their
                                                  root filesystem) they let it leak into the second one, which is where all the
                                                  user home directories lived (which is why the mount was called /usr).
                                                  http://lists.busybox.net/pipermail/busybox/2010-December/074114.html

                                                  I suppose Thompson and Ritchie just saw it as self-evident because I can't find any direct quote or note from them describing the name choice. I could've sworn I saw something like that at one point, but I certainly can't find anything now.
                                                  All in all I'm pretty sure /usr meant "user" in the beginning, and because that is confusing with how those directories are used nowadays someone coined the "Unix System Resources" backronym to draw attention away from the original meaning and have people focus on the (new) de facto meaning of the directory.

                                                  Sebastian No, you can just in terminal do sudo nano /etc/environment and add GSK_RENDERER=gl there

                                                  been two days. not a glitch. but sometimes it goes many days without a glitch. but nothing 'slow out of the gate' either. so time will tell. I think it made a difference to add the gsk, though.

                                                  thanks again. p.s.---how do you know all this stuff? 🙂

                                                      brent Well, I don't know that much. Most things I know is because I was experiening an issue and googled and found something out by accident. Same with this issue. With introduction of GNOME46 my system began to behave weird. First I ignored it and thought, well, someone will solve it. Then it persisted and I did some research.
                                                      To be sure you can wait maybe a week. Then, when no strange behaviour occured, undo it by running sudo nano /etc/environment in terminal and put a # before GSK_RENDERER=gl,save and reboot and just observe if strange behaviour returns. Then you can be pretty sure that you found the source of your weird behaviour.

                                                        Sebastian Thanks for starting this, Sebastian! It's great to have a designated space for off-topic chats within the forum. I agree, it's nice to see the community come together and exchange ideas beyond Solus-related topics. Let's keep it light, respectful, and enjoyable for everyone. Looking forward to seeing where this experiment takes us!