yakuake can not get activated.

Bug #248661 reported by hunger
44
This bug affects 4 people
Affects Status Importance Assigned to Milestone
yakuake
Invalid
Medium
yakuake (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Yakuake is started here and a small window informs me that I can activate it with the following message: "Press to activate" (notice the missing keycombo!).

I have not set a custom key-combo, so F12 should activate the console, but that does not work either. I have so far found no way to make the yakuake-konsole appear.

This die work when I initially set up yakuake. The problems started to appear once I logged out/in again.

Tags: intrepid
Revision history for this message
Japje (x-launchpad-japje-nl) wrote :

i also experience this bug, as of the upgrade to alpha4 i can not use yakuake anymore. There is no way anymore to open/close the console.

Revision history for this message
Rich Johnson (nixternal) wrote :

First off I apologize for the length of time it took for someone to respond to this report. I am currently using Intrepid and I do not witness this problem at all. If possible, could you please list any information that may make it easier for me to help you triage this problem if it still exists.

Also take a look at the following:

System Settings -> Keyboard & Mouse -> Keyboard Shortcuts

Select the drop down and highlight Yakuake. Look at the setting for the shortcut and if it doesn't work for you, try and change it to something else.

Thanks.

Changed in yakuake:
assignee: nobody → nixternal
status: New → Incomplete
Revision history for this message
Chris Snyder (csnyder) wrote :

I am also experiencing this problem. I am using Yakuake under Gnome. The shortcut will retract Yakuake if it is open, but will not open it again. I have checked to make sure that it is still running. Neither my custom shortcut (meta+space) nor the default F12 work.

Interestingly, when I changed the shortcut command back to F12 to test, I was presented with a dialog box saying that the chosen command conflicted with a different action (Yakuake open/retract). This alternate action was not listed anywhere in the shortcut keys dialog - perhaps there is another configuration that is conflicting?

Revision history for this message
Chris Snyder (csnyder) wrote :

I've just gotten my Yakuake to work. The trick was to delete the current config (~/.kde/share/config/yakuakerc) and then launch Yakuake. Attached is my old, non-working yakuakerc to help in debugging the issue.

Revision history for this message
Japje (x-launchpad-japje-nl) wrote :

@Chris,

Tried that but didnt help. The first run window does not allow me to select ` as the key. And when i set it in the shortcuts it does not work.

The default f12 does work though. Even when i set it in yakuakerc it does not allow me to use my tilde (` or ~ ) as the toggle key.

this is what is in my rc when i freshly set it up the way i used to:

FirstRun=false

[Shortcuts]
toggle-window-state=`

Revision history for this message
meanasspenguin (jason-meanasspenguin) wrote :

I encountered this behavior as well (running yakuake under gnome in intrepid). It started happening after I enabled the visual effects.

As a note, anybody who just wants to get their session to re-appear should be able to run:
        qdbus org.kde.yakuake /yakuake/window toggleWindowState
and it will pop-up.

If you're not running intrepid (kde4) then a similar dcop command will unhide the yakuake window:
        dcop yakuake DCOPInterface slotToggleState

HTH,
meanasspenguin

Revision history for this message
Rich Johnson (nixternal) wrote :

Marking as confimed due to other responses and a duplicate bug report.

Changed in yakuake:
status: Incomplete → Confirmed
Changed in yakuake:
status: Unknown → Confirmed
Revision history for this message
wolfger (wolfger) wrote :

I've had this problem for a while now too, just too lazy to report it. I did define a custom key (scroll-lock) and used it successfully for quite some time, then one day it just quit. If I open the window (from the start menu, selecting Yakuake) I can close it using the shortcut, but I can't reopen it. Defining anything else as the shortcut does not have any effect.

I am using Yakuake Version 2.9.3 Using KDE 4.1.4 (KDE 4.1.4) on Intrepid, although I am running the KDE-nightly repo, so I don't believe that KDE version is accurate (and since my KDE is non-standard, I'm not sure my participation in this bug is helpful)

Tried to delete ~/.kde/share/config/yakuakerc but that did not work. On first run it asks me to define a key, but it does not actually set any key. I manually open the shortcuts and set it there and I am back to where I started. The shortcut will close the window but not open it.

Revision history for this message
jtheuer (mail-jtheuer) wrote :

In Y. 2.9.4 the problem seems to be that yakuake assigns the shortcut only for the app but not globally. It was lost during one of the update from intrepid to jaunty.

If you reassign the shortcut for global it will work.

Revision history for this message
Mohamed Fawzy (mohammed-m-fawzy) wrote :

I had faced this problem before.
This issue raised when I installed the "Desktop search" where the application's shortcut is also the same F12.
So I had changed the "Desktop search" shortcut, the quit the application.
then I stopped the running process of yakuake.
Then delete ~/.kde/share/config/yakuakerc.
restart yakuake again, at it worked for me.

Hope this could help.

Revision history for this message
jdh239 (jdh239) wrote :

I have the same problem with yakuake-2.9.5-5.1 on OpenSuse 11 (x86). I am using Gnome for my desktop. Interestingly enough, if I set the "Open window when the mouse pointer touches the screen edge" then that works. F12 never works except to close the screen.

Revision history for this message
t-lo (th-sc) wrote :

Same problem here. This is why I kept version 2.8(.1) which worked for me. But sadly this version will be removed from the package manager of my distro in a few days. So I will have to use >=2.9.6. Default F12 retracts but doesn't open yakuake. There is no conflict with the global shortcuts of other applications. I can set local yakuake shortcuts . I guess that is the shortcut type which retracts yakuake then. But if i try to input a global one it just switches back to "None". [And in the startup notification popup no key combination, too]

I see two workarounds for me which might work for others, too. Maintaining the 2.8 version locally (not with package manager) or defining a global shortcut in my window manager which opens up yakuake (btw, no qdbus or dcop required for that - just "yakuake" while it is running is enough).

But well, yes. They are workarounds.. If there is something I can do to help resolving the issue just let me know.

Cheers!

P.S.: Just found that in konsole when running yakuake I get: Undecodable sequence: \001b(hex)[?1034h
Maybe that helps.

Rich Johnson (nixternal)
Changed in yakuake (Ubuntu):
assignee: Richard Johnson (nixternal) → nobody
Changed in yakuake:
importance: Unknown → Medium
Revision history for this message
Ashley McMahon (ashleymcmahon) wrote :

Using Sabayan 7 Gnome, here is my workaround.
In a terminal enter: gconf-editor
Navigate to: apps-metacity-global_keybindings
assign run_command_1 to F8

Navigate to: apps-metacity-keybinding_commands
assign command_1 to value /usr/bin/yakuake

in yakuake assign F7 to Open/Retract Yakuake
Assign alternate F6 to Full Screen Mode

Control Yakuake with F8, F7 and F6 (or whatever you want)

Changed in yakuake:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.