Bug 393198

Summary:	adjusting filter mask properties results in gray overlay over picture, inability to move properties window
Product:	[Applications] krita	Reporter:	rebuilderster
Component:	Filter Layers	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	scottpetrovic
Priority:	NOR
Version:	4.0.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Screenshot of gray overlay when editing filter layer

Description rebuilderster 2018-04-16 17:31:18 UTC

I'm running Centos 7.

When applying a filter mask to a layer for the first time, everything works fine. When trying to adjust the settings for an existing filter mask by right-clicking on the mask layer in the layer docker and selecting properties, I get a gray overlay drawn over the Krita program window under the properties window that pops up, making it hard to see what color changes I'm making. Additionally, I can not reposition the properties window by dragging it, as doing so drags the entire Krita window around.

Comment 1 Scott Petrovic 2018-04-17 15:54:46 UTC

I think you are going to have to say what filter you are trying to use. I tried adding a couple different filter masks, then edited then, and did not see any grey overlay. Maybe it is specific to Centos.

Maybe a screenshot would help too to see what this overlay looks like.

Comment 2 rebuilderster 2018-04-17 17:18:56 UTC

Created attachment 112081 [details]
Screenshot of gray overlay when editing filter layer

Here's a screenshot of the issue.

Comment 3 rebuilderster 2018-04-17 17:20:43 UTC

I've added a screenshot of the issue. It's possible this issue is related to window management on Centos in some way. I'm running the default Gnome desktop environment that ships with Centos.

Comment 4 rebuilderster 2018-04-17 17:23:06 UTC

Sorry for the trouble, I've confirmed this is an issue with Centos. By default, the Gnome setting "Attached modal dialogues" is on, which results in this issue. Turning it off solves my problem.

Comment 5 Scott Petrovic 2018-04-17 17:53:14 UTC

Thanks for following up with that information. I am marking this bug as resolved.