Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Artifacts left behind after drawing, fullscreen toggle removes them #948

Open
ElijahLynn opened this issue Nov 21, 2018 · 8 comments
Open
Labels
cat.Canvas Issue relates to the canvas platform.Linux.Wayland Issue is reported on Wayland protocol type.Bug Something isn't working as intended
Milestone

Comments

@ElijahLynn
Copy link

Description of the problem

Cursor-like artifacts left behind while drawing. Full-screen removes them or any type of action that seems to refresh the canvas.

mypaint-artifacts

Basic system details

MyPaint version: 1.2.1+gitexport.bcf5a28du
Operating system: Arch Linux - Rolling Release
Desktop environment: Gnome 3

Steps to reproduce

See GIF above

Backtraces or error messages

None

@ElijahLynn
Copy link
Author

The artifacts went away for about an hour, I don't know why. Then without restarting the application they came back.

@strikekat
Copy link

I'm getting the exact same issue as above. Any operation like moving the window, fullscreen, etc will refresh the canvas and remove the artifacting. They seem to appear with any element that appears on the canvas, i.e. the buttons in Inking mode.

image

I'm unfortunately stuck on X11 with the official Nvidia drivers, so wouldn't surprise me if that was responsible. I'll turn on hybrid graphics and try with Intel when I get a chance.

Basic System Details
Version: 1.2.1 (Both RPM and Flatpak)
Operating System: Fedora 30
Desktop: Gnome 3
Hardware: ThinkPad P52 Xeon with Quadro P2000

Steps to Reproduce
Any action drawing onto the canvas

Backtraces or Error Messages
None

@inigoval
Copy link

I get the same problem on ubuntu 19.10.
Anyone manage to fix this>

@jplloyd jplloyd added the cat.Input.Pointer Issue relates to pointing capabilities label Dec 10, 2019
@MMesch
Copy link

MMesch commented Sep 13, 2020

Same issue on NixOS 20.03 with Gnome 3, mypaint 1.2.1

@jplloyd
Copy link
Member

jplloyd commented Sep 14, 2020

These artifacts look like the result of invalidation rectangles not being aligned properly, or behaving differently on different systems. It would be good to know if anyone can reproduce this, at least semi-consistently, with the latest alpha builds.

@AesaraB
Copy link
Contributor

AesaraB commented Jan 17, 2024

Can confirm on OpenSuse CoreOS running Wayland, this doesn't occur for me with the Flatpak (which runs under xwayland)

I'll need to confirm this on X, too

@AesaraB AesaraB added this to the v2.02 milestone Jan 17, 2024
@AesaraB AesaraB added type.Bug Something isn't working as intended platform.Linux.Wayland Issue is reported on Wayland protocol cat.Canvas Issue relates to the canvas and removed cat.Input.Pointer Issue relates to pointing capabilities labels Jan 17, 2024
@odysseywestra
Copy link
Member

I am on the latest Build on Arch and I'm unable to reproduce the issue. That build is working under Wayland natively. I did install the flatpack, but the same results as the native build even though that one is using Xwayland.

I can say from hardware, I'm using all AMD with Ryzen 5 5600X and Radeon 5700 XT.

@AesaraB
Copy link
Contributor

AesaraB commented Jan 17, 2024

I can consistently reproduce this by enabling fractional scaling on Gnome. That would explain why xwayland is handling this fine.

I'm unsure if this applies with integer scaling... and I can't be bothered to go through dconfig right now.

@odysseywestra can you attempt to reproduce this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cat.Canvas Issue relates to the canvas platform.Linux.Wayland Issue is reported on Wayland protocol type.Bug Something isn't working as intended
Development

No branches or pull requests

7 participants