ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

[Fernando Anton]

Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 13:03:51 2020
ExecutablePath: /usr/libexec/ibus-ui-gtk3
ProcCmdline: /usr/libexec/ibus-ui-gtk3
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fee4f4e8f5b <buffered_vfprintf+27>: orq $0x0,(%rsp)
 PC (0x7fee4f4e8f5b) ok
 source "$0x0" ok
 destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: ibus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
 ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__STRINGv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 ibus_bus_call_sync (bus=bus@entry=0x5605cf8b1a60, bus_name=bus_name@entry=0x7fee4f6a1f9a "org.freedesktop.IBus", path=path@entry=0x7fee4f6a1f70 "/org/freedesktop/IBus", interface=interface@entry=0x7fee4f6a1f9a "org.freedesktop.IBus", member=member@entry=0x7fee4f6a2323 "GetEnginesByNames", parameters=0x7fee3c222ac0, reply_type=0x7fee4f6a2318) at ibusbus.c:2560
 ibus_bus_get_engines_by_names (bus=0x5605cf8b1a60, names=0x5605d029afc0) at ibusbus.c:1926
 panel_update_engines ()
 ___lambda32__g_settings_changed ()
 g_cclosure_marshal_VOID__STRINGv () from /tmp/apport_sandbox_yzwlkrdv/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6400.1

[Gunnar Hjalmarsson (gunnarhj)]

Called upstream's attention to this via:

https://github.com/ibus/ibus/issues/2203

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Fernando Anton (fer7785)]

Hi Sebastien and team,

The bug is not reproducible. It always appeared just after login, after
loading the desktop and without having started any application.

El dom., 5 abr. 2020 a las 11:30, Sebastien Bacher (<email address hidden>)
escribió:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> ** 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/1870843
>
> Title:
> ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
>
> Status in ibus package in Ubuntu:
> Incomplete
>
> Bug description:
> Description: Ubuntu Focal Fossa (development branch)
> Release: 20.04
>
> ProblemType: Crash
> DistroRelease: Ubuntu 20.04
> Package: ibus 1.5.22-2ubuntu2
> ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
> Uname: Linux 5.4.0-18-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> ApportVersion: 2.20.11-0ubuntu22
> Architecture: amd64
> CrashCounter: 1
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Apr 4 13:03:51 2020
> ExecutablePath: /usr/libexec/ibus-ui-gtk3
> ProcCmdline: /usr/libexec/ibus-ui-gtk3
> ProcEnviron:
> LANGUAGE=es_AR:es
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=es_AR.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7fee4f4e8f5b <buffered_vfprintf+27>: orq
> $0x0,(%rsp)
> PC (0x7fee4f4e8f5b) ok
> source "$0x0" ok
> destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region
> (needed writable region)!
> Stack memory exhausted (SP below stack segment)
> SegvReason: writing unknown VMA
> Signal: 11
> SourcePackage: ibus
> StacktraceTop:
> ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
> ibus_bus_get_engines_by_names () from
> /lib/x86_64-linux-gnu/libibus-1.0.so.5
> ?? ()
> ?? ()
> g_cclosure_marshal_VOID__STRINGv () from
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: ibus-ui-gtk3 crashed with SIGSEGV in
> ibus_bus_get_engines_by_names()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
> separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+subscriptions
>

[Sebastien Bacher (seb128)]

Thanks, next time you see it could you look at the timestamp from the /var/crash entry and see if it corresponding to the new boot or to the previous shutdown?

[baslow (barrysolow)]

I am affected by the same bug. I just checked the time stamp of /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash and found that it corresponds to the time I first logged in this morning, not last night's shutdown:

[Gunnar Hjalmarsson (gunnarhj)]

This crash type seems to not be present in 20.10, so let's consider it fixed for now. Closing.