Package Details: gnome-terminal-transparency 3.48.1-1

Git Clone URL: (read-only, click to copy)
Package Base: gnome-terminal-transparency
Description: The GNOME Terminal Emulator with background transparency
Upstream URL:
Keywords: gnome terminal transparency
Licenses: GPL
Conflicts: gnome-terminal
Provides: gnome-terminal
Submitter: hoschi
Maintainer: hoschi
Last Packager: hoschi
Votes: 108
Popularity: 0.073652
First Submitted: 2016-04-12 21:23 (UTC)
Last Updated: 2023-05-08 22:17 (UTC)

Pinned Comments

hoschi commented on 2017-04-26 15:38 (UTC) (edited on 2022-11-06 16:47 (UTC) by hoschi)


This is less invasive than gnome-terminal-fedora because it doesn't include the notification feature. Therefore you can stay with the regular vte3 and vte-common! To fulfill the makedepends you probably need to install the packages itstool, docbook-xsl, appstream-glib and yelp-tools. Ensure that you have installed the package group base-devel, which is a requirement to use AUR.

Top Workaround with devilspie, fore- and background are transparent.

Bottom Background transparency with gnome-terminal, better readability.

@Users of Manjaro

Please check if Manjaro is providing the same version of GNOME, especially the dependencies vte3 and vte-common. If you want the package for an older release, you can pick the required files from the git log.

Latest Comments

1 2 3 4 5 6 .. 10 Next › Last »

hoschi commented on 2023-02-19 21:48 (UTC) (edited on 2023-02-19 21:48 (UTC) by hoschi)

I've removed the debug option. The vanilla package also removed it.

hoschi commented on 2022-12-01 11:29 (UTC) (edited on 2022-12-01 13:19 (UTC) by hoschi)

Thanks for your reports! If I get it right this is actually an issue within glib2 2.74.2-1 and a fix is already in testing glib2 2.74.2-2:

Therefore all packages using this g_str_equal() from ghash.h in glib2 with C++ should be affected. You can temporarily downgrade glib2, use the package from testing or just wait until it is moves to core (i.e. stable).
C++ is more restrictive about types than C which improves safety.

// edit
I've upgraded to glib2 2.47.2-2 and the issue is solved.

fsociety3765 commented on 2022-12-01 01:09 (UTC) (edited on 2022-12-01 01:15 (UTC) by fsociety3765)

The latest update 3.46.6-1 is failing to build for me.

Could I be missing something?

It fails shortly after the ninja build process starts.

[25/229] Compiling C++ object src/gnome-terminal-preferences.p/
FAILED: src/gnome-terminal-preferences.p/

It proceeds to [30/229] and then stops.

[30/229] Compiling C object src/gnome-terminal-server.p/meson-generated_.._terminal-search-provider-gdus-generated.c.o
ninja: build stopped: subcommand failed

Seems to be the same issue @Cryen reported. I am also seeing those same errors between build steps 25 and 30.

Cryen commented on 2022-11-30 23:44 (UTC) (edited on 2022-11-30 23:44 (UTC) by Cryen)

error: invalid conversion from ‘const void*’ to ‘const char*’ [-fpermissive]

Basically everywhere is (gconstpointer) (v1) or (gconstpointer) (v2)

hoschi commented on 2022-11-20 23:39 (UTC) (edited on 2022-11-20 23:40 (UTC) by hoschi)

Between mutter 43.0 and 43.1 a change was applied which probably causes the black background in fullscreen. Fedora shipped 43.1 on Thursday and is now also affected.

hoschi commented on 2022-11-16 16:18 (UTC) (edited on 2022-11-16 16:18 (UTC) by hoschi)

It is not related the the graphics card. Seems like Arch (on Wayland) is affected but Fedora not.

serene-arc commented on 2022-11-16 00:15 (UTC)

I am using a Nvidia card, a GTX 1660 Ti I believe. This is a fairly recent change (or I noticed it fairly recently).

hoschi commented on 2022-11-15 17:45 (UTC) (edited on 2022-11-15 23:13 (UTC) by hoschi)

I confirm this. The background becomes black with F11 when using Wayland upon an Intel HD3000 (Sandy Bridge). But when using X11 it remains transparent! With Fedora 37 running Wayland upon an RX 560 (AMD Polaris 21) the background remains transparent. Also within a virtual-machine, again with Fedora 37 and Wayland.

What graphics card are you using? Also an Intel?

serene-arc commented on 2022-11-14 09:01 (UTC)

@hoschi That's not the same fullscreen, I mean F11 where it fills the entire screen.

hoschi commented on 2022-11-08 23:50 (UTC)

I've tested with the light and dark theme on X11 and Wayland, it works fine in fullscreen (i.e. ALT+F10). Maybe an issue with a special theme?