Comment # 7 on bug 922023 from Martin Vidner

The above test, with 13.2 code, failed with:
2015-04-24 16:49:01 <1> dhcp139(878) [ui-component]
YUIComponentCreator.cc(createInternal):124 Creating UI component for ""
2015-04-24 16:49:01 <3> dhcp139(878) [ui-component]
YUIComponent.cc(createUI):144 createUI() called before setServerOptions() !


With the linking problem fixed, we get a little further:
2015-04-24 16:57:54 <1> dhcp139(1086) [ui-component]
YUIComponentCreator.cc(createInternal):124 Creating UI component for ""
2015-04-24 16:57:54 <2> dhcp139(1086) [ui-component]
YUIComponent.cc(createUI):156 Using dummy UI, NOT creating a UI
https://github.com/yast/yast-ruby-bindings/commits/347506fa098e9f847d95cf28754c2ff5dff62751

With ui_name changed from "UI" to "ncurses" in src/binary/Yast.cc, it does show
the dialog (yay!) but then crashed during deinitialization (even if I add
UI.CloseDialog)

2015-04-24 17:06:53 <1> dhcp139(1239) [ui] YUILoader.cc(deleteUI):104 Shutting
down UI
2015-04-24 17:06:53 <1> dhcp139(1239) [ncurses] YNCursesUI.cc(~YNCursesUI):113
Stop YNCursesUI
2015-04-24 17:06:53 <3> dhcp139(1239) [ui] YUI.cc(~YUI):88 shutdownThreads()
was never called!
2015-04-24 17:06:53 <3> dhcp139(1239) [ui] YUI.cc(~YUI):89 shutting down now -
this might segfault
(and it indeed crashes, though not with a segv, the details are better visible
with
strace -s999 -o strace.log -f ./ui-without-y2base.rb 
)

Branch updated.