Version: 3.4 (using KDE 1.2) OS: Linux I apply changes from a source file to a destination file during the diff. But, I can't save the destination file if it is read-only. Kompare doesn't ask if I want to save file anyway or even offer to change the file mode to make it writable. If I'm merging code diffs from on project version to another, it may often be the case that all destination files are read-only. I want to make these writable and merge the diffs. Kompare should offer to change buffer mode and then save the file (this is what Araxis diff does). Reproducible: Always Steps to Reproduce: Compare two files (ensure that destination file is read-only). Apply a change shown in the diff. Now try to save the destination file. Actual Results: The following message pops up: "Could not upload the temporary file to the destination location xxx/xxx. The temporary file is still available under: /tmp/komparexdW2Jb.tmp. You can manually copy it to the right place." Expected Results: If I 'chmod u+w' the destination file and then try saving, it works fine. Would be great if Kompare can offer to automatically change file mode in this way. OS: Linux (x86_64) release 2.6.26-2-amd64 Compiler: Target: x86_64-linux-gnu
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!