![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1192148 https://bugzilla.suse.com/show_bug.cgi?id=1192148#c3 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #3 from Stefan Hundhammer <shundhammer@suse.com> --- Unlike the simple YaST Qt control center, the YaST Qt UI (libyui-qt) does not save its window size and position to a config file and restores it upon the next restart; rather, it has a quite elaborate algorithm to calculate the initial size of "default size" (wizard-style) windows: https://github.com/libyui/libyui/blob/master/libyui-qt/src/YQUI.cc#L360-L407 The starting point of this is whatever Qt considers the "primary screen": https://doc.qt.io/qt-5/qguiapplication.html#primaryScreen-prop So it will take the size of your primary screen, and since all of your screens are larger than 1024x786, it will use 70% of it for both dimensions. This usually works well. But if the dimensions or, as in your case, even the orientation of a multi-screen setup are radically different, problems like the one you described can occur: The initial calculation can be way off. The problem may be that Qt made a wrong decision what exactly is your primary screen. Maybe that can even be configured somewhere (in KDE? With xrandr?), but if yes, I don't know where. As a workaround (admittedly a kludge) I could offer using the -geometry command line option when starting a YaST module from the command line; like this: yast2 -geometry 1000x800 module_name or yast2 -geometry 1000x800+0+0 module_name -- You are receiving this mail because: You are on the CC list for the bug.