| Summary: | Randomly fails to show reload prompt when file modified by other process | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | php4fan |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | christoph, kde.org, null, waqar.17a |
| Priority: | NOR | ||
| Version First Reported In: | 21.08.3 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
php4fan
2021-02-21 13:14:09 UTC
Operating System: openSUSE Tumbleweed 20210205 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.3 GiB of RAM Graphics Processor: Mesa DRI Intel® Iris® Plus Graphics Seems like your kate version is really old, can you try switching to a newer version (21.08+) and see if it happens. Can you please check and report back if this issue is still present with Kate 21.08.2, or later? I did a quick test with 21.08.2 and couldn't reproduce, although that doesn't mean much, as the issue has always been (apparently) random and never systematically reproducible (with known steps). I'll report back if it happens again. 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! The issue still exists. It has just happened to me. As already noted, it's not systematically reproducible. The reproduction steps sometimes will reproduce the issue, sometimes won't. Please reopen. Apparently I forgot to mention an important detail: Whenever this issue happens (that is, I give focus to Kate, and the prompt about the current file having been modified by another process fails to show up), if I switch focus between TABS back and forth within Kate (assuming I have several files open in Kate), then the prompt _will_ show up. The view needs focus to be able to show the externally modified message. Switching tabs does that, so that's why you get it. Can you try enabling this setting under "behavior" Show dialog for externally modified files And see if it resolves the issue? > The view needs focus to be able to show the externally modified message. Switching tabs does that, so that's why you get it. I'm not sure I understand what you mean, perhaps because I'm not sure what "the view" is exactly. Note that when I give focus to kate, the currently focused tab is the one where the modified file is, so I expect it to show the warning. The workaround is to switch to another tab *and then back* to the one that should have shown the warning in the first place. > Can you try enabling this setting under "behavior" > Show dialog for externally modified files > And see if it resolves the issue? To know whether or not it fixes the issue I would need to use it in this mode for a while, as the issue is random and doesn't reproduce always. But this option is completely unusable to me, because the effect is that the separate dialog will *immedietely* show up when the file is modified, and it *steals focus* from whatever I'm using even if Kate is not focused at the moment. That is: - open a few file in kate - give focus to something else - something else (whether it's related to what I'm doing outside of kate or it's some third unrelated process) modifies a file that is open in kate => KABOOM, kate's separate dialog with the warning (and Kate's main window itself behind it) pops up and steals focus from whatever I'm doing. I don't know if someone can find that behavior useful, I certainly don't and will never use it (actually I think that's a separate bug or design flaw but I wouldn't want it even if it worked properly). The only thing I care about is that the issue is fixed for the case where the "separate dialog" option is not enabled. By view I mean the current tab. And sure, feel free to take time to test it out. In the meantime I will see what we can do about this focus stealing issue. There is a bug for it already I'd I recall correctly. > And sure, feel free to take time to test it out.
I guess I wasn't too clear about that: I won't.
With the focus-stealing bug, it's not a viable workaround for the issue.
Once that is fixed, I don't really care whether or not the separate dialog is a workaround, I don't want the separate dialog.
> By view I mean the current tab So, just in case this isn't already clear from the original description and from comment 10, when I observe the issue the current tab, with the modified file, _has_ focus. The dialog stealing focus issue is now fixed. What is exactly the remaining issue here? > What is exactly the remaining issue here? I think the one originally described in the report (note also comments 7 and 8). Ignore the part that starts with "Perhaps I should note that another...", that turned out to be completely irrelevant. I have stopped using Kate long ago so I can't tell whether the issue still exists or not (again as per comment 7 it's not systematically reproducible, in any way that I know of, it happens rarely apparently randomly) but there has been no mention of it being fixed. The thing that apparently has been fixed is the unrelated issue described in comment 10 that made the workaround to this issue unusable. Hi, if you no longer use our software, I don't see us trying to reproduce this on our own. I am happy with the current state of the notifications in the default configuration. |