ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Bug #1968478 reported by bryn1u
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ibus (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04

ibus:
  Installed: 1.5.26-3
  Candidate: 1.5.26-3
  Version table:
 *** 1.5.26-3 500
        500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

4) What happened instead
closed

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: ibus 1.5.26-3
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 10 16:44:38 2022
Disassembly: => 0x7fba2e2504f0: Cannot access memory at address 0x7fba2e2504f0
ExecutablePath: /usr/libexec/ibus-x11
InstallationDate: Installed on 2022-04-10 (0 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
ProcCmdline: /usr/libexec/ibus-x11
SegvAnalysis:
 Segfault happened at: 0x7fba2e2504f0: Cannot access memory at address 0x7fba2e2504f0
 PC (0x7fba2e2504f0) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
bryn1u (m-bryn1u) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x5573bba6a230, return_value=0x0, n_param_values=2, param_values=0x7fff34f4f050, invocation_hint=0x7fff34f4efd0) at ../../../gobject/gclosure.c:830
 signal_emit_unlocked_R (node=node@entry=0x5573bb91fa70, detail=detail@entry=350, instance=instance@entry=0x5573bb97d7a0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff34f4f050) at ../../../gobject/gsignal.c:3743
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff34f4f220) at ../../../gobject/gsignal.c:3496
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../../../gobject/gsignal.c:3553

tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Thanks for your report.

I'm not sure if it's related, but accidentally I have just uploaded a fix of bug #1968459. It would be good if you could upgrade to ibus 1.5.26-4 when it becomes available, and let us know if the problem persists with that version.

Changed in ibus (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ibus (Ubuntu) because there has been no activity for 60 days.]

Changed in ibus (Ubuntu):
status: Incomplete → Expired
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.