Yakuake

System Software https://cgit.kde.org/yakuake.git/

Score 92%

Description:

Yakuake is a drop-down terminal emulator made by KDE.

--- What's new ---

3.0.4:
Yakuake v3.0.4 is a hotfix release that fixes building with Qt 5.7.

v3.0.4 download: http://download.kde.org/stable/yakuake/3.0.4/src/

3.0.3:
Yakuake v3.0.3 is a maintenance release that includes bugfixes and updated AppStream metadata and updated translations.

Full changelog at: https://cgit.kde.org/yakuake.git/tree/ChangeLog

--- Essential links ---

Yakuake's website: http://yakuake.kde.org/
Report bugs and wishes at: https://bugs.kde.org/enter_bug.cgi?product=yakuake
Older releases: http://developer.berlios.de/project/showfiles.php?group_id=7376

Last changelog:

Changes in 3.0.4: 9 months ago

* Fixed build on Qt 5.7.

1023 comments

1
2

3

4

5

6

7

8

9

10

Comments

Please login or register to add a comment

matafleur
2 months ago

most useful console emulator that i ever seen!

Report

malevolent666
1 year ago

Great app, undoubtedly a must have! But in 3.0.2 it seems to have troubles with multiple screens... it cannot stick at the monitor we specify (arch linux), sometimes it changes from screen A to screen B.
Also sometimes, it cannot stay over other windows, and is sent to back...

Report

themage
1 year ago

Thanks for continuing to offering yakuake.

One question is it possible to set full screen mode as permanent?

Report

avi9526
1 year ago

ctrl+ins not working, you can make it work in konsole 15.12.2, but not in yakuake 3.0.2

Report

flipwise
1 year ago

Greetings,

the latest Yakuake version (3.0.2) has broken the bash code for a blurry background effect.

The error thrown out is: "xprop: error: No window with name Yakuake exists!"

Has there been any change that leads back to this (window name)?

Report

SlyDeath
1 year ago

Yet another fix. You neeed to install "xdotool" from official repositories and change code for blurring like this:

active_wpid=`xdotool getactivewindow`
if [ `xdotool getwindowname $active_wpid | grep Yakuake` ]; then
xprop -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 -id $active_wpid;
fi

Report

Rojo
1 year ago

I'm having the same problem.
My system running yakauke 3.0.2 doesn't blur, but the system running yakuake 2.9.9 does.
On the system with 2.9.9, xprop shows WM_NAME(STRING) = "Yakuake". But on the system running 3.0.2, WM_NAME(STRING) = is blank.

Below is the code I'm using. It still works for Konsole, just not Yakuake 3.0.2.
konsolex=$(qdbus | grep konsole | cut -f 2 -d\ )
if [ -n konsolex ]; then
for konsole in $konsolex
do
for (( c=1; ; c++ ))
do
konsolewindows=$(qdbus org.kde.konsole | grep MainWindow_$c )
if [ -n "$konsolewindows" ]; then
xprop -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 -id `qdbus $konsole /konsole/MainWindow_$c winId`;
else
break;
fi
done
done
fi
if [ `qdbus | grep yakuake` ]; then
xprop -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 -name Yakuake;
fi

Report

slester
1 year ago

I noticed while using Powerline-patched fonts that Yakuake has weird spacing/clipping issues with the fonts, whereas they render perfectly in Konsole. They're using the exact same configuration as far as I can tell as well.

Compare the two: http://imgur.com/a/D2mJ1

Report

Sho
1 year ago

Probably Qt 4 vs Qt 5

Report

slester
1 year ago

Ah, okay, I didn't know they were using different things. Is there a timeline for Yakuake to start using Qt 5?

Report

Sho
1 year ago

It's been ported for a while, but I need to make a release still.

Report

flyingsheep
1 year ago

seems like you did, yay!

Report

Sho
1 year ago

Yeah finally! Sorry for the long long wait.

Report

sipovac
2 years ago

Just to say thanks for this great app.
Keep up the good work!

Report

Sho
2 years ago

Thanks!

Report

jospoortvliet
1 year ago

Yes, yakuake continues to rock ;-)

The only thing I miss is session management so it remembers all the tabs I have to open each time... But I don't restart that often ;-)

Report

rkrell
2 years ago

It would be nice to have a KDE Frameworks for this nice application.

Report

flyingsheep
2 years ago

There is!

https://projects.kde.org/projects/extragear/utils/yakuake/repository/show?rev=frameworks

it not released yet but you can build it. Using it every day.

Report

kaliif
3 years ago

I tried a skin with no titlebar and lost the buttons it contained. How can I access yakuake menu without the titlebar button, if only to revert the change?

Report

jucato
3 years ago

Not sure this is the official way, but one method is to edit the config file. Close yakuake, navigate to the ~/.kde/share/config/ folder and open up the yakuakerc file. In there you will see the lines:

[Appearance]
Skin=[name of your current skin]

You can delete those two to revert to the default skin.

Hope that helps.

Report

kaliif
4 years ago

Hi,

I can run a process in yakuake terminal like this:
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.runCommand "emacsclient smth". Is there a way to keep an eye on the process once it's started? What I need to do is to wait until the emacsclient in the terminal is closed and then do some cleanup. But there are some intermediate steps which mean the started process is not a child process anymore and the script where I run it from does not wait for it to end. Is there some built-in way to do this or at least get the pid of a process? Atm I have solved it by finding the pid and then using the while.. sleep loop but that's not particularly elegant solution.

Report

kaliif
4 years ago

Report

kaliif
4 years ago

Report

Sho
4 years ago

Can't think of a way, sorry.

Report

themage
4 years ago

Thanks for yakuake.

Without a doubt it has improved accessabity to terminal access for me and at the same time allowed me to keep my panel / desktop as minimalistic as possible.

I have had it configured so that it remains hidden at all times even after start up, until required.

For some time now it drops down as soon as I login, requiring me to hide it manually before doing any other task.

Is there a way to correct this behaviour, perhaps I've overlooked a setting with my most recent reinstall (due to HDD failure).

Report

Changes in 3.0.4: 9 months ago

* Fixed build on Qt 5.7.

Changes in 3.0.3: 9 months ago

* Fixed Yakuake sometimes showing up in the Task Manager.
* Much improved Wayland support on Plasma 5.
* Added a security warning when using the runCommand DBus API (as recently added to KDE Konsole as well).
* Switched to a different API for getting the user home path to avoid blocking on network logins.
* The bell notification event now uses the correct Plasma 5 sound file name instead of an old KDE 4 one that may not be present.
* Fixed standard CLI arguments like --help and --version.
* Code cleanups, e.g. porting away from deprecated API.
* Updated AppStream metadata.

12 years ago

Changes in 3.0.2:
* Added back a description file implementing the freedesktop.org AppData specification.

Changes in 3.0.1:
* Fixed installation and integratin of hicolor application icon.

Changes in 3.0:
* Yakuake was ported to KDE Frameworks 5 and Qt 5.
* A new default skin follows the Plasma 5 Breeze design.
* Terminal focus is now preserved more reliably when closing and reopening Yakuake.
* Config changes made via the title bar menu are now synced to disk immediately, and thus preserved if Yakuake is killed instead of quit gracefully.
* The option to auto-update tab titles with the title bar contents no longer interferes with manually setting a tab title. To return to auto-updating just clear the title.
* Performance improvements in the compositor-unassisted animation code path.
* Fixed bug causing incorrect window height calculation in multi-monitor systems.

Changes in older releases: https://projects.kde.org/projects/extragear/utils/yakuake/repository/revisions/master/entry/ChangeLog