This tag is for tasks that do lack an assigned project.
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.
Thu, Sep 23
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.
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
Tue, Sep 21
The PKGBUILD in the AUR is also adding this dedicated directory.
Mon, Sep 20
Fri, Sep 17
you're right. I took a quick look at the Makefiles and they intentionally put them to /etc/ - I don't know. But it would nice to change that. I've found the PKGBUILD of ArchLinux. They do the same, I think: https://github.com/archlinux/svntogit-community/blob/packages/apcupsd/trunk/PKGBUILD
Mon, Sep 13
ffmpeg-chromium is shared between opera, vivaldi-snapshot and vivaldi-stable. Unfortunately there doesn't seem to be a single version of ffmpeg-chromium that supports all three for the time being.
@joebonrichie thanks for the promptly reply.
Can you try and install the old version of ffmpeg-chromium and report back? sudo eopkg it https://packages.getsol.us/shannon/f/ffmpeg-chromium/ffmpeg-chromium-88.0.4324.192-10-1-x86_64.eopkg
What I need is the ability to do #include <emscripten.h>, and I think that is not affected by emscripten's version.
I could build and run the linked example without the need of copying or symlinking, perhaps what you've experimented with probably another project was because of the version of emscripten was too old. I'll try to update it this week.
Sun, Sep 12
In the meantime, if you can also upgrade emscripten to its latest version, that would be fantastic ^_~
@YakoYakoYokuYoku At least to my knowledge, it also affects the JS output, so that you can directly call a function in JS on the .js output file using its original name.
I'll do the job by myself, thanks. But isn't the purpose of the Emscripten headers only for WASM output.
Thu, Sep 9
i've also been getting another type of crash, much more like this one...
Wed, Sep 8
I can tell that my battery life time has been gone down from about 8-10 hours to 1-2 hours in the last months. So I'm experiencing this as well.
Tue, Sep 7
Tue, Aug 31
@Staudey Yes, exact same setup (software-wise) as on my notebook.
Mon, Aug 30
Do you use Only Office on your iMac as well?
@coffee_bean In this case you clearly ran out of memory. It seems like you have at least 13 Only Office processes running there. (oom-kill also nuked one of those when you ran out of memory)
I would have to observe that, crashes/freezes are so frequent now that I find it hard to make out a pattern. I almost always have some music running in the background. However, when that particular crash happened, I had been running a Youtube video on repeat for three hours to find out whether it might have to do something with media playback. Unfortunately, I haven't been able to reproduce the issue. FUN FACT: My laptop actually crashed while typing this just a few minutes ago. No media playback going on. I am getting sort of desperate and am seriously thinking about moving on to another distribution although I really love Solus :/. Latest crash log looks like this:
Sun, Aug 29
really just a guess, but i notice....
nearly; thats the start of the journal, from when the os boot starts.
Sat, Aug 28
when you NEXT login, after the issue, check the previous boots journal?
Fri, Aug 27
Thu, Aug 26
printrun, mypaint, displaycal reply on py2 numpy. Printrun is on rc8 for py3 support, mypaint has an update available for py3 but is blocked by gimp and displaycal is seemingly never going to receive py3 support.
Aug 25 2021
This should be fixed with a rebuild of ffmpeg. Probably other revdeps of libvpx might be affected by this?