Bug 974744
| Summary: | [abrt] ibus-1.5.2-5.fc19: bus_dbus_impl_dispatch_message_by_rule: Process /usr/bin/ibus-daemon was killed by signal 6 (SIGABRT) | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | kakoskin | ||||||||||||||||||||
| Component: | ibus | Assignee: | fujiwara <tfujiwar> | ||||||||||||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||
| Version: | 19 | CC: | i18n-bugs, kakoskin, m.k.wadee, shawn.p.huang, tfujiwar | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||
| Whiteboard: | abrt_hash:75db545dfce1b8ef1c186df1d5bdae4464510fd7 | ||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2013-06-25 01:52:03 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
kakoskin
2013-06-15 09:19:45 UTC
Created attachment 761541 [details]
File: backtrace
Created attachment 761542 [details]
File: cgroup
Created attachment 761543 [details]
File: core_backtrace
Created attachment 761544 [details]
File: dso_list
Created attachment 761545 [details]
File: environ
Created attachment 761546 [details]
File: limits
Created attachment 761547 [details]
File: maps
Created attachment 761548 [details]
File: open_fds
Created attachment 761549 [details]
File: proc_pid_status
(In reply to kakoskin from comment #0) > Thread 1 (Thread 0x7f5193012700 (LWP 1600)): > #0 0x0000003046035819 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 > #1 0x0000003046036f28 in __GI_abort () at abort.c:90 > #2 0x000000304846bbc6 in g_assertion_message (domain=domain@entry=0x4195d3 "IBUS", file=file@entry=0x419a9f "dbusimpl.c", line=line@entry=1887, func=func@entry=0x419fe0 <__PRETTY_FUNCTION__.24438> "bus_dbus_impl_dispatch_message_by_rule", message=<optimized out>) at gtestutils.c:1912 > #3 0x000000304846bc24 in g_assertion_message_expr (domain=domain@entry=0x4195d3 "IBUS", file=file@entry=0x419a9f "dbusimpl.c", line=line@entry=1887, func=func@entry=0x419fe0 <__PRETTY_FUNCTION__.24438> "bus_dbus_impl_dispatch_message_by_rule", expr=expr@entry=0x419e78 "skip_connection == NULL || BUS_IS_CONNECTION (skip_connection)") at gtestutils.c:1923 > #4 0x0000000000409f91 in bus_dbus_impl_dispatch_message_by_rule (dbus=dbus@entry=0x229b010, message=message@entry=0x7f518c003450, skip_connection=skip_connection@entry=0x2343980) at dbusimpl.c:1887 > #5 0x000000000040a417 in bus_dbus_impl_connection_filter_cb (dbus_connection=<optimized out>, message=0x7f518c003450, incoming=<optimized out>, user_data=0x229b010) at dbusimpl.c:1564 > #6 0x00000030498b390f in on_worker_message_about_to_be_sent (worker=<optimized out>, message=0x236a000, user_data=0x23c18b0) at gdbusconnection.c:2414 > #7 0x00000030498c8148 in _g_dbus_worker_emit_message_about_to_be_sent (message=0x236a000, worker=0x7f517c002280) at gdbusprivate.c:502 > #8 continue_writing (worker=0x7f517c002280) at gdbusprivate.c:1496 > #9 0x00000030498c8349 in continue_writing_in_idle_cb (user_data=<optimized out>) at gdbusprivate.c:1557 > #10 0x0000003048447e06 in g_main_dispatch (context=0x2323470) at gmain.c:3054 I cannot reproduce your backtrace. Are you still able to reproduce your backtrace? No. The problem appeared only once after installing KDE with yum install @kde-desktop, loging out of Gnome and into KDE without rebooting. I didn't see this in a subsequent reinstall. |