Version: 4.3.2 (KDE 4.3.2) (using 4.3.2 (KDE 4.3.2), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.31-5.slh.4-sidux-686 In konqueror I tried to change the case of a fstab mounted samba folder from a Debian Lenny machine, from /mountpoint/lowercase to /mountpoint/Lowercase. This kicked up a dialog box that said: A similar file named '/mountpoint/Name' already exists The source file is '/mountpoint/name' I chose Write Into. Then I got the following dialog box: A similar file named '/mountpoint/Name/File1' already exists The source file is ''/mountpoint/name/File1' It offered me the following buttons: Rename (greyed out) - Skip - Auto Skip - Overwrite - Overwrite All - Cancel Overwrite & Overwrite All has no effect, I just get the dialog box again with the same file names. If I chose SKIP I get the dialog box with the next file. I can continue to choose SKIP and am given new dialog boxes. If at that point I choose Cancel the folder keeps its old name, nothing happens. If, however, I chose SKIP for all files or AUTO SKIP the directory disappears, it is not hidden, not in trash:/, it is apparently consigned to /dev/null. Even an 'ls -al' as root on my samba server shows no sign of the directory. This is a bit distressing. I played around with renaming the case of files, I didn't seem to have a problem. And changing the case of a folder in my home directory didn't give me this problem. I kept trying to make scratch folders with Dolphin and Konqueror and copying files in to them and then renaming them by changing the case. In Konqueror I managed to repeat my feat of making the folder disappear when renaming. Then I noticed a strange thing, I could create directories on my samba share but I could no longer copy files in to the new directories that I created with Konqueror or Dolphin. I get a dialog box: "INFORMATION - DOLPHIN: Count not write to /mountpoint/New Folder/testcopyfile.txt." However I can still use the GUI tools to copy in to other folders that I created earlier. When I looked that the Properties-Permissions I was the owner of the folder, but all the Advanced Permissions fields were greyed out, Owner, Group, Other. I could change the owner and permissions of the folder by chown & chmod using ssh to reach my share on the server but I still couldn't copy files to the directory with the GUI or using konsole as myself (me@client_hostname). I can copy files to the created folders with konsole if I am logged in to the server, either as root or as a user. But I can't see those files from the server either with konsole or with Dolphin/Konqueror. However if I "ls" the new directory via SSH as a user on the server the copied files are there. More weirdness, I can't copy files to the KDE GUI-created directories with Nautilus or PCMANFM, either. But if I create a folder with Nautilus or with Konsole at the command line, either logged in to my client or SSHed to my server I can copy files to the directory normally, even with Dolphin and Konqueror. By the way, if I use nautilus try to change the case of a directory name from "nautiluscreated" to "Nautiluscreated" I get the following message: The item could not be renamed. The name "Nautiluscreated" is already used in this folder. Please use a different name. It fails, but that is a better outcome than destroying the folder. But if I move the folder from my samba mount to my home directory and then try to change the case it works as expected, it changes the name of the directory to the new case. Here is another weirdness. Every time I disappear a directory by renaming it with Konqueror I get a .tmp file in the root folder on which my SAMBA share is mounted. So I deleted 4 directories by changing their case, three in my /mountpoint/multi sub-directory, one in my /mountpoint/DL sub-directory. Here is a "ls -l" of the pertinent files. drwxr-sr-x 9 ed ed 0 2009-11-10 10:29 DL/ -rw------- 1 ed ed 0 2009-11-10 10:06 DLoY2986.tmp drwxr-xr-x 171 ed ed 0 2009-11-10 08:56 multi/ -rw------- 1 ed ed 0 2009-11-10 08:49 multiGX3047.tmp -rw------- 1 ed ed 0 2009-11-10 08:53 multiwa3047.tmp -rw------- 1 ed ed 0 2009-11-10 08:39 multizt3047.tmp I know this is convoluted and hard to follow. This is apparently some sort of weird interaction between samba and Konqueror. I'm going to submit this report and then reboot my client and see what is happening. Maybe the directories will be back, I hope to at least be able to make folders on my samba share with konqueror and be able to copy to them. If not, I'll also reboot the server and see how it goes and report back. Oh, also, these are the options for my samba entry in my FSTAB: uid=1000,gid=1000,noperm,nocase,file_mode=0777,dir_mode=0777 I'm going to remove the noperm & nocase options and see if anything changes about this behavior after a reboot.
OK, I rebooted and still don't see any sign of my deleted folder(s), but mounting my share without the noperm,nocase options seems to fix the problem. Now I can rename a folder on my share by changing its case alone without deleting it, victory over communism. I searched through a reasonably recent version of Samba-3 by example PDF and the current samba man page and didn't find any reference to noperm or nocase, those are probably deprecated and no longer in common use. Probably only the 'nocase' option was at fault. I guess my case is of very limited interest to anyone, never mind, but you might leave this in place in case anyone else has this issue. It is still annoying to lose a whole directory, luckily I have it backed up.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!