Bug 415086 - A file won't "draw"
Summary: A file won't "draw"
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: unspecified
Platform: Windows CE Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-12 11:38 UTC by Jessie
Modified: 2020-02-15 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jessie 2019-12-12 11:38:21 UTC
SUMMARY
A previous file, when opened, will not display new drawings via tablet, mouse, etc.

STEPS TO REPRODUCE
1. Open a previously saved drawing .kra with several layers
2. Enter a new layer, any kind
3. Attempt to draw. No success. Accepts Ctrl+Z, no visible result.

OBSERVED RESULT
No visible drawing, despite changes in brush, color, opacity, layer type. "Select all" and then "Deselect" fixes the issue.

EXPECTED RESULT
Drawing as normal?


SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Most recent Krita update, no hardware or software issues on user end (all other programs and hardware work just fine). New files and restored unsaved files do not have the same issue.
Comment 1 Tiar 2019-12-12 12:29:06 UTC
More information:
- it is hard to reproduce or catch the issue, but I've got several reports of this happening already:
Example: https://www.reddit.com/r/krita/comments/e55mmq/i_cant_create_any_new_lines_and_cant_transform/ (then it happened again to the same user...)
- Jessie reported they are using two displays, one of which has a web browser etc. which they switch to often
- making new layers is possible, drawing isn't; when Krita is locked like that, closing and opening the file won't work, but opening new files will work.
- the file that was supposedly locked can be opened later with no issues.
- it only affects some .kra files but not others? 
- usually happens when there are more than one krita windows open? (mode: tabs)

Jessie can you please share the output of Help -> Show system information for the bug reports?
Comment 2 vanyossi 2019-12-12 15:33:41 UTC
Hi Jessie! Does this happen with one particular file or with all files previously saved and reopened?

I ask because Krita saves the active selection to the file, so when reopening the selection is still there. Make sure you don't have something selected outside the canvas area, or a very tiny selection, wich will make it hard to see. You can see current global selections in the menus: Select -> Show Global Selection Mask. If you have one just Deselect it: Select -> Deselect.
Comment 3 Tiar 2019-12-13 01:57:06 UTC
@vanyossi:
1) The Select -> Deselect menu entry was greyed out. The only way to fix it that we've found for now was Select -> Select All and then Select -> Deselect. I believe there are other ways, but I haven't found them yet (and I've never personally got this issue either).
2) If the file that appeared broken was saved and later opened in new Krita instance, it would be working again.
So no, while it can still be a user error, it's not such an obvious one.

I believe it can be related to switching focus (Qt does have a problem with it) or multiple displays (likewise), probably with input.
Comment 4 Tiar 2019-12-27 23:50:29 UTC
Note: https://www.reddit.com/r/krita/comments/egie0m/either_a_problem_or_ive_accidentally_messed/

Possible reason, stroke not ended correctly?

But the person above:
- had this issue with only one specific file.
- the issue persisted after reopening.
Comment 5 Tiar 2020-01-16 12:03:52 UTC
@Jessie please download Krita Plus version and check if this issue happens there.
Comment 6 Bug Janitor Service 2020-01-31 04:33:13 UTC
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!
Comment 7 Bug Janitor Service 2020-02-15 04:33:22 UTC
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!