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
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.
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.
Unable to download linux-firmware update - resolved
There was a problem downloading the latest linux-firmware package update from the stable repository using the CDN. To address this, we have split that package into several subpackages.
Note: Installing the package update will take a significant amount of time (likely between 8 and 15 minutes). Many file conflict warnings will also appear if the update is done in the terminal; these can be completely ignored.
