I can't confirm the temporary workaround described by Harry Krueger. For me, I had to downgrade both ruby1.8 and libruby1.8 to the previous version as well, then it worked.
I can't confirm the temporary workaround described by Harry Krueger. For me, I had to downgrade both ruby1.8 and libruby1.8 to the previous version as well, then it worked.