Lost key combinations in KDE

Bug #90405 reported by Reuben Firmin
6
Affects Status Importance Assigned to Milestone
meta-kde (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kde

I found this bug by being stupid.

I was doing some "tidyup" of hidden/config files in my home directory (which is the product of 5 years and a dozen or more distros) and assumed that files outside of .kde would not affect my desktop. Oops.

Anyway, I had a konqueror menu item mapped to win + K keys. Because the "cleanup", the application launchers on the panel became non-functional, so I deleted them and added them back. win + K changed behaviour -- whereas before it had loaded konqueror with a specific view profile, now it loaded the generic konqueror. I went into the menu editor to find it - but couldn't, it was no longer in the menu. I went into kcontrol, and searched on "key", and found the key mapping dialogs, and looked through them all. win + K is not there either. I then decided to make a new menu item and map that to win + K; however, I can't, because it's already in use. So now I'm stuck with an key combination that is not editable through the UI.

In summary, I consider the bug to be that application launching key combinations both are and are not bound to the KDE menu. Clearly, it is possible to remove a menu item, but leave the key mapped, thus making that key combination uneditable going forward. I would like the application launching key combinations to be directly editable from kcontrol, perhaps in addition to the menu editor.

Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

Hi,
Thanks for sending in this report. I'm trying to understand what you're experiencing.

You say:
"I then decided to make a new menu item and map that to win + K; however, I can't, because it's already in use."

Could you describe this more fully? Are you doing this from kcontrol? What exactly happens? Do you get the 'key conflict' dialog? ("The 'Win+k' key combination has already been allocated to the [something] action. Do you want to reassign it from that action to the current one?")

Could you also tell us which version of ubuntu you're using?

Dan

Changed in meta-kde:
assignee: nobody → daniel-ohuiginn
status: Unconfirmed → Needs Info
Revision history for this message
Reuben Firmin (reubenf) wrote :

Hi,

I do the following:

1) Open the K menu
2) Right click, edit menu
3) Browse to the konqueror item (there is only one konqueror in the whole menu)
4) Click on current shortcut key, which is currently set to "none"
5) Press win + K
6) A dialog pops up: "The key win+K can not be used here because it is already used to activate Konqueror"

Like I said, there is no other menu item for Konqueror (and if I look at key mappings under kcontrol or similar, it isn't listed). The problem with the mapping is that the Konqueror view profile it launches with is sub-par, so I'd really like to be able to edit the launch item.

Changed in meta-kde:
assignee: daniel-ohuiginn → nobody
Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in meta-kde:
status: Incomplete → Invalid
Revision history for this message
TTL (supernova-2149) wrote :

I had a similar problem after upgrading from 8.04 to 9.04 and using the KDE 3.5.10 from an alternate repo. The kmenuedit did not let me assign a key.
As workaround, open ~/.kde3/share/config/khotkeysrc
search for the key combination and remove the entry where it is found.
After this, it is possible to re-assign the key combination.

Note: This bug looks similar to the KDE 4.1 Bug: https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/296533

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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