Question

5

Guake Terminal transparency sometimes acts weird

rated 0 times [ 5] [ 0] / answers: 1 / hits: 4363 / 3 Years ago, sun, october 17, 2021, 2:36:07

I am using Guake since 11.04, and I like it very much, it's my default terminal. Obviously I am using it's transparency option.

Because I haven't paying too much attention to it, I am not sure if the default transparency should be. Should it make all the background window transparent and show me the desktop behind? Or should it be transparent only to the first application It has open in the background.

I ask this question because I have noticed in the past week both situation happen on my Ubuntu 11.10 install. So right now I am puzzled about how it should be. And because it shouldn't behave different from day to day, I am suspecting Guake not be fully compatible with Unity.

Any Ideas?

I attach a picture of how I have it now, transparent to the desktop through Chrome and Nautilus quake transparency to desktop

Edit:
I have just looked at Guake homepage on this screenshot.

I can clearly see that the transparency should not go until the desktop, but it should show the first application it has in the background.

Edit2:
Killed Guake and restarted it. The transparency works ok now:
enter image description here

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

damomnning

Add To Favorites

Follow

Total Points: 422

Total Questions: 90

Total Answers: 106

Location: Mali

Member since Thu, Aug 13, 2020

4 Years ago

answered 3 Years ago aclavadoug · Accepted Answer

As far as I know, this issue occurs with other terminals with transparency too (like Terminator) if they are set to start when you log in. If however, you manually start them (that's why it worked after you killed Guake), this issue doesn't occur.

So to fix it, you can create a simple script to launch Guake with a delay. Create a file called "guake-start.sh" in your home folder and paste this:

#!/bin/bash

sleep 15 && guake

"sleep 15" will make Guake start with a 15 seconds delay. If 15 isn't working for you, try a different value. Then save the file and make it executable using the following command:

chmod +x ~/guake-start.sh

And add guake-start.sh to your startup applications instead of the regular Guake executable.