|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-ncurses doesn't handle spawning of interactive programs | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Peter Poeml <poeml> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | kkaempf, ma, mc, mlazar, suse-beta |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Peter Poeml
2006-02-14 14:23:32 UTC
I'm afraid nobody from YaST is able to fix this. Ask Werner or other ncurses guru. Edith, please assign to who's tasked to integrated lynx/w3m 'screen' works nicely. Daniel, please close bug, as soon as ncurses registration is tested. For native mode of YaST this is true. But launching it without threading solves the problem (according to stano). We thinkt about launching the ncurses YaST without threads. stano: could you make nacurses start without threads always!? We need to adapt /sbin/yast2 and YaST2.call to add --nothreads for ncurses as a server parameter. Added to /sbin/yast{,2} in yast2-2.13.34 and YaST2.call in yast2-installation-2.13.31.
|