Greetings. Since I upgraded to openSUSE 13.1 (from openSUSE 12.3), YaST stopped working on GUI mode. I can still use the console interface, and I can also use WebYaST. But when I start YaST from the application menu (my desktop environment is KDE), or when I execute
yast2 --qt
on a root console, I get to see the initial screen, the one that lists all the module, but when I click on any of them, none will start. If I execute, say
yast2 repositories
, I immediately get the prompt back and the module doesn’t start, without giving any output (it doesn’t matter if I use the --qt flag). I if execute
echo $?
immediately after, I get 16, which according to the yast2 man pages means ‘Generic module error’. It’s the same with every other module.
That’s all the info I’ve got, and I don’t know where can I get more detailed error information. I’d be happy to provide more info if you tell me where to look.
I’m running openSUSE 13.1 64 bits on a Dell N4050 laptop, Core I5 processor, Intel HD 3000 integrated graphics.
[Y2Ruby] binary/YRuby.cc(callClient):238 cannot require yast:cannot load such file -- fast_gettext at /usr/lib64/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
Turns out rvm was overriding the system ruby and messing up the gems, and that seemed to be the reason why YaST was failing. I uninstalled rvm (I don’t need it right now), restarted my laptop and YaST is working again now!
I think this was my fault, because I had some folders with root permission on my ~/.rvm. If I need rvm again I’ll be careful and looking for this not to happen again.
If you do want to use rvm again in the future, you should remove those env vars from the login scripts (~/.bashrc f.e.), put them in a separate script, and call this whenever you want to use it, I’d say, so that the system’s ruby path is not overridden by default.
YaST has been translated to ruby for 13.1, it needs a working ruby installation with some additional gems, f.e rubygem-fast_gettext.
In your case this could not be loaded, because your rvm installation apparently did not include that (otherwise it would have even worked I guess).
