Version-Release number of selected component: ibus-1.4.99.20121109-8.fc18 Additional info: backtrace_rating: 4 cmdline: ibus-daemon -d crash_function: bus_dbus_impl_name_owner_changed executable: /usr/bin/ibus-daemon kernel: 3.6.11-3.fc18.x86_64 remote_result: 806495 uid: 1000 var_log_messages: Dec 28 13:16:01 server abrt[12837]: Saved core dump of pid 8794 (/usr/bin/ibus-daemon) to /var/spool/abrt/ccpp-2012-12-28-13:16:01-8794 (39612416 bytes) Truncated backtrace: Thread no. 1 (9 frames) #4 bus_dbus_impl_name_owner_changed at dbusimpl.c:1226 #9 bus_name_service_remove_owner at dbusimpl.c:458 #10 bus_dbus_impl_connection_destroy_cb at dbusimpl.c:1631 #15 ibus_object_dispose at ibusobject.c:135 #17 ffi_call_unix64 at ../src/x86/unix64.S:75 #18 ffi_call at ../src/x86/ffi64.c:486 #19 g_cclosure_marshal_generic at gclosure.c:1454 #24 emit_closed_in_idle at gdbusconnection.c:1377 #29 bus_server_run at server.c:143
Created attachment 669808 [details] File: backtrace
Created attachment 669809 [details] File: cgroup
Created attachment 669810 [details] File: core_backtrace
Created attachment 669811 [details] File: dso_list
Created attachment 669812 [details] File: environ
Created attachment 669813 [details] File: limits
Created attachment 669814 [details] File: maps
Created attachment 669815 [details] File: open_fds
Created attachment 669816 [details] File: proc_pid_status
(In reply to comment #1) > Created attachment 669808 [details] > File: backtrace > #0 0x00007f4fada32ba5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63 > resultvar = 0 > pid = 8794 > selftid = 8794 > #1 0x00007f4fada34358 in __GI_abort () at abort.c:90 > save_stage = 2 > act = {__sigaction_handler = {sa_handler = 0x25f2d60, sa_sigaction = 0x25f2d60}, sa_mask = {__val = {140737074334944, 139980201472704, 139980214113268, 5, 0, 139980192103592, 8791026475546661507, 39471504, 139980201472704, 99, 139980214139365, 0, 0, 139980195948400, 4294967295, 139980195948352}}, sa_flags = 1, sa_restorer = 0x0} > sigs = {__val = {32, 0 <repeats 15 times>}} > #2 0x00007f4fae03ab27 in g_assertion_message (domain=domain@entry=0x419b53 "IBUS", file=file@entry=0x41a023 "dbusimpl.c", line=line@entry=1226, func=func@entry=0x41af40 <__PRETTY_FUNCTION__.23869> "bus_dbus_impl_name_owner_changed", message=<optimized out>) at gtestutils.c:1877 > lstr = "1226\000\177\000\000\300\212R\347\377\177\000\000\250\273\375\255O\177\000\000l\241A\000\000\000\000" > s = 0x25a4990 "" > #3 0x00007f4fae03b044 in g_assertion_message_expr (domain=domain@entry=0x419b53 "IBUS", file=file@entry=0x41a023 "dbusimpl.c", line=line@entry=1226, func=func@entry=0x41af40 <__PRETTY_FUNCTION__.23869> "bus_dbus_impl_name_owner_changed", expr=expr@entry=0x41a16c "new_owner != NULL") at gtestutils.c:1888 > s = <optimized out> > #4 0x000000000040a6cf in bus_dbus_impl_name_owner_changed (dbus=0x2193010, connection=<optimized out>, name=0x25f2d60 "org.freedesktop.IBus.Panel", old_owner=0x232dbc0 ":1.1", new_owner=0x0) at dbusimpl.c:1226 > __PRETTY_FUNCTION__ = "bus_dbus_impl_name_owner_changed" > message = <optimized out> I cannot reproduce your problem. Are you still able to see this backtrace?
I've looked up and down this bug a few times, but I can't find my original message how/why this happened... So I'm afraid I can't reproduce this either. I have honestly no clue as to why this happened, sorry :(
Oh wait! I already remember how/why this happened. This was due to a little issue with the Java game Minecraft in which dead keys weren't passed along properly. To "fix" this, ibus is killed, then Minecraft is started, and then ibus is restarted. Apparently the restarting of ibus failed once, but it turns out this isn't necessary anymore since one of the more recent versions of Minecraft. Now that I remember this, I tried to reproduce it but for some reason I can't.
If you find how to reproduce your problem with steps, please comment here again.