During testing for bug #633556 I performed a downgrade to MATE-1.16.x With +gtk3 the window background transparency slider for mate-terminal is non-functional (unable to use non-opaque background). This is a regression compared to MATE-1.18.x which works as-expected.
Thank you for the report. Please *attach* the logfiles, https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide#Report_a_build-time_bug_.28emerge_failed.29 and reopen this ticket (Status:unconfirmed).
UPDATE: Changing to a setting USE -gtk3 doesn't fix this particular issue. It does, however, fix bug #633578 Really, I'd say this is an upstream issue, since it's fixed in 1.18.x I'd prefer dropping bug #633556 and mark these 1.16.x issues wontfix, that way time can be spent focusing on QA / runtesting, etc. for bug #625838 instead. ---------- (In reply to Jonas Stein from comment #1) > Thank you for the report. Please *attach* the logfiles, > https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide#Report_a_build- > time_bug_.28emerge_failed.29 > and reopen this ticket (Status:unconfirmed). See above. If you still want build.log I can provide that but I'll need to do it manually: [bash ~ #] ebuild `equery which mate-terminal` compile (emerge succeeds normally because this issue isn't a build-time bug, and it just shows up during runtesting)
Created attachment 497814 [details] emerge --info
Created attachment 497816 [details] emerge -pv x11-terms/mate-terminal As-per: https://bugs.gentoo.org/633580#c1 (if build.log is still desired please let me know)
Unexpectedly, re-tested using: mate-base/mate-common-1.18.0 x11-terms/mate-terminal-1.18.1 yet, the issue persists. This issue is coming from some other package, because when using a full MATE-1.18.x installation (instead of mixing older/newer branch 1.16 and 1.18 branches) this issue doesn't occur. Either way, USE +gtk3 is irrelevant for this problem.
Created attachment 497838 [details] /etc/portage/package.keywords/mate-terminal-1.16.x New testing with >x11-wm/marco-1.17 (plus various other deps which couldn't be avoided due to breakage, etc. when mixing branches) seems to explain why MATE-1.18.x resulted in a fix for this particular transparent background issue: the x11-wm/marco-1.18.1 package (probably?) is a workaround. That is to say: The issue wasn't caused by mate-terminal-1.16.1-r2 itself (created attachment for package.keywords entries)
Hypothetically, tracking down some non-mate window managers could be a route to run additional tests on mate-terminal (build or runtesting), but as I see it the only remedies for bug #633580 (at least for MATE users) might be: 1. The upstream-fixed version of x11-wm/marco from MATE-1.18.x version (at that point you'll have several deps on packages from MATE-1.18.x) 2. Switching to non-mate window manager (untested) if there's a strict requirement to use MATE-1.16.x
For testing bug #633556 I scrapped my 1.18 install and all it's deps completely, also I deleted all mate/gtk2/gtk3/apps-settings. Starting with a clean 1.16 -gtk3 install I do not hit this bug. Do you use any special settings for your terminal or simply the default ones?
(In reply to ernsteiswuerfel from comment #8) > For testing bug #633556 I scrapped my 1.18 install and all it's deps > completely, also I deleted all mate/gtk2/gtk3/apps-settings. > > Starting with a clean 1.16 -gtk3 install I do not hit this bug. > > Do you use any special settings for your terminal or simply the default ones? Other than the semi-opaque / transparent background, the only significant non-default I use for x11-terms/mate-terminal is a scaled up version of the terminus font to help accessibility-vision-type concerns. You seem to have pointed something out, possibly without realizing it: Seeing as I had downgraded from 1.18.x, but didn't think to wipe all MATE settings; this weekend I'll re-downgrade to 1.16.x, and then see if I can still reproduce the issue testing against a fresh user profile (save myself some hassle before I wipe my "everything the way I like it" custom theme, etc.) It really could just be "yet another broken theme issue" since the last time I did any work on that theme was during the few months I had tested 1.18.x Thanks for the insight / I'm looking into it.
Created attachment 498184 [details] $ ls -d /var/db/pkg/*/{mate,marco,caja,nvidia}* (In reply to ernsteiswuerfel from comment #8) > For testing bug #633556 I scrapped my 1.18 install and all it's deps > completely, also I deleted all mate/gtk2/gtk3/apps-settings. > > Starting with a clean 1.16 -gtk3 install I do not hit this bug. > > Do you use any special settings for your terminal or simply the default ones? It's not clear what you meant about scrapping all your deps... It's possible one of my deps could be affecting transparency on MATE-1.16 (x11-wm/marco-1.16.0-r1, mainly seems to be the one acting up) which makes the transparency break. Specifically, USE flags may affect xorg and/or window manager [ /etc/portage/make.conf ] USE="-gtk3 xa xvmc egl gallium vaapi vdpau dri osmesa -ibus -llvm -gstreamer" --- To eliminate all possible config/profile issues, I did the latest test with a clean /home/testmate/ (fresh as-of today, created via useradd -m) there was no difference. Attachment shows my currently installed MATE-1.16 packages, and the issue with non-transparent backgrounds still persists for x11-terms/mate-terminal-1.16.1-r2
After my second MATE 1.16 test drive with gtk2 vs. gtk3 I realized that I misconceived you initial post somehow... I can confirm that background transparency of mate-terminal is non-working in my MATE 1.16 install, be it with gtk2 or gtk3.
Please feel free to reopen with more info if you are still experiencing this bug
