https://bugs.kde.org/show_bug.cgi?id=394376

--- Comment #4 from Beatrice <will89...@gmail.com> ---
I can't particularly say that I know what was going on with that either, or why
ticking unticking the "read only" box in my dropbox folder's properties made
any difference, if that actually had anything to do with it.  

Now I'm not even sure if that's the case, because I attempted to export moments
ago and the issue is still happening, which makes me think that something ELSE
I'd done in the meantime might've temporarily fixed the issue and the stuff
with the read-write permissions was unrelated.

It seems that I can still export to any folder outside of my dropbox folder
just fine. I can't say for certain that the dropbox client is causing the issue
somehow, but shutting it down seems to solve the problem. 

Starting the dropbox client up again seems to cause the issue to start
happening again, but not immediately. I'm not sure if it's just kicking in
after several minutes, or if it's allowing a few exports to go through before
it starts happening, but shutting down dropbox immediately restores export
functionality to krita. Maybe changing the read-write permissions caused the
dropbox client to treat the folder differently for a short time, and that's why
messing with those properties had an effect? Can't really do much more than
speculate there.

Additionally, I should have investigated this before, but Krita produces one
file that looks like these, on each failed export:
https://www.dropbox.com/s/fhnzu788jn66zdz/dda5742f045de3ed97334ab2df27f31c.png?dl=0

Removing the additional extension at the end of the filename seems to reveal a
properly exported file. This suggests that krita actually is managing to
export, but can't complete the process and properly name the file, for some
reason. 

Here's a copy of one of the files in question, if that's any help:
https://www.dropbox.com/s/trhgws7sc50q6mu/1-4.png.Ya7988?dl=0

Is there some sort of log I could dump that might provide more information?
Because I'm not sure if there's much more I can do to investigate here
otherwise.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to