Created attachment 125028 [details] Kate with file modification option enabled with saved file SUMMARY When a file open in Kate is modified by a foreign process, Kate appears as an unusable split screen without any menu. Unmodified file content cannot be saved. STEPS TO REPRODUCE 1. Open Kate. 2. Enable monitoring for file changes outside of Kate. 3. Save the file to disk. (KateModifiedFileIssueImage1.png) 4. Modify the file outside of Kate. OBSERVED RESULT Kate becomes unusable (see KateModifiedFileIssueImage2.png attachment) EXPECTED RESULT Previous versions of Kate displayed a dialog box for the user to select appropriate action. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 31 with 5.4.7-200.fc31.x86_64 kernel (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2-1.fc31.x86_64 ADDITIONAL INFORMATION Problem has been occurring since fresh install of Fedora 31 KDE spin
Created attachment 125029 [details] IMage of problem when file has been modified
Tested with Kate launched from konsole. The following is output "Ignore changes" is selected but not when the other buttons are selected.
The same problem does NOT occur with kwrite.
Larry can you please expand on what you mean by kate becomes unusable? I've just echo'd a line "Test" into an existing document and it prompts me with the reload/overwrite/etc but it is still usable.
Created attachment 132888 [details] Kate window before ececuting "date >> /tmp/Msg.txt"
Created attachment 132889 [details] Same Kate window after executing "date >> /tmp/Msg.txt" and moving resulting dialog box lower
I reproduced the issue, moving the dialog box lower to help illustrate the symptom. Please see attachments. A vertically split screen condition is created that cannot be unsplit without closing Kate and all documents. Closing documents does not rectify the situation.
Requested information was added with comment 6; changing status for inspection.
Created attachment 133284 [details] Video
Larry can you please review the video I attached and confirm that's what you're trying to do?
Unfortunately not. Please view the image uploaded 2020-10-30 12:07 UTC and note that the menu bar has disappeared. Pressing "Ctrl-M" does not restore it and pressing "Ctrl-Shift-R" does not remove the split condition. I have found no way to resume editing without closing Kate. I am a developer and may have many files open including JSON or log files. Testing an application change without closing any files that might be modified (user-error, perhaps) forces me to close all open files. I may have to save unsaved files to /tmp if I don't know what changes have been made and not saved because I can't see the contents and then open each, identify the original file and diff them. The problem does not seem to be related to the number of open files. What OS did you test with? I have had this problem since Fedora 25 with fresh OS installs and updates. I just tried to recreate the sympton on a Fedora 31 server and Kate behaved as expected, prompting me for action and no split window. This server has very little customization in KDE, Plasma or Kate. Could some "preference" setting be a contributor? If you identify configuration files that may affect this feature, I can scrub and attach them to the case for your review to ascertain the cause(s).
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!
Information provided
Hi, does this happen in some Wayland session or X11?
just installed Fedora 35 and this problem no longer occurs.
Thanks for testing a new version and good that it is solved!