ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ibus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
...
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: ibus 1.5.19-4ubuntu2
ProcVersionSign
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 13 02:40:36 2019
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2019-09-13 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7fb50345becb <buffered_
PC (0x7fb50345becb) ok
source "$0x0" ok
destination "(%rsp)" (0x7ffda1a7afc0) 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_
ibus_bus_
?? ()
?? ()
g_cclosure_
Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
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 #1842022, 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.