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 find a bug, and don't find it listed here, please search our issue tracker and open a new issue if necessary.
Budgie 10.9.3 breaks Electron-based apps that use safeStorage causing an error to appear at launch
On Budgie, when starting Signal-Desktop (and other Electron apps) you may see an error:
Database Error
Unable to access the database encryption key because the OS encryption keyring backend has changed from gnome_libsecret to basic_text. This can occur if the desktop environment changes, for example between GNOME and KDE.
Please switch to the previous desktop environment or try to run signal with the command line flag --password-store="gnome_libsecret".
There's an issue on the Budgie-Desktop tracker for this. Until this is fixed, use the workaround mentioned in the last sentence of the error.
Old kernels being left and filling up /boot causing failures when updating clr-boot-manager or kernels
See this open issue
You may see something like this when running updates through eopkg
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/kernel.c:L740): Failed to install extra initrds /usr/lib64/kernel/initrd-com.solus-project.current.6.12.17-314: No space left on device
[FATAL] cbm (../src/bootman/update.c:L250): Failed to install default-current kernel: ///usr/lib/kernel/com.solus-project.current.6.12.17-314
The problem is that sometimes clr-boot-manager doesn't properly remove old kernels.
Workaround: Manually remove old kernels
For systems with an AMD Zen 5 processor, at boot you may see "RDSEED32 is broken. Disabling the corresponding CPUID bit"
This is due to an AMD security issue with the Zen 5. The kernel is disabling RDSEED 16 & 32-bit forms (32-bit is fine).
This is not a bug with the kernel or Solus. The message can be ignored.
See this bulletin from AMD for details.
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 page in the Help Center 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.
KDE Plasma - virtual / onscreen keyboard doesn't appear when clicking the button on the login screen
While we install a virtual keyboard by default, it doesn't respond to mouse clicks. The Virtual Keyboard button on the login screen only responds to touch. There is an upstream issue on the KDE bug tracker to fix this.
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
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
