Summary: | media-gfx/gimp struggles with updating the screen to reflect image changes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | rnddim |
Component: | Current packages | Assignee: | Sergey Torokhov <torokhov-s-a> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | proxy-maint, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
rnddim
2020-09-17 06:22:10 UTC
This is a long-shot but wondering if it's somehow related to the recent masking (then unmasking) of USE=openmp on libmypaint. > my package.use settings > that change VIDEO_CARDS: > > x11-base/xorg-drivers VIDEO_CARDS: -radeonsi > x11-libs/libdrm VIDEO_CARDS: radeon > > My video card is an AMD Radeon RX 5600. Why did you have to change VIDEO_CARDS settings for this packages? As mentioned in https://wiki.gentoo.org/wiki/AMDGPU for RX 5600 VIDEO_CARDS="amdgpu radeonsi" is required. Could you please re-check also kernel configuration? gimp-2.10.20-r1 compare to gimp-2.10.20 just allows to be configured against mypaint-brushes-2.0. You could test re-emerge gimp against mypaint-brushes-1.3. But warning messages most probably just warnings from mypaint-brushes. Could you also check if OpenCL option is disabled in menu "Edit - Preferences - System Resources - Hardware acceleration - Use OpenCL"? I've tried recompiling libmypaint without openmp, and that didn't affect anything (even after recompiling GIMP, just in case). I also checked and OpenCL is disabled in preferences (which is good, since I don't have an OpenCL implementation installed at the moment). For those special video card settings, as I recall for libdrm certain cards which need the radeonsi useflag also need the radeon useflag. My card doesn't need this, but for whatever reason the maintainers of the libdrm ebuild feel that this is one area where Gentoo users can't be trusted to figure out how to configure packages for their system, and thus require you to have that flag enabled (see bug #697552 for details). I can't quite recall the deal with xorg-drivers, but I think that's just an issue of not installing what isn't needed; I _could_ install whatever drivers come with leaving radeonsi enabled, but my card doesn't use them. And yes, the warnings are unrelated. Installing the older mypaint-brushes and the version of GIMP that requires them (2.10.18-r1), the warnings don't appear at all. A couple other hints: doing the same "create image from paste" operation in Krita works just fine, and I have no apparent issues with being able to use that program. I also recently encountered a random and currently unreproduceable bug with one firefox window suddenly being incapable of updating its contents graphically, and had to restart the program (the other firefox window I had open worked fine still, though). Overall this makes me think that this is a Gtk issue if the freak firefox bug is related, or definitely a GIMP issue if not. I don't know exactly what parts of kernel configuration you want me to check, but I'll give the needed settings on the AMDGPU page a once-over when I update my kernel just to be sure. >GIMP nowadays fails to update the screen when attempting to edit. For
>example, creating a new image from the clipboard will show the
>rectangle the image should appear in, but all you see is the
>transparency-indicating checkerboard. Zooming in/out or toggling layer
>visibility does nothing. If you draw on the image with the pencil or
>pen tool, then small blocks of the image, where drawing has occurred,
>will suddenly appear with the drawing.
I was having a near identical problem on gimp-2.10.28. I fixed the issue by clearing the GIMP ~/.config directory. I'm assuming some configuration option was deprecated and shouldn't have been preserved in an upgrade. I don't know if the problem is identical because of the difference in version and build flags, but have you tried that?
(In reply to Ian Ressa from comment #5) > >GIMP nowadays fails to update the screen when attempting to edit. For > >example, creating a new image from the clipboard will show the > >rectangle the image should appear in, but all you see is the > >transparency-indicating checkerboard. Zooming in/out or toggling layer > >visibility does nothing. If you draw on the image with the pencil or > >pen tool, then small blocks of the image, where drawing has occurred, > >will suddenly appear with the drawing. > > > I was having a near identical problem on gimp-2.10.28. I fixed the issue by > clearing the GIMP ~/.config directory. I'm assuming some configuration > option was deprecated and shouldn't have been preserved in an upgrade. I > don't know if the problem is identical because of the difference in version > and build flags, but have you tried that? Thank you so much for this, that fixed it for me also. Unfortunately I didn't have enough foresight to preserve a copy of my config directory beforehand so I can't debug which option was the root cause. If it happens again I'll save a copy and try and figure out what exactly is the cause. |