Bug 415501 - kate don't run because network resouce in recent files not avaliable
Summary: kate don't run because network resouce in recent files not avaliable
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: 19.08.2
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 421716 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-12-23 19:26 UTC by bes.internal
Modified: 2023-08-05 16:26 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description bes.internal 2019-12-23 19:26:51 UTC 
SUMMARY
kate don't load run most likely timeout for cheking recently opened files from network resource


STEPS TO REPRODUCE
1. open file to edit on network resource like (smb \\192.0.2.0\path)
2. close kate
3. make resouce unavaliable
4. open kate

OBSERVED RESULT
start as expected

EXPECTED RESULT
process run, but nothing happens


SOFTWARE/OS VERSIONS
Windows: 10 1809
most likely independent of OS
Comment 1 Justin Zobel 2020-11-02 01:48:50 UTC 
I can't reproduce this on Linux on Kate from git master.

Kate opens and I get an error, that's all.

Can you please confirm this is still an issue?
Comment 2 bes.internal 2020-11-02 06:40:53 UTC 
Problem still here with 60 sec timeout before open kate with resource unavaliable at Windows 10 2004 and kate 20.08.02
Comment 3 Justin Zobel 2020-11-02 07:30:05 UTC 
Seems it's limited to Windows then, have adjusted the field.
Comment 4 Donno 2020-11-05 19:42:51 UTC 
(In reply to Justin Zobel from comment #3)
> Seems it's limited to Windows then, have adjusted the field.

Have same problem in linux https://bugs.kde.org/show_bug.cgi?id=421716
Comment 5 Justin Zobel 2020-11-06 05:33:40 UTC 
*** Bug 421716 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Cullmann 2023-08-05 16:26:21 UTC 
That is fixed, we no longer check for existence on startup.