View Tweet Yellow river piano concerto, warm green tea, pineapple tarts and snow falling out my back door. Pity these pharma slides!
Subscribe to Twitter
Unhappy Mac Logo

Mac OS X Can’t Copy and Paste, Drag and Drop and Spotlight’s Dead

Posted from Lambeth, England, United Kingdom.

Hi all, just recovered from a brief scare where (somehow) all copy and paste (including cmd-x v and c), and drag and drop functionality ceased to work on my MacBook Pro. Not to mention that Spotlight has decided to excuse itself without official leave.

Apparently this crisis is not OS sub-version centric. From google i’ve learnt it affects various iterations of OS X – thought it was a problem associated with a system update.

It’s rather scary, but don’t worry. There’s absolutely no need to tear your hair out, prep for reinstallation (i was toying with this as i frantically google-surfed), or turn to nukes. Strangely, this issue felt more unexpected than a total system failure or a physical hard disk meltdown.

Here’s a good way to undo your lockup or ****up (sorry, couldn’t help) and restore your mac’s chastity. Spanking is not an alternative in this situation.

SOLUTION

  1. boot up Terminal
  2. sudo mkdir /private/tmp
  3. (key in your password as prompted. don’t worry Terminal virgins, though there are no asterisks or characters, your input has been acknowledged by your errant computer)
  4. sudo chmod 1777 /private/tmp
  5. reboot/log out then in

It should work now.

(there really isn’t any need to kiss my feet)

Unhappy Mac Logo

Tags: , , , ,



  • justin

    hey faii. long time no talk. so they revealed that schumi is stig haha. how are you man?

  • Linda

    HI faii,
    I have exactly the same problem – cannot paste, cannot drag and drop and spotlight not working. Mac OS 10.5.7 installed. But, I tried your trick in the Terminal and it still doesnt work! I tried reparing diskpermissions, verify disk was ok, Tech Tool Deluxe, Apple hardware/software check – no signs of anything wrong. Also used ClamXav to check for viruses.
    Maybe I am not savvy enough to use the Terminal properly, can you give any more tips? How do I know that it actually did the thing you recommend here? I got “file exist” after i entered my password, but after i did the chmod there was no feedback. then i did “exit” and also restarted the computer, but still same problem.

    Thanks,

  • faii

    Hi Linda,

    apologies for the delayed reply. returned from overseas today.

    my guess is that accidentally deleting the file (i was clearing up unwanted files several days back) or having a programme that didn’t behave itself was the reason for the accidental deletion of my temp folder. it is used as a cache by the OS for everything from copying and pasting to the trashcan.

    from what you’ve mentioned i understand you’ve created the temp folder and changed the permissions. did you follow each of the steps and ensured there were wasn’t a typo with the second command? the first time i tried it it did not work because i was fooling around with other solutions involving the terminal.

    how about trying it out after a fresh restart? just launch the terminal after logging in. don’t forget to reboot as well.

    i didn’t receive confirmation on Terminal upon using the ‘sudo chmod 1777 /private/tmp’ command. don’t worry about that.

    basically disk permissions and the hardware/software diagnoses do not work, and it most probably isn’t caused by a virus.

    i hope this works for you! :)

    btw (for other readers),

    The sticky bit 't' means:
    'do not let anyone delete this folder or change it's permissions'">

  • The Naive Kid

    I typed in everything you wrote but nothing. Can you help me with this issue? It’s such a drag since I have to be using FCP to copy paste timecodes. :S

    Thanks in advance.

  • Anon

    If I knew where you were, I really would kiss your feet. You are my saviour!!!

  • Mrbadger42

    You ‘da man! That worked. It pays to pay attention when the OS asks  you for a password when you go to delete something.

blog comments powered by Disqus