Bug 2229162 - [abrt] ibus: g_datalist_id_dup_data(): ibus-daemon killed by SIGSEGV
Summary: [abrt] ibus: g_datalist_id_dup_data(): ibus-daemon killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: glib2
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:50a80e97d9cf3da260d20f7015c...
: 2264243 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-04 13:46 UTC by Tony Asleson
Modified: 2024-05-28 13:40 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:40:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: environ (1.41 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: mountinfo (3.71 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: backtrace (26.30 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: proc_pid_status (1.46 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: os_info (734 bytes, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: limits (1.29 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: open_fds (2.84 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: maps (3.96 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: core_backtrace (10.49 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: cpuinfo (2.79 KB, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: exploitable (81 bytes, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details
File: dso_list (715 bytes, text/plain)
2023-08-04 13:46 UTC, Tony Asleson
no flags Details

Description Tony Asleson 2023-08-04 13:46:27 UTC
Description of problem:
Using wayland , screen locked.  Unlocked and problem was reported.

Version-Release number of selected component:
ibus-1.5.28-6.fc38

Additional info:
reporter:       libreport-2.17.11
package:        ibus-1.5.28-6.fc38
type:           CCpp
cmdline:        /usr/bin/ibus-daemon --panel disable
crash_function: g_datalist_id_dup_data
uid:            17209
rootdir:        /
journald_cursor: s=38a8d990a9b041a1a6d0e5cfe1368b8f;i=957016;b=9a0935a609044e0db4d71079bf135496;m=2237b6329d;t=602188e8967bb;x=99b98a82c3ae5e72
executable:     /usr/bin/ibus-daemon
comment:        Using wayland , screen locked.  Unlocked and problem was reported.
cgroup:         0::/user.slice/user-17209.slice/user/session.slice/org.freedesktop.IBus.session.GNOME.service
reason:         ibus-daemon killed by SIGSEGV
backtrace_rating: 4
runlevel:       N 5
kernel:         6.4.6-200.fc38.x86_64

Truncated backtrace:
Thread no. 1 (11 frames)
 #0 g_datalist_id_dup_data at ../glib/gdataset.c:977
 #1 g_datalist_id_get_data at ../glib/gdataset.c:916
 #2 toggle_refs_notify at ../gobject/gobject.c:3609
 #3 message_to_write_data_free at ../gio/gdbusprivate.c:904
 #4 write_message_cb at ../gio/gdbusprivate.c:1370
 #5 g_task_return_now at ../gio/gtask.c:1309
 #6 complete_in_idle_cb at ../gio/gtask.c:1323
 #10 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
 #12 gdbus_shared_thread_func at ../gio/gdbusprivate.c:284
 #13 g_thread_proxy at ../glib/gthread.c:831
 #15 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Comment 1 Tony Asleson 2023-08-04 13:46:31 UTC
Created attachment 1981623 [details]
File: environ

Comment 2 Tony Asleson 2023-08-04 13:46:32 UTC
Created attachment 1981624 [details]
File: mountinfo

Comment 3 Tony Asleson 2023-08-04 13:46:34 UTC
Created attachment 1981625 [details]
File: backtrace

Comment 4 Tony Asleson 2023-08-04 13:46:35 UTC
Created attachment 1981626 [details]
File: proc_pid_status

Comment 5 Tony Asleson 2023-08-04 13:46:37 UTC
Created attachment 1981627 [details]
File: os_info

Comment 6 Tony Asleson 2023-08-04 13:46:39 UTC
Created attachment 1981628 [details]
File: limits

Comment 7 Tony Asleson 2023-08-04 13:46:40 UTC
Created attachment 1981629 [details]
File: open_fds

Comment 8 Tony Asleson 2023-08-04 13:46:42 UTC
Created attachment 1981630 [details]
File: maps

Comment 9 Tony Asleson 2023-08-04 13:46:44 UTC
Created attachment 1981631 [details]
File: core_backtrace

Comment 10 Tony Asleson 2023-08-04 13:46:46 UTC
Created attachment 1981632 [details]
File: cpuinfo

Comment 11 Tony Asleson 2023-08-04 13:46:48 UTC
Created attachment 1981633 [details]
File: exploitable

Comment 12 Tony Asleson 2023-08-04 13:46:50 UTC
Created attachment 1981634 [details]
File: dso_list

Comment 13 fujiwara 2023-08-07 09:24:08 UTC
Are you still able to reproduce your issue?
I don't know why this issue could happen.

(In reply to Tony Asleson from comment #3)
> Created attachment 1981625 [details]
> File: backtrace

#0  g_datalist_id_dup_data (datalist=datalist@entry=0x7fc5f00292d0, key_id=72, dup_func=dup_func@entry=0x0, user_data=user_data@entry=0x0) at ../glib/gdataset.c:977
        val = 0x0
        retval = 0x0
        d = 0x4b4b4b4b4b4b4b48
        data = 0x4b4b4b4b4b4b4b50
        data_end = <optimized out>
#1  0x00007fc60bf3372d in g_datalist_id_get_data (datalist=datalist@entry=0x7fc5f00292d0, key_id=<optimized out>) at ../glib/gdataset.c:916
#2  0x00007fc60c05fb14 in toggle_refs_notify (object=0x7fc5f00292c0, is_last_ref=1) at ../gobject/gobject.c:3609
#3  0x00007fc60c1bb5de in message_to_write_data_free (data=data@entry=0x7fc5f001c720) at ../gio/gdbusprivate.c:904
#4  0x00007fc60c1c4435 in write_message_cb (source_object=<optimized out>, res=<optimized out>, user_data=0x7fc5f001c720) at ../gio/gdbusprivate.c:1370
#5  0x00007fc60c15309c in g_task_return_now (task=0x7fc5f0038f40) at ../gio/gtask.c:1309
#6  0x00007fc60c1530d5 in complete_in_idle_cb (task=task@entry=0x7fc5f0038f40) at ../gio/gtask.c:1323
#7  0x00007fc60bf5048d in g_idle_dispatch (source=0x7fc5f000f730, callback=0x7fc60c1530c0 <complete_in_idle_cb>, user_data=0x7fc5f0038f40) at ../glib/gmain.c:6163
#8  0x00007fc60bf5448c in g_main_dispatch (context=0x55bbf9056830) at ../glib/gmain.c:3460
#9  g_main_context_dispatch (context=0x55bbf9056830) at ../glib/gmain.c:4200
#10 0x00007fc60bfb2648 in g_main_context_iterate.isra.0 (context=0x55bbf9056830, block=1, dispatch=1, self=<optimized out>) at ../glib/gmain.c:4276
#11 0x00007fc60bf53a8f in g_main_loop_run (loop=0x55bbf9056920) at ../glib/gmain.c:4479
#12 0x00007fc60c1bb4b2 in gdbus_shared_thread_func (user_data=0x55bbf9056800) at ../gio/gdbusprivate.c:284
#13 0x00007fc60bf82983 in g_thread_proxy (data=0x55bbf904b450) at ../glib/gthread.c:831
#14 0x00007fc60bda6907 in start_thread (arg=<optimized out>) at pthread_create.c:444
#15 0x00007fc60be2c870 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Comment 14 Tony Asleson 2023-08-07 13:10:07 UTC
(In reply to fujiwara from comment #13)
> Are you still able to reproduce your issue?
> I don't know why this issue could happen.

I'm using a kvm switch.  I'm wondering if the repeated disconnect/reconnect of keyboard & mouse USB hot-plug events could be the cause of this?

Comment 15 Tony Asleson 2023-09-05 13:25:15 UTC
This occurance occurred without me doing anything of note.


reporter:       libreport-2.17.11
package:        ibus-1.5.28-6.fc38
type:           CCpp
cmdline:        /usr/bin/ibus-daemon --panel disable
crash_function: g_datalist_id_dup_data
uid:            17209
rootdir:        /
journald_cursor: s=38a8d990a9b041a1a6d0e5cfe1368b8f;i=967104;b=9a0935a609044e0db4d71079bf135496;m=2a62c781f61;t=6049c834b547e;x=6ae748a5868f4a4
executable:     /usr/bin/ibus-daemon
comment:        This occurance occurred without me doing anything of note.
cgroup:         0::/user.slice/user-17209.slice/user/session.slice/org.freedesktop.IBus.session.GNOME.service
reason:         ibus-daemon killed by SIGSEGV
backtrace_rating: 4
runlevel:       N 5
kernel:         6.4.6-200.fc38.x86_64

Comment 16 Tony Asleson 2023-09-22 21:51:15 UTC
Simply using the system as normal.


reporter:       libreport-2.17.11
package:        ibus-1.5.28-6.fc38
type:           CCpp
cmdline:        /usr/libexec/ibus-extension-gtk3
crash_function: g_datalist_id_dup_data
uid:            17209
rootdir:        /
journald_cursor: s=38a8d990a9b041a1a6d0e5cfe1368b8f;i=979c5e;b=9a0935a609044e0db4d71079bf135496;m=40318538333;t=605f96f26b851;x=60a069e383007305
executable:     /usr/libexec/ibus-extension-gtk3
comment:        Simply using the system as normal.
cgroup:         0::/user.slice/user-17209.slice/user/session.slice/org.freedesktop.IBus.session.GNOME.service
reason:         ibus-extension-gtk3 killed by SIGSEGV
backtrace_rating: 4
dso_list:       /usr/libexec/ibus-extension-gtk3 ibus-1.5.28-6.fc38.x86_64 (Fedora Project) 1686681545
runlevel:       N 5
kernel:         6.4.6-200.fc38.x86_64

Comment 17 fujiwara 2023-10-10 14:07:00 UTC
(In reply to Tony Asleson from comment #14)
> (In reply to fujiwara from comment #13)
> > Are you still able to reproduce your issue?
> > I don't know why this issue could happen.
> 
> I'm using a kvm switch.  I'm wondering if the repeated disconnect/reconnect
> of keyboard & mouse USB hot-plug events could be the cause of this?

I don't know what kind of GIO message causes this issue.
I also think the plugging USB device issue would not be ibus.

Comment 18 Parag Nemade 2024-04-25 04:23:27 UTC
*** Bug 2264243 has been marked as a duplicate of this bug. ***

Comment 19 Aoife Moloney 2024-05-28 13:40:34 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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.