This happens from 5.2.0 onwards up to current master, but was fine in 5.1.5 STEPS TO REPRODUCE 1. Go to the gamut masks docker 2. Select a Gamut mask, click edit 3. The canvas now turns into the Gamut Mask Editor, but it stays completely grey. It should show the color wheel and the current mask instead. If you know where the mask is supposed to be, you can still for example drag the shape, then Krita will start to update the canvas properly. See video: https://www.youtube.com/watch?v=uc84Hyd_dGs Krita Version: 5.2.0 and also 5.3.0-prealpha (git 7058e47) Hidpi: false Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.10.0-26-amd64 Pretty Productname: Debian GNU/Linux 11 (bullseye) Product Type: debian Product Version: 11 Desktop: GNOME Appimage build: Yes Locale Languages: en_US, en, en_Latn_US, en, en_US, en_Latn_US C locale: en_GB.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) HD Graphics 630 (KBL GT2)" Driver version: "4.6 (Core Profile) Mesa 20.3.5" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.3, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 4.6, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat
Confirmed, and by accident I found it's only when Canvas Graphics Acceleration is enabled. There's an error logged when doing this, too, but it's apparently unrelated. > Parsing error in contents.svg! Aborting! > In line: 1 , column: 1 > Error message: "unexpected end of file"