This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Fixing Skype Call recorder on KDE

Tags: None
(comma "," separated)
User avatar
JZA
Registered Member
Posts
12
Karma
0
OS

Fixing Skype Call recorder on KDE

Fri Oct 12, 2012 5:03 am
Hi, Skype Call Recorder is a Qt app which I struggle because DBus has changed in recent KDE updates (not so recent). When I start Skype I get the following error:
Loaded 18 preferences from '/home/guest/.skypecallrecorder.rc'
GUI initialized
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Service com.Skype.API not found on DBus


I have looked at the Git repo and the issue seems to be somewhere on the DBus way of handling skype.

Code: Select all
 86 void Skype::serviceOwnerChanged(const QString &name, const QString &oldOwner, const QString &newOwner) {
87         if (name != skypeServiceName)
88                 return;
89
90         if (oldOwner.isEmpty()) {
91                 debug(QString("DBUS: Skype API service appeared as %1").arg(newOwner));
92                 if (connectionState != 3)
93                         connectToSkype();
94         } else if (newOwner.isEmpty()) {
95                 debug("DBUS: Skype API service disappeared");
96                 if (connectionState == 3)
97                         emit connected(false);
98                 timer->stop();
99                 connectionState = 0;
100         }
101 }

The whole file can be found here.


Alexandro Colorado
http://jza.me
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
In this case the real issue appears to be that either Skype itself has changed it's D-Bus interface, or it is not running when you started Skype Call Recorder. I would suggest you start Skype itself before hand.

There is nothing immediately wrong in that code as far as I can tell.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
JZA
Registered Member
Posts
12
Karma
0
OS
Thanks for your information, the odd thing is that I havent really update Skype in a really long time. So I dont think Skype change anything from before. But you are right, Dbus just dont see Skype anymore. Doing Dbus-monitor also doesnt get any calls from com.Skype.API or others.

The error message lead me to believe this was a QtDbus implementation.

Regards.


Alexandro Colorado
http://jza.me
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
With Skype running, please check the output of the following command:
Code: Select all
qdbus | grep -i skype


If nothing is listed - the fault must be in Skype.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], markhm, rblackwell, sethaaaa, Sogou [Bot], Yahoo [Bot]