On the 4.4 test ISO OpenCL has a similar error that clinfo is required to display this page, but could not be found

It's eopkg instead of eopit.

Works for me, can you please run sudo eopit check gimp via terminal?

It is possible to set your keyboard layout in the kernel command line:

I can confirm this issue as it happened to me, too!

Budgie just ties into standard systemd / logind interfaces for it over dbus. No reason for it to be Budgie related.

I think I have been running in to the same issue a few times. Quite annoying. I am also seeing it on Budgie if that has something to do with it. Though I am still running on an updated install of Solus 4.1 and not a reinstall of 4.2, if it matters.

I think there's some confusion here in how I presented the issue - on the fresh install I deleted both partitions (in GParted) and let the Solus installer completely reformat the drive. Is it possible this is still some sort of config issue if that's the case?

This is not a valid issue. Per your report on Reddit, your ESP ran out of space. Please ensure your ESP is of the recommend 500MB size.

update2: Did some RTFMing and turns out this is mainly sudo's fault.

update: I've done some digging and connected some dots and I think I figured out what's going on.

Just an extra check that the search path is correct, I did this:

Python 2.7.17 (default, Oct 22 2019, 18:27:39) 
[GCC 9.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import socks
>>> socks.__file__
'/usr/lib/python2.7/site-packages/socks.pyc'
>>> import ypkg2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named ypkg2
>>>

there aren't any defined variables with that check (I think that's the normal?)
I also checked for ypkg's integrity with eopkg check
Dirs like /usr/lib/python2.7/site-packages/ypkg2 exist

Can you check your environment for any python-related variables?

I see, so here's what I did:
1- reinstalled ypkg (eopkg it --reinstall ypkg)
2- made sure I'm not in a virtualenv, and that my python is the latest one from repos:

 ~ ; eopkg sf `which python`
Searching for /usr/bin/python
Package python has file /usr/bin/python

3- made sure I'm not inside any weird environment or anything like that

sudo eopkg install --reinstall ypkg ?

Nevermind on this, just realized that 9.0.0 actually was released, just they didn't release the zips on GitHub, I'll submit a commit for it once I've built and tested.

Nice catch. This explains my graphical corruption at shutdown too.

See T8021.

Thank you for your help. I have resolved this issue by reinstating the DNS nameservers manually which prevented me from using Eopkg.

I have replaced the corrupted files on my box with the ones on my live boot. This has fixed all corrupted files and packages without needing internet.

I have these logs from checking eopkg.

Thank you. I’ll work on my box tonight :)
I’ll update about the status soon

okay, it seems you have to chroot into it https://getsol.us/articles/troubleshooting/boot-rescue/en/, after chrooting check if you really fully up to date and as well as for broken packages https://getsol.us/articles/troubleshooting/general-troubleshooting/en/, if this still doesn't solve it rollback the update https://getsol.us/articles/package-management/history-and-rollback/en/

Stable. Can’t get into tty with ctr alt f2. I installed libinput and fusuma before this.

stable or unstable repo? Can you get into TTY? What did you do before this boot?

There's a patch in 4.19.2 for this iirc.

Do not change priority. We will set it as needed.

In T6828#128217, @JoshStrobl wrote:

Closing as resolved. I'd like to see more consideration be put in from the VBA-M devs in ensuring existing configurations more gracefully upgrade / are supported for newer releases. Having our users experience these issues is not ideal.

Closing as resolved. I'd like to see more consideration be put in from the VBA-M devs in ensuring existing configurations more gracefully upgrade / are supported for newer releases. Having our users experience these issues is not ideal.

In T6828#127320, @JoshStrobl wrote:

I assigned this to you seeing as you're the maintainer and developer of VBA-M. Marking as Needs More Info, @nekoseam can you confirm whether or not you're on rel 13?

In T6828#127319, @ZachBacon wrote:

Well it's resolved on my end as far as I can tell, if @nekoseam can confirm that would be great.

I assigned this to you seeing as you're the maintainer and developer of VBA-M. Marking as Needs More Info, @nekoseam can you confirm whether or not you're on rel 13?

Well it's resolved on my end as far as I can tell, if @nekoseam can confirm that would be great.

Not sure if it was thrown on the build server yet

This was updated by @DataDrake as of https://dev.solus-project.com/R3137:409d711a9841f96e547830edd996597e90006023
Not sure if it was thrown on the build server yet

So everything worked as intended then. The Software Center removed the packages you requested. For a reinstall of a package, I'd suggest following https://solus-project.com/articles/package-management/basics/en/#reinstalling-software

OK, I found the problem. Somehow inside org/gnome/desktop/lockdown/disable-lockscreen was enabled. I don't know how, but it was set to true. I haven't tampered with dconf editor before