http://bugzilla.suse.com/show_bug.cgi?id=1116584 http://bugzilla.suse.com/show_bug.cgi?id=1116584#c7 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #7 from Stefan Hundhammer <shundhammer@suse.com> --- yast2-control-center-qt is a simplistic Qt (not libyui-qt!) program that does not need libyui-qt. It needs something to start YaST modules with, and that's just libyui, not any specific UI. Remember we also used to have libyui-gtk which was also a viable way to start YaST modules. Admittedly, it might look pretty awkward to run the Qt YaST control center and see YaST started in NCurses mode, but it's not up to us to actively prohibit this if a user absolutely wants it. There is no technical reason to enforce libyui-qt when using yast2-control-center-qt. So, this clearly comes down to patterns. It is up to the patterns designer (i.e. the release managers?) to set up patterns for reasonable choices of bundles of software. Will that work if you use plain "zypper dup" and have the "install recommended packages" disabled? I don't know. But IMHO this is an expert setting where the expert should know that there are consequences. You might just have discovered one of them. This might be another instance of "Doctor, it hurts when I do that!" - "Then don't do that!" (i.e. WORKSFORME). -- You are receiving this mail because: You are on the CC list for the bug.