|Use Case:||Commercial and high security use|
Maybe it would be a good idea to add this approach to the Help Center. So anyone can search for "automount" on Solus and will find that approach.
removed obsolete command in install section (from testing)
Updated on GitHub, but this is almost certainly a bug with librsvg rather than numix-icon-theme; the height and width attributes are optional in the SVG spec (default 100%, with us controlling size via viewbox). We can add a width attribute to any SVG file missing them in Numix to work around the problem for now, but that should only be a temporary fix until librsvg fixes whatever the problem is on their end.
The root cause has been determined upstream. The file /usr/share/icons/Numix/scalable/actions/system-shutdown-symbolic.svg apparently was missing a width attribute, and all of a sudden that seems to have become a problem with librsvg-2.52.0. See: https://github.com/numixproject/numix-icon-theme/issues/1405.
Did some additional testing. I used zram-perf to bench zram modifying as required and then modified it again to bench a swapfile on a sata ssd.
Please update your information in accordance with https://getsol.us/articles/packaging/request-a-package-update/en/
Thanks @pillmuncher for filing the issue upstream at https://github.com/numixproject/numix-icon-theme/issues/1405
@algent: Thank you so much. That fixed it for me, too. I've opened an issue on the Numix github: https://github.com/numixproject/numix-icon-theme/issues/1405
@JoshStrobl I found that the issue is with librsvg.
I downgraded librsvg from 2.52.0 to 2.50.7 and rebuild adwaita-icon-theme version 41.0 against it.
Then installed adwaita-icon-theme. After this system-shutdown-symbolic.svg icon from Numix theme is loading fine.
Sorry, by "missing" I didn't mean to say "missing in the file folders", but "icon file exists, but icon isn't shown on the panel".
Is this an issue with our packaging of numix itself? Given the discussion on the forum post.
@algent Is this an issue with our packaging of numix itself? Given the discussion on the forum post.
This should really be reported to the respective icon theme developers. They need to add the icon, it isn't on Solus (or Budgie for that matter).
I don't know how to rebuild like @chax, but can confirm my redshift is broken https://discuss.getsol.us/d/7444-redshift-help-please
If you're open to an alternative approach (= workaround), I've had success with configuring systemd automounts too. The trick seems to be to configure systemd to have an unlimited timeout for the units in question.
@TClark77 we need the new usysconf for that.
Agree, with @Adrian-Turjak we need some tooling. ClamAV cover some aspect but not all and since Solus is unique it would a bit more difficult to get another solution.
Also, the systemd unit is created, but not enabled. Given that the purpose of autofs is to automatically mount a filesystem at startup, I recommend making the install of autofs enable the system unit and start autofs