Bug 1781372 - [abrt] ibus: invoke_set_property_in_idle_cb(): ibus-daemon killed by SIGABRT
Summary: [abrt] ibus: invoke_set_property_in_idle_cb(): ibus-daemon killed by SIGABRT
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 31
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:75f531706153dfdd85ddf0be169...
: 1784598 1784599 1787727 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-09 21:29 UTC by Daniel Demus
Modified: 2020-09-22 15:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-22 06:37:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (44.96 KB, text/plain)
2019-12-09 21:29 UTC, Daniel Demus
no flags Details
ibus-daemon journalctl output (8.25 KB, text/plain)
2019-12-10 10:35 UTC, Daniel Demus
no flags Details

Description Daniel Demus 2019-12-09 21:29:16 UTC
Version-Release number of selected component:
ibus-1.5.21-4.fc31

Additional info:
reporter:       libreport-2.11.3
backtrace_rating: 4
cmdline:        ibus-daemon --panel disable -r --xim
crash_function: invoke_set_property_in_idle_cb
executable:     /usr/bin/ibus-daemon
journald_cursor: s=c4148406e0464aa6b028a69dbd858103;i=2332cb;b=9b80660c325a4e97b03f82a722e4c4df;m=49832e189;t=59943b5e4b38d;x=d732a9d65ff2477
kernel:         5.3.14-300.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Daniel Demus 2019-12-09 21:29:19 UTC
Created attachment 1643411 [details]
File: backtrace

Comment 2 fujiwara 2019-12-10 04:29:07 UTC
Can you attach the log of `journalctrl -b /usr/bin/ibus-daemon` here?

Comment 3 fujiwara 2019-12-10 04:30:02 UTC
(In reply to fujiwara from comment #2)
> Can you attach the log of `journalctrl -b /usr/bin/ibus-daemon` here?

Correction:

journalctl

Comment 4 Daniel Demus 2019-12-10 10:35:21 UTC
Created attachment 1643590 [details]
ibus-daemon journalctl output

I've rebooted a few times since the glitch, so I'll just send you the entire journalctl output for the ibus-daemon, which isn't huge.

Comment 5 Daniel Demus 2019-12-17 20:08:35 UTC
*** Bug 1784599 has been marked as a duplicate of this bug. ***

Comment 6 Matthias Andree 2020-01-04 18:42:56 UTC
*** Bug 1787727 has been marked as a duplicate of this bug. ***

Comment 7 fujiwara 2020-01-29 04:18:20 UTC
(In reply to Daniel Demus from comment #4)
> Created attachment 1643590 [details]
> ibus-daemon journalctl output
> 
> I've rebooted a few times since the glitch, so I'll just send you the entire
> journalctl output for the ibus-daemon, which isn't huge.

From your log, I cannot find ibus-daemon has SEGV.

Are you still able to reproduce your backtrace?
When you reproduce it again, please get the log of journalctl again.

Comment 8 fujiwara 2020-01-29 04:20:05 UTC
*** Bug 1784598 has been marked as a duplicate of this bug. ***

Comment 9 Daniel Demus 2020-04-15 08:21:46 UTC
No, it happened in the background, so I don't know what caused it, and it hasn't repeated itself yet.

Comment 10 Parag Nemade 2020-09-22 06:37:56 UTC
Closing this now. If you see crash again do report again in bugzilla. Thanks.

Comment 11 Matthias Andree 2020-09-22 13:51:37 UTC
How about duplicate (limited visibility) reports such as mine, #1787727 -  do they help shed some light on this issue?

Comment 12 Parag Nemade 2020-09-22 15:18:01 UTC
Bugs which are auto created using crash reports, many times don't provide any information about what scenario this bug got produced. I will request you if you can still produce this crash on your system then do share here what were you doing when crash happened? What applications were open when you try to use ibus?


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