running budgie-desktop without ibus installed causes desktop to crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
budgie-desktop (Ubuntu) |
Fix Released
|
High
|
fossfreedom | ||
Jammy |
Fix Released
|
High
|
fossfreedom | ||
Kinetic |
Fix Released
|
High
|
fossfreedom | ||
Lunar |
Fix Released
|
High
|
fossfreedom |
Bug Description
[ Impact ]
* Where ibus has been manually uninstalled, budgie desktop will crash
This is a regression in Jammy due to the SRU patch applied in
issue #1956240
[ Test Plan ]
* Test that ibus-daemon is running
ps -ef | grep ibus-daemon
if the process is running then proceed with the test plan
if the process is not running then install ibus, logout and login
to test that ibus-daemon is indeed running
* 1) on login open a terminal (CTRL+ALT+T) or an application and type a character such as the quote key or the currency key.
* If the quote key defaults to something else such as the @ key or the currency key defaults to $ then you have a default layout of en_US.
* Add the keyboard layout applet to your panel
* from the list provided choose another keyboard layout
* Repeat test step "1)" above. Check that your chosen keyboard layout is correctly applied.
* from the proposed repo install the following packages:
sudo apt update
sudo apt install budgie-desktop budgie-core libbudgie-plugin0 libbudgie-private0 libbudgietheme0 libraven0 gir1.2-budgie-1.0
* Logout and login
* Repeat the above testing again - on login your expected layout should be applied e.g. en_GB if that was your last chosen layout.
* Lastly purge ibus
sudo apt purge ibus
* logout and login
* check that the first keyboard layout is applied
[ Where problems could occur ]
* Primarily the key issue is introducing a stability issue on budgie such as crash on login.
* Additionally the other issue is introducing a regression in applying keyboard layouts for more people rather than eliminating the issue.
* As such this fix has been iteratively developed through a multi-month testing regime with multiple community team members
https:/
https:/
[ Other Info ]
* This issue is specifically for Jammy - it backports the same patch
already applied in lunar/kinetic to Jammy - hence the UB team
regard this as well tested since it is now more than a month since
release on 22.10 and no reported issues here on launchpad or on
our discourse forum.
----
Regression noted for the budgie-desktop (jammy) -ubuntu2 upload.
For installs that have manually decided to uninstall ibus (and therefore removed ibus-daemon) - budgie-desktop crashes.
This is a regression from -ubuntu1~22.04 where such desktop installs did not crash
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: budgie-core 10.6.1-1ubuntu2
ProcVersionSign
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: Budgie:GNOME
Date: Sun Nov 27 11:21:21 2022
InstallationDate: Installed on 2022-11-16 (10 days ago)
InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
SourcePackage: budgie-desktop
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
mtime.conffile.
description: | updated |
description: | updated |
Changed in budgie-desktop (Ubuntu Lunar): | |
status: | New → Fix Released |
Changed in budgie-desktop (Ubuntu Kinetic): | |
status: | New → Fix Released |
description: | updated |
Changed in budgie-desktop (Ubuntu Jammy): | |
status: | New → In Progress |
Hello fossfreedom, or anyone else affected,
Accepted budgie-desktop into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ budgie- desktop/ 10.6.1- 1ubuntu3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- jammy to verification- done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- jammy. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.