Bugzilla – Bug 461136
yast2 segfault over ssh -X
Last modified: 2009-03-17 16:22:07 UTC
> ssh -l root -t -X titi0 tcsh -l titi0|root[1]:~# yast2 YaST got signal 11 at YCP file /usr/share/YaST2/clients/menu.ycp:32 /sbin/yast2: line 437: 4741 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Exit 139
Created attachment 261564 [details] yast logs
Ok it needs some yast x11 stuff, pattern x11_yast will do. With that it works, but each font character is 3 metres wide. With xorg-x11-fonts-core it works, but looks ugly.
For the bold headers in large font sizes of the various modules, package liberation-fonts is also needed. Would it be possible to put appropriate dependencies into the X11 yast pattern without blowing the installation size too much?
Reassign to yast2-maintainers
The backtrace looks like this: Frame 0: /usr/lib/liby2.so.2 log_backtrace() Frame 1: /usr/lib/liby2.so.2 signal_handler(int) Frame 2: [0xffffe400] Frame 3: /usr/lib/libQtGui.so.4 QFontDatabase::load(QFontPrivate const*, int) Frame 4: /usr/lib/libQtGui.so.4 QFontPrivate::engineForScript(int) const Frame 5: /usr/lib/libQtGui.so.4 QFontMetricsF::leading() const Frame 6: /usr/lib/libQtGui.so.4 [0x4134f973] Frame 7: /usr/lib/libQtGui.so.4 [0x41350031] Frame 8: /usr/lib/libQtGui.so.4 QFontMetrics::boundingRect(QRect const&, int, QString const&, int, int*) const Frame 9: /usr/lib/libQtGui.so.4 [0x415d9884] Frame 10: /usr/lib/libQtGui.so.4 QLabel::minimumSizeHint() const Frame 11: /usr/lib/libQtGui.so.4 QLabel::sizeHint() const Frame 12: /usr/lib/YaST2/plugin/libpy2qt.so.2 YQLabel::preferredHeight() Frame 13: /usr/lib/libyui.so.3 YWidget::preferredSize(YUIDimension) Frame 14: /usr/lib/libyui.so.3 YLayoutBox::totalNonWeightedChildrenPreferredSize(YUIDimension) Frame 15: /usr/lib/libyui.so.3 YLayoutBox::calcPrimaryGeometry(int, std::vector<int, std::allocator<int> >&, std::vector<int, std::allocator<int> >&) Frame 16: /usr/lib/libyui.so.3 YLayoutBox::setSize(int, int) Frame 17: /usr/lib/YaST2/plugin/libpy2qt.so.2 YQLayoutBox::setSize(int, int) Frame 18: /usr/lib/YaST2/plugin/libpy2qt.so.2 YQDialog::setSize(int, int) Frame 19: /usr/lib/libyui.so.3 YDialog::setInitialSize() Frame 20: /usr/lib/libyui.so.3 YDialog::open() Frame 21: /usr/lib/YaST2/plugin/libpy2UI.so.2 YCP_UI::OpenDialog(YCPTerm const&, YCPTerm const&) Frame 22: /usr/lib/YaST2/plugin/libpy2UI.so.2 YUINamespace::OpenDialog(YCPTerm const&, YCPTerm const&) Frame 23: /usr/lib/YaST2/plugin/libpy2UI.so.2 YUIFunction::evaluateCall_int() Frame 24: /usr/lib/YaST2/plugin/libpy2UI.so.2 YCPBuiltinCaller::call() Frame 25: /usr/lib/libyui.so.3 YUI::uiThreadMainLoop() Frame 26: /usr/lib/libyui.so.3 start_ui_thread(void*) Frame 27: /lib/libpthread.so.0 [0x402ab1b5] Frame 28: /lib/libc.so.6(clone+0x5e) [0x4068f38e]
Sounds like a font issue. Mike, could you please help?
Yes a font issue is very possible. Is this related to bug #464214?
I don't know about the details here but as far as I see whatever font issue should never ever crash the whole YaST so that from my point of view it is a bug in yast2-core or in a sub-system or library which is used by yast2-core. Therefore I assign it to the default assignee for the current component YaST so that he can have a look. According to comment #2 it seems the segfault goes away after some appropriate packages have been installed but now a bad-looking font issue appears but this one according to comment #3 seems to also go away after one more package has been installed so that in the end the whole issue is solved when some required packages are installed?
(In reply to comment #8) > whatever font issue should never ever crash the whole YaST > so that from my point of view it is a bug in yast2-core > or in a sub-system or library which is used by yast2-core. Yes, except YaST crashes are not always due to yast2-core. In this case I pass it on to yast2-qt.
For further info the crash also occurs with SuSE 10.3 since an on-line update to yast2. It segfaults repeatably, specifically when calling the software management module.
This also seems to be causing quite wide-ranging effects for a few users of yast as witness the SuSE forums in various references to segfault with yast and yast2 over the past few weeks. All seem to have the same X-error quoted with only very slight variations. For myself it seems to have broken "On-line update" in SuSE 10.3 as well as the Software management module. (Software management even from a console)
got this one: Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... Failed to load x11 FrontEnd module. Loading simple Config module ... Creating backend ... Reading pinyin phrase lib failed <00001161>:scim_skk_imengine.cpp:122 > Create SKK Factory : <00001162>:scim_skk_imengine.cpp:123 > Lang : ja_JP <00001163>:scim_skk_imengine.cpp:124 > UUID : ec43125f-f9d3-4a77-8096-de3a35290ba9 Loading socket FrontEnd module ... Starting SCIM as daemon ... Failed to open the panel socket Failed to open the panel socket YaST got signal 11 at YCP file Wizard.ycp:571 /sbin/yast2: line 437: 9869 Speicherzugriffsfehler $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... Failed to load x11 FrontEnd module. e.g. if i try to change settings in xinetd, i try it 4-5 times, 4 times i got this message, on the 5th try not... then it func correct. but i can reproduce this with yast2 not only with xinetd...
The backtrace is similar to bug #464214 's backtrace. => duplicate. *** This bug has been marked as a duplicate of bug 464214 ***