ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Bug #1869484 reported by Antonello
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

i don't know what's happened

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 27 23:00:56 2020
ExecutablePath: /usr/libexec/ibus-ui-gtk3
InstallationDate: Installed on 2018-08-07 (598 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcCmdline: /usr/libexec/ibus-ui-gtk3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
Antonello (antonello-pierini) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message.cold () from /tmp/apport_sandbox_cgqoqn2m/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /tmp/apport_sandbox_cgqoqn2m/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 panel_construct ()
 _application_bus_name_acquired_cb_gd_bus_signal_callback ()
 emit_signal_instance_in_idle_cb (data=0x7fb1940119c0) at ../../../gio/gdbusconnection.c:3777

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ibus (Ubuntu):
importance: Undecided → Medium
summary: - ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
+ ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

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
Revision history for this message
Antonello (antonello-pierini) wrote : Re: [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Il mar 31 mar 2020, 12:30 Sebastien Bacher <email address hidden> ha scritto:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
> * Is this reproducible? Sorry i don't know
> * 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/1869484
>
> Title:
> ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
>
> Status in ibus package in Ubuntu:
> Incomplete
>
> Bug description:
> i don't know what's happened
>
> ProblemType: Crash
> DistroRelease: Ubuntu 20.04
> Package: ibus 1.5.22-2ubuntu1
> ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
> Uname: Linux 5.4.0-18-generic x86_64
> ApportVersion: 2.20.11-0ubuntu21
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Mar 27 23:00:56 2020
> ExecutablePath: /usr/libexec/ibus-ui-gtk3
> InstallationDate: Installed on 2018-08-07 (598 days ago)
> InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> ProcCmdline: /usr/libexec/ibus-ui-gtk3
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=it_IT.UTF-8
> SHELL=/bin/bash
> Signal: 6
> SourcePackage: ibus
> StacktraceTop:
> ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> g_assertion_message_expr () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> ?? ()
> ?? ()
> ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
> UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+subscriptions
>

Revision history for this message
Michael (mike190) wrote :

Had this happen to me as well. Ill try and reproduce but not sure that will happen. For me i logged out of a session then logged back in and clicked on "software update" and got the error.

Changed in ibus (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

@Michael: Why did you close the bug with "Fix Released" without justification?

Changed in ibus (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
Michael (mike190) wrote :

Was a mistake, miss-clicked and wouldn't let me revert. sorry!

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

On 2020-04-03 21:52, Michael wrote:
> Was a mistake, miss-clicked and wouldn't let me revert. sorry!

N.p., thanks for explaining.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Called upstream's attention to this via:

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

Revision history for this message
Lyubomir (mystiquewolf) wrote :

I also experienced this, my bug was auto-marked as duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.