Upon request from Felipe Contreras, I'm leaving this info here, basically to explain why is this project stalled.
On 7/2/07, Jaime A Lopez Sollano  wrote:
> Well, the difference is mainly that I started working in this project at a
> time when there was only dbus-ruby
> (http://rubyforge.org/projects/dbus-ruby) which has
> stagnated,
> and didn't even compile. I tried modifying it to get it working, but got
> stuck because the api changed a lot.
> Then I decided I had to make an implementation in ruby. Apparently I wasn't
> the only one thinking about this (
> http://www.ruby-forum.com/topic/95389), however
> I needed something working quickly, and instead of waiting for someone to
> provide, I wrote this project.
> Basically, my project suffices for a demo I had to write, but isn't
> complete. I have decided to stop working on it and see how the other
> projects progress.

Yeah, I've heard dbus-ruby doesn't even compile.

Would it be possible to state this on your project's page?

It's a little confusing that there are so many projects for dbus.
Perhaps if you provide a link to ruby-dbus stating that they are
working on that project more actively right now...

What do you think?

So, if you are needing DBus support under Ruby, I would recommend you try Ruby D-Bus

You can still visit the pr-dbus' page at RubyForge