I don't see how libhal's ABI changed here... libhal should be exactly the same but linked against the new libdbus-1.
According to the vmware forum thread it's caused by having libdbus-1.so.2 and libdbus-1.so.3 on the same system at the same time. vmware loads the former, hal the second and things explode (for whatever reason). IMHO this is a vmware bug but unfortunately we can't fix anything there....
What exactly are you proposing? Reverting the dbus transition?
Another workaround mentioned there is
LD_PRELOAD=/usr/lib/libdbus-1.so.3 vmware
Maybe we should go with that until vmware is fixed...
I don't see how libhal's ABI changed here... libhal should be exactly the same but linked against the new libdbus-1.
According to the vmware forum thread it's caused by having libdbus-1.so.2 and libdbus-1.so.3 on the same system at the same time. vmware loads the former, hal the second and things explode (for whatever reason). IMHO this is a vmware bug but unfortunately we can't fix anything there....
What exactly are you proposing? Reverting the dbus transition?
Another workaround mentioned there is /usr/lib/ libdbus- 1.so.3 vmware
LD_PRELOAD=
Maybe we should go with that until vmware is fixed...