|
Bugzilla – Full Text Bug Listing |
| Summary: | upgrading from 9.3 to 10.0 over ssh weird | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jonathan Arsenault <jonharson> |
| Component: | YaST2 | Assignee: | Stanislav Visnovsky <visnov> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jonathan Arsenault
2005-10-11 02:39:46 UTC
Yes. Please read: http://www.opensuse.org/Bug_Reporting_FAQ#YaST and provide the information described there. Morover, this sounds to me like a problem that is not caused by YaST itself, rather than by the terminal(-settings). Which encoding do you use on the system you're connecting from? UTF-8 is standard in 10.0, so this problem might be located here. Can you read all special characters at any yast2-dialog? Result of a locale on the machine used to connect from : jarson@sds-workstation:~> locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" /* all showing utf8 */ LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= This one is a i686 intel machine running suse 10.1a1 and yeah all dialog of YaST or other ncurse based program work fine. The target was running 9.3 on a duron with ati redeaon 7000. locale also show as utf-8 (didnt check before upgrade but was probably in utf8 too). So the installation finished and i was prompted to do a reboot as expected because of new kernel and the terminal unfrozed , was able to remotlly reboot the machine. Problem at reboot graphic are corrupted cpu all taken by X and box randomlly freeze. runlevel-5 is unusable. open other bug ? YaST wasnt instructed to log during the update, taugh this should be done automaticlly, so i dunno what to furnish as asked. OK, maby Stanislav can help us here? Could be a problem with the ncurses-Interface itself. I can't reproduce the problem. I'm afraid even the logs can't help here :( |