Source: budgie-extras Version: 1.9.0-1 Severity: grave Control: block 1118363 by -1 X-Debbugs-CC: [email protected]
While preparing the major pygobject 3.54 transition that required transitioning libpeas in https://bugs.debian.org/1118363, we erroneously thought that Budgie was not affected by the transition. While the default configuration appeared unaffected in my testing (sudo apt install budgie-desktop), several applets do use Python. Here is a test case that will freeze Budgie: Test Case ======= Have the new python3-gi, python3-gi-cairo, gir1.2-peas-1.0, and libpeas-1.0-0 from Unstable installed. sudo apt install budgie-desktop budgie-countdown-applet Log out. Log into Budgie Desktop Open the apps menu and launch Budgie Desktop Settings Switch to Bottom Panel. Click Add applet. Add Count Down In this test case, after rebooting my computer, I was able to get back into Budgie. However, if that applet was already added to your panel before upgrading, then the panel(s) won't load. (It doesn't matter which panel the applet is added to). Workaround ========= In the Budgie session, you can use Alt+F2 to run a command. Run gnome-terminal or ptyxis or whatever your favorite installed terminal is. In the terminal, run gsettings reset-recursively com.solus-project.budgie-panel At this point, I ran sudo reboot now. I was then able to log into a working default Budgie desktop. Affected ====== Other components that are probably affected, all shipped by source package budgie-extras: budgie-clockworks-applet budgie-dropby-applet budgie-kangaroo-applet budgie-keyboard-autoswitch-applet budgie-quickchar budgie-rotation-lock-applet budgie-takeabreak-applet budgie-workspace-stopwatch-applet Budgie maintainer David told me that Budgie upstream is launching a beta around the middle of this month. The Beta has a fix for this issue but it needs at least 2 NEW packages. Thank you, Jeremy Bícha
