Back off also if IBus on Budgie

[Gunnar Hjalmarsson]

[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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package im-config - 0.45-1ubuntu2

---------------
im-config (0.45-1ubuntu2) hirsute; urgency=medium

  * debian/patches/drop-the-Budgie-exception.patch:
    - Let im-config back off also if IBus on Budgie (LP: #1901460)

 -- Gunnar Hjalmarsson <email address hidden> Wed, 28 Oct 2020 17:29:24 +0100

[Timo Aaltonen (tjaalton)]

Hello Gunnar, or anyone else affected,

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

[Timo Aaltonen (tjaalton)]

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.

[Gunnar Hjalmarsson (gunnarhj)]

I verified the test case for groovy using im-config 0.45-1ubuntu1.1 from groovy-proposed.

As regards focal I couldn't reproduce the test case successfully. IBus input methods are simply not recognized by the Keyboard Layout applet, also when budgie-desktop 10.5.1-6ubuntu0.1 is present.

@David: Is there more into it to make IBus work smoothly on Budgie 20.04?

[fossfreedom (fossfreedom)]

Hi!

Yes - the support for Ibus non-xkb layouts via the applet is broken in
focal - fixed as you have seen in groovy.

Thus I have backported the patch and SRU'd here
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1902317

Hopefully the SRU team will be kind enough to review soonish. Thanks. Regards

On Fri, 30 Oct 2020 at 21:15, Gunnar Hjalmarsson
<email address hidden> wrote:
>
> I verified the test case for groovy using im-config 0.45-1ubuntu1.1 from
> groovy-proposed.
>
> As regards focal I couldn't reproduce the test case successfully. IBus
> input methods are simply not recognized by the Keyboard Layout applet,
> also when budgie-desktop 10.5.1-6ubuntu0.1 is present.
>
> @David: Is there more into it to make IBus work smoothly on Budgie
> 20.04?
>
> ** Tags removed: verification-needed-groovy
> ** Tags added: verification-done-groovy
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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...

[Gunnar Hjalmarsson (gunnarhj)]

On 2020-10-31 13:21, fossfreedom wrote:
> Thus I have backported the patch and SRU'd here
> https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1902317
>
> Hopefully the SRU team will be kind enough to review soonish.

Ah, nice. Then I'll just wait with the verification of the detail in this bug until that SRU has made it to focal-updates.

[Gunnar Hjalmarsson (gunnarhj)]

I installed the budgie-desktop 10.5.1-6ubuntu0.2 packages from focal-proposed, and could then successfully verify the test case using im-config 0.44-1ubuntu1.3 from focal-proposed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package im-config - 0.45-1ubuntu1.1

---------------
im-config (0.45-1ubuntu1.1) groovy; urgency=medium

  * debian/patches/drop-the-Budgie-exception.patch:
    - Let im-config back off also if IBus on Budgie (LP: #1901460)

 -- Gunnar Hjalmarsson <email address hidden> Wed, 28 Oct 2020 17:29:24 +0100

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for im-config has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package im-config - 0.44-1ubuntu1.3

---------------
im-config (0.44-1ubuntu1.3) focal; urgency=medium

  * d/p/back-off-if-ibus-on-gnome.patch:
    - Let im-config back off also if IBus on Budgie (LP: #1901460)

 -- Gunnar Hjalmarsson <email address hidden> Wed, 28 Oct 2020 17:33:15 +0100