guake icon indicating copy to clipboard operation
guake copied to clipboard
verified publisher icon Guake

Guake theme issues

Open sanderkoenders opened this issue 7 years ago • 8 comments

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 avatar Jun 12 '18 08:06 sanderkoenders

I am just going to casually bump this.

sanderkoenders avatar Jun 26 '18 06:06 sanderkoenders

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

gsemet avatar Jun 26 '18 10:06 gsemet

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

sanderkoenders avatar Jun 27 '18 11:06 sanderkoenders

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

gsemet avatar Jun 27 '18 11:06 gsemet

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

sanderkoenders avatar Jun 27 '18 12:06 sanderkoenders

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.

sanderkoenders avatar Dec 13 '18 08:12 sanderkoenders

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

Davidy22 avatar Apr 20 '22 03:04 Davidy22

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.

sanderkoenders avatar Apr 25 '22 12:04 sanderkoenders