While the 1.0.0.20 fc3 rpm worked fine on my Fedora Core 4 system, 1.1.0.3 won't install because of a missing dependency on libdbus-1.so.0, because FC4 has a newer version of dbus (0.32). Can you please create an rpm for systems with newer dbus versions?

[quote=ferrylandzaat]While the 1.0.0.20 fc3 rpm worked fine on my Fedora Core 4 system, 1.1.0.3 won't install because of a missing dependency on libdbus-1.so.0, because FC4 has a newer version of dbus (0.32). Can you please create an rpm for systems with newer dbus versions?[/quote]

You can use the static version of skype. That will work just fine.

write:
ln -s libdbus-1.so.1.0.0 libdbus-1.so.0

it works fine

No symlinking the .so wont's work, the dbus API is different.

It gives this error :

/opt/skype/skype.bin: symbol lookup error: /opt/skype/skype.bin: undefined symbol: dbus_bus_service_exists

and the static version looks very bad, and it's fonts are messed up.

So will the devs please compile a version against the new version of dbus ?

On my computer it works! Why?

Dude, gexcite, thank you. This was driving me nuts. What's the deal with needing to rename the lib? Did I not read something somewhere?

[quote=gexcite]write:
ln -s libdbus-1.so.1.0.0 libdbus-1.so.0

it works fine [/quote]

how can that ever help installing the rpm? if you create a symlink, the rpm database still thinks you dont have it. and there probably was a reason they changed the .so's name (usually API changes), so it will either crash your skype at some point or not work at all.

[quote=dwainegarden]You can use the static version of skype. That will work just fine.[/quote]

no it wont. it has the same problem as the rpm:



that 'symlink hack' from gexcite doesnt work either (like expected):

Take source package dbus and compile it manually. Then take Dynamic binary of Skype and install it manually.
I always install everything from source - it is the best solution for me. Always everything works fine.

Yes Skype, can we please see a compiled version for the newer libdbus, or perhaps that requires that the dbus is version x.xx or greater, rather than exactly at x.xx ... You can then just make a disclaimer that it may not work on dbus greater than the x.xx as thats its stable version.

[quote=gexcite]Take source package dbus and compile it manually. Then take Dynamic binary of Skype and install it manually.
I always install everything from source - it is the best solution for me. Always everything works fine.[/quote]

good luck compiling skype from source...

but do you have any idea what you are talking about? dbus is not just used by skype. its used in gnome, hal, cups and more, and i would count it as a critical system component. installing an older version of dbus wont work, since gnome/hal/etc need the newer version. so please stop talking crap ok? its not my dbus version that has to change, but the programs using it.

and yes, i wouldve compiled skype from source myself if the code was available, but since it isnt, someone who has access to it must do it. i think skype is really great software, but still its biggest flaw is the lack of publicly available source code.

@fink: you cant link to 2 versions of a library. the binary is either compiled for libdbus-1.so.0 or libdbus-1.so.1, but not both.

ok scratch that idea then... back to the please support the latest version of dbus then! argument

1. Download the RPMS from here:

http://spout.ussg.indiana.edu/linux/fedora....22-10.i386.rpm

2. Then, take this RPM and OPEN it with the archive viewer. Do NOT install it.

It will have the libdbus-1.so.0.0.0 file in the /usr/lib folder. Extract this to your home directory.

3. Then, copy the libdbus-1.so.0.0.0 file to /usr/lib.

cp ~/libdbus-1.so.0.0.0 /usr/lib

4. Next, symlink that sucker.

ln -s /usr/lib/libdbus-1.so.0.0.0 /usr/lib/libdbus-1.so.0

5. Issue the ldconfig command.

ldconfig

6. Then, try to RPM install skype again. Or, use the tar.bz2 package and run the executable from there. It should work now.

BTW guys, it was an API change. Skype is behind the times here, but hopefully they will get it fixed.

what will this do to the system wide daemon? I mean if skype is sending messages on th bus that the daemon can't understand because its an old API the result is undefined.

I still haven't seen what happens exactly, but I can say that I have experienced no app crashes, and the dbus daemon is still running with no errors.

i really dont like the idea of installing possibly incompatible versions of system components. i'll just stick with 1.0.0.20 for now, as long as they dont fix it...

seems that work-around has worked for me, though i did have to install no-deps the rpm... i'll back it out when the new rpm's supporting the dbus versions come out

Using FC3

I think it's a bad idea to use two libdbus versions. Skype uses the old dbus API and sends messages that the running dbus daemon might not understand. The result is undefined. I don't know what that could do to stability or security.

thanks vectorsc

the temp fix works for my slackware 10.1

still no new version?

fedora core 4 is officially coming out in about 2 weeks, and i can already see the threads popping up here about skype not working on their new OS.

Well, I joined this forum only to solve this problem.
I think it's their right to keep the source code, but I know that everything is in change in computer's world...
I think it's not that hard job to change a .spec file to use lidbus.so.1...

not even any need to change spec files. with most libs its a simple recompile, if the api hasnt changed. i dont know how compatible .1 is with .0, but i think its taking them quite long

1.1.0.13 seems to solve this issue.

thanks skype team