Bug 441368 - Canvas displays black when changing frames in 5.0 beta1 - kubuntu
Summary: Canvas displays black when changing frames in 5.0 beta1 - kubuntu
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: OpenGL Canvas (show other bugs)
Version: 5.0.0-beta1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-08-22 14:32 UTC by Wojtek Trybus
Modified: 2021-08-23 20:11 UTC (History)
1 user (show)

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


Attachments
Displaying canvas fails when went loading existing frame (129.33 KB, image/png)
2021-08-22 14:32 UTC, Wojtek Trybus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wojtek Trybus 2021-08-22 14:32:32 UTC
Created attachment 140950 [details]
Displaying canvas fails when went loading existing frame

SUMMARY
Marked as OpenGL, but also related to Animation. OpenGL fails on kubuntu 20.04 when displayed frame is changed, and other existing frame needs to get loaded. You can create new frames and draw on them, but going back to any of them causes the whole screen to go black (screenshot attached).

The data is still there, and is displayed properly in the layers docker, but the only way to fix displaying the canvas is to reopen a document.

Bug is Linux, or KDE Plasma specific - I confirmed it works well on Windows 10.

STEPS TO REPRODUCE
1. Create a new animation document
2. Paint two frames in one layer
3. Go back to the first frame

OBSERVED RESULT
Black canvas as shown in screenshot

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-81-generic
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 31,4 GiB
Comment 1 Halla Rempt 2021-08-23 09:10:18 UTC
Does this also happen with the appimage? With the appimage, on KDE Neon, I cannot reproduce this.
Comment 2 Wojtek Trybus 2021-08-23 18:09:23 UTC
After more testing: this is caused by some of my settings - removing kritarc fixed the issue. So far I couldn't find a setting that caused it - it's not any obvious 'Display' setting, and may as well result from some add-on that left its trace in kritarc.

Should I close the report as "not a bug"?
Comment 3 Halla Rempt 2021-08-23 19:17:42 UTC
Yes, I don't think we'll be able to find the root cause.