Using a wired aluminium Apple keyboard, Command-V has suddenly stopped
working in all applications. Command key is working. V key is working.
But together, no paste.

An Apple bluetooth keyboard is working fine, so not a System issue.

Apple forums and Google haven't provided a solution.

I have tried resetting the SMC. I have tried logging in as a new user. I
have checked Keyboard Shortcuts in System Preferences.

Any suggestions?

--
mhphillips at gmail dot com

On 21/06/2023 11:08, Michael Phillips wrote:
> Using a wired aluminium Apple keyboard, Command-V has suddenly stopped
> working in all applications. Command key is working. V key is working.
> But together, no paste.
>
> An Apple bluetooth keyboard is working fine, so not a System issue.
>
> Apple forums and Google haven't provided a solution.
>
> I have tried resetting the SMC. I have tried logging in as a new user. I
> have checked Keyboard Shortcuts in System Preferences.
>
> Any suggestions?

Hello Michael

As you've already tried various troubleshooting steps and the Command-V
combination is still not working on your wired Apple keyboard, here are
a few additional suggestions you can try:

1. Check for conflicting applications: Some applications may have
specific keyboard shortcuts that override the system defaults. Make sure
there are no conflicting keyboard shortcuts set within the applications
you're using. You can usually find these settings in the application's
preferences or settings menu.

2. Reset the keyboard settings: Go to "System Preferences" > "Keyboard"
> "Modifier Keys" and check if the Command key is correctly assigned to
the "Command" function. If it is, try clicking the "Restore Defaults"
button to reset all modifier keys to their default settings.

3. Test the keyboard on another computer: Connect your wired Apple
keyboard to another computer, preferably a Mac, and check if the
Command-V combination works there. This step will help determine if the
issue is specific to your keyboard or if it's related to the computer's
configuration.

4. Update macOS: Make sure you have the latest macOS updates installed
on your computer. Sometimes, software updates can resolve compatibility
issues or bugs that may be affecting keyboard functionality.

5. Use a different USB port or adapter: Try connecting the wired Apple
keyboard to a different USB port on your computer or use a USB adapter
if you're using a USB-C port. There could be an issue with the USB port
or adapter you're currently using.

6. Contact Apple Support: If none of the above steps resolve the issue,
it's recommended to reach out to Apple Support directly. They can
provide further assistance and help diagnose the problem.

Remember to mention the troubleshooting steps you've already taken when
contacting Apple Support, as it will help them understand the situation
better and provide more targeted solutions.

HTH

--
David

In article <jimaGBtBDPENwprxIvdyjuVAHFrnLtQr@news.usenet.farm>, Michael
Phillips <me@odtaa.com.invalid> wrote:

> Using a wired aluminium Apple keyboard, Command-V has suddenly stopped
> working in all applications. Command key is working. V key is working.
> But together, no paste.
>
> An Apple bluetooth keyboard is working fine, so not a System issue.

try the wired keyboard on a different mac and see if the problem still
exists.

On 21 Jun 2023 at 12:03:28 IST, "nospam" <nospam@nospam.invalid> wrote:

> try the wired keyboard on a different mac and see if the problem still
> exists

Only one Mac here, so no can do.

--
mhphillips at gmail dot com

On 21/06/2023 12:36, Michael Phillips wrote:
> On 21 Jun 2023 at 12:03:28 IST, "nospam" <nospam@nospam.invalid> wrote:
>
>> try the wired keyboard on a different mac and see if the problem still
>> exists
>
> Only one Mac here, so no can do.

Did you read my response to you, Michael?

Michael Phillips <me@odtaa.com.invalid> wrote:
> Using a wired aluminium Apple keyboard, Command-V has suddenly stopped
> working in all applications. Command key is working. V key is working.
> But together, no paste.
>
> An Apple bluetooth keyboard is working fine, so not a System issue.
>
> Apple forums and Google haven't provided a solution.
>
> I have tried resetting the SMC. I have tried logging in as a new user. I
> have checked Keyboard Shortcuts in System Preferences.

This app will print the key codes being generated:
https://apps.apple.com/us/app/key-codes/id414568915

There is also an event viewer in Karabiner Elements:
https://karabiner-elements.pqrs.org/

I'm not sure if it'll show command being pressed on its own, but it should
show Cmd+... combinations.

If the key code is showing, it's a software problem. If it's not, it may be
a hardware problem.

If hardware, I suppose it's possible for the key matrix to go bad in such a
way that no contact for Cmd+V to be detected, although that sounds pretty
unlikely to me.

If you have another USB keyboard or can borrow one from somewhere, see if
Windows+V works.

Theo

In article <lrTnkbkWtuUocbMgMummBLlTwuHtaFbN@news.usenet.farm>, Michael
Phillips <me@odtaa.com.invalid> wrote:

>
> > try the wired keyboard on a different mac and see if the problem still
> > exists
>
> Only one Mac here, so no can do.

try it on a friend or relative's mac.

On 21/06/2023 12:52, nospam wrote:
> In article <lrTnkbkWtuUocbMgMummBLlTwuHtaFbN@news.usenet.farm>, Michael
> Phillips <me@odtaa.com.invalid> wrote:
>
>>
>>> try the wired keyboard on a different mac and see if the problem still
>>> exists
>>
>> Only one Mac here, so no can do.
>
> try it on a friend or relative's mac.

Or take it into an Apple Shop and ask to try it on one of their display
machines!

On 21 Jun 2023 at 12:46:08 IST, "Theo"
<theom+news@chiark.greenend.org.uk> wrote:

> If the key code is showing, it's a software problem. If it's not, it may be
> a hardware problem.
>
> If hardware, I suppose it's possible for the key matrix to go bad in such a
> way that no contact for Cmd+V to be detected, although that sounds pretty
> unlikely to me.

In Keyboard Viewer:

Command and V separately highlight as expected.
Command and V simultaneously show no highlight.
Command followed by V highlights Command only.
V followed by Command highlights V only.

> If you have another USB keyboard or can borrow one from somewhere, see if
> Windows+V works.

The Apple bluetooth keyboard works fine so it must be hardware, right?

--
mhphillips at gmail dot com

On 21 Jun 2023 at 12:52:38 IST, "nospam" <nospam@nospam.invalid> wrote:

> <div id="editor" contenteditable="false">try it on a friend or relative's mac.
> </div>
> <div class="footer" onclick="setCursorToBottom()"></div>

None with a Mac within striking distance, unfortunately.

--
mhphillips at gmail dot com

On 21 Jun 2023 at 15:07:08 BST, "Michael Phillips"
<me@odtaa.com.invalid> wrote:

> On 21 Jun 2023 at 12:46:08 IST, "Theo"
> <theom+news@chiark.greenend.org.uk> wrote:
>
>> If the key code is showing, it's a software problem. If it's not, it may be
>> a hardware problem.
>>
>> If hardware, I suppose it's possible for the key matrix to go bad in such a
>> way that no contact for Cmd+V to be detected, although that sounds pretty
>> unlikely to me.
>
> In Keyboard Viewer:
>
> Command and V separately highlight as expected.
> Command and V simultaneously show no highlight.
> Command followed by V highlights Command only.
> V followed by Command highlights V only.
>
>> If you have another USB keyboard or can borrow one from somewhere, see if
>> Windows+V works.
>
> The Apple bluetooth keyboard works fine so it must be hardware, right?

Well... you'd think so, but I'm reminded of the time I had to detach the
wired Apple aluminium keyboard and use a generic PC one in order to get
to the (hold opt) boot menu on a Mac Mini, some years ago. Later
confirmed that one of my bluetooth Apple keyboards also worked for it,
while the wired one still didn't.

Pretty sure I've also had copy and paste not working in an early OS
beta, 10.13 or so, and another time when the clipboard daemon had hung -
needed rebooting for that one.

Cheers - Jaimie
--
"People can be educated beyond their intelligence"
-- Marilyn vos Savant

Michael Phillips <me@odtaa.com.invalid> wrote:
> On 21 Jun 2023 at 12:46:08 IST, "Theo"
> <theom+news@chiark.greenend.org.uk> wrote:
>
> > If the key code is showing, it's a software problem. If it's not, it may be
> > a hardware problem.
> >
> > If hardware, I suppose it's possible for the key matrix to go bad in such a
> > way that no contact for Cmd+V to be detected, although that sounds pretty
> > unlikely to me.
>
> In Keyboard Viewer:
>
> Command and V separately highlight as expected.
> Command and V simultaneously show no highlight.
> Command followed by V highlights Command only.
> V followed by Command highlights V only.
>
> > If you have another USB keyboard or can borrow one from somewhere, see if
> > Windows+V works.
>
> The Apple bluetooth keyboard works fine so it must be hardware, right?

I'm not sure that's as watertight as testing another USB keyboard, since
there's a different software pathway for USB and for Bluetooth.

If you try the above with another key such as Cmd+C or Cmd+P, do you get the
same as above?

(C is adjacent to V, P is far away, just in case there's damage in the
vicinity of V that's causing troubles.)

It would help to try one of the apps that displays keycodes, since Cmd is a
modifier key - whether you get the unmodified keycode or not. Keyboard
Viewer is interpreting the keycode, and perhaps showing the full keycode
would give clues as to what's happening.

Theo

On 21 Jun 2023 at 16:57:13 IST, "Theo"
<theom+news@chiark.greenend.org.uk> wrote:

> I'm not sure that's as watertight as testing another USB keyboard, since
> there's a different software pathway for USB and for Bluetooth.

With the bluetooth keyboard connected by USB, Bluetooth off, all keys
are functioning correctly.

> If you try the above with another key such as Cmd+C or Cmd+P, do you get the
> same as above?

No, it's only Cmd+V that is dead.

> It would help to try one of the apps that displays keycodes, since Cmd is a
> modifier key - whether you get the unmodified keycode or not. Keyboard
> Viewer is interpreting the keycode, and perhaps showing the full keycode
> would give clues as to what's happening.

I downloaded Key Codes from the App Store. It shows no input for Cmd+V.

--
mhphillips at gmail dot com

Michael Phillips <me@odtaa.com.invalid> wrote:
> On 21 Jun 2023 at 16:57:13 IST, "Theo"
> <theom+news@chiark.greenend.org.uk> wrote:
>
> > I'm not sure that's as watertight as testing another USB keyboard, since
> > there's a different software pathway for USB and for Bluetooth.
>
> With the bluetooth keyboard connected by USB, Bluetooth off, all keys
> are functioning correctly.
>
> > If you try the above with another key such as Cmd+C or Cmd+P, do you get the
> > same as above?
>
> No, it's only Cmd+V that is dead.
>
> > It would help to try one of the apps that displays keycodes, since Cmd is a
> > modifier key - whether you get the unmodified keycode or not. Keyboard
> > Viewer is interpreting the keycode, and perhaps showing the full keycode
> > would give clues as to what's happening.
>
> I downloaded Key Codes from the App Store. It shows no input for Cmd+V.

That's starting to sound like a hardware problem, eg a PCB fracture in the
Cmd / ZXCV area.

Theo

On 21/06/2023 17:43, Theo wrote:
> Michael Phillips <me@odtaa.com.invalid> wrote:
>> On 21 Jun 2023 at 16:57:13 IST, "Theo"
>> <theom+news@chiark.greenend.org.uk> wrote:
>>
>>> I'm not sure that's as watertight as testing another USB keyboard, since
>>> there's a different software pathway for USB and for Bluetooth.
>>
>> With the bluetooth keyboard connected by USB, Bluetooth off, all keys
>> are functioning correctly.
>>
>>> If you try the above with another key such as Cmd+C or Cmd+P, do you get the
>>> same as above?
>>
>> No, it's only Cmd+V that is dead.
>>
>>> It would help to try one of the apps that displays keycodes, since Cmd is a
>>> modifier key - whether you get the unmodified keycode or not. Keyboard
>>> Viewer is interpreting the keycode, and perhaps showing the full keycode
>>> would give clues as to what's happening.
>>
>> I downloaded Key Codes from the App Store. It shows no input for Cmd+V.
>
> That's starting to sound like a hardware problem, eg a PCB fracture in the
> Cmd / ZXCV area.

But he's already said that CMD works with other keys, and V works on
it's own. So I think it's unlikely to be a hardware fault.

Best I can suggest is that Michael has somehow re-mapped CMD+V to do
something else. I don't know of a way to specify a key combination and
have the Mac say what it is mapped to - he'll need to trawl through both
the keyboard and accessibility settings in System Settings to see.

However since he has also said that logging on as a new user didn't fix
the issue then it would need to be a system-wide configuration change.

A long-shot is to install Karabiner Elements
<https://karabiner-elements.pqrs.org> which is free and might be able to
work out what CMD+V is set to if it's been changed somehow? It also
might be able to override and re-assign CMD+V back to something else.
That would at least rule out a hardware fault.

--
Bruce Horrocks
Surrey, England

On 21 Jun 2023 at 22:52:10 IST, "Bruce Horrocks" <07.013@scorecrow.com>
wrote:

> So I think it's unlikely to be a hardware fault.

I can now happily confirm that it was a hardware fault. After slapping
the keyboard hard on its backside, Cmd+v is now working again!
After slapping the keyboard hard on its backside, Cmd+v is now working
again!
After slapping the keyboard hard on its backside, Cmd+v is now working
again!
After slapping the keyboard hard on its backside, Cmd+v is now working
again!
After slapping the keyboard hard on its backside, Cmd+v is now working
again!
See?

--
mhphillips at gmail dot com

Michael Phillips <me@odtaa.com.invalid> wrote:
> On 21 Jun 2023 at 22:52:10 IST, "Bruce Horrocks" <07.013@scorecrow.com>
> wrote:
>
>> So I think it's unlikely to be a hardware fault.
>
> I can now happily confirm that it was a hardware fault. After slapping
> the keyboard hard on its backside, Cmd+v is now working again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> See?

How cruel ;) I think I’ll report you to the RSPCK! Glad it’s working though
:)

--
Cheers, Alan

On 22/06/2023 09:28, Alan B wrote:
> Michael Phillips <me@odtaa.com.invalid> wrote:
>> On 21 Jun 2023 at 22:52:10 IST, "Bruce Horrocks" <07.013@scorecrow.com>
>> wrote:
>>
>>> So I think it's unlikely to be a hardware fault.
>>
>> I can now happily confirm that it was a hardware fault. After slapping
>> the keyboard hard on its backside, Cmd+v is now working again!
>> After slapping the keyboard hard on its backside, Cmd+v is now working
>> again!
>> After slapping the keyboard hard on its backside, Cmd+v is now working
>> again!
>> After slapping the keyboard hard on its backside, Cmd+v is now working
>> again!
>> After slapping the keyboard hard on its backside, Cmd+v is now working
>> again!
>> See?
>
> How cruel ;) I think I’ll report you to the RSPCK! Glad it’s working though
> :)
>

I'm told some keyboards enjoy it! see alt.spanking.keyboards
--
Graeme Wall
This account not read.

On 22/06/2023 09:24, Michael Phillips wrote:
> On 21 Jun 2023 at 22:52:10 IST, "Bruce Horrocks" <07.013@scorecrow.com>
> wrote:
>
>> So I think it's unlikely to be a hardware fault.
>
> I can now happily confirm that it was a hardware fault. After slapping
> the keyboard hard on its backside, Cmd+v is now working again!

Learn something new every day!

> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!
> After slapping the keyboard hard on its backside, Cmd+v is now working
> again!

Half the other keys have now stopped working though...

--
Bruce Horrocks
Surrey, England