[Fedora-i18n-bugs] [Bug 715251] [abrt] ibus-1.3.99.20110419-2.fc15: g_variant_type_info_check: Process /usr/bin/ibus-daemon was killed by signal 6 (SIGABRT)

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=715251

fujiwara <tfujiwar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |needinfo?(bcao at redhat.com)

--- Comment #10 from fujiwara <tfujiwar at redhat.com> 2011-06-24 06:00:29 EDT ---
(In reply to comment #9)
> It runs on gnome3
> #ps -eaf|grep gnome-shell
> mike     10015  7824  0 17:20 pts/3    00:00:00 grep --color=auto gnome-shell
> mike     22291 22097  3 Jun22 ?        01:52:54 /usr/bin/gnome-shell
> mike     22394     1  0 Jun22 ?        00:00:00
> /usr/libexec/gnome-shell-calendar-server
> #rpm -qf /usr/bin/gnome-shell
> gnome-shell-3.0.2-1.fc15.x86_64

OK, I tried gnome-shell + ibus-pinyin but I don't see any problems.


> btw ,this bug was generated by ABRT itself ,I don't know how to reproduce

I know it but just filing the bug does not give the enough information in this
case.
The following is the your first abrt report:

>> (In reply to comment #0)
>>> :#2  0x0000003ff3c665bd in g_assertion_message (domain=<optimized out>,
>>> file=<optimized out>, line=<optimized out>, func=0x3ff3cf7490
>>> "g_variant_type_info_check", message=0x7fcb8c00aaa0 "assertion failed: (0 <=
>>> index && index < 24)") at gtestutils.c:1358

Your problem is caused by the failure of the index but it would not be happened
normally.
And the assertion was caused in glib so I need to know whether root cause is
glib or ibus.

>>> :#10 0x0000003ff780f6c1 in g_object_unref (_object=0x7fcb8c01e990) at
>>> gobject.c:2734
>>> :        object = 0x7fcb8c01e990 [GDBusMessage]
>>> :        old_ref = <optimized out>
>>> :        __PRETTY_FUNCTION__ = "g_object_unref"
>>> :#11 0x000000000040a81d in bus_dbus_impl_connection_filter_cb
>>> (dbus_connection=<optimized out>, message=<optimized out>, incoming=<optimized
>>> out>, user_data=0x240e820) at dbusimpl.c:1407
>>> :        new_message = 0x7fcb8c01ea30 [GDBusMessage]
>>> :        __PRETTY_FUNCTION__ = "bus_dbus_impl_connection_filter_cb"
>>> :        dbus = 0x240e820 [BusDBusImpl]
>>> :        connection = 0x7fcb8c002d80 [BusConnection]

Your problem is caused by the unref of the dbus connection.
It would depends on how you unreferred the network connection of ibus to know
your problem.

> manually .but it really occurs more than 3 times .I will try to change a
> account to see whether will hit it .

Yes, it's good to compare the results. BTW, I'd ask a new account which can be
created by 'useradd' command instead of the existent another account.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.