Announcement

Collapse
No announcement yet.

Crl+V paste not working

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Crl+V paste not working

    Hi,
    I have installed Kubuntu 21.10 3 days ago, got all the updates, added a few programs.
    Ctrl+V is not working. Shift+Insert works, middle click to paste works. This is for Kate, Firefox, LibreOffice Writer, but it's the same for Dolphin when copy/pasting files.
    Checked under shortcuts and "Ctrl+V" and "Shift+Ins" is marked for paste. Ctrl+C does work. Tried to add some shortcut just to see if it would work, but it still doesn't. Tried restart as well, didn't work.
    I am on HP Laptop. From neofetch:

    Code:
    OS: Kubuntu 21.10 x86_64
    Host: HP EliteBook 8470p A1029D1102
    Kernel: 5.13.0-23-generic
    Uptime: 15 mins
    Packages: 2059 (dpkg), 3 (snap)
    Shell: bash 5.1.8
    Resolution: 1600x900
    DE: Plasma 5.22.5
    WM: KWin
    Theme: Breeze Light [Plasma], Breeze [GTK2/3]
    Icons: breeze [Plasma], breeze [GTK2/3]
    Terminal: konsole
    CPU: Intel i5-3320M (4) @ 3.300GHz
    GPU: Intel 3rd Gen Core processor Graphics Controller
    Memory: 1533MiB / 3790MiB
    Does anyone have any ideas what to try?
    Thank you.

    #2
    When you state: "Checked under shortcuts and "Ctrl+V" and "Shift+Ins" is marked for paste" what or where exactly do you mean? Here, there's no mention of "Ctrl-V" in System Settings > Shortcuts. meaning that it's default

    Please Read Me

    Comment


      #3
      Mine does. If you go to System settings>Shortcuts>Edit you can see default as well as anything you change. Or just write "paste" in settings search bar. I'm not sure how to embed a picture and it looks like I don't have the permission to add is an attachment. Here it is from google drive https://drive.google.com/file/d/1Q7l...ew?usp=sharing


      Comment


        #4
        OK, I see that now. Never looked that far South I guess. No need to share the pic, but you are correct in that you can't share pics yet. I suspect by the end of this thread, you will have enough posts to ad pics going forward.

        This is odd - never had this reported before. Sounds to me like some keymap or program function has grabbed the Crtl-V combo.

        In a terminal, what does "showkey -a" show?

        Please Read Me

        Comment


          #5
          So I did a bit more digging.

          First showkey does not see Ctrl+v:

          Code:
          showkey -a
          Press any keys - Ctrl-D will terminate this program
          
          ^C        3 0003 0x03
          v         118 0166 0x76
          ^[[2~     27 0033 0x1b
                       91 0133 0x5b
                       50 0062 0x32
                      126 0176 0x7e
          ^D       4 0004 0x04
          The sequence of presses was:
          LCtrl+c
          LCtrl+v - nothing
          RCtrl+v - nothing
          v
          Ins
          LShift - nothing
          Ctrl+d

          I tried "xev" as well. Here it is just for Ctrl+c and Ctrl+v:

          Code:
          KeyPress event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7560269, (33,42), root:(33,79),
          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 0x4400001,
          root 0x178, subw 0x4400002, time 7560736, (33,42), root:(33,79),
          state 0x4, keycode 54 (keysym 0x63, c), same_screen YES,
          XLookupString gives 1 bytes: (03) ""
          XmbLookupString gives 1 bytes: (03) ""
          XFilterEvent returns: False
          
          KeyRelease event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7560824, (33,42), root:(33,79),
          state 0x4, keycode 54 (keysym 0x63, c), same_screen YES,
          XLookupString gives 1 bytes: (03) ""
          XFilterEvent returns: False
          
          KeyRelease event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7561078, (33,42), root:(33,79),
          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 0x4400001,
          root 0x178, subw 0x4400002, time 7565044, (33,42), root:(33,79),
          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 0x4400001,
          mode NotifyGrab, detail NotifyAncestor
          
          FocusIn event, serial 40, synthetic NO, window 0x4400001,
          mode NotifyUngrab, detail NotifyAncestor
          
          KeymapNotify event, serial 40, synthetic NO, window 0x0,
          keys: 120 0 0 0 32 0 4294967168 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 0x4400001,
          root 0x178, subw 0x4400002, time 7565480, (33,42), root:(33,79),
          state 0x4, keycode 55 (keysym 0x76, v), same_screen YES,
          XLookupString gives 1 bytes: (16) ""
          XFilterEvent returns: False
          
          KeyRelease event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7565621, (33,42), root:(33,79),
          state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
          XLookupString gives 0 bytes:
          XFilterEvent returns: False
          
          MotionNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7570480, (40,35), root:(40,72),
          state 0x0, is_hint 0, same_screen YES
          
          MotionNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7570494, (47,27), root:(47,64),
          state 0x0, is_hint 0, same_screen YES
          
          MotionNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7570507, (54,21), root:(54,58),
          state 0x0, is_hint 0, same_screen YES
          
          MotionNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x4400002, time 7570522, (63,14), root:(63,51),
          state 0x0, is_hint 0, same_screen YES
          
          EnterNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x0, time 7570537, (76,4), root:(76,41),
          mode NotifyNormal, detail NotifyInferior, same_screen YES,
          focus YES, state 0
          
          KeymapNotify event, serial 40, synthetic NO, window 0x0,
          keys: 2 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 0 0 0 0
          
          MotionNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x0, time 7570537, (76,4), root:(76,41),
          state 0x0, is_hint 0, same_screen YES
          
          MotionNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x0, time 7570549, (84,0), root:(84,37),
          state 0x0, is_hint 0, same_screen YES
          
          LeaveNotify event, serial 40, synthetic NO, window 0x4400001,
          root 0x178, subw 0x0, time 7570563, (91,-4), root:(91,33),
          mode NotifyNormal, detail NotifyAncestor, same_screen YES,
          focus YES, state 0
          
          ClientMessage event, serial 40, synthetic YES, window 0x4400001,
          message_type 0x15c (WM_PROTOCOLS), format 32, message 0x15d (WM_DELETE_WINDOW)
          Sorry for the long paste.

          It looks like Ctrl+v does get captured, just not by showkey?

          By the way Ctrl+Shift+v works in terminal (Konsole), and I found another "Ctrl+v not working" thread, but the original OP gave up. What's interesting is that he was also on KDE, just Arch:
          https://bbs.archlinux.org/viewtopic.php?id=242090

          There are some others, but for older Ubuntu versions (16.04 or earlier). That was solved (for some) by enabling "Track Mouse" effect in gnome-tweaks. Tried that in KDE settings as well, but without success.

          Then I started looking at X11. I am running X11 so I just tried Wayland, and it works now (Ctrl+c, Ctrl+v, Ctrl+D):
          Code:
          showkey -a
          Press any keys - Ctrl-D will terminate this program
          
          ^C 3 0003 0x03
          ^V 22 0026 0x16
          ^D 4 0004 0x04
          Going back to X11 doesn't work. It's still strange that it doesn't work, and probably worth taking a look. If anyone needs any more info from my system do let me know. Would be glad to help.

          For now I guess I'll start using Wayland. Thanks for the help.

          Comment


            #6
            CTRL-v here in from showkey -a : ^V 22 0026 0x16

            CTRL-v in a terminal does not work by default since forever- something to do with break sequences I think. You're supposed to use CTRL-Shift-V in the terminal.

            Anyway, weird unless you changed something with a keymap or similar

            Please Read Me

            Comment


              #7
              Maybe this is a physical problem with your keyboard?

              Comment


                #8
                @oshunluvr
                Ctrl+v doesn't work in the terminal, but it should get displayed by showkey. However, when I am using X11 it doesn't display, only when using wayland.
                @Fred47
                There are no issues with the keyboard. It works with wayland. ctrl works for everything else, and "v" as well. And I haven't changed keymaps. All is default.

                Comment


                  #9
                  Originally posted by spiro2903 View Post
                  I have installed Kubuntu 21.10 3 days ago, got all the updates, added a few programs.
                  [emphasis added]

                  What programs did you add? Before you added 'them', were the shortcuts working as expected; did you try them?

                  Also, see https://www.kubuntuforums.net/forum/...647#post628647
                  Last edited by Snowhog; Jan 17, 2022, 02:39 PM.
                  Using Kubuntu Linux since March 23, 2007
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                  Comment


                    #10
                    I am not sure if Ctrl+v was working immediately on install. I think it was, but I was not paying attention to that to be 100% sure. It's one of those things that you use without thinking about it. Only when it doesn't work that you notice it.
                    The sw I installed was:
                    Educational SW:
                    • Blinken
                    • Cantor
                    • GCompris
                    • Kanagram
                    • KDE Marble
                    • KGeography
                    • KHangman
                    • Kig
                    • Minuet
                    Other:
                    • Kid3-qt
                    • Flacon
                    • Krita
                    • MyPaint
                    • Vim
                    • VLC
                    • Yakuake
                    Yakuake was actually my first suspect, but only because (I believe) it's the only sw here that changes shortcuts after install. It sets F12 as launch shortcut. I removed this, but there was no change in Ctrl+V behaviour, and it only uses F12, not Ctrl+V.

                    Before I installed any sw I did a 'sudo apt update' 'sudo apt upgrade' and rebooted.

                    Comment


                      #11
                      Originally posted by spiro2903 View Post
                      Ctrl+v doesn't work in the terminal
                      Normally in a "tty" (such as a shell prompt in a terminal) ^V is the "lnext" key, short for "literal next" I presume, which lets you put control characters in a command line. So you'd type it twice to get a ^V. Run stty -a to check that out.

                      Have you tried the assign it to something else trick? Choose some shortcut that's not important to you, and try to set it to ^V. Normally, the settings app warns you about what it's already set to; but I expect it will be ignored.
                      Regards, John Little

                      Comment

                      Working...
                      X