Comment 4 for bug 2043442

Revision history for this message
L. P. Luigi Espenlaub (luigiwriter2) wrote : Re: [Bug 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Thankyou for your quick response and question.
I opened the following to check
Settings > Input Devices > Keyboard > Generic 104-key PC is selected there
Then noticed the object of your question.
IBus Wayland is apparently the default with Ubuntu Studio.
Help me, my assumptions are often suspect, thus this question. Is selecting
Settings > Input Devices > Virtual Keyboard > [None] the same as
"im-config -n none" in Konsole
I have selected [None] and will reboot.
Also if you have the time.
Does "im" only concern the Virtual Keyboard, or am I turning off other
features as well?
A point to a source that will help me understand "im" will help me in the
future.

[image: 🤓] L. P. Luigi Espenlaub.
<email address hidden>
Passed 3/4 of a Century mark. My neck was broken. Almost blown up in the
Bermuda Triangle, Thinking "Death Has A Love / Hate Relationship With Me"
might be a good Auto-Bio title.

On Tue, Nov 14, 2023 at 4:30 PM Gunnar Hjalmarsson <
<email address hidden>> wrote:

> Thanks for your report.
>
> I see Plasma and Wayland, which reminds me of
> <https://askubuntu.com/q/1490498> and <https://bugs.debian.org/1052005>.
>
> * Have you applied the IBus Wayland virtual keyboard?
>
> * If you have, can you please run this command:
>
> im-config -n none
>
> and reboot, and then let us know if that improves things.
>
> ** Bug watch added: Debian Bug tracker #1052005
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052005
>
> ** Changed in: ibus (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2043442
>
> Title:
> /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes
>
> Status in ibus package in Ubuntu:
> Incomplete
>
> Bug description:
> Apport captured a system freeze [crash] which required a hard reboot.
> However I could not confirm that the report was successfully uploaded.
>
> The /var/log/apport.log entry is as follows.
> --------
> ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable
> already crashed 2 times, ignoring
> INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786,
> signal 11, core limit 0, dump mode 1
> INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
> ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
> INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
> INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746,
> signal 11, core limit 0, dump mode 1
> INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
> ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
> Note: The last line may explain why I could not verify the file
> upload when I performed the following proceedure per:
> https://help.ubuntu.com/community/ReportingBugs
>
> -------
> luigi@l-g905:~$ ubuntu-bug
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>
> luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
>
> 7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80
>
>
> https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
> No such file or directory
> -----
>
>
> This upload fialure seemed confirmed when in:
> https://answers.launchpad.net/ubuntu/+questions?
> a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
> "ibus-ui-gtk3" is not mentioned in the release notes bugs section.
>
> In
> https://errors.ubuntu.com/?release=Ubuntu%2023.10&period=day
> text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above
> both returned "phrase not found"
>
> I reproduced the executable failure using Terminal with these results
> ------
> ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daemon-args --xim\ --panel\ disable
>
> Returns:
> ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daemon-args --xim\ --panel\ disable
>
> (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
> assertion '(offset + len) <= string_length' failed
>
> (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
> assertion '(offset + len) <= string_length' failed
>
> ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global
>
> Trace/breakpoint trap (core dumped)
> -----
>
> I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
> /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
> - modified on 11/13/23 9:07 PM - US-ASCII)
>
> Platform Information ------------------------
> Operating System: Ubuntu Studio 23.10
> KDE Plasma Version: 5.27.8
> KDE Frameworks Version: 5.110.0
> Qt Version: 5.15.10
> Kernel Version: 6.5.0-10-lowlatency (64-bit)
> Graphics Platform: Wayland
> Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
> Memory: 31.0 GiB of RAM
> Graphics Processor: NV172
> Manufacturer: MicroElectronics
> Product Name: G905
> System Version: 1.0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2043442/+subscriptions
>
>