Description of problem: After installing sflphone-gnome-plugins, sflphone does not start (it did before when only sflphone-gnome and dependencies were installed) and the following info is shown in journald: máj 07 12:45:13 zork sflphone.desktop[2905]: (sflphone-client-gnome:2905): GLib-GObject-WARNING **: cannot register existing type 'EDBusSource' máj 07 12:45:13 zork sflphone.desktop[2905]: (sflphone-client-gnome:2905): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed máj 07 12:45:13 zork sflphone.desktop[2905]: (sflphone-client-gnome:2905): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed máj 07 12:45:13 zork sflphone.desktop[2905]: (sflphone-client-gnome:2905): GLib-GObject-WARNING **: invalid cast from 'EDBusSourceProxy' to '<invalid>' Removing sflphone-gnome-plugins solves the problem. Version-Release number of selected component (if applicable): Name : sflphone-gnome Version : 1.4.1 Release : 7.fc21 Architecture: x86_64
This looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1197848, however even installing evolution-ews I cannot reproduce this here (rawhide). Which evolution related packages do you have installed?
I searched for "evolution" in yumex and displayed installed packages (I do not know how to do it from command line) and I have: evolution-data-server evolution-ews evolution-help evolution folks Name : evolution-data-server Version : 3.12.11 Release : 2.fc21 Architecture: x86_64 Name : evolution-ews Version : 3.12.11 Release : 1.fc21 Architecture: x86_64 Name : evolution-help Version : 3.12.11 Release : 1.fc21 Architecture: noarch Name : evolution Version : 3.12.11 Release : 1.fc21 Architecture: x86_64 Name : folks Epoch : 1 Version : 0.10.1 Release : 1.fc21 Architecture: x86_64
Right, I can reproduce this on F21. But considering that I cannot reproduce this on rawhide, where sflphone is the same version, I wonder whether this is an evolution bug. I'll narrow down the issue more to confirm.
Ok, I've narrowed this down, see https://bugzilla.redhat.com/show_bug.cgi?id=1197848#c12
I'm going to mark this as a duplicate of 1197848, though I suspect the quickest way to have this issue out of the way is to upgrade to F22. *** This bug has been marked as a duplicate of bug 1197848 ***