Hello Gunnar, or anyone else affected,

Accepted im-config into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/im-
config/0.44-1ubuntu1.3 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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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/PerformingSRUVerification .  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.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1901460

Title:
  Back off also if IBus on Budgie

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Focal:
  Fix Committed
Status in im-config source package in Groovy:
  Fix Committed
Status in im-config package in Debian:
  Unknown

Bug description:
  [Impact]

  This is a follow-up of bug #1893551, where we stopped im-config from
  interfering in case of a GNOME desktop. Even if Budgie uses the same
  applicable GNOME components, we didn't change it for Budgie at that
  time since IBus input methods were not reliably reflected in the
  Keyboard Layout applet.

  However, that issue has been fixed now. Also, the most common ibus
  crash type is now Budgie related:

  https://errors.ubuntu.com/problem/f0690c64c769b06c2ce0513667bd7a52f53ebd27

  We have reasons to hope that letting im-config back off also for
  Budgie will reduce the number of crashes as has already happened for
  standard Ubuntu (see comment #2 at bug #1879958). At least we have
  nothing to lose by trying...

  [Test case]

  I'm not aware of a way to reproduce the crashes, and thus can't
  confirm in advance that the proposed upload makes a difference.

  However, we should confirm that IBus input methods can be used
  smoothly on Budgie:

  * Install Budgie in a VM

  * Install the version of im-config from -proposed

  * Install ibus-libpinyin

  * Add the Keyboard Layout applet in Budgie Desktop Settings

  * Re-login

  * Add Intelligent Pinyin to the input sources in Settings

  * Confirm that switching between the input sources works
    without problems and that you can input Chinese characters

  [Regression risk]

  When used, im-config does two things: It launches an IM framework and
  sets some IM related variables. The test case serves the purpose of
  confirming that those things are properly accomplished without im-
  config in case of IBus. So given a successful verification the
  regression risk due to the proposed change should be low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1901460/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to