Termonad relies on VTE for the underlying terminal emulator. It would be nice to have an actual terminal emulator written in Haskell as well. If someone wanted to write that, I'd love to use it in Termonad.
Void Linux doesn't usually patch features. Transparency is the job of the compositor.
Transparency support was removed in 2013: https://wiki.gnome.org/Apps/Terminal/FAQ#How_can_I_make_the_terminal_transparent.3F
Not really, VTE seems to be operating exactly as advertised. Termite probably should not have existed in the first place if its sole stake is in a library that doesn't want to be what they're trying to use it for. Suggesting GTK and other projects from GNOME aren't intended to be used by others because a specific library doesn't want to change to be usable how the author of termite wants is, well, kind of stupid. Termite didn't even get a mention on gnome's page about VTE, https://wiki.gnome.org/Apps/Terminal/VTE.
In my view, the folks trying to get VTE to change didn't handle themselves or their updates very well. It ended up just being Termite users advocating for Termite, to the point where a maintainer in the bug reports had to remind them what was what. Their complaint was that "we're forking and now we have to maintain more packages", way before any discussion had even had a chance to take place. They put the ox before the cart, in my view.
Well, it is exaxtly what happens. Starting gnome terminal using a different terminal gives some more insight:
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8
https://wiki.gnome.org/Apps/Terminal/FAQ#Exit_status_8:
>The environment that gnome-terminal-server is started with does not correctly set the locale to a UTF-8 locale. Consult your distribution's documentation on how to fix this. Note that is it not relevant to check the locale settings from a different terminal (e.g. xterm); what counts is the environment that the session dbus-daemon passes to the processes it starts.
u/SumakQaw say: Don't know whether that applies to you, but being in the same situation not too long ago, I did the very same dpkg-reconfigure locales
, locale-gen
, editing etc/default/locale
and what not, to absolutely no avail, before finally stumbling upon an old Forum post, trivially suggesting to go to Settings --> Region & Language --> Language --> English.
It worked..
As far as I understood, that options is removed from the gnome-terminal app (I just assumed you're using that app). https://wiki.gnome.org/Apps/Terminal/FAQ#How_can_I_make_the_terminal_transparent.3F
I ran into the same issue as you did and, at the end, I decided to uninstall the gnome-terminal and install xfce4-terminal.
It was not on Wayland. I also tried remotely launching gnome-terminal
instead of instructing the X2Go Client to launch a Gnome session, which also failed. But I was able to capture an exit code of 10, which is explained here.
Do you have this directory ~/.dircolors
Rename that directory and close and open your terminal. To see if the colors have change for you. I believe it will created another ~/.dircolors directory. Wasn't for sure, that's why I had you rename it. Instead removing/delete it.
You can also try this.
./set_dark.sh
or
./set_light.sh
That's if you have these scripts and there executable.
You also try again. Maybe be successful next time around.
https://github.com/Anthony25/gnome-terminal-colors-solarized
Gnome 3.8 or higher
Be sure to have the dconf-cli package installed and do:
$ dconf reset -f /org/gnome/terminal/legacy/profiles:/PROFILE_ID"
Replace PROFILE_ID by your profile ID (you can get it in your profile configuration in gnome-terminal).