or Connect
AppleInsider › Forums › Mobile › iPod + iTunes + AppleTV › Apple fixes hidden '/Users' folder bug introduced in OS X 10.9.3 with iTunes update
New Posts  All Forums:Forum Nav:

Apple fixes hidden '/Users' folder bug introduced in OS X 10.9.3 with iTunes update

post #1 of 30
Thread Starter 
Apple on Friday released a minor version update to its iTunes content management software for Mac, bringing a fix for the recently discovered bug introduced in OS X Mavericks 10.9.3 that inadvertently hides the "/Users" folder.



Apple's iTunes 11.2.1 carries the same release notes as version iTunes 11.2, which was released on Thursday alongside the latest OS X Mavericks 10.9.3 maintenance update.

Not listed among the modifications, version 11.2.1 contains a fix for a bug discovered in the Mac operating system that hides the system's "/Users" folder at the top level of an affected machine's hard drive.

The issue is easily solved with the routine Terminal command sudo chflags nohidden /Users, while a less permanent fix can be had by using the following method:

  • Open a Finder window and select the "Go" menu, then choose "Go to Folder"
  • Once the dialog appears, type "/Users" (without quotes) and click the "Go" button
  • Control-click on the "/Users" folder and select "Make Alias"

In either case, the new iTunes 11.2.1 release appears to patch the bug for users experiencing the issue. The latest iTunes version can be downloaded for free via Software Update. No restart is required for the change to occur, suggesting the update automatically modifies the sudo command.
post #2 of 30

/Users is still hidden after this update on my server. Rebooting afterward had no apparent effect either.

 

So I downloaded the .dmg from Apple and "manually" installed a second time. That fixed it.


Edited by Cpsro - 5/17/14 at 10:06am
post #3 of 30
How absolutely intriguing that Apple could turn around a bug fix within 24 hours of the initial release of iTunes 11.2! This tells me two things. First, the bug was an easy fix. Second, Apple is clearly committed to iTunes and Mac OS X functioning as they should. And while this is gratifying, I must admit my frustration with Apple not fixing bugs like the memory leak in Aperture 3.5.1 that have persisted for months. We're talking about an issue critical to the workflow of many photography professionals. Many have left Aperture because this bug triggers kernel panics and crashes. And we haven't heard a word from Apple, notwithstanding extensive threads in Apple's support forum. I guess it's all a matter of what Apple considers a priority.
post #4 of 30
Quote:
Originally Posted by AppleInsider View Post

The issue is easily solved with the routine Terminal command sudo chflags nohidden /Users, while a less permanent fix can be had by using the following method:
 
  • Open a Finder window and select the "Go" menu, then choose "Go to Folder"
  • Once the dialog appears, type "/Users" (without quotes) and click the "Go" button
  • Control-click on the "/Users" folder and select "Make Alias"

Yet again AI gets this wrong.

 

The chflags workaround is removed at every reboot.

 

The alias/symlink workaround is persistent through reboots.

 

It is best if AI readers do not read this site for technical information, but simply for rumors and gossip.


Edited by mpantone - 5/16/14 at 9:25pm
post #5 of 30

I can confirm that the iTunes 11.2.1 update fixes the /Users and /Users/Shared folders issue. Both are now visible again. 

post #6 of 30
Quote:
Originally Posted by mpantone View Post
 

Yet again AI gets this wrong.

 

The chflags workaround is removed at every reboot.

 

The alias/symlink workaround is persistent through reboots.

 

It is best if AI readers do not read this site for technical information, but simply for rumors and gossip.

 

What’s the point? The just released update to iTunes fixes the issue.

post #7 of 30

Without a doubt, there will be a handful of readers who insist on not installing iTunes 11.2.1.

 

;)

 

In any case, if this update had not been released, AI's advice would still have remained inaccurate.

 

The point is that AI is not a valid source for technical information. It's no longer an issue because Apple fixed it, not because AI was able to identify a workaround.

post #8 of 30
Quote:
Originally Posted by Cpsro View Post

/Users is still hidden after this update on my server.

Do the release notes say this update is for client or server software?

Quote:
Originally Posted by defraserii View Post

How absolutely intriguing that Apple could turn around a bug fix within 24 hours of the initial release of iTunes 11.2! This tells me two things. First, the bug was an easy fix. Second, Apple is clearly committed to iTunes and Mac OS X functioning as they should. And while this is gratifying, I must admit my frustration with Apple not fixing bugs like the memory leak in Aperture 3.5.1 that have persisted for months. We're talking about an issue critical to the workflow of many photography professionals. Many have left Aperture because this bug triggers kernel panics and crashes. And we haven't heard a word from Apple, notwithstanding extensive threads in Apple's support forum. I guess it's all a matter of what Apple considers a priority.

Huh? First you commend Apple on releasing an update to this bug through iTunes but then make remarks on a supposedly memory leak issue in Aperture. While I don't have this issue myself on my Mac I wonder what could be the cause of your hardware/software suffering. Are you using 'stock Apple stuff', ie no 3rd party plugins installed, or 3rd party RAM?
Quote:
Originally Posted by mpantone View Post

It is best if AI readers do not read this site for technical information, but simply for rumors and gossip.

Only a fool would go to a rumour site to get technical info from and apply that to their setup because it was 'stated as fact'. But you're not a fool are you. This site never proclaimed to be a 'valid source for technical information', but you knew this before posting, right?
How to enter the Apple logo  on iOS:
/Settings/Keyboard/Shortcut and paste in  which you copied from an email draft or a note. Screendump
Reply
How to enter the Apple logo  on iOS:
/Settings/Keyboard/Shortcut and paste in  which you copied from an email draft or a note. Screendump
Reply
post #9 of 30

The /Users folder issues are all cleared up on my system after the update!

 

That was a fairly quick fix from Apple.

Disclaimer: The things I say are merely my own personal opinion and may or may not be based on facts. At certain points in any discussion, sarcasm may ensue.
Reply
Disclaimer: The things I say are merely my own personal opinion and may or may not be based on facts. At certain points in any discussion, sarcasm may ensue.
Reply
post #10 of 30

I'm not sure what is so befuddling about what I said. Yes, I commended Apple for responding quickly to the iTunes bug. But I also wished they were equally responsive about a major bug in one of their pro apps that impacts how many of us professional photographers (and long time Aperture users) make our living. As to your "supposed memory leak," it is apparent you're not an Aperture user, of if you are, the environment in which you use it differs from the many photographers who have taken to the Apple Support Forum to ask Apple to fix it. You don't have to shed your skepticism; go look for yourself. 

 

Let's be clear about something. I am not new to Macs, and I am not new to Aperture. I've been using Aperture since version 1, and Macs  since 2002. I have had extensive conversations with Aperture engineers at Apple and have provided them extensive crash logs and system reports. And no, the kernel panics are not caused by third party hardware or software. As incredulous as it may seem, there are bugs that Apple often has to iron out in applications. 

 

iTunes is obviously important to Apple, so they made haste in fixing a bug. I am merely pointing out that those of us who have been waiting for several months for them to fix a bug on an application we bought and depend on professionally, would like Apple to be just as aggressive in fixing that bug. It has been several months. 

post #11 of 30
Quote:
Originally Posted by defraserii View Post

^ post

But is it a bug? These memory leak articles have been here since v3 was release in 2010 (one, two three four). I know people perceive Apple as not giving Aperture 'any love' because they haven't released any updates (which is a different discussion altogether as they have consistently updated the software for free, but no 'v4' version) but I haven't seen any memory leaks at my end.

Sometimes/often this can be the result of 3rd party memory sticks, hence my question on that. I read that plugins can be the cause of this as well.

I'm sorry if I came across as being skeptic, or negative or something, in no way was that my intention. Maybe you would like to add the fix memory leak issue in this 'v4 Wish List' thread I created here:
http://forums.appleinsider.com/t/179038/aperture-wish-list-aperturex-aperture-v4
How to enter the Apple logo  on iOS:
/Settings/Keyboard/Shortcut and paste in  which you copied from an email draft or a note. Screendump
Reply
How to enter the Apple logo  on iOS:
/Settings/Keyboard/Shortcut and paste in  which you copied from an email draft or a note. Screendump
Reply
post #12 of 30
Quote:
Originally Posted by mpantone View Post

Yet again AI gets this wrong.

The chflags workaround is removed at every reboot.

The alias/symlink workaround is persistent through reboots.

It is best if AI readers do not read this site for technical information, but simply for rumors and gossip.
Here's a chflags workaround that persists across reboots. Just copy this into a .plist file and put it in your LaunchDaemons folder (with the correct permissions). This one's to show the ~/Library folder, but you can adapt it to show any folder that Apple decides to hide.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Label</key>
        <string>com.putwhateveryouwanthere.showlibrary</string>
        <key>ProgramArguments</key>
        <array>
                <string>/usr/bin/chflags</string>
                <string>nohidden</string>
                <string>/Users/***put your username here***/Library</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
</dict>
</plist>
post #13 of 30
Less than 24 hours and fixed, yet people still won't just say 'well done' - this is software, there are always going to be bugs. The beta testing is intense, apple are improving the beta testing by further opening the route to becoming a beta tester for more users.

On the aperture issue - On aperture 3.5.1 here - 20 installs of it in the office, across various macs old and new - zero issues - there must be something specific to your machine - conflict somewhere, third party RAM etc. etc. I would very much like to see a new version however.
While I feel your pain, this article is about apple fixing something incredibly quickly, and they should be commended for it.
post #14 of 30
Quote:
Originally Posted by PhilBoogie View Post
 
Only a fool would go to a rumour site to get technical info from and apply that to their setup because it was 'stated as fact'.

 

Well then I'm as foolish as a monkey in a minefield. I thought anyone writing such an article would have taken a moment to verify that what they ⌘+C / ⌘+V would actually work.

 

Journalism according to its traditional definition is truly dead.

Lorin Schultz (formerly V5V)

Audio Engineer

V5V Digital Media, Vancouver, BC Canada

Reply

Lorin Schultz (formerly V5V)

Audio Engineer

V5V Digital Media, Vancouver, BC Canada

Reply
post #15 of 30
QFT. There's indeed too much rehashing what others have already stated on the Internet.

And no, I don't think you're foolish.
How to enter the Apple logo  on iOS:
/Settings/Keyboard/Shortcut and paste in  which you copied from an email draft or a note. Screendump
Reply
How to enter the Apple logo  on iOS:
/Settings/Keyboard/Shortcut and paste in  which you copied from an email draft or a note. Screendump
Reply
post #16 of 30
Quote:
Originally Posted by nkhm View Post

Less than 24 hours and fixed, yet people still won't just say 'well done' - this is software, there are always going to be bugs. The beta testing is intense, apple are improving the beta testing by further opening the route to becoming a beta tester for more users.

On the aperture issue - On aperture 3.5.1 here - 20 installs of it in the office, across various macs old and new - zero issues - there must be something specific to your machine - conflict somewhere, third party RAM etc. etc. I would very much like to see a new version however.
While I feel your pain, this article is about apple fixing something incredibly quickly, and they should be commended for it.

 

This always happens. This totally minor glitch caused a firestorm of people running around with their hair on fire. The so-called power users instantly began issuing terminal commands from on high then arguing as to who’s terminal command is better. In the Apple discussions forums the obligatory “Steve is dead, Apple’s QA has goner down the tubes, this is horrible!” ranting and raving started almost immediately.

 

Then of course we have the ‘adders on’ who are miffed that this issue got fixed but THEIR issue still remains after ‘months.’ The fact that, as you point out, the vast majority of users are not experiencing the issue they obsess over doesn’t persuade them to investigate further or try something else. Nope, they continue to sit on their dead asses waiting for Apple to do something even though nothing needs to be done.

 

I’m also wondering what’s happening to those users who applied all those terminal commands, automator scripts, voodoo incantations to ‘fix’ this piddly bug? Is the iTuners update going to choke on their modifications? Will they scream bloody murder at Apple if it does?

post #17 of 30
What would be more interesting would be to know why the /Users bug affected some people and not others (and perhaps why iTunes would ever set a not visible flag for that folder).

FWIW my Mac was not affected by the bug, but I'm not sure I would have noticed if it had been. Unless one uses the Shared folder I can't think of a reason to access the /Users folder.
post #18 of 30

The fix works as advertised. Thank you, appleinsider.  BTW, if the fix hasn't worked for you, be certain to restart your machine or kill the Finder process for the fix to kick in.

post #19 of 30
Quote:
Originally Posted by NeilM View Post

What would be more interesting would be to know why the /Users bug affected some people and not others (and perhaps why iTunes would ever set a not visible flag for that folder).

FWIW my Mac was not affected by the bug, but I'm not sure I would have noticed if it had been. Unless one uses the Shared folder I can't think of a reason to access the /Users folder.

I haven't seen anyone reporting exactly how iTunes 11.2 caused this, but the reason for why it only affected some people is known.

 

The bug only affects Macs which have iTunes 11.2 installed, and which have the "Find my Mac" feature of iCloud enabled. With this combination, each time you restart the computer, something causes the hidden flag to be set for /Users and /Users/Shared, and also messes up the permissions on those folders. It has been observed to occur on OS X 10.9.2 and 10.9.3, but I wasn't able to repeat it on OS X 10.8.5, which suggests it only happens if the Mac is running Mavericks.

 

Prior to Apple fixing the bug in iTunes 11.2.1, the workaround was to disable Find my Mac and manually fix the hidden flag and permissions of those folders (or used Repair Disk Permissions in Disk Utility).

 

The symptoms suggest that one of the system-level components installed by iTunes (which was running on each startup or login) was manipulating visibility and/or permissions for some files inside /Users/Shared, and due to a bug it accidentally modified the hidden flag and permissions of the parent folders as well.

 

I had a look inside the iTunes installer using Pacifist and noticed that it included a script which was manipulating permissions and hiding "/Users/Shared/SC Info" and "/Users/Shared/adi". That particular script would have only run at the point iTunes was installed, so doesn't explain the recurring problem. Best clue I've found: the "/Users/Shared/adi" folder is probably related to "/System/Library/PrivateFrameworks/CoreADI.framework", and that framework was the only component I could find which had a different size between the iTunes 11.2 and 11.2.1 installers, making it the most likely suspect for the bug. I have no idea what this framework does as it isn't documented, but it appears to be related to the iTunes Store, App Store and/or iBookStore.

 

The dependency on Find my Mac to trigger the bug is still a mystery.

post #20 of 30

I never test beta software but this bug probably indicates that either the beta OS X did not contain the beta iTunes or else there are not enough people doing beta testing either in the community or at Apple. A hidden /Users folder should be pretty obvious. It sure got noticed quickly after the general release.

Life is too short to drink bad coffee.

Reply

Life is too short to drink bad coffee.

Reply
post #21 of 30

The Mac App Store asks me to close Xcode before it installs the iTunes 11.2.1 update. Anyone have the faintest idea why?

post #22 of 30
Quote:
Originally Posted by Durandal1707 View Post


Here's a chflags workaround that persists across reboots. Just copy this into a .plist file and put it in your LaunchDaemons folder (with the correct permissions). This one's to show the ~/Library folder, but you can adapt it to show any folder that Apple decides to hide.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Label</key>
        <string>com.putwhateveryouwanthere.showlibrary</string>
        <key>ProgramArguments</key>
        <array>
                <string>/usr/bin/chflags</string>
                <string>nohidden</string>
                <string>/Users/***put your username here***/Library</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
</dict>
</plist>

 

Just an FYI, there's a checkbox in your Home Folder's "View Options" that will tell the Finder to "Show Library Folder".

 

Also, when changed this can be used to unhide the /Users and /Users/Shared folder, the permissions of those folders are still wrong. :(

Disclaimer: The things I say are merely my own personal opinion and may or may not be based on facts. At certain points in any discussion, sarcasm may ensue.
Reply
Disclaimer: The things I say are merely my own personal opinion and may or may not be based on facts. At certain points in any discussion, sarcasm may ensue.
Reply
post #23 of 30
Quote:
Originally Posted by mstone View Post
 

I never test beta software but this bug probably indicates that either the beta OS X did not contain the beta iTunes or else there are not enough people doing beta testing either in the community or at Apple. A hidden /Users folder should be pretty obvious. It sure got noticed quickly after the general release.

OS X updates don't include iTunes (easily confirmed by looking into the 10.9.3 combo update with Pacifist), so this was a case of iTunes beta testing not catching the bug. It might have been a new bug introduced after the last build made available to developers and/or other beta testers.

 

Perhaps nobody noticed because the testers didn't have Find my Mac enabled, or they had tweaked Finder to always show invisible files, or they never happened to look at / or /Users in Finder. Another possibility is that the problem had been noticed but the cause wasn't isolated until someone did the necessary detective work after the problem got widespread attention.

Quote:
Originally Posted by DarkLite View Post
 

The Mac App Store asks me to close Xcode before it installs the iTunes 11.2.1 update. Anyone have the faintest idea why?

Xcode and iTunes share some system-level components relating to managing iOS devices. I expect Xcode has them open and they need to be closed before the iTunes installer can update them.

post #24 of 30
Quote:
Originally Posted by Durandal1707 View Post

Here's a chflags workaround that persists across reboots. Just copy this into a .plist file and put it in your LaunchDaemons folder (with the correct permissions). This one's to show the ~/Library folder, but you can adapt it to show any folder that Apple decides to hide.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Label</key>
        <string>com.putwhateveryouwanthere.showlibrary</string>
        <key>ProgramArguments</key>
        <array>
                <string>/usr/bin/chflags</string>
                <string>nohidden</string>
                <string>/Users/***put your username here***/Library</string>
        </array>
        <key>RunAtLoad</key>
        <true/>
</dict>
</plist>

Good info for but since a correctly working system allows these changes to persist after an update I have used Terminal for this.
Code:
chflags nohidden ~/Library/

Quote:
Originally Posted by mjtomlin View Post

Just an FYI, there's a checkbox in your Home Folder's "View Options" that will tell the Finder to "Show Library Folder".

Also, when changed this can be used to unhide the /Users and /Users/Shared folder, the permissions of those folders are still wrong. 1frown.gif

Excellent find. When did you first discover/hear about this?



Quote:
Originally Posted by dempson View Post

OS X updates don't include iTunes (easily confirmed by looking into the 10.9.3 combo update with Pacifist), so this was a case of iTunes beta testing not catching the bug. It might have been a new bug introduced after the last build made available to developers and/or other beta testers.

Perhaps nobody noticed because the testers didn't have Find my Mac enabled, or they had tweaked Finder to always show invisible files, or they never happened to look at / or /Users in Finder. Another possibility is that the problem had been noticed but the cause wasn't isolated until someone did the necessary detective work after the problem got widespread attention.

1) A wonderfully thought out comment from the developer's PoV.

2) Perhaps they need to go back to offering iTunes betas to developers or even a non-dev seed program so these issues aren't as likely to go unnoticed by having normal users in the mix.
Edited by SolipsismX - 5/17/14 at 10:09am

"The real haunted empire?  It's the New York Times." ~SockRolid

"There is no rule that says the best phones must have the largest screen." ~RoundaboutNow

Reply

"The real haunted empire?  It's the New York Times." ~SockRolid

"There is no rule that says the best phones must have the largest screen." ~RoundaboutNow

Reply
post #25 of 30
Quote:
Originally Posted by PhilBoogie View Post

Do the release notes say this update is for client or server software?

Too funny!

post #26 of 30
Quote:
Originally Posted by defraserii View Post

I must admit my frustration with Apple not fixing bugs like the memory leak in Aperture 3.5.1 that have persisted for months. We're talking about an issue critical to the workflow of many photography professionals. Many have left Aperture because this bug triggers kernel panics and crashes. And we haven't heard a word from Apple, notwithstanding extensive threads in Apple's support forum. I guess it's all a matter of what Apple considers a priority.

It's perhaps easier and cheaper for Apple to develop Aperture X than to fix Aperture. Or perhaps Aperture is dead.

post #27 of 30

I didn’t get that /Users problem.

 

What I noticed is that iTunes plays DTS and DTS-HD MA audio!


Edited by einsteinbqat - 5/17/14 at 3:30pm

iMac mid 2011 • 27 in • 3,4 GHz Core i7 • 32 GB RAM • AMD Radeon HD 6970M 2GB VRAM

Reply

iMac mid 2011 • 27 in • 3,4 GHz Core i7 • 32 GB RAM • AMD Radeon HD 6970M 2GB VRAM

Reply
post #28 of 30

I just want to say that this is a case of the internet and user forums doing the work and getting things right. Many people here identified the problem, saw that the workarounds would not work and Apple made the necessary correction pretty quickly. All good.

AppleInsider = Apple-in-cider. It's a joke!

I've used macs since 1985 when I typed up my first research paper. Never used anything else never wanted to.
Reply
AppleInsider = Apple-in-cider. It's a joke!

I've used macs since 1985 when I typed up my first research paper. Never used anything else never wanted to.
Reply
post #29 of 30
Quote:
Originally Posted by Eluard View Post
 

I just want to say that this is a case of the internet and user forums doing the work and getting things right. Many people here identified the problem, saw that the workarounds would not work and Apple made the necessary correction pretty quickly. All good.

 

There were actually a couple of workarounds... even a permanent fix, but you had to have some experience with a command line.

Disclaimer: The things I say are merely my own personal opinion and may or may not be based on facts. At certain points in any discussion, sarcasm may ensue.
Reply
Disclaimer: The things I say are merely my own personal opinion and may or may not be based on facts. At certain points in any discussion, sarcasm may ensue.
Reply
post #30 of 30
Quote:
Originally Posted by DarkLite View Post
 

The Mac App Store asks me to close Xcode before it installs the iTunes 11.2.1 update. Anyone have the faintest idea why?

 

Probably because somewhere they share a common library and that library is going to get updated.  The file needs to be closed for that to happen.

Just say no to MacMall.  They don't honor their promotions and won't respond to customer inquiries.  There are better retailers out there.
Reply
Just say no to MacMall.  They don't honor their promotions and won't respond to customer inquiries.  There are better retailers out there.
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: iPod + iTunes + AppleTV
AppleInsider › Forums › Mobile › iPod + iTunes + AppleTV › Apple fixes hidden '/Users' folder bug introduced in OS X 10.9.3 with iTunes update