Comment # 6 on bug 1022727 from Rainer Krienke

Thanks for the qdirstat link, SLES12SP2 does not really contain many qt
programs ...

But first one more thing. Are you sure qt is to blame? I used yast2

rzinstal1:~ # bash -x yast2 
+ '[' -f /.instsys.config ']'
...
+ DESKTOP_GUI=gtk
+ '[' gtk = qt -a '!' -x /usr/lib/YaST2/bin/y2controlcenter ']'
+ '[' gtk = gtk -a '!' -x /usr/lib/YaST2/bin/y2controlcenter-gnome ']'
+ WANTED_SHELL=gtk
+ y2ccbin=
+ case "$WANTED_SHELL" in
+ y2ccbin=/usr/lib/YaST2/bin/y2controlcenter-gnome
+ '[' menu == menu -a -x /usr/lib/YaST2/bin/y2controlcenter-gnome ']'
+ /usr/lib/YaST2/bin/y2controlcenter-gnome

So its using the gnome version by default.

yast2 --qt leads to a call of /usr/lib/YaST2/bin/y2base menu qt

yast2 (gnome) is the one that works after a gnome-terminal call. yast2 --qt
does then still not work, it hangs when started, no message and no window.

qdirstat prints a one line message "Logging to /tmp/qdirstat-0.log" and then
hangs just like yast2 --qt.

The SLES12SP2 servers I manage are all VMs running on a Citrix XenServer 6.2.
They are no fresh installs, thats what just came to my mind. They were upgraded
from SLES11SP4 to SLES12, SLES12SP1 and then to SLES12SP2. I am right now
installing a fresh physical SLES12SP2 to see, if this makes any difference.