Version: (using KDE 4.3.3) OS: Linux Installed from: Ubuntu Packages Have a LAN with one Linux PC and 1 Windows XP Home Edition SP3 PC. When I install Ubuntu Desktop 9.10 on the Linux PC, I can access files on the XP shared folder seamlessly. I am never prompted for authorisation, login names, etc. I can read and write to those files using simple text editors and Open Office. When however I run Kubuntu Desktop 9.10 on the same Linux PC, I have intermittent access problems, namely: 1. Sometimes I can just browse through and open folders and files without any restriction. Intermittently however I will be prompted by smb for a login name and password. When I enter a valid login name and password for the XP PC it is always rejected. I have attached a trace from Wireshark which shows a valid access followed by a sudden smb authorisation request which is denied (file - 'successful then failed win access'). From the trace it appears that the login credentials I submitted are not being passed through, instead a login by 'anonymous' is being used. If however I access the Windows XP share directly from SMB the correct credentials are submitted (file - 'smb credentials accepted'). 2. Even when I can successfully write to the files on the XP PC, using a simple text editor such as Kate it works fine. If however I use Open Office the changes are not saved back to the XP PC. Instead I find the modified file has been stored on the Linux machine in folder \var\tmp\kdecache-ken\krun. These cached changes were never committed to the XP PC. These problems relate to an existing bug # 209431. I notice that bug seems to have no priority and no sign of anyone trying to confirm it. I do feel that the priority of this should be very high, because of those of trying to convince business Microsoft users to try Linux it is a show-stopper. Such users will never move wholesale to Linux, but can be convinced to try a Linux machine. They do however expect Linux to wortk seamlessly with Microsoft, and I don't believe this is unreasonable.
Many of these issues are caused by KIO not actually mounting the filesystem locally, which enables all software to interact with files and folders on the share normally as if they were local files; instead KIO provides transparent access only to KDE software; LibreOffice doesn't use KIO and so there are issues of the sort that you name. Unfortunately this requires either work in all non-KDE software, or else a major re-architecting of KIO. *** This bug has been marked as a duplicate of bug 330192 ***
*** This bug has been marked as a duplicate of bug 75324 ***
*** This bug has been marked as a duplicate of bug 40115 ***