Now Yast2 seems to have given up its ghost. At least in my installation. After typing in "su" in the Konsole and gone to Yast2, nothing at all happens when I click on any of the modules. I type: # yast2 Yast opens. After clicking on the Software Management function, this happens at the command line: Command: /sbin/yast2 sw_single & The same happens with all the Yast2 modules, also with Graphics Card and Monitor, which yields this message at the command line prompt: Command: /sbin/yast2 x11 & So, if Yast cannot be made to work I have nothing else to do than to revert back to 11.0 unless there is a fix coming soon. Per Inge Oestmoen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Dec 24, 2008 at 6:07 AM, Per Inge Oestmoen
Now Yast2 seems to have given up its ghost.
At least in my installation. After typing in "su" in the Konsole and gone to Yast2, nothing at all happens when I click on any of the modules.
I type:
# yast2
Yast opens.
After clicking on the Software Management function, this happens at the command line:
Command: /sbin/yast2 sw_single &
The same happens with all the Yast2 modules, also with Graphics Card and Monitor, which yields this message at the command line prompt:
Command: /sbin/yast2 x11 &
So, if Yast cannot be made to work I have nothing else to do than to revert back to 11.0 unless there is a fix coming soon.
Per Inge Oestmoen
Check to see if zypper is working. I've had a similar issue to yours when I installed gcc33, which overwrites the version of libc.so (iirc) provided by gcc43. Running zypper threw an error message about loading libc till I removed gcc33. Nkoli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Nkoli
-
Per Inge Oestmoen