Comment 7 for bug 571664

Hi Stefaan

Today I ugraded to Maverick Meerkat Alpha 2. I have uninstalled everything somehow connected with ruby form ubuntu and then freshly reinstalled the dep package 0.3.3 of digiwf. The old SIGSEV and SIGABRT have gone, but now the program terminates with another message:

/usr/lib/ruby/1.8/glib2.rb:71:in `require': no such file to load -- glib2.so (LoadError)
 from /usr/lib/ruby/1.8/glib2.rb:71
 from /usr/lib/ruby/1.8/gtk2/base.rb:11:in `require'
 from /usr/lib/ruby/1.8/gtk2/base.rb:11
 from /usr/lib/ruby/1.8/gtk2.rb:10:in `require'
 from /usr/lib/ruby/1.8/gtk2.rb:10
 from /usr/lib/ruby/1.8/libglade2.rb:8:in `require'
 from /usr/lib/ruby/1.8/libglade2.rb:8
 from /usr/bin/digiwf:26:in `require'
 from /usr/bin/digiwf:26

The library glib2.so exists - not in /usr/lib/ruby/1.8/ but in /usr/lib/ruby/1.8/i486-linux/. I can now put an symbolic link to the i486-linux folder (sudo ln -s /usr/lib/ruby/1.8/i486-linux/glib2.so /usr/lib/ruby/1.8/), but after that more broken paths are popping up (atk.so pango.so etc.) every time I try to start digiwf from the console. In nautilus the option "Edit metadata" appears, but selecting it does nothing.

I hope you can solve this ugly ruby problems! André