This post is a central place for us to publicize high visibility known issues, with links to bug reports when we have them and workarounds where available. This will be updated over time, check back if you experience problems. General help and troubleshooting are available on our Help Site
If you don't find your issue listed here, please search our issue tracker and open a new issue if necessary.
Failure to update kernels during updates with an error no space left on device
This is caused by the /boot partition running out of space, which can happen for a few reasons.
See this for instructions on how to check if your /boot partition is at least 1GB, and how to remove old kernels properly to free up space.
GNOME displays a black screen with nouveau drivers
The tracking issue is here
This may be an upstream issue, as it was reported as happening with Fedora 41 as well
GNOME VM black screen with X cursor
See this issue
This appears to be an upstream bug.
Workaround: Do a forced reset on the VM
Budgie only has a black background with mouse cursor after login
There is an open issue here
Workaround: install the proprietary Nvidia drivers and see if that allows Budgie to load normally.
KDE Plasma - virtual / onscreen keyboard doesn't appear when clicking the button on the login screen
There are two aspects to this.
The user must install a virtual keyboard, and then set it to be used in System Settings.
There's a issue on our tracker to consider installing and configuring a virtual keyboard by default in a new Solus install.
The Virtual Keyboard button on the login screen doesn't respond to clicks, only touch. There is an upstream issue on the KDE bug tracker to fix this.
eopkg / Discover errors
KDE Discover / eopkg update error
If you see an error that starts like the below one:
$sudo eopkg.bin it qjackctl
Program terminated.
Component.localName: 'ar' language of tag 'LocalName' is empty.
Component.localName: 'bg' language of tag 'LocalName' is empty.
Component.localName: 'he' language of tag 'LocalName' is empty.
Workaround
Run this:
sudo eopkg dc
or
sudo eopkg ur --force
bash not loading scripts in ~/.bashrc.d (e.g. the packaging scripts like gotosoluspkgs)
If you try to run gotosoluspkgs or another command from your scripts in ~.bashrc.d you may get an error like
bash: gotosoluspkgs: command not found
This is because a bug was fixed recently in this PR
The files in ~.bashrc.d had been incorrectly sourced for all shells, which had caused errors in non-bash shells. Unfortunately, this means that existing users will no longer have ~.bashrc.d sourced by /usr/share/defaults/etc/profile.
New users created after this change will have the scripts sourced normally.
Workaround for existing users
Add this to ~/.bashrc
# User specific bash aliases and functions
if [ -d ~/.bashrc.d ]; then
for rc in ~/.bashrc.d/*; do
if [ -f "$rc" ]; then
. "$rc"
fi
done
unset rc
fi
There's an open issue to correct the problem for users created before this change.
