Thats my problem at the moment, i cant open YAST without using the command “xhost +” before on bash.
openSUSE 11.4 64 bits.
Thanks !
On 09/12/2011 03:16 AM, assas1n wrote:
> Thats my problem at the moment, i cant open YAST without using the
> command “xhost +” before on bash.
i would expect you to be able to launch the GUI version of YaST in a
terminal using this:
kdesu yast2 <if KDE is installed, or
gnomesu yast2 <if Gnome is installed
or in a user terminal you could switch to root (using “su -l” and then
just yast2 for the GUI version or yast for the curses version
and, yes there is another way using xhost, but i’ve not used it…
oh!! are you saying you can get to YaST only by using “xhost” and none
of the other (usual) methods work? if so, did this “just happen” or was
your system born that way? and, could you give a few more details,
like: operating system and version; desktop environment and version;
what preceded this problem (like: months of working great, and then
after an update/app install/config edit–BLAM…)
–
DD
Caveat
openSUSE®, the “German Automobiles” of operating systems
You forgot to mention how you start YaST.
. By clicking on a YaST icon in the maian KDE/Gnome (what are you using?) menu?
. By using one of the methods shown by DenverD?
. Other?
How can we know???
yast2 (GUI) is actually started with:
/usr/bin/xdg-su -c /sbin/yast2
This is the command behind the menu. It doesn’t require xhost.
You can also start yast (ncurses) in a terminal, which doesn’t require access to the X display at all, by typing:
sudo yast
Im using openSUSE 11.4 64 bits.
Kernel 3.0.3
KDE 4.6.5
If i clicked on the YAST icon on KDE launcher menu it would ask me for root password, but nothing happens after that.
Strange, I guess the majority of us do it like this for years and have no problems.
On 09/13/2011 04:16 PM, assas1n wrote:
>
> Im using openSUSE 11.4 64 bits.
> Kernel 3.0.3
> KDE 4.6.5
>
> If i clicked on the YAST icon on KDE launcher menu it would ask me for
> root password, but nothing happens after that.
then your system is broken!
how did that happen?
was it ok for a while and then not??
what about if you use a openSUSE version, KDE version and kernel version
known to work together, correctly…(i’ve not seen your particular mix
before)…
and with all the file/directory permissions, appArmor and policyKit and
other security settings set up correctly…
then what? does it work okay then?
–
DD
Hardware-Software-
openSUSE®, the “German Automobiles” of operating systems
Sorry for the delay, its been some awesome days for mountainbiking 
Just did a fresh restart of my system after 1 month and YAST did open as its supposed to now.
On a side note, if i wanted to reformat a Windows hardrive to serve as an EXT4 extra storage space, would the YAST partitioner tool work ok?
Nice it works!
Yes, you can use YaST as partitioner tool.
Thanks, amazed by how helpful opensuse users are 
You are welcome.
And wait until the time comes that we ask something that you can answer. I bet you will be then one of those “helpful opensuse users” 