WetGeek Will this affect nfs shares that are mounted in /mnt and linked to my home directory with symlinks?

Depends which permissions you go with for home, if you are the only user accessing it and what permissions you have on the nfs mounts themselves.

Lets assume your username is wetgeek your home folder is set to 751 User wetgeek owns it so they have full permissions for them nothing has changed. User derek navigates to /home/wetgeek/ they can enter but they will see nothing. However they noticed the permissions and remember the folders path. they can navigate just fine to /home/wetgeek/nfsshare/ and everything is normal.

This is due to standard Linux folder permissions being 755 and files being644 The 1 allowed them in your home dir and the standard permissions let them do more. You can of course lock down your own sensitive files further while still having 751 set on the home dir but it is more to consider.

Same scenario but /home/wetgeek is 700 user wetgeek notices nothing different. derek can not enter the folder the end. They could still access it via /mnt/* tho.

WetGeek Should I plan on needing it after I install the new Solus from a new .ISO, or will my having been the one to create the symlinks make that unnecessary?

The file / folders owner has full permission so no further steps are required assuming you are happy with the new default.

      The Dev Tracker takes a different account? Well anyway, on the matter of Firefox VAAPI:

      GPU: R9 270X
      DE: Budgie
      System: up to date - stable

      After changes, About:support shows Compositing:Webrender, however all three line under WEBRENDER_COMPOSITOR are blocklisted.

      There is no VAAPI section.

      After starting Firefox, this shows in the console:

      ATTENTION: default value of option mesa_glthread overridden by environment.
      libva info: VA-API version 1.18.0
      libva info: User environment variable requested driver 'radeonsi'
      libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
      libva info: Found init function __vaDriverInit_1_18
      ATTENTION: default value of option mesa_glthread overridden by environment.
      libva info: va_openDriver() returns 0!<

      When going to the page of the Costa Rica video, which was served in VP9/opus, this seemed interesting:

      Utility 5450: MediaSupervisor #1]: D/PlatformDecoderModule Agnostic decoder supports requested type 'audio/opus'
      [RDD 5448: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Initialising VA-API FFmpeg decoder
      [RDD 5448: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Format vp9 is not accelerated
      [RDD 5448: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: Initialising FFmpeg decoder
      [RDD 5448: MediaPDecoder #1]: D/PlatformDecoderModule FFVPX: codec vp9 : Google VP9
      [Child 5353: MediaPDecoder #3]: D/PlatformDecoderModule Sandbox RDD decoder supports requested type video/vp9
      [Child 5353: RemVidChild]: D/PlatformDecoderModule RemoteMediaDataDecoder[7f4729e8c350] ::RemoteMediaDataDecoder: 7f4729e8c350 is created
      [RDD 5448: MediaSupervisor #1]: D/PlatformDecoderModule FFmpeg decoder supports requested type 'video/vp9'!<

      According to wikipedia VP9 decode wasn't added by AMD until Raven Ridge APU/RDNA discreet, so sure enough it was software decoding. But it looks from the above that at least part of the process worked.

      Mod edit: Fixed link 🙂

      Not having to install the flatpak version of easyeffects anymore sounds awesome. Thank you!

      • [deleted]

      • Post #16

      Introduced EasyEffects for PipeWire audio effects goodness

      That's nice. I was just going to look up how the situation is under Solus, as EasyEffects (formerly PulseEffects) has the legacy maintenance branch for Pulseaudio and the newer one for Pipewire.

      Solus 4.4 Harmony! Yay!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

      Pipewire is activated per default or we have to do something. Because EasyEffects fails to run :

      $ easyeffects 

(easyeffects:480915): easyeffects-ERROR **: 10:04:13.794: 	pipe_manager.cpp:1463	context connection failed
Trappe pour point d'arrêt et de trace (core dumped)

        • [deleted]

        • Post #20

        olivir Pipewire is not enabled by default.

          I'm having some problems with the MATE and Plasma .ISOs. I filed a bug report for the MATE .ISO, and I'll report one for Plasma, too, if I find out that I can't refer to one I've already created. The bugs are identical.

          In preparation for creating a VM, I create a 32 GB virtual disk drive, and partition it like so:

          I need a boot partition in order to do an efi-type boot, and a swap partition large enough for me to hibernate the VM.

          With a disk like this, and choosing to use these partitions to install the OS, I had no trouble at all installing Budgie and GNOME. On MATE and Plasma, however, the boot partition was not recognized and a bootloader couldn't be installed there.

          In the installers, the partitions are assigned to mount points, after choosing to use those partitions, their mount points are chosen on the next page. The swap and root partitions can be assigned to the swap and / mount points, but there is no mount point available for the boot partition. It's used according to its FAT32 format and (with GParted) the boot and esp flags that are set.

          During the MATE and Plasma installations, on the next page, an error message is displayed, saying that a location can't be found for a bootloader, and one must be provided for an efi iinstallation. There's no way to continue. I've double-checked that the disks are created properly, as in the above image, and as a reminder, the Budgie and GNOME installations worked correctly.

          Any advice from the team?

            WetGeek Since you already created an issue on the issue tracker (here, for anyone else that wants to follow along), I would say to watch that for responses. People may have additional questions or thoughts, and it would be good to have that all in one place. Also, if the same issue appears on another edition, you can just add that to the current issue. No need to create a separate one, I would say.

            Also, thank you for filing issues on the tracker, that's exactly what we're looking for! 🙂

              WetGeek an error message is displayed, saying that a location can't be found for a bootloader, and one must be provided for an efi iinstallation

              I plan to continue by allowing the installer to partition the disk, but that will leave me with BIOS-based VMs that can't be hibernated, which is not my customary workflow. I'll need to create new ones if/when this bug is fixed.

                I'm going to abandon the MATE .ISO and try to install the Plasma edition. With MATE, I deleted the partitions I'd created, and let the installer create its own. That seemed to work fine. The bootloader was installed. The next page is shown here:

                That's correctly filled in, my password and confirmation field match, and yet the [+Add now] button and the [Next] button remain disabled, so I can go no farther with it. With a new installer planned, I'll look forward to trying that.

                  WetGeek The icons indicate a problem with the username. Is there an extra space at the end, by accident?

                      @EbonJaeger : Looking at this page again, I notice a different symbol after the line with my user name. Before, I'd only checked the fields to be sure that my user name and the confirmation field agree, which they did here.

                      I don't know what could be wrong with "jerry" as a user name. It's what I've always used.

                      I noticed that Swap Usage in Usage Monitor Raven widget is activated after the last or previous update(s). I am pretty sure I disabled it before.

                      EbonJaeger Is there an extra space at the end, by accident?

                      I'll check it. These text fields should be trimmed in the code to prevent that from happening.

                      EDIT: Yes, that was it, one space at the end. It's now installing. Thanks for suggesting that.

                        I've created four VMs to test the 4.4.ISO files, and I've configured the Plasma VM to be a useful daily driver.

                        • Launched Konsole and tried an eopkg UP, but as expected, there were no upgrades available.

                        • Installed packages I'd need - nfs-utils, micro editor, Vivaldi-stable, aisleriot, kshisen, gnome-mahjongg.

                        • Launched System Settings and adjusted the ones that dim or turn off the screen, and created 8 virtual
                          desktops. Also checked the option to start each session as an continuation of the previous one. That used to
                          be the deault, but it's not in this version.

                        • Accessed my LAN from Dolphin and fetched my bashrcAdditions file and the shares to add to /etc/fstab.

                        • In Konsole, I added bashrcAdditions to my home folder, and source statements in .bashrc to reference it.

                        • In Konsole, I addedthe extensions to /etc/fstab to access my NAS shares.

                        • In my home directory, I deleted all the folders, except Desktop, and replaced them with symlinks to my NAS.

                        • Configured Vivaldi, to include installing LastPass and doing a sync (results in image, above).

                        • Configured Thunderbird with email accounts for Jerry and Wetgeek.

                        • Launched and configured the three solitaire games -- Spider, Shisen-sho, and Mahjongg.

                          Note to @EbonJaeger: I plan on configuring this VM farther (address books and calendars in Thunderbird, named tab stacks in Vivaldi, etc.) but I want to get all the VMs up to this point first. Also, do we have a specific place to document what we've tested, or just put it here?

                        In this setup and configuration, I've run into no errors of any kind, so nothing to log in the dev tracker.

                          The second testing VM I've configured today is Budgie. Since I'm making the initial configurations the same for all four editions, I won't detail what I've tested here -- the list would be the same as in the Plasma message above.

                          I'll point out, for Budgie, that the Nemo file manager looks and works great. It accepts my choice of a dark theme with no problem, and the folders, except for Desktop, are linked to shares from my NAS.

                          As with the Plasma VM, I encountered no errors during any part of this installation and configuration. Congrats to the team!

                          WetGeek Also, do we have a specific place to document what we've tested, or just put it here?

                          `I would say to put testing stuff in the dedicated Solus 4.4 ISO task. Makes it easier to keep track of what's been tested and what hasn't.

                              EbonJaeger I would say to put testing stuff in the dedicated Solus 4.4 ISO.

                              So, just open up the .ISO with ark and put a file in it? A text file would probably be easiest, but least readable, especially with no formatting. How about a LibreOffice document?