Comment # 25 on bug 1037891 from Josef Reidinger

(In reply to Fabian Vogt from comment #24)
> (In reply to Josef Reidinger from comment #23)
> > (In reply to Fabian Vogt from comment #22)
> > > (In reply to Josef Reidinger from comment #21)
> > > > ok, so we at least move forward. I will check this icon issue, how to do it
> > > > in qt properly.
> > > 
> > > It's not the icon, it's the WM_CLASS. It should be enough to just override
> > > the passed argv[0] to the QApplication constructor, restoring the behaviour
> > > before YaST launched with argv[0] == "ruby"
> > 
> > and that's the part that is not so easy, as libyui obtain it from /proc
> > 
> > see
> > https://github.com/libyui/libyui-qt/blob/
> > 817ddbe637c98a54460b1152ec9d51e7f2d9422e/src/YQUI.cc#L126
> > 
> > in past it works due to this dirty hack, but we no longer want such nasty
> > hack. So we need find better way to pass it
> > https://github.com/libyui/libyui-qt/blob/
> > 817ddbe637c98a54460b1152ec9d51e7f2d9422e/src/YQUI.cc#L141
> 
> Maybe QCoreApplication::setApplicationName("YaST2") works here. As YaST does
> not use QSettings, that shouldn't have any ill side effects

that is what we already doing, so title is correct, but for not known reason
yet, no effect for icon

https://github.com/libyui/libyui-qt/blob/master/src/YQApplication.cc#L777

maybe we need to call also this
qApp->setWindowIcon ( QIcon ( pixmap ) );
to some predefined icon for yast, but I am not sure how it works with all
modules, as it probably have own icons.