Previous 1 7 8 9 10 11 Next 193 Replies Latest reply: Jan 10, 2016 4:47 PM by donaldfromwaverly Go to original post
  • superjones Level 1 (0 points)

    P.S. Bonjour will still display any network drives it finds and can work with. If you updated and saved the correct file and invoked automount as instructed, the workaround is implemented.

  • Kurt Lang Level 8 (36,660 points)

    I'll go ahead and assume you'll be fine with this workaround in place, markmc78.

    We've seen no problems with it here. All Macs running Mavericks with the modified file can still access all networked drives the same as always. The only thing that changes is the annoying delay in every single save or open dialogue box is gone. The delay even affected opening your own local partitions. All fixed now.

  • superjones Level 1 (0 points)

    Yes it certainly did. So many levels of longstanding irritation and annoyance with this one...

  • darwinp5101 Level 1 (5 points)

    In October I was in the states for a week. So I installed a large SSD and mavericks. Thought I'd do it in case there were any issues. Although that breaks the "only one change at a time" rule, I felt that it would be OK. since they were quite disparate items.  oops...


    After that, I found this "hang" on save (and on open from an app). It was killing me. since I made 2 major changes, I suspected that it was the SSD, that was having trouble.


    However, after (just now) finding this thread, I implemented it and Voila! it works!


    So, this is a REALLY??? for Apple OSX designers: At what point did it become ok to go and check drive availability in the entire known universe just to open or save a file, especially when the destination/source of the file is local? And what was it in Mavericks that you changed to make that happen?


    I'm guessing that some genius made the assumption that once you've connected your computer to a network, you would always have that network and those connections available. What part of "laptop" or "portable" don't they get?


    Well, a workaround that deletes some system functionality is really not acceptable from a design perspective. I hope this is on a bug report somewhere...


    But big kudos to the guy who figured this out. you are my hero for the week!

  • superjones Level 1 (0 points)

    Update: Just to share my experience. I reverted the changes made for the workaround, installed 10.9.2, and then went about testing a number of applications' Open/Save/Export dialogs (Firefox, Thunderbird, iTunes, TextEdit, Adobe Bridge CS6, Adobe Photoshop CS6, Adobe Audition CS6, Finder and Preview, among a few others), and I no longer have any spin condition nor must I wait for more than a microsecond for the contents of directories to be displayed regardless of how the contents are displayed.


    So for me, reverting the workaround and updating to OS X 10.9.2 resolved the issue reported for this thread! Hooray! Maybe all of us and others that reported the issue got things done here.


    (Sorry if my cheerfulness clashes with anyone who may still have the problem after applying 10.9.2...)


    Super huge thanks to Snaggletooth_DE for the excellent find and sharing of a great workaround!!!

  • MindFad Level 1 (0 points)

    Hallelujah, 10.9.2 fixes this issue for me.


    I never tried any of the workarounds and have just been tolerating the problem, but it appears to be fixed! Those feedback emails paid off, guys and gals.

  • zer0ed Level 1 (20 points)

    Same procedure here. Undid the Snaggletooth workaround and I'm happy to finally say it looks like 9.2 has finally resolved the issue!

  • AJDesignCo Level 1 (10 points)

    My quick fix (delete the preferences.plist file) worked for me in the short term, but the slow Open dialog issue reappeared every few days. I eventually tired of that drama and braved Snaggletooth_DE's solution. I wasn't familiar with editing files in vi, so it was scary to me :-) The solution, while scary, was effective for me with no side effects.


    I'm happy to report that 10.9.2 also appears to have corrected the problem for me. I reverted Snaggletooth_DE's solution by removing the # symbol.


    Thank you all so much for sharing your experience and expertise!

  • jrome Level 1 (0 points)

    Isn't it a shame that Apple never responded to this. millions of frustrated people wasted a lot of time waiting for file lists to appear, and thousands wasted many hours trying to find the cause. Apple's policy needs to be changed on such matters. If Microsoft did the same thing, everyone would be up in arms about it.

  • thomasfromelkhorn Level 1 (0 points)

    it works! Thank You!

  • d60Dave Level 1 (10 points)

    Hi All,


    Hoping that 10.9.2 is going to fix it, what is the procedure to reverse the Snaggletooth workaround, in particular the terminal commands which is somthing I'm not very familiar with.


    Thanks in advance,



  • Eric Hildum Level 2 (265 points)

    jrome - As is well documented, Apple does not monitor or respond to anything posted here. Instead, Apple clearly states that it monitors bug reports submitted via the bug reports mechanism. In this case, Apple reviewed the bug reports that many submitted and fixed the issue. Seems like Apple is being responsive to me.


    I will add that if you submit a quality bug report that Apple engineers need your assistance with resolving, they will contact you.


    Finally, I will note that I have reported bugs to both Apple and Microsoft. In Apple's case many of the bugs I reported via the bug reporter have been fixed, and Apple staff has contacted on a (very) few occasions to get more information. In Microsoft's case, where my company had a seven figure support contract, the Microsoft staffer assigned to us would not even take the bug report - and this for a bug causing catastrophic data loss in Word documents.

  • jrome Level 1 (0 points)

    Well, I do file bug reports, but many people do not know how to, and do not know something is a bug. And I filed a bug in November that kills my bluetooth periodically, and they have not yet responded to it! Apple needs to be more public about problems that many people encounter so that people do not waste their time. And there is no reason for Apple to NOT monitor these forums. Microsoft monitors their forums, and offers people help.


    I say this is unresponsive.

  • Kurt Lang Level 8 (36,660 points)

    Apple does read these forums, they just don't respond here. Only very occasionally will you see a host post something. And then it's usually related to these forums.


    A few months back, Apple also hired employees to openly post as Apple employees to answer questions (they have a black apple as an avatar). Notice that one of them is in at least one of the topics on this issue. You can bet that person moved the information up the chain.

  • mlp_72 Level 1 (0 points)

    I do not have the problem with dialog boxes, but I do have the problem when opening FCP X 10.1.1. Updated to Mavericks 10.9.2 did not help--- only unplugging the ethernet cable helps.

Previous 1 7 8 9 10 11 Next