Konsole uses keyboard shortcut ctrl-pageup needed by some CLI apps

Bug #69231 reported by Thomas Zander
2
Affects Status Importance Assigned to Milestone
KDE Base
Invalid
Medium
kdebase (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: konsole

Using konsole from dapper, but also from edgy I see that the keyboard shortcut used in irssi to scroll back in the buffer no longer works.
The key is ctrl-pageup.

I found that the keyboard shortcut was reserved for switching tabs, so I opened the shotcuts settings dialog and pressed 'default' there.
I could no longer switch tabs, but the scrolling in the irssi buffer still is not possible.

Revision history for this message
Thomas Zander (zander-kde) wrote :

After logging in again it started working. No clue why.

I guess you can close the bug, the only problem is that the defaults are changed which grabs the key for switching tabs. Which I think is a mistake (its not even the same as other apps in KDE)

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Interesting thing is that when you go to configure shortcuts, konsole warns you about using ctrl+anything for shortcuts and tells you about the ones you have set. Of course, you never get this message when it's set like that by default.

ctrl+pageup/down are actually set to switch tabs in konqueror as well (on Feisty) so it is the same in other apps in KDE. However, in both it is the alternate shortcut for switching tabs. I don't know how wise it is to take shortcuts used by console programs for kde/konsole by default, especially when there's already another short cut for that function (shift + right/left).

Changed in kdebase:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Still a problem with Konsole 4.0.83. crtl + Page up in Irissi switches tabs instead of going back up.

Changed in kdebase:
importance: Undecided → Unknown
status: New → Unknown
status: Confirmed → Triaged
Changed in kdebase:
status: Unknown → New
Changed in kdebase:
status: New → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Looks like upstream won't fix this, which means we probably won't either. (Unless you can petition upstream)

Changed in kdebase:
status: Triaged → Won't Fix
Changed in kdebase:
importance: Unknown → Medium
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.