Bug 573962

Summary: The incorrect character in the field of the package size (probably output for limits of the array)
Product: [openSUSE] openSUSE 11.2 Reporter: Andrey Karepin <egdfree>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED UPSTREAM QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: aschnell, mvidner
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: wrong character

Description Andrey Karepin 2010-01-26 16:34:48 UTC 
User-Agent:       Opera/9.80 (X11; Linux i686; U; ru) Presto/2.2.15 Version/10.10

In an installation broad gull it is possible for packages, than the size is represented four characters (1000 Kb), after the first character is output as the unprintable character (look a screenshot in the application).

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



yast2-libyui-2.18.8-2.1.i586                                              
yast2-core-2.18.19-2.3.i586                                               
yast2-installation-2.18.33-1.1.2.noarch                                   
patterns-openSUSE-yast2_install_wf-11.2-20.22.1.i586                      
yast2-qt-2.18.7-2.1.i586                                                  
yast2-trans-ru-2.18.1-16.19.1.noarch                                      
yast2-2.18.25-2.5.i586
yast2-packager-2.18.13-1.1.3.i586
yast2-branding-openSUSE-2.18.0-2.1.noarch
yast2-perl-bindings-2.18.0-2.1.i586
yast2-control-center-qt-2.18.12-1.1.1.i586
yast2-control-center-2.18.12-1.1.1.i586
yast2-theme-openSUSE-Oxygen-2.18.10-1.1.1.noarch
yast2-theme-openSUSE-2.18.10-1.1.1.noarch
yast2-qt-graph-2.18.4-4.1.i586
yast2-metapackage-handler-0.8.10-0.1.1.noarch
Comment 1 Andrey Karepin 2010-01-26 16:35:58 UTC 
Created attachment 338888 [details]
wrong character
Comment 2 Arvin Schnell 2010-01-27 10:20:14 UTC 
The thousands separator in russian locale is broken. Already reported
upstream for gcc, see:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39243