ibus-daemon crashed with SIGABRT in g_assertion_message_expr()

Bug #1794869 reported by tom
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

No

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: ibus 1.5.19-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 27 15:35:04 2018
ExecutablePath: /usr/bin/ibus-daemon
InstallationDate: Installed on 2018-09-11 (15 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180908)
ProcCmdline: ibus-daemon --xim --panel disable
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.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-daemon crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
tom (tombuntus) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545811, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ibus (Ubuntu):
status: New → Confirmed
Revision history for this message
jurosh (jurosh) wrote :

Just had system report of this bug on Ubuntu 20.04.02. It looks like duplicate bug was removed (or I cannot access it) ? Is it still open ?

Do we know what does this bug report mean to users who see it ?

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

The duplicate bug is old, and it's open now.

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.