Staudey Uhh get this Martina Mariea Schiff and I was born in same hospital
but I was two years early...lol

    I finished the mystery I was reading, so Ii finally got a chance to start on Red Mars. I'm glad to be able to say that so far, I remember nothing of the story, It's been long enough since I read it originally, that it's very much like reading it for the first time. I'd forgotten how long the chapters are.

    Tomorrow I need to take my wife to get a CAT-scan, and I'll take my spare tablet to keep me company in the waiting room.

      WetGeek Happy for you! Nothing better than starting a new binge knowing you have a couple thousand pages between you and your next major literary decision!

      Wish I could do a tablet, as they make all the sense in the world.... but i cant comfortably hold them, and I read fast enough that turning pages distracts and annoys me. I am too attached to the rituals of the legacy book I suppose.

        Phheew, I have been working hard with Inkscape the last couple of days, but it's so addictive. So I've actually been sitting infront of the screen while the spring weather screaming at me to go out. 15 degrees Celsius and lightly clouded.
        Anyway we have a dinner club where I live, where people meet from the neighborhood to eat and socializing - which is every month big event for me 🙂

          4 days later

          Sebastian

          I installed the flatpak version in the meantime 🙂. I can't see any difference in the speed though between the eopkg and the flat. Though the flatpak doesn't follow the theme rules - just had to cope with it until then.
          I have reach the letter K in the apps of my Nordic Gold icon theme for Plasma/KDE - there's a lot of apps starting with K. The most used letter for apps on Linux is C, O and for KDE the K.

            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.