After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 161362 - resize_reiserfs, ntfsrezize (and maybe other operations) doesn't work, because command line tools gets new size with thousand separator
resize_reiserfs, ntfsrezize (and maybe other operations) doesn't work, becaus...
Status: RESOLVED FIXED
Product: gparted
Classification: Other
Component: application
unspecified
Other Linux
: High major
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
: 315577 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-12-15 12:21 UTC by Mantas Kriaučiūnas
Modified: 2005-09-13 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mantas Kriaučiūnas 2004-12-15 12:21:02 UTC 
1. resize ntfs partition
2. press apply

Actual Results: ntfs partition remains the same size (doesn't resized)

Expected resuld: ntfs partition should be resized

It seems this problem is because ntfsresize gets new size with thousand separator
I started gparted in terminal and noticed this output:

echo y | ntfsresize -f /dev/hda1 -s 15.983M

My LANG is set to lt_LT (not UTF8)
Comment 1 Plors (Bart H) 2004-12-15 12:42:22 UTC 
hi ,

Could you attach the output of 'set' to this bug?

thanks
Comment 2 Plors (Bart H) 2004-12-15 19:40:14 UTC 
ah, nevermind. Fixed in CVS.

Thanks for reporting :)
Comment 3 Mantas Kriaučiūnas 2005-03-28 21:29:41 UTC 
This bug isn't fixed - I tried resize reiserfs with gparted version
cvs2005022001 in lt_LT.UTF8 locale and got an error and this output in terminal
window:

echo y | LC_NUMERIC=C resize_reiserfs /dev/hdc2 -s 4.519M

when I did "export LC_ALL=C and export LANG=C" resizing reiserfs starts to work
correctly and in terminal window output dot in 4.519 dissapeared
Comment 4 Plors (Bart H) 2005-09-08 21:14:09 UTC 
*** Bug 315577 has been marked as a duplicate of this bug. ***
Comment 5 Plors (Bart H) 2005-09-13 15:00:51 UTC 
ok, fixed in CVS (this time for real hopefully :) )
The error was caused by a custom int to string function which used the users
locale while creating the new string. If you had support for thousandseparation,
the resulting string would also include thousandseparators.