Version: (using KDE 4.1.3) Installed from: Ubuntu Packages Close tab in konsole shortcut is not working because kopete also uses the same short cut . I noted before that close tab short cut was not working. I accidentally found this is the issue when I tried the short cut when I was offline and kopete popped up an errro.
Confirmed using current trunk too.
Isn't this a bug in the shortcut system? If there is a global shortcut and a window-specific shortcut bound to the same combination is the window-specific one supposed to take precedence? In any case, Ctrl+D can be used to exit the shell in any terminal which also results in the tab being closed - this may not work if you have other interactive applications running in the terminal and you will need to repeat this if you have nested shells running.
You're right Robert: do you suggest to move this bug to kdelibs?
ping? this 'bug' is pretty annoying. Anyway I suggest the kopete developers to change the 'Set away/back' shortcut to something else or retrograde it to window-specific shortcut as a temporary solution.
currently even CTRL+SHIFT+S is used by both kopete and konsole
It seems to me that there's bound to be overlap between applications' global shortcuts and per-application shortcuts. I'm not sure the Kopete guys could pick any default global shortcut without stepping on someone's toes. And this is a major annoyance: it's a problem even if you never start up Kopete. Maybe the right thing to do it to accept that there will be overlap, and change KShortcutsDialog (kdeui) to give some indication of this? My knee-jerk reaction was to check Settings -> Configure Shortcuts in Konsole, and I think that the dialog could grey-out the line for 'close tab' and show "overlaps X from application Y". That way, we leave the decision to the user: do they want ctrl-shift-w to close tabs, or toggle their away/present state?
*** Bug 279940 has been marked as a duplicate of this bug. ***
Assign it to kdelibs. See comment #2.
*** Bug 212022 has been marked as a duplicate of this bug. ***
Hi, kdelibs (version 4 and earlier) is no longer maintained since a few years. KDE Frameworks 5 or 6 might already have resolved this bug. If not, please re-open against the matching framework if feasible or against the application that shows the issue. We then can still dispatch it to the right Bugzilla product or component. Greetings Christoph Cullmann