if you rename a file (F6) whose name consists of three letters, first letter is lost and is equal to the third
(SLED 11 SP2 is new-fresh installed)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I must not be understanding completely. I have a file named ‘tes’ and I
can rename it to ‘qwe’ without any difficulty. Could you provide the
file name you are using and the name to which you are trying to
move/rename it? Having the location of this file in your filesystem may
also help. Does your user own this file, and through the user or the
group? If not anything else interesting about the file? Longer/Shorter
names have the issue?
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPZXxCAAoJEF+XTK08PnB571QP/j198rRsUcOJGyURliNDvqti
LfvghkackP4IAA920iWXDzrXY9CRsj0q0Eu531ZGUGQYNMen0jD0gsN3+TlttZQn
OxfJPunquW3cpF5WjDvp5JmK59btej61mqNRiAgl4a34h2t+jdy5RMyA9f+qbQ8R
EtbyPBvCKBPhpqNuMC3Os867LHcg+cIIkJ8gqybFkxiNQFrQxZFqFzXCYbYdq3Ek
EBkZ6Oi5cKqKxwTntlsr//JDB0CmqiO3HInK0l6hqDKJR/M9n5p5rohgUShg7zBX
/KGN7ol2lb9RYZiClkFhmmJqRCWzqZ6d2sRiFKjlQEheZk9pjWTalpvHPO9gs2V7
sleGLdI5SpWlDmz9rfvP+ETT34qoCwH/YuXFz6YSSsEM3+gFE4ZYSZYDkScb1Ana
QRR//oxOrDnCSg8F51P4GmldVA+HO0WhnCX/t3a3BDwk86tYmMyT4QSfhhfWRf7z
kJ96iaeBb6y+91iRm9Yx5cSNUw65a0RJ/QaxAy2L0UJjxM2Yn2h8aC1Y6gpF5U4g
WWfl23gXffgoUApYim7nGjXFPnMan/V4yFJS9yw+TyoQCmvPB/G1x9F5ZHao9qhc
u42L6ojfVZmjTAIhJTUHOiWV1n1Xelb1oNVCi6NX1NiO409AOpDhgYaHU9SZdNxj
v/fOgLV8bUnm7mssUF9U
=y1/U
-----END PGP SIGNATURE-----
SLED 11 SP2 is new-fresh standard installed (ext3, one default user), + mc, gcc.
When install was chosen Russian language and US keybord.
if you rename a file (F6) whose name consists of three letters, first letter is lost and is equal to the third
X11 or not, it does not matter;
anyone user, any file, any rights, everywhere
for example:
*** F6 xyz ->zyz
Moreover, sometimes lost third from the end letter and is equal to the end letter.
Viewing in mc tar.gz
Instead “./bldinfo”, I see “./bldoifo”
I think Trouble in termcap, or utf8
PS. Installation was repeated, the error remains
PS.PS. I am sorry for bad english.
Silence? Kidding?
The above bug error rewrites root rights (700)
SLES 11 SP2 also
[QUOTE=dhrhdr;3210]Silence? Kidding?
[/QUOTE]
The forums are a place for people who use SLED to discuss it and help each other. Some people from Novell/SUSE may read and post on the forum but the forum is not a channel for getting support from Novell/SUSE. If you wish to get official support from Novell/SUSE for this issue you need to raise a Service Request.
You should also bear in mind that not everyone is in the same timezone as you. Whilst it is 10:00 where you are, it may be the person you are expecting to respond may be asleep because it is 02:00 where they are.
I cannot recreate the problem you describe with en_GB.UTF-8. What value do you have for $LANG?
I’m writing the third day of a serious error.
Wow! I need registering and to write to bugreport have only a trial copy.
locale:
LANG=ru_RU.UTF-8
This bug compromise your system no matter what my locale.
[QUOTE=mikewillis;3212]The forums are a place for people who use SLED to discuss it and help each other. Some people from Novell/SUSE may read and post on the forum but the forum is not a channel for getting support from Novell/SUSE. If you wish to get official support from Novell/SUSE for this issue you need to raise a Service Request.
[/QUOTE]
I tried it yesterday. Loginig but I could not to post to this forum and could not open Novell bugreport. ((
I can recreate your problem.
SLED 11 SP2 x86_64.
$ echo $LANG
en_GB.UTF-8
$ cd /tmp
$ mkdir mctest
$ cd mctest
$ touch rabbit dog monkey goldfish cat
$ mc
Select goldfish. Press F6 and rename goldfish to qwertyuiop. Works as expected.
Select dog. Press F6 and rename to qwe. Results in a file called ewe. Verify this in a second terminal window using ls.
Select cat. Press F6 and rename to qwe. Results in warning that file called qwe already exists. This is interesting, because there doesn’t appear to be a file called qwe. Say No to overwriting the file. Rename the file to tiger. Works as expected.
Select rabbit. Press F6 and rename to asd. Results in a file called asa. Verify this in a second terminal window using ls.
Select monkey. Press F6 and rename to asd. Results in warning that a file called asd already exists. Instead rename file to gorilla. Results in a file called goriala. This is an new variation on the problem.
Select tiger. Press F6 and rename to gorilla. Results in warning that a file called gorilla exists. Rename file to ape. Results in a file called epe.
cd /tmp
mkdir ./232
sudo chown root ./232
sudo chmod 700 ./232
cd /tmp
mkdir ./123
mc
F6 ./123 to 132
I don’t understand. What are the results you expect from that and what are the results you get? This
[QUOTE=dhrhdr;3229]cd /tmp
mkdir ./232
sudo chown root ./232
sudo chmod 700 ./232
[/QUOTE]
does not include mc and doesn’t appear to have anything to do with this
[QUOTE=dhrhdr;3229]
cd /tmp
mkdir ./123
mc
F6 ./123 to 132[/QUOTE]
I also see the problem on a SLED 11 SP1 x86 install but I’ve just tried on another SLED 11 SP2 x86_64 install and do not see the problem on it. So it seems the problem is not always present.
When I get time I’ll try building the latest version of mc and see if I get the problem with that.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bug# 752980 reported against the SLES side of things; mc is the same for
both. It may be worth trying mc 4.7.5.3 from the OpenSUSE side of
things as I do not see the problem there.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPZ+I6AAoJEF+XTK08PnB5hU0QAIOzr+elPCz4usP8DJsoVol/
CMZnq4/ojCL4MEDtogMdCPng9kgrHLjNrdOCXAtt30Vga853urpaqniw3F9rktDx
7kGuDCPcdhGKJOd3qD/UPJb/hnRWaW5vsnVoiPGqbDoIQ/676K3Yk4cb7LNTribT
b4Ht6L4M1YrDdgjI8ZHqyqQrHWZ1EWhgMxCnSriEg+UPlOwF/dLEgsUQ0LvkRbno
euQACa7IEDeAQFCilB9/ntVBV6lQg7/K6DajOe9GdQ+RF0/EGWsooO+9SBJ7n7zo
CAvUIHfdVONNw7J2Jr0U2wyUksKD4/rAn8yNmXqfPYcNuB2FInS3wg+kVnYQpf7S
Yw9/Jy5f0zrjnBs7nfn4IQQ6dxMgXYxduPD4H+4JNTG+jsPuxV0WtwSCVMlokePR
wd36zF2LsBK75y0r21pzR3i1UcXdALyuFyz/sEYhytpK9QHSjG0QzpXRzyakaWCy
TfpyPxi45QPOdD2GIAhvnkWIBGsT3FiRL8Lqsj9NEcFESwwpFK/WC6nkhchNNDYA
Ip9RAa8UCoMVJM87OdqZz8axvW37Yqc2UGQmXTTpBmAUdHzqsfAEo4Ye98xn0f83
z6r6hG0uw6XLIJstOXaH+MKFgMnMYxRB5PVR9VyCIpPJSYgxu+6cZihYnUhA10Rp
MxPWdNOeKf3NXZqmopJV
=YuuT
-----END PGP SIGNATURE-----
It looks like this issue is fixed in this update http://download.novell.com/Download?buildid=1ukQxnOYX80~
If you see this, install that update and let us know how you get on.