Bug 472419 - Changing resource drive prevents krita from opening when drive not present
Summary: Changing resource drive prevents krita from opening when drive not present
Status: REPORTED
Alias: None
Product: krita
Classification: Applications
Component: General (other bugs)
Version First Reported In: 5.1.5
Platform: Other Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-20 07:07 UTC by samacro14
Modified: 2023-07-20 07:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented 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 samacro14 2023-07-20 07:07:49 UTC 
SUMMARY


STEPS TO REPRODUCE
1. Change resource drive to an external drive in settings
2. Close krita and dismount drive
3. start krita

OBSERVED RESULT
Krita closes with missing databases

EXPECTED RESULT
Krita opens and detects the missing drive and allows the user to select a new drive

SOFTWARE/OS VERSIONS
Windows: krita 5.15

ADDITIONAL INFORMATION
I only noticed because I'm using an external drive as both storage for resources and recording my progress. The drive started to fail while I was working, so I closed krita and tried to open it again only to get a database error. I fixed the drive and everything is working again, but it bothered me that it forced itself to close when other than my external drive, the computer was fine.

I know that a failing drive might be outside the scope. That when you tell krita where the resources go, that is where they go. It seems capable of making the resources on the fly, so why force close when a drive is missing? I'd still like to use the software, even if it's resource drive fails, since the resources/drive can always be replaced. I'd rather not dig around in user folders to rename/remove files just to allow the software to run again.