Version: 4.0.0 (using KDE 4.4.2) OS: Linux I am not able to create a new Kdevelop4 project file from a CMakeLists.txt file, if the project directory is located on a Windows/Samba drive. This happens on both regular samba mounts and VirtualBox mounts (also Samba?), and for two different projects, on two different machines (one was a direct samba mount and the other was a VirtualBox sharing mount (which I believe is also Samba?). drives mounted rw, with uid, gid set to the same username as in linux, probably not a rights issue. I can open, read, write, make, execute project files using CMake, gedit & other tools. The problem seems to be with KDevelop's ability to create/write/rename the kdev4 file. I can also open and save new and revised text files from Kdevelop4 to the windows/samba directory with no issues. When copying all files to the Linux side, all works well and the project file is created successfully - so the problem does not appear on the Linux side of the Great Divide. When I copy the src.kdev4 file from the linux side to the windows side, and then proceed with the project on the windows side, all works perfectly well. There is therefore a problem with creating the file, via samba on a windows ntfs drive. Gedit has a problem that it tries to rename an open file on windows (= not allowed). Could this be similar? Reproducible: Always Steps to Reproduce: open a CMakeLists.txt file, located on a samba mounted Windows ntfs drive. in KDevelop do menu: <Project><Open project for current file> select the file <Next><Finish> then get a message: "Unable to load the project file /media/winw/MyApps/random/src/src.kdev4" Actual Results: Dialog box with above message appears. Expected Results: I would expect a valid Kdevelop project file src.kdev4. There is however not a single new file written to the windows/samba directory. OS: Linux (i686) release 2.6.32-22-generic Compiler: cc Ubuntu 10.4, fully up to date and upgraded as on 2010-06-24
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!