SLES11 strange behaviour with YaST after dup to SP2
Today I found the time to upgrade my SLES11 SP XEN Server to SP2. The serious stuff went well, all of my domUs are up and running. There is one strange thing about YaST (QT and ncurses) and some other ncurses based packages, however.
When starting YaST (QT) locally or over nxclient everything seems to work. But as soon as I quit a module (Partitioner, for Example) it pops up again, starting from scratch. The same happens when I try to start ncurses based yast modules over ssh connection. I have to kill the processes which is not what I want to do on a production machine.