Bug Triage Team
Thu, Sep 9
Wed, Sep 8
Aug 10 2021
Aug 7 2021
Jul 30 2021
Jul 29 2021
Jun 25 2021
May 28 2021
Mar 2 2021
It is possible to set your keyboard layout in the kernel command line:
I can confirm this issue as it happened to me, too!
Feb 17 2021
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.
Jan 30 2021
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.
Oct 11 2020
Oct 10 2020
Jul 4 2020
Jan 26 2020
update2: Did some RTFMing and turns out this is mainly sudo's fault.
Jan 25 2020
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
Jan 22 2020
Can you check your environment for any python-related variables?
Jan 21 2020
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
Jan 17 2020
sudo eopkg install --reinstall ypkg ?
Nov 10 2019
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.
Nov 9 2019
Oct 10 2019
Sep 28 2019
Nice catch. This explains my graphical corruption at shutdown too.
Sep 8 2019
Sep 7 2019
Aug 27 2019
Jul 15 2019
May 25 2019
Apr 1 2019
Thank you for your help. I have resolved this issue by reinstating the DNS nameservers manually which prevented me from using Eopkg.