search

Guake / guake

Drop-down terminal for GNOME
https://guake.github.io
GNU General Public License v2.0
4.42k stars 574 forks source link

Guake theme issues #1346

Open sanderkoenders opened 6 years ago

sanderkoenders commented 6 years ago

Issue I configured guake to start at login however it seems that the compositor isn't always loaded properly at that time and that causes the Guake theme to look awfull. A few seconds later the compositor will be up and running but guake has already encountered the error and will not repair itself. When I restart Guake everything looks fine again (because the compositor has now started). Would it be possible to implement a small delay after which Guake starts so the compositor has time to start? This issue mostly occurs on systems with Nvidia proprietary drivers installed.

Screenshot broken_guake

OS: Arch Linux Kernel: x86_64 Linux 4.16.13-2-ARCH DE: KDE 5.47.0 / Plasma 5.12.5 / Qt 5.11.0 Guake Version: 3.2.1

sanderkoenders commented 6 years ago

I am just going to casually bump this.

gsemet commented 6 years ago

Indeed I saw that on ubuntu 16.04 and 18.04 with autostart. A small delay might help indeed. Did you tried to add it in /usr/local/share/applications/guake.desktop: 

X-GNOME-Autostart-Delay=15
sanderkoenders commented 6 years ago

I don't think that will affect the autostart feature of guake.

gsemet commented 6 years ago

Ho, this file is actually in ~/.config/autostart

sanderkoenders commented 6 years ago

Ah let me try that. Will get back to you.

sanderkoenders commented 5 years ago

I am sorry that this took quite a while for me to get back on. The issue is still present and adding

X-GNOME-Autostart-Delay=15

to ~/.config/autostart/guake.desktop did not work. When I add it to the file and reboot it seems to work once but doesn't persist. When I inspect ~/.config/autostart/guake.desktop after a reboot it is set back to it's default values omitting the changes I made.

Davidy22 commented 2 years ago

On an Nvidia system and not able to reproduce, are you still encountering this issue?

sanderkoenders commented 2 years ago

I am no longer encountering this because this issue lead me to switch to Yakuake. So am I therefore not able to tell whether this issue is still a problem or whether an internal / external code change changed the situation.