Bugzilla – Bug 252302
yast ncurses hangs on abort of installation sources module
Last modified: 2007-03-23 14:54:56 UTC
Yast2 ncurses hangs reproducibly when pressing abort in the installation sources module right after starting it (i.e. without doing anything else than looking at what installation sources are there). It sits there consuming CPU and spilling these two lines into the logfile: 2007-03-07 19:56:38 <3> sphinx(15586) [libycp] clients/menu.ycp:225 WaitForEvent(): No dialog existing 2007-03-07 19:56:38 <2> sphinx(15586) [YCP] clients/menu.ycp:262 Event or widget ID not handled: nil I've seen similar hangs in other modules, but don't remember exactly where and how to reproduce. Backtrace looks like this: (gdb) thread apply all bt Thread 1 (Thread -1218533680 (LWP 14945)): #0 0xb7652b43 in _int_free () from /lib/libc.so.6 #1 0xb7652d79 in free () from /lib/libc.so.6 #2 0xb7642646 in fclose@@GLIBC_2.1 () from /lib/libc.so.6 #3 0xb7b5d006 in y2_vlogger_function () from /usr/lib/liby2util.so.3 #4 0xb7b5d713 in y2_logger_function () from /usr/lib/liby2util.so.3 #5 0xb7e01652 in YCPBuiltinMap::YCPBuiltinMap () from /usr/lib/libycp.so.3 #6 0xb7e01b7f in YCPBuiltinMap::YCPBuiltinMap () from /usr/lib/libycp.so.3 #7 0xb7d891b6 in YEBuiltin::evaluate () from /usr/lib/libycp.so.3 #8 0xb7d9803a in YSExpression::evaluate () from /usr/lib/libycp.so.3 #9 0xb7db4be8 in YBlock::evaluate () from /usr/lib/libycp.so.3 #10 0xb7d97c14 in YSBlock::evaluate () from /usr/lib/libycp.so.3 #11 0xb7d989db in YSIf::evaluate () from /usr/lib/libycp.so.3 #12 0xb7d989db in YSIf::evaluate () from /usr/lib/libycp.so.3 #13 0xb7d989db in YSIf::evaluate () from /usr/lib/libycp.so.3 #14 0xb7d989db in YSIf::evaluate () from /usr/lib/libycp.so.3 #15 0xb7d989db in YSIf::evaluate () from /usr/lib/libycp.so.3 #16 0xb7db4be8 in YBlock::evaluate () from /usr/lib/libycp.so.3 #17 0xb7d97c14 in YSBlock::evaluate () from /usr/lib/libycp.so.3 #18 0xb7d989db in YSIf::evaluate () from /usr/lib/libycp.so.3 #19 0xb7db4be8 in YBlock::evaluate () from /usr/lib/libycp.so.3 #20 0xb7d97c14 in YSBlock::evaluate () from /usr/lib/libycp.so.3 #21 0xb7da79bd in YSWhile::evaluate () from /usr/lib/libycp.so.3 #22 0xb7db4be8 in YBlock::evaluate () from /usr/lib/libycp.so.3 #23 0xb7d73243 in YCPCodeRep::evaluate () from /usr/lib/libycp.so.3 #24 0xb7f461a7 in Y2WFMComponent::doActualWork () from /usr/lib/YaST2/plugin/libpy2wfm.so.2 #25 0xb7d16fff in main () from /usr/lib/liby2.so.2 #26 0xb7602f9c in __libc_start_main () from /lib/libc.so.6 #27 0x08048521 in main () Steps to reproduce: * start yast ncurses * enter the installation source module * hit abort * see a yast "blue screen"
Created attachment 123011 [details] y2logs: decompresses to 106MB!
Well, control center is not started afterwards again, rather than that, it is suspended and resumed back after the module has finished :-) Yet WFM::CallFunction (used in 10.2) might be the cause of endless loop (I remember running into pretty the same situation while I was implementing and testing UI::RunInTerminal), or it might not. Reporter, please try if you can reproduce by running standalone installation sources module from the terminal (i.e. by typing 'yast inst_source', not by choosing an item in a control center menu). If not, you can grab yast2-2.15.0, yast2-ncurses-2.15.1 and yast2-core-2.15.1 or newer from Factory, where the problem should be fixed. If yes, return back to us.
Can confirm that the bug does not appear with yast inst_source and is fixed in yast2-2.15.19-3, yast2-core-2.15.4-4 and yast2-ncurses-2.15.12-3. Thanks for help :) Am looking forward to having 10.3 on my servers.
*** This bug has been marked as a duplicate of bug 148683 ***