Bug 1406699 - [abrt] ibus: bus_dbus_impl_name_owner_changed(): ibus-daemon killed by SIGABRT
Summary: [abrt] ibus: bus_dbus_impl_name_owner_changed(): ibus-daemon killed by SIGABRT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 26
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:66a116a4eb17e5001efb611047b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-21 09:33 UTC by Han Han
Modified: 2017-09-30 06:29 UTC (History)
7 users (show)

Fixed In Version: ibus-1.5.16-9.fc26 ibus-1.5.16-9.fc27
Clone Of:
Environment:
Last Closed: 2017-09-17 22:50:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.09 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: cgroup (259 bytes, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: core_backtrace (9.54 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: dso_list (2.32 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: environ (1.26 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: limits (1.29 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: maps (11.97 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: mountinfo (3.73 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: namespaces (102 bytes, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: open_fds (1.82 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: proc_pid_status (1.26 KB, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details
File: var_log_messages (305 bytes, text/plain)
2016-12-21 09:33 UTC, Han Han
no flags Details

Description Han Han 2016-12-21 09:33:07 UTC
Description of problem:


Version-Release number of selected component:
ibus-1.5.14-3.fc26

Additional info:
reporter:       libreport-2.9.0
backtrace_rating: 4
cmdline:        /usr/bin/ibus-daemon -r --xim
crash_function: bus_dbus_impl_name_owner_changed
executable:     /usr/bin/ibus-daemon
global_pid:     17643
kernel:         4.9.0-1.fc26.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 890645

Comment 1 Han Han 2016-12-21 09:33:14 UTC
Created attachment 1234268 [details]
File: backtrace

Comment 2 Han Han 2016-12-21 09:33:15 UTC
Created attachment 1234269 [details]
File: cgroup

Comment 3 Han Han 2016-12-21 09:33:17 UTC
Created attachment 1234270 [details]
File: core_backtrace

Comment 4 Han Han 2016-12-21 09:33:19 UTC
Created attachment 1234271 [details]
File: dso_list

Comment 5 Han Han 2016-12-21 09:33:21 UTC
Created attachment 1234272 [details]
File: environ

Comment 6 Han Han 2016-12-21 09:33:22 UTC
Created attachment 1234273 [details]
File: limits

Comment 7 Han Han 2016-12-21 09:33:24 UTC
Created attachment 1234274 [details]
File: maps

Comment 8 Han Han 2016-12-21 09:33:26 UTC
Created attachment 1234275 [details]
File: mountinfo

Comment 9 Han Han 2016-12-21 09:33:28 UTC
Created attachment 1234276 [details]
File: namespaces

Comment 10 Han Han 2016-12-21 09:33:29 UTC
Created attachment 1234277 [details]
File: open_fds

Comment 11 Han Han 2016-12-21 09:33:31 UTC
Created attachment 1234278 [details]
File: proc_pid_status

Comment 12 Han Han 2016-12-21 09:33:32 UTC
Created attachment 1234279 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2017-02-28 10:50:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 14 Leslie Satenstein 2017-07-07 02:34:21 UTC
Similar problem has been detected:

I have been trying to run Fedora 26 candidate (July5 version) with btrfs.  Gnome crashes too often with btrfs. Gnome is stable with ext4

Since I could not stay with btrfs for /home (which was a subvolume of / ), I created a new /home as ext4 and copied  
all my data to it.  Gnome works better (my gnome extensions do not crash) and thats about it.
I am finding, perhaps due to my making changes, that it can take two logons to get into the system. Again, this may be due to my actions

My fstab will give you an idea of what I did.

[leslie@F26E ~]$ cat /etc/fstab 

#
# /etc/fstab
# Created by anaconda on Thu Jul  6 12:01:01 2017
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=565ec02e-b425-426d-bc25-f8e30b6eaf19 /                       btrfs   subvol=root00   0 0
UUID=6bc50bc6-11e9-487f-849e-91792ec96022 /backup                 ext4    defaults        1 2
UUID=038ab00b-9a02-4047-af8f-3cd1d287f616 /boot                   ext4    defaults        1 2
#UID=565ec02e-b425-426d-bc25-f8e30b6eaf19 /home                   btrfs   subvol=home00   0 0   commented out
UUID=83db6873-4963-4816-a781-dde689593eb7 /home                   ext4    defaults        0 0
UUID=bdf0d983-0430-4b8b-8dd1-474769e797dd /scratch                ext4    defaults        1 2
UUID=bd42259a-e385-49d1-a8e0-3520f392a038 swap                    swap    defaults        0 0
[leslie@F26E ~]$ 

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/ibus-daemon -r --xim
crash_function: bus_dbus_impl_name_owner_changed
executable:     /usr/bin/ibus-daemon
journald_cursor: s=1a6bd87ed7b4403e908f727a9bb3d7c9;i=29ad;b=760a9dd1f0d44cebac235620fec47755;m=12ffe48e;t=553b0ec31417a;x=97614579f318a83f
kernel:         4.11.8-300.fc26.x86_64
package:        ibus-1.5.16-2.fc26
reason:         ibus-daemon killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 David Conarton II 2017-07-28 22:06:12 UTC
Similar problem has been detected:

dont know how it happened.  was just crusing the web in firefox and stepped away for say 5 to ten minutes.  Returned and moved the mouse(trackpad).  everything went to the logon screen.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/ibus-daemon -r --xim
crash_function: bus_dbus_impl_name_owner_changed
executable:     /usr/bin/ibus-daemon
journald_cursor: s=39d4d5b267114c6f8f1eb0dbce27e98a;i=160191;b=9885d9d41b274fd69b7497cdac7d4c7d;m=d673e75d;t=55567ce95f731;x=348c089f152e7c2d
kernel:         4.11.11-300.fc26.x86_64
package:        ibus-1.5.16-3.fc26
reason:         ibus-daemon killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Fedora Update System 2017-09-14 10:51:23 UTC
ibus-1.5.16-9.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ee7868ca2e

Comment 17 Fedora Update System 2017-09-14 10:51:41 UTC
ibus-1.5.16-9.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-7c8156fe9c

Comment 18 Fedora Update System 2017-09-14 18:22:56 UTC
ibus-1.5.16-9.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-7c8156fe9c

Comment 19 Fedora Update System 2017-09-15 04:52:27 UTC
ibus-1.5.16-9.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ee7868ca2e

Comment 20 Fedora Update System 2017-09-17 22:50:30 UTC
ibus-1.5.16-9.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 21 Fedora Update System 2017-09-30 06:29:48 UTC
ibus-1.5.16-9.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.


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