Bug 2247144 - [abrt] bijiben: g_type_check_instance_is_fundamentally_a(): bijiben-shell-search-provider killed by SIGSEGV
Summary: [abrt] bijiben: g_type_check_instance_is_fundamentally_a(): bijiben-shell-sea...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: bijiben
Version: 39
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f3b39bd7641211a5e0ae1bcdb56...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-30 22:22 UTC by Solomon Peachy
Modified: 2024-11-27 21:37 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:37:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: maps (3.95 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: exploitable (81 bytes, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: open_fds (3.29 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: environ (2.37 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: dso_list (633 bytes, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: cpuinfo (3.03 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: limits (1.29 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: os_info (734 bytes, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: proc_pid_status (1.45 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: backtrace (33.19 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: core_backtrace (38.34 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details
File: mountinfo (3.24 KB, text/plain)
2023-10-30 22:22 UTC, Solomon Peachy
no flags Details

Description Solomon Peachy 2023-10-30 22:22:17 UTC
Description of problem:
No idea what it's crashing on.

Version-Release number of selected component:
bijiben-40.1-7.fc39

Additional info:
reporter:       libreport-2.17.11
cmdline:        /usr/libexec/bijiben-shell-search-provider
type:           CCpp
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Notes.SearchProvider.slice/dbus-:1.2-org.gnome.Notes.SearchProvider
runlevel:       N 5
package:        bijiben-40.1-7.fc39
journald_cursor: s=fea2f6f822134171a29c3d77946f6043;i=1c6aea;b=ea2a407dd79f487390bbaae42373a132;m=637524b92;t=608c6548eb7fa;x=9446a4a767c5bbd3
executable:     /usr/libexec/bijiben-shell-search-provider
rootdir:        /
kernel:         6.5.6-300.fc39.x86_64
reason:         bijiben-shell-search-provider killed by SIGSEGV
backtrace_rating: 4
comment:        No idea what it's crashing on.
crash_function: g_type_check_instance_is_fundamentally_a
uid:            1000

Truncated backtrace:
Thread no. 0 (7 frames)
 #0 g_type_check_instance_is_fundamentally_a at ../gobject/gtype.c:4184
 #2 g_source_callback_unref at ../glib/gmain.c:1758
 #4 g_source_destroy_internal at ../glib/gmain.c:1423
 #6 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
 #7 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
 #8 g_main_context_iteration at ../glib/gmain.c:4414
 #9 g_application_run at ../gio/gapplication.c:2577


Potential duplicate: bug 1120235

Comment 1 Solomon Peachy 2023-10-30 22:22:20 UTC
Created attachment 1996274 [details]
File: maps

Comment 2 Solomon Peachy 2023-10-30 22:22:21 UTC
Created attachment 1996275 [details]
File: exploitable

Comment 3 Solomon Peachy 2023-10-30 22:22:22 UTC
Created attachment 1996276 [details]
File: open_fds

Comment 4 Solomon Peachy 2023-10-30 22:22:23 UTC
Created attachment 1996277 [details]
File: environ

Comment 5 Solomon Peachy 2023-10-30 22:22:25 UTC
Created attachment 1996278 [details]
File: dso_list

Comment 6 Solomon Peachy 2023-10-30 22:22:27 UTC
Created attachment 1996279 [details]
File: cpuinfo

Comment 7 Solomon Peachy 2023-10-30 22:22:28 UTC
Created attachment 1996280 [details]
File: limits

Comment 8 Solomon Peachy 2023-10-30 22:22:30 UTC
Created attachment 1996281 [details]
File: os_info

Comment 9 Solomon Peachy 2023-10-30 22:22:31 UTC
Created attachment 1996282 [details]
File: proc_pid_status

Comment 10 Solomon Peachy 2023-10-30 22:22:33 UTC
Created attachment 1996283 [details]
File: backtrace

Comment 11 Solomon Peachy 2023-10-30 22:22:35 UTC
Created attachment 1996284 [details]
File: core_backtrace

Comment 12 Solomon Peachy 2023-10-30 22:22:36 UTC
Created attachment 1996285 [details]
File: mountinfo

Comment 13 Michael Bass 2024-01-22 23:28:14 UTC
I was using Gnome searching for an application alphabetically.


reporter:       libreport-2.17.11
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Notes.SearchProvider.slice/dbus-:1.2-org.gnome.Notes.SearchProvider
backtrace_rating: 4
comment:        I was using Gnome searching for an application alphabetically.
journald_cursor: s=3f6af4d418704f9e85b8f99f5d763f75;i=7f1c4;b=3084d922375a42ac981801a80d371c26;m=28692a39;t=60f90cd5c7126;x=92dff8abdab25d7c
kernel:         6.6.12-200.fc39.x86_64
package:        bijiben-40.1-7.fc39
rootdir:        /
reason:         bijiben-shell-search-provider killed by SIGSEGV
runlevel:       N 5
executable:     /usr/libexec/bijiben-shell-search-provider
uid:            1000
crash_function: g_type_check_instance_is_fundamentally_a
type:           CCpp
cmdline:        /usr/libexec/bijiben-shell-search-provider

Comment 14 Jan Vlug 2024-05-18 15:59:25 UTC
The count for this crash is 453 on my Fedora 40 laptop.

Comment 15 Jan Vlug 2024-05-23 11:48:29 UTC
Maybe related to this?
May 23 13:45:44 hostname goa-daemon[356774]: goa_ews_client_autodiscover() failed: 404 — Not Found

Comment 16 Solomon Peachy 2024-05-23 11:55:09 UTC
> Maybe related to this?
> May 23 13:45:44 hostname goa-daemon[356774]: goa_ews_client_autodiscover() failed: 404 — Not Found

EWS autodiscovery is never guaranteed to succeed, and IME, almost always fails due to reasons outside of individual/user control.  (ie the organization didn't set it up!)

In other words, this is a "routine" failure and should never trigger a crash.  It's also only relevant during initial account setup, not during runtime.

Comment 17 Fedora Admin user for bugzilla script actions 2024-10-19 01:51:07 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 18 Aoife Moloney 2024-11-13 09:57:58 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 19 Aoife Moloney 2024-11-27 21:37:35 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.