ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Bug #1988643 reported by Khairul Aizat Kamarudzzaman
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

occurred when toggle darkmode

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: ibus 1.5.27-2
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 4 02:00:33 2022
Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0
ExecutablePath: /usr/libexec/ibus-x11
InstallationDate: Installed on 2020-06-25 (799 days ago)
InstallationMedia:

JournalErrors:
 Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in groups 'adm', 'systemd-journal' can see all messages.
       Pass -q to turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcCmdline: /usr/libexec/ibus-x11
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
 Segfault happened at: 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0
 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: ibus
StacktraceTop:
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago)
UserGroups: nordvpn sudo
separator:

Revision history for this message
Khairul Aizat Kamarudzzaman (fenris) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x5585a8f5d740, return_value=0x0, n_param_values=2, param_values=0x7fffa8e38000, invocation_hint=0x7fffa8e37f80) at ../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=node@entry=0x5585a8e36990, detail=detail@entry=349, instance=instance@entry=0x5585a8e98840, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffa8e38000) at ../../../gobject/gsignal.c:3796
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffa8e381c0) at ../../../gobject/gsignal.c:3549
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../../../gobject/gsignal.c:3606

tags: removed: need-amd64-retrace
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
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
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.