[Bug 374259] New: YaST CLI doesn't work in text mode

newer
[Bug 301660] New: XGL management...

bugzilla_noreply＠novell.com

27 Mar 2008 27 Mar '08

08:06

https://bugzilla.novell.com/show_bug.cgi?id=374259 Summary: YaST CLI doesn't work in text mode Product: openSUSE 11.0 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: lslezak@novell.com ReportedBy: jsuchome@novell.com QAContact: jsrain@novell.com Found By: --- If I run any CLI command with /sbin/yast (e.g. /sbin/yast ldap help), YaST tries to open UI, closes it immediately and ends without any other result. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

28 Mar 28 Mar

08:38

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c1 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@novell.com AssignedTo|lslezak@novell.com |sh@novell.com --- Comment #1 from Ladislav Slezak 2008-03-28 02:38:01 MST --- It seems that the terminal is somehow reconfigured by ncurses UI. Starting the interactive mode via /usr/lib/YaST2/bin/y2base ldap '("interactive")' ncurses shows that echo is off (the pressed keys are not displayed). Stty returns these flags when started in ncurses UI: y2internal("tty: %1", SCR::Execute(.target.bash_output, "/bin/stty -a")); "speed 38400 baud; rows 24; columns 80; line = 0;\nintr = ^C; quit = ^\\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?;\nswtch = M-^?; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;\nlnext = ^V; flush = ^O; min = 1; time = 0;\n-parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts\n-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl ixon -ixoff\n-iuclc ixany imaxbel iutf8\nopost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0\nisig -icanon iexten -echo echoe echok -echonl -noflsh -xcase -tostop -echoprt\nechoctl echoke\n" Stty invoked in a console returns: # stty -a speed 38400 baud; rows 24; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; swtch = M-^?; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts -ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc ixany imaxbel iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:30

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c2 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com Status|NEW |NEEDINFO Info Provider| |mvidner@novell.com --- Comment #2 from Stefan Hundhammer 2008-03-28 04:30:06 MST --- Martin, isn't this the same thing as in all the YCP modules' test suites when the "dummy UI" is used? It works there, so what's wrong here? Is that something in the /sbin/yast2 script (not correctly using the dummy UI in such cases or something like that)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

1 Apr 1 Apr

10:49

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c3 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mvidner@novell.com | --- Comment #3 from Martin Vidner 2008-04-01 04:49:06 MST --- No. There is no attempt to use the dummy UI for the CLI. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

8 Apr 8 Apr

13:24

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c4 --- Comment #4 from Stefan Hundhammer 2008-04-08 07:24:52 MST --- Created an attachment (id=206759) --> (https://bugzilla.novell.com/attachment.cgi?id=206759) Patch for proposed solution (SVN base dir: http://svn.opensuse.org/svn/yast/branches/SuSE-SLE-10-SP2-Branch/qt ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:27

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c5 --- Comment #5 from Stefan Hundhammer 2008-04-08 07:27:37 MST --- (In reply to comment #4 from Stefan Hundhammer)

...

Created an attachment (id=206759) --> (https://bugzilla.novell.com/attachment.cgi?id=206759) [details] Patch for proposed solution (SVN base dir: http://svn.opensuse.org/svn/yast/branches/SuSE-SLE-10-SP2-Branch/qt )

wrong bug - sorry -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

9 Apr 9 Apr

13:23

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c6 Katarina Machalkova changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kmachalkova@novell.com --- Comment #6 from Katarina Machalkova 2008-04-09 07:23:50 MST ---

...

shows that echo is off (the pressed keys are not displayed).

It is done on purpose. Normally, you want to disable echoing the keys in curses app in general and enable it only in restricted areas of the screen (input fields etc.). Otherwise some key strokes (up, down, enter, space) will mess up your screen. It has been like that for ages and commandline worked fine just up to 10.3. I really very much doubt this is ncurses bug ... Why btw Commandline needs to initialize UI? Does it need it for some specific purpose? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:57

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c7 --- Comment #7 from Martin Vidner 2008-04-09 08:57:31 MST --- So, the output is realized by ag_tty, but ncurses prevents it by setting echo off. Therefore we should prevent the initialization of ncurses. I ran Y2DEBUG=1 .../y2base nfs-client '("help")' ncurses and looked for "curses" in the log. The initialization is provoked by UI::GetDisplayInfo which is done to initialize a global variable in Progress.ycp. I think it should be enough to modify GetDisplayInfo not to initialize ncurses and instead just return the info map. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:11

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c8 --- Comment #8 from Katarina Machalkova 2008-04-09 09:11:00 MST --- I just tried to rearrange the code of Progress.ycp and call UI::GetDisplayInfo not on the global level, but in the function that really uses it (there is only one such place - display properties are queried to find out if we are able to display these uber-cool greying out and coloring back again images ), and it seems to resolve the issue as well Got a fix, going to check in -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:17

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c9 --- Comment #9 from Katarina Machalkova 2008-04-09 09:17:12 MST --- Ok, but it does not help :( It does, for trivial commands such as help, or exit, but does not for those that actually add something - thus, call Read() function which in 99% of cases contains Progress::New and we're there again -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:32

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c10 --- Comment #10 from Katarina Machalkova 2008-04-09 09:32:55 MST --- Wait ... it fails for Perl modules only - YCP modules seem to work fine (tested with firewall and lan) This is what I get with users (perl-based): 2008-04-09 17:45:52 <0> dhcp14(4157) [libycp] ExecutionEnvironment.cc(pushframe):105 Push frame Mode::testMode () 2008-04-09 17:45:52 <0> dhcp14(4157) [libycp] ExecutionEnvironment.cc(pushframe):105 Push frame GetDisplayInfo () 2008-04-09 17:45:52 <0> dhcp14(4157) [ui] YUINamespace.cc(evaluateCall):703 Late creation of UI instance -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:44

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c11 --- Comment #11 from Stefan Hundhammer 2008-04-09 09:44:49 MST --- Somehow I get the impression that the yast2-perl-bindings simply always instantiate a UI, no matter what. Martin? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:04

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c12 --- Comment #12 from Martin Vidner 2008-04-09 10:04:26 MST --- No. Only when you call YaST::YCP::init_ui it creates the UI Y2Component. But in this case genericfrontend.cc does it at the very start anyway. But that's probably not what you mean by instantiating the UI. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23 Apr 23 Apr

13:47

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c13 --- Comment #13 from Jiří Suchomel 2008-04-23 07:47:07 MST --- Stefan, any news on this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Apr 24 Apr

13:05

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c14 --- Comment #14 from Stefan Hundhammer 2008-04-24 07:05:27 MST --- A UI is created in all cases, for Qt as well as for NCurses. Of course it is; why would it _not_ be created if there are UI calls? In the Qt case you are just lucky: The Qt UI doesn't do anything with your tty. It will probably create an X connection, however. You just don't see anything until a window is opened. In the NCurses case OTOH you realize that a UI is created because it initializes its tty, which of course it needs to do for subsequent NCurses operations. Sample GDB session using the Qt (!) UI: sh @ snell] ...share/YaST2/clients 18 % gdb /usr/lib/YaST2/bin/y2base GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) break YUIComponent.cc:150 No source file named YUIComponent.cc. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (YUIComponent.cc:150) pending. (gdb) run ldap '("interactive")' qt Starting program: /suse/sh/util/y2base ldap '("interactive")' qt Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1215056176 (LWP 24559)] Breakpoint 2 at 0xb75c0b2d: file YUIComponent.cc, line 150. Pending breakpoint "YUIComponent.cc:150" resolved [Switching to Thread -1215056176 (LWP 24559)] Breakpoint 2, YUIComponent::createUI (this=0x80677e0) at YUIComponent.cc:150 150 YUILog::setLoggerFunction( yui_y2logger ); Current language: auto; currently c++ (gdb) bt #0 YUIComponent::createUI (this=0x80677e0) at YUIComponent.cc:150 #1 0xb75d584d in YUIFunction::evaluateCall (this=0x8071068) at YUINamespace.cc:704 #2 0xb7de48a4 in YEFunction::evaluate (this=0x822ad98, cse=false) at YExpression.cc:3126 #3 0xb7df0c01 in YEBracket::evaluate (this=0x8252450, cse=false) at YExpression.cc:1747 #4 0xb7de6126 in YEPropagate::evaluate (this=0x822acc8, cse=false) at YExpression.cc:1156 #5 0xb7dfc496 in YSAssign::evaluate (this=0x8252400, cse=false) at YStatement.cc:653 #6 0xb7e1a448 in YBlock::evaluate (this=0x8206478, cse=false) at YBlock.cc:604 #7 0xb7d7003b in Y2Namespace::initialize (this=0x8206480) at Y2Namespace.cc:307 #8 0xb7dfc195 in YSImport::evaluate (this=0x8206450, cse=false) at YStatement.cc:1793 #9 0xb7e1a448 in YBlock::evaluate (this=0x81752f8, cse=false) at YBlock.cc:604 #10 0xb7d7003b in Y2Namespace::initialize (this=0x8175300) at Y2Namespace.cc:307 #11 0xb7dfc195 in YSImport::evaluate (this=0x8175240, cse=false) at YStatement.cc:1793 #12 0xb7e1a448 in YBlock::evaluate (this=0x8160378, cse=false) at YBlock.cc:604 #13 0xb7d7003b in Y2Namespace::initialize (this=0x8160380) at Y2Namespace.cc:307 #14 0xb7dfc195 in YSImport::evaluate (this=0x81602e8, cse=false) at YStatement.cc:1793 #15 0xb7e1a448 in YBlock::evaluate (this=0x815ea98, cse=false) at YBlock.cc:604 #16 0xb7d7003b in Y2Namespace::initialize (this=0x815eaa0) at Y2Namespace.cc:307 #17 0xb7dfc195 in YSImport::evaluate (this=0x815e920, cse=false) at YStatement.cc:1793 #18 0xb7e1a448 in YBlock::evaluate (this=0x8079478, cse=false) at YBlock.cc:604 #19 0xb7d7003b in Y2Namespace::initialize (this=0x8079480) at Y2Namespace.cc:307 #20 0xb7dfc195 in YSImport::evaluate (this=0x8050048, cse=false) at YStatement.cc:1793 #21 0xb7e1a448 in YBlock::evaluate (this=0x8072518, cse=false) at YBlock.cc:604 #22 0xb7dd59e3 in YCPCodeRep::evaluate (this=0x8871518, cse=false) at YCPCode.cc:82 #23 0xb7ee3e2f in Y2WFMComponent::doActualWork (this=0x8072cb8, arglist=@0xbfc76d80, displayserver=0x80677e0) at Y2WFMComponent.cc:177 #24 0xb7d75541 in main (argc=0, argv=0xbfc76eb4) at genericfrontend.cc:680 #25 0xb7952f9c in __libc_start_main () from /lib/libc.so.6 #26 0x080484d1 in _start () (gdb) up #1 0xb75d584d in YUIFunction::evaluateCall (this=0x8071068) at YUINamespace.cc:704 704 m_comp->createUI(); (gdb) 127 void 128 YUIComponent::createUI() 129 { .. .. 148 y2debug( "Creating UI" ); 149 150 YUILog::setLoggerFunction( yui_y2logger ); 151 YUILog::setEnableDebugLoggingHooks( set_log_debug, // from y2log 152 get_log_debug ); // from y2log 153 154 try 155 { 156 if ( _requestedUIName.empty() ) 157 YUILoader::loadUI( _withThreads ); 158 else 159 YUILoader::loadPlugin( _requestedUIName, _withThreads ); 160 161 _ui = YUI::ui(); -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:14

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c15 --- Comment #15 from Stefan Hundhammer 2008-04-24 07:14:39 MST --- Created an attachment (id=210195) --> (https://bugzilla.novell.com/attachment.cgi?id=210195) y2log.bz2 Last log lines: 2008-04-24 15:11:45 <0> snell(24959) [libycp] ExecutionEnvironment.cc(pushframe):105 Push frame GetDisplayInfo () 2008-04-24 15:11:45 <0> snell(24959) [ui] YUINamespace.cc(evaluateCall):703 Late creation of UI instance 2008-04-24 15:11:45 <0> snell(24959) [ui-component] YUIComponent.cc(createUI):148 Creating UI -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:17

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c16 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sh@novell.com |lslezak@novell.com --- Comment #16 from Stefan Hundhammer 2008-04-24 07:17:17 MST --- Obviously, if there is a UI::GetDisplayInfo() call, a UI needs to be created. If creating a UI is not desirable, I suggest to not call UI built-ins. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:23

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c17 --- Comment #17 from Stefan Hundhammer 2008-04-24 07:23:38 MST --- [15:17:57] <jsuchome> HuHa: note that CLI is sometimes used only to gather some special argument, but still open UI (see yast2 online_update cd_update) [15:18:15] <HuHa> that's not a problem from the UI point of view [15:18:30] <HuHa> but as long as you don't want a UI to be created, don't use UI stuff ;-) [15:18:40] <HuHa> somewhere a UI::GetDisplayInfo() is hiding [15:19:15] <HuHa> the reason why bug #374259 was no problem in older versions might have been a different order of UI-internal initializations in NCurses [15:19:19] <buggy> bug #374259: YaST CLI doesn't work in text mode Product: openSUSE 11.0, Component: YaST2, Severity: Normal, Assigned to: lslezak@novell.com, Status: NEW https://bugzilla.novell.com/show_bug.cgi?id=374259 [15:19:23] <HuHa> but this is not something we can rely on or promise [15:20:15] <bubli> In the older versions UI::GetDisplayInfo did not create instance of UI [15:20:28] <HuHa> well, now it does [15:20:40] <HuHa> the only thing I could offer would be a special call [15:20:46] <HuHa> like UI::shutUp() [15:20:47] <bubli> It simply returned a map [15:21:02] <HuHa> at some point, a UI _needs_ to be created [15:21:17] <HuHa> and when that happens is an implementation detail [15:21:22] <bubli> UI::* should not be called unless one really wants to create UI instance [15:21:28] <HuHa> right [15:21:44] <HuHa> and if we find we can't guarantee that, we could introduce two special UI built-ins [15:21:51] <bubli> if (!Mode::commandline) UI::GetDisplayInfo; for example [15:21:58] <HuHa> one that makes each subsequent call return nil [15:22:03] <HuHa> until the other one is called -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:39

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Apr 25 Apr

09:34

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c18 Ladislav Slezak changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #18 from Ladislav Slezak 2008-04-25 03:34:47 MST --- Yeah, finally found it in PackageCallbacks module. Fixed in yast2-2.16.58. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

2 May 2 May

12:58

New subject: [Bug 374259] YaST CLI doesn't work in text mode

https://bugzilla.novell.com/show_bug.cgi?id=374259 User lslezak@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=374259#c19 --- Comment #19 from Ladislav Slezak 2008-05-02 06:58:23 MST --- Another fix is in yast2-2.16.61 - Mode::test() and some package callbacks called UI::GetDisplayInfo() -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5847

Age (days ago)

5883

Last active (days ago)

List overview

Download

20 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 374259] New: YaST CLI doesn't work in text mode

tags

participants (1)