bijiben-shell-search-provider crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[Gene Soo]

Error encountered during first boot after installing edubuntu-desktop on Ubuntu Live Server 23.10 Daily build.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: bijiben 40.1-6
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 18 05:12:38 2023
ExecutablePath: /usr/libexec/bijiben-shell-search-provider
InstallationDate: Installed on 2023-08-15 (3 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Daily amd64 (20230814)
ProcCmdline: /usr/libexec/bijiben-shell-search-provider
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f25a8a90c41 <g_type_check_instance_is_fundamentally_a+17>: mov (%rax),%rax
 PC (0x7f25a8a90c41) ok
 source "(%rax)" (0x7f227a590bc4) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bijiben
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: bijiben-shell-search-provider crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
separator:

[Apport retracing service (apport)]

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 #2030468, 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.