Summary: | ctrl-t does not work, no effection, in all kde environment, with dolphin, chrome & terminal | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | tom888 <suzhengchun> |
Component: | keyboard | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | nate |
Priority: | NOR | ||
Version: | 18.04.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
tom888
2018-11-18 01:50:09 UTC
Does the issue reproduce with a new user account? Does it reproduce when using KWin as your window manager? (In reply to Nate Graham from comment #1) > Does the issue reproduce with a new user account? Does it reproduce when > using KWin as your window manager? I don't know the relationship between kwin and plasma, there's a kwin process in my computer. I will make it clear. I tested with another user, it's the same situation. It's okay with the command line login (ctrl-alt-F1), vim ctags works normally. And this is the xev's output: ctrl-t & ctrl-g --------------------------------------------------- KeyPress event, serial 40, synthetic NO, window 0x5000001, root 0x13f, subw 0x0, time 28397485, (246,276), root:(246,300), state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False FocusOut event, serial 40, synthetic NO, window 0x5000001, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 40, synthetic NO, window 0x5000001, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 40, synthetic NO, window 0x0, keys: 0 0 0 0 32 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 40, synthetic NO, window 0x5000001, root 0x13f, subw 0x0, time 28399689, (246,276), root:(246,300), state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ------------------------------------------------ KeyPress event, serial 40, synthetic NO, window 0x5000001, root 0x13f, subw 0x0, time 28418949, (246,276), root:(246,300), state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 40, synthetic NO, window 0x5000001, root 0x13f, subw 0x0, time 28420226, (246,276), root:(246,300), state 0x4, keycode 42 (keysym 0x67, g), same_screen YES, XLookupString gives 1 bytes: (07) "" XmbLookupString gives 1 bytes: (07) "" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x5000001, root 0x13f, subw 0x0, time 28420337, (246,276), root:(246,300), state 0x4, keycode 42 (keysym 0x67, g), same_screen YES, XLookupString gives 1 bytes: (07) "" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x5000001, root 0x13f, subw 0x0, time 28420559, (246,276), root:(246,300), state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ---------------------------------------------------- KWin is Plasma's window manager. This seems to be a user configuration issue. What seems to be happening is that you have two window managers going at once and one of them is eating the shortcut. This would explain why it works when you log in via the console, with no GUI. Please ask for help in a venue particular to your distro or KDE software rather then on the bug tracker. Thanks! |