OK now while I don't like yast's package management interface, and thus use
zypper, there are times when I need yast or yast2 to do something else...
Now If I understand correctly yast2 is supposed to be the gui version of
yast that required X and yast is the curses equivalent that can be run in a
virtual console such as tty1 without X... But while I'm glad that there is
a curses equivalent, I find the gui version less confusing.
Ever since kde4 proved incompatible with my brain, the only gui's I use are
E17 and E16 Or under extreme duress xfce... And by default, I use E17
And if it matters I boot to runlevel 3 and use startx when/if I'm
ready for a gui. Though admittedly, most of the time my first user
command is startx...
E17's applications menu only mentions yast once. And that is at
menu->applications->System->YaST (Administrator Settings)
Since there isn't a separate choice for yast2 I would tend to assume that
the menu choice would actually point at the gui yast2, but I can't prove it.
You see when I select yast from the menu, I get a small popup that prompts
me for the password. I don't know if it's based on the sudo settings or not
but since my sudoers file has "targetpw" on the defaults line it shouldn't
matter because it should want root's password. Which appears to be true
because if I use my own the pop-up simply exits immediately. But if I enter
my root password, some text output that looks like the stdout and/or stderr
I'd expect in an xterm if I call a gui application from it. But this text
scrolls by so fast I can't read any of it before "Poof" the popup window
closes. And yast2 doesn't start. I guess it's possible that it's trying to
start the curses version of yast, but in that case it should be opening an
xterm to run it in, and that doesn't happen either.
I've tried starting yast2 from an "xterm" (actually a "konsole" window,
{konsole being one of the few KDE apps I still use in spite of kde4}):
I've done this in three ways with different results:
su -c /sbin/yast2
which yields over 300 lines of stderr (see http://pastebin.com/AgwCap3W )
and no yast of any kind...
sudo /sbin/yast2
which actually starts the curses version in the current konsole window...
But if I open a root shell first:
su -
yast2
I get only about 9 lines of stderr (see http://pastebin.com/CwJtbKLS )
before the gui yast2 control center does actually open a functional window.
This bothers me because I much prefer to use either:
'su -c "command arglist"' or 'sudo command arglist' to start an
admin level gui than to leave an open root shell that I might
forget to close hanging around.
And of course because there should be a working yast menu choice in the gui
menu on an OpenSuSE system, shouldn't there???
Can anybody tell me how to fix this?
TIA
--
| ~^~ ~^~
| <?> <?> Joe (theWordy) Philbrook
| ^ J(tWdy)P
| \___/ <