@joebonrichie I stumbled upon this while running into the same error so I just wanted to add the additional info you asked, I was testing with some OpenVPN config files and running into the same error so I believe these are required as a part of qomui itself rather than just the wireguard component

@alecbcs I noticed 1.7.5 was released a few days ago so I just wanted to bump this in case you think 1.7.5 is safe to upgrade to

It seems that has fixed the issue on my system!

I can confirm that the command sudo unlink /usr/lib64/haswell/libopenblas.so. 0 fixes the issue on my machine.

After some googling, I don't think that would relink the other openblas library.

@Voltti I am also bad at Linux but trying to learn :)

@joebonrichie and @DataDrake

Just dropping this, It seems earlyoom is still being actively maintained by the author and Pull Requests are still being accepted. I don't know if this counts as enough "movement" for the Solus Devs but wanted to drop this note anyway since I wasnt sure when I created this request if the package was being actively maintained or not.

@kccit and @serebit these might be good shouts. My machine has an Intel 8770k. However the VM initialized by the same machine does not present this issue. Idk if possibly that is becuase of it being a VM or if it means something else

Alright, for me:

@kccit and @gs and @auspicrypt

If this VM is not a work machine (I. E. If you kill the VM and have to reinstall it wouldn't be a big deal) could you try running @joebonrichie 's commands from above regarding glibc?

@joebonrichie I have been trying to break my VM install of R so that I can attempt this fix on my VM rather than my work machine but I have been unsuccessful. Do you know if there is a way to copy the entirety of my work machine's R install to the VM (in theory bringing the bug with it) so that I can attempt this fix there?

I may have misunderstood but I ran your above command and here is the output:

Soooo. On a completely brand new solus OS 4.0 budgie within a VM with R installed all the tests succeed.

Alright, well, I purged my entire R install of all packages, then removed R and Rstudio via the software center, and then deleted their directories as sudo.

@gs could be completely unrelated but I just thought of this. Reinstalling R does not purge other CRAN packages. It is possible one of them may have corrupted the stats package.

@gs sadly I thought of that and I tested R on my machine after reinstalling but before reinstalling rstudio. Was a good shout though.

Reinstall did not fix the issue. Same error persists and test on "stats" package still fails

@gs Awesome thank you. That confirms were on the same version.

@joebonrichie you did the last update to R 3.6.1, is there anything I could give you (console outputs, etc.) that might help in chasing down this issue, as your time permits of course.

@gs , can you post the full output you recieve if you open R in terminal and run the codes? Since you arrive at the correct value perhaps it is an issue with a particular version of R?

Are you sure this is a Solus issue and not an issue with R itself or the CRAN package used? If you test this on another machine not running Solus do you receive the correct p-value?

Sure thing, I was originally going to write this request as being for "earlyoom" since I am not a very big fan of Python either however since it was less active I decided to write this for nohang.

In T8359#158168, @JoshStrobl wrote:

This is GNOME's Control Center, I would suggest filing a bug report with them. Do note however that we will be pushing out a new stack upgrade, GNOME 3.34, in the next week or two (depending on both testing locally as well as the unstable repo), so this may be resolved in that new release of GNOME Control Center. Doubtful, but worth checking regardless.