Looks like I found the solution to my previously stated problem on my own. As stated before, the problem was that some X programs didn't connect to my machine.

2. I am getting an annoying Xlib error when I try to display an X-window from another host. For example, this is what I get when I try to run tkrat on my office machine from home, being connected up via ssh: Xlib: connection to "physical36:11.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key Application initialization failed: couldn't connect to display "physical36:11.0" Error in startup script: invalid command name "wm" while executing "wm withdraw ." (file "/usr/X11R6/lib/tkratlib/tkrat" line 54)

A similar error happens when I try to run vmware: Xlib: connection to "colomba:0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: colomba:0.0

Trying to use the xhost command to add the host names to the list of allowed hosts won't work either and produces the same error:

Xlib: connection to "colomba:0.0" refused by server Xlib: Client is not authorized to connect to Server xhost: unable to open display "colomba:0.0"

This actually happened with *any* X program, even xterm and emacs. So, something was *really* wrong. I then started an X session as root and did not have any of these problems. Clearly, there was a permission problem with some file that I couldn't open as a normal mortal user. I finally came to the point where I reversed a YaST setting I had always used on previous installations with impunity, i.e., file permissions were set to secure. I always wanted my system to be as secure as possible, albeit still useable. So, this time, by choosing the secure file permissions I ended up prohibiting myself (user alex) from connecting to my own display. I don't think that this is the intended use of this feature, or is it? Is there any information available which files are affected by using the secure permissions setting? I am obviously running in the easy file permission mode and can use my X applications again (when I call them up from within an xterm), but feel a little uneasy what other files are now insecure. Since this is my home box, I am not so worried about it, but eventually I will try to upgrade my office box, too, which hangs on the internet 24hours 7days a week. Best regards, Alex. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/