Bug 156961 - yast ncurses does not run after update
Summary: yast ncurses does not run after update
Status: VERIFIED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Karl Eichwalder
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 09:56 UTC by Karl Eichwalder
Modified: 2008-09-02 18:07 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Eichwalder 2006-03-10 09:56:11 UTC 
I did the update using yast ncurses.  After the reboot, calling "yast" on the text console results in a warning and asks for:

You need to install yast2-ncurses to use YaST2 text mode  interface

But yast2-ncurses is installed.
Comment 1 Michael Gross 2006-03-13 15:06:17 UTC 
Is there anything in the logs? On my machine it starts fine in Beta7 however I did not use the ncurses interface for installation.
Comment 2 Karl Eichwalder 2006-03-13 15:19:56 UTC 
Sorry, I forgot to save the logs.  Feel free to close it as "worksforme".  Or assign it back to me for reproduction (but that may take time).
Comment 3 Michael Gross 2006-03-13 15:38:57 UTC 
I don't think this can be fixed without more information. I assign it back to you for now and you can decide if you want to persue this further. If more people will experience this problem I'm quite sure more reports will be filed.
Comment 4 Karl Eichwalder 2006-03-14 13:30:22 UTC 
later
Comment 5 Karl Eichwalder 2006-05-09 12:35:49 UTC 
it does not seem to be occur for other people.
Comment 6 Bugzilla Account Maintenance 2008-09-02 18:07:44 UTC 
Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from LATER to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."