Hi,

I have a problem when starting programs from Suse 10.1 from quicklaunch.
For example : when starting Yast , I get a prompt for the admin password.
When I type it in, nothing happens, so no Yast.
When I open a terminal en do 'su -' followed by the password en then type 'yast2' i get the wished result : Yast starts.

This seems to have occured after an upgrade from Suse 10.0 to 10.1.
I am running a fully up2date suse 10.1 on my x86_64 architecture now.

Does anyone know how to fix this?
I was thinking of a configuration thing in Xorg , or in user groups, but I do not know where to look.

Your help is greatly appreciated!

Does 'kdesu yast2' work from x-console?

Check the log files for errors:

dmesg (after the problem occured)
~/.xsession-errors
/var/log/kdm.log
/var/log/YaST2/y2log
~/.y2log
(not sure about the names of the YaST logfiles)

Have a look at the end of those files for errors related to x or yast.

kdesu yast2 works.
When I just click the link, there is another window, so I guess it uses the gnome equivalent.
I am on another machine, will check the log later.
Any1 knows the Gnome equivalent of kdesu?
And what would be causing the problem?
(The logged in user is in the wheel group)

I figured out that gnomesu was the alternative for kdesu .
That's where the problem seems to be:
This is the output when typing it in the terminal:
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key

(gnome-terminal:31403): Gtk-WARNING **: cannot open display:
me@here:~>

seems like an X restiction.
Some googling gave me the answer :
http://nixforums.org/about12335-asc-15.html

i types xhost + as a normal user, the terminal responding with:
access control disabled, clients can connect from any host .
Now, when typing gnomesu , a terminal comes up and the links work again.
Isn't this a security issue?
Is there a way to allow my logged in user to this?

Thanks for your help!

It's a normal security feature that other users (including root) cannot connect to the X server of another user. But normally, gnomesu or kdesu are being used to circumvent this feature. So there is some misconfiguration on your system.

Have a look at this article: http://en.opensuse.org/SDB:X_Client_...splay%22_Error
This is little more information than the link you provided.

My guess is that one of the access control files in your users homedirectory is locked. It would be interesting to know, if gnomesu works from another/new users desktop. In that case I'd use brute force and delete (backup!) all dot-files (not folders) in the faulty users homedirecory.

But maybe you should wait until someone with deeper knowledge finds this thread.

thanks , that's a usefull link.
I think I already tried removing the .gnome-directories in the current users home folder.

Anyway, while xhost +x works, this is lost after a reboot.
Does anyone know how to specifically add my user to do the thing the command xhost +x does, but not for every user, still working after reboot?