http://bugzilla.opensuse.org/show_bug.cgi?id=972783 Bug ID: 972783 Summary: YaST2 modules and contol center crash on initialization Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: avsco@mail.ru QA Contact: jsrain@suse.com Found By: --- Blocker: --- After some update (perhaps in 2016, I guess), YaST can only launch its Control Center in GUI mode (Qt), but none of its modules work there; in TUI mode (ncurses in Konsole), even Control Center may fail to launch. If it matters, I am using LXDE desktop, since KDE freezes almost always with Noveau in Leap 42.1. Manually updating packages with `zypper patch` still does not help to fix YaST. Worth to note is that different modules and invocation methods produce different output, but the net result is the same: modules crash on initialization reporting a segfault, and thus YaST is practically non functioning at all. Below are several examples. yast2 --ncurses

YaST got signal 11 at file /usr/share/YaST2/clients/menu.rb:192 sender PID: 11 /sbin/yast2: line 440: 4123 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS PID 11 corresponds to "rcuos/0". No UI is shown at all (this is the default behavior in all examples, unless noted otherwise).

signal file:

YaST got signal 11 at file /usr/share/YaST2/clients/menu.rb:192 sender PID: 11 Liberating suppressed debugging messages: End of suppressed debugging messages Backtrace: /usr/lib64/liby2.so.4(signal_log_backtrace()+0x18)[0x7fd4ffe14628] /usr/lib64/liby2.so.4(signal_handler(int, siginfo_t*, void*)+0x164)[0x7fd4ffe14834] /lib64/libpthread.so.0(+0x10d60)[0x7fd4ff7dfd60] /lib64/libncursesw.so.6(mvderwin+0x38)[0x7fd4fbca4bd8] /usr/lib64/yui/libyui-ncurses.so.7(NCursesWindow::mvsubwin(NCursesWindow*, int, int)+0x2d)[0x7fd4fbf31d2d] /usr/lib64/yui/libyui-ncurses.so.7(NCWidget::wMoveTo(wpos const&)+0x160)[0x7fd4fbf583c0] /usr/lib64/yui/libyui-ncurses.so.7(NCWidget::wMoveChildTo(NCWidget&, wpos const&)+0x123)[0x7fd4fbf5a0a3] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::moveChild(YWidget*, int, int)+0x178)[0x7fd4fbf646a8] /usr/lib64/libyui.so.7(YLayoutBox::doResize(std::vector&, std::vector&, std::vector&, std::vector&)+0x8e)[0x7fd4fca9658e] /usr/lib64/libyui.so.7(YLayoutBox::setSize(int, int)+0x197)[0x7fd4fca96927] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::setSize(int, int)+0x99)[0x7fd4fbf64989] /usr/lib64/yui/libyui-ncurses.so.7(NCDialog::setSize(int, int)+0x137)[0x7fd4fbf614f7] /usr/lib64/libyui.so.7(YDialog::open()+0x1f)[0x7fd4fca8dcbf] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YCP_UI::OpenDialog(YCPTerm const&, YCPTerm const&)+0x2c6)[0x7fd4fcd08366] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YUINamespace::OpenDialog(YCPTerm const&, YCPTerm const&)+0x24)[0x7fd4fccedee4] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YUIFunction::evaluateCall_int()+0x284)[0x7fd4fccef984] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YCPBuiltinCaller::call()+0x1d)[0x7fd4fcd0d89d] /usr/lib64/libyui.so.7(YUI::uiThreadMainLoop()+0x41)[0x7fd4fca62f81] /usr/lib64/libyui.so.7(start_ui_thread(void*)+0xe)[0x7fd4fca630ce] /lib64/libpthread.so.0(+0x74a4)[0x7fd4ff7d64a4] /lib64/libc.so.6(clone+0x6d)[0x7fd4fe1abbdd]

/usr/share/YaST2/clients/menu.rb:192

UI.OpenDialog(Opt(:defaultsize), VBox(VStretch(), Label(_("Loading modules, please wait ...")), VStretch())) By the way, Konsole is running with 160x40 characters window. And, unlike in bug 955381, I only have one physical display (1920x1200) and run all programs on the first virtual desktop only.

/usr/lib/YaST2/bin/y2base disk qt

libGL error: unable to load driver: nouveau_dri.so libGL error: driver pointer missing libGL error: failed to load driver: nouveau libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast The GUI shows up at first, displaying the usual warning about partitioning dangers, then crashes upon proceeding. YaST got signal 11 at file /usr/lib64/ruby/vendor_ruby/2.1.0/yast/i18n.rb:134 sender PID: 32 PID 32 corresponds to "[migration/3]".

signal file:

YaST got signal 11 at file /usr/lib64/ruby/vendor_ruby/2.1.0/yast/i18n.rb:134 sender PID: 32 Liberating suppressed debugging messages: End of suppressed debugging messages Backtrace: (use c++filt to demangle) That is, backtrace is empty.

/usr/lib64/ruby/vendor_ruby/2.1.0/yast/i18n.rb:134

lang = WFM.GetLanguage.gsub(/\..*$/, "") By the way, I use LANG=en_US.UTF-8 without LC_* overrides.

/usr/lib/YaST2/bin/y2base disk ncurses

YaST got signal 11 at file /usr/share/YaST2/modules/Wizard.rb:424 sender PID: 11

signal file:

YaST got signal 11 at file /usr/share/YaST2/modules/Wizard.rb:424 sender PID: 11 Liberating suppressed debugging messages: End of suppressed debugging messages Backtrace: /usr/lib64/liby2.so.4(signal_log_backtrace()+0x18)[0x7f5339c59628] /usr/lib64/liby2.so.4(signal_handler(int, siginfo_t*, void*)+0x164)[0x7f5339c59834] /lib64/libpthread.so.0(+0x10d60)[0x7f5339624d60] /lib64/libncursesw.so.6(mvderwin+0x38)[0x7f53358abbd8] /usr/lib64/yui/libyui-ncurses.so.7(NCursesWindow::mvsubwin(NCursesWindow*, int, int)+0x2d)[0x7f5335b38d2d] /usr/lib64/yui/libyui-ncurses.so.7(NCWidget::wMoveTo(wpos const&)+0x160)[0x7f5335b5f3c0] /usr/lib64/yui/libyui-ncurses.so.7(NCWidget::wMoveChildTo(NCWidget&, wpos const&)+0x123)[0x7f5335b610a3] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::moveChild(YWidget*, int, int)+0x178)[0x7f5335b6b6a8] /usr/lib64/libyui.so.7(YLayoutBox::doResize(std::vector&, std::vector&, std::vector&, std::vector&)+0x8e)[0x7f53368db58e] /usr/lib64/libyui.so.7(YLayoutBox::setSize(int, int)+0x197)[0x7f53368db927] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::setSize(int, int)+0x99)[0x7f5335b6b989] /usr/lib64/libyui.so.7(YLayoutBox::doResize(std::vector&, std::vector&, std::vector&, std::vector&)+0x68)[0x7f53368db568] /usr/lib64/libyui.so.7(YLayoutBox::setSize(int, int)+0x197)[0x7f53368db927] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::setSize(int, int)+0x99)[0x7f5335b6b989] /usr/lib64/libyui.so.7(YLayoutBox::doResize(std::vector&, std::vector&, std::vector&, std::vector&)+0x68)[0x7f53368db568] /usr/lib64/libyui.so.7(YLayoutBox::setSize(int, int)+0x197)[0x7f53368db927] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::setSize(int, int)+0x99)[0x7f5335b6b989] /usr/lib64/libyui.so.7(YLayoutBox::doResize(std::vector&, std::vector&, std::vector&, std::vector&)+0x68)[0x7f53368db568] /usr/lib64/libyui.so.7(YLayoutBox::setSize(int, int)+0x197)[0x7f53368db927] /usr/lib64/yui/libyui-ncurses.so.7(NCLayoutBox::setSize(int, int)+0x99)[0x7f5335b6b989] /usr/lib64/yui/libyui-ncurses.so.7(NCDialog::setSize(int, int)+0x137)[0x7f5335b684f7] /usr/lib64/libyui.so.7(YDialog::open()+0x1f)[0x7f53368d2cbf] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YCP_UI::OpenDialog(YCPTerm const&, YCPTerm const&)+0x2c6)[0x7f5336b4d366] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YUINamespace::OpenDialog(YCPTerm const&, YCPTerm const&)+0x24)[0x7f5336b32ee4] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YUIFunction::evaluateCall_int()+0x284)[0x7f5336b34984] /usr/lib64/YaST2/plugin/libpy2UI.so.2(YCPBuiltinCaller::call()+0x1d)[0x7f5336b5289d] /usr/lib64/libyui.so.7(YUI::uiThreadMainLoop()+0x41)[0x7f53368a7f81] /usr/lib64/libyui.so.7(start_ui_thread(void*)+0xe)[0x7f53368a80ce] /lib64/libpthread.so.0(+0x74a4)[0x7f533961b4a4] /lib64/libc.so.6(clone+0x6d)[0x7f5337ff0bdd]

/usr/share/YaST2/modules/Wizard.rb:424

UI.OpenDialog(Opt(:wizardDialog), dialog)

/usr/lib/YaST2/bin/y2base sw_single qt

YaST got signal 11 at file :0 sender PID: 32

signal file:

YaST got signal 11 at file :0 sender PID: 32 Liberating suppressed debugging messages: End of suppressed debugging messages Backtrace: (use c++filt to demangle) That is, backtrace is empty.

/usr/lib/YaST2/bin/y2base sw_single ncurses Same result as with Qt interface. Currently, I receive the same results (at file :0 sender PID: 32) for `online_update` module in both GUI and TUI mode; but earlier in this session and previous sessions I always got `i18n.rb:134` related reports, as well as I do now for `sound` and `network` module. So, to summarize, the printed error message, if any, always points to one of these Ruby source files, whatever YaST module and UI backend I try: * /usr/lib64/ruby/vendor_ruby/2.1.0/yast/i18n.rb:134 * /usr/share/YaST2/modules/Wizard.rb:424 I do not recall any other source file or line being reported. I also have no idea whether this is a single issue or multiple issues seen as the same problem from the end-user point of view. If additional information is needed, please, let me know. -- You are receiving this mail because: You are on the CC list for the bug.