So I've run into this issue more than once with Kate, and it's very frustrating. I've been testing a program that requires me to disable the internet connection on my computer. I run the program with the network card disabled, and then I re-enable it and run the program again. During this time Kate is open and I have text files in it that are open on the network. The issue isn't instantaneous, it does take a while before Kate will crash. Initially I just thought it was a once-off but it happened regularly enough during my program test that I had to save the files I needed on the desktop (I lost some rough notes that weren't saved during the crash too). I appreciate that this is an edge-case but Kate should at least handle this scenario gracefully as network outages can occur. Ideally if the network connection drops, it shouldn't bother Kate until a save is attempted at which point Kate should tell the user the network is down and give them the chance to save locally. I know that Kate does make temporary saves, maybe that's the trigger for this? STEPS TO REPRODUCE 1. Create a text file on a network share, or network drive 2. Open it with Kate 3. Disable your network card 4. (You may need to make saves prior to disabling, I'm not sure the exact process, but it does happen) 5. Do some other work and wait for Kate to crash OBSERVED RESULT If left alone, Kate will eventually crash EXPECTED RESULT The network being down shouldn't affect Kate at all SOFTWARE/OS VERSIONS Windows: 10
Is it possible for you to get a stack trace of the crash?
Marking as waiting for infor
Unfortunately, I don't have the time to look into that. I mentioned that I'm currently working on a project and I can't get sidetracked.
I just did a bit of testing there, the problem is consistent. Open the file on the network, disable the network and click into Kate. It crashes every time. I wanted to try and save the file once the network was disabled but Kate is crashing when you click into it (with a network file open and the network disabled). Given that the bug is easy to reproduce and consistent, a stack trace from me isn't required at all.
> a stack trace from me isn't required at all. Its always helpful and needed. No matter how easy/hard the bug seems to reproduce. There are a thousand factors at play here. This bug doesn't occur on linux which makes this tricky and we dont have people who actively work on windows problems. That is why I asked for a stacktrace.
Still needs a backtrace
Fair enough, can you provide any links to do a stacktrace for Kate on Windows?
easiest way is to install windbg from Microsoft and start the debug nightmake in it.
nightly Kate versions available here: https://kate-editor.org/get-it/
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.
reopening as obtaining a backtrace is non trivial for a non technical user
> reopening as obtaining a backtrace is non trivial for a non technical user Unfortunately, I still don't have free time to follow this up. I'm still interested in a fix, and it's on my todo list... and I'll get to it, but a bot janny sweeping bugs from reporters within 15 days is hilarious. The developers aren't held to this standard, but reporters have to respond after 15 days? The developers are volunteers along with the bug reporters, but you want to put us on a deadline? Either do the same for developers or why should anyone report? Fuck this deadline shit. I'm eyeballs deep in other stuff at the minute, I'll get around to it when I have spare time. "WORKSFORME" is probably the worst concept ever devised and will drive people away from even reporting. I've only seen this 'WORKSFORME' occur recently, which is pure bollocks. It goes from 'NEEDSINFO', to no info provided, and then suddenly to "WORKSFORME". How does that even make sense? A bug is provided, no info for 30 days and then suddenly "WORKSFORME", yeah, brilliant. I'll get back to you when I find the time, put a deadline on it and I'm fucking out.
I agree that sometimes that bot is not helpful, but even if it closes the bug, you can still provide the info whenever you like and just re-open it. That is close to zero extra effort. Without automation like this, we will just be swamped with stuff.