Previous 1 4 5 6 7 8 Next 193 Replies Latest reply: Jan 10, 2016 4:47 PM by donaldfromwaverly Go to original post
  • brilor Level 1 (20 points)

    electrocuter wrote:


    Just adding a "me too" here.

    Thanks electrocuter. Might want to file feedback with Apple too and use my bug reporter # ( 15437435 )

  • iching6 Level 1 (0 points)

    The workaround doesn't solve the problem in my environment.  Just an FYI.

  • zer0ed Level 1 (20 points)

    iching6: Then you are experiencing a different issue other then the one we are stating in this thread! Different also in the fact that none of us experienced this symptom in the 10.8.x release.

  • me-hutch Level 1 (0 points)

    Is it just me, or is anyone else perplexed that Apple hasn't fixed this yet? I've been all over the web and its universal in mavericks, & our IT people have been on the horn to Apple and they plain & simple don't know why this is happening. Very unusual and surprised there isn't more outcry in the IT press and by Mavericks users. OH how I wish I hadn't upgraded to Mavericks. Photoshop CS apps open quicker than I can bring up a file open dialogue. Gads!


    This issue has singlehandedly submarined my effort to get more Mac's into the workplace as NO ONE wants to wait 10-20 seconds for a file dialogue box to open during a busy day of multi-tasking. Kills efficiency & creates a serious multi-tasking hiccup. Our head of IT works for me, but I honestly can't push the MAC issue with this serious bug.



  • zer0ed Level 1 (20 points)

    Honestly, I'm shocked as well that Apple hasn't addressed this critical issue yet! Guess now we know why Mavericks was offered for free!


    Jan 3, 2014 12:09 PM (in response to Eric Hildum)


    Eric Hildum wrote:


    Then please reproduce the problem, collect the sysdiagnostics report, and submit the bug report to Apple


    brilor, has already told Eric he's submitted this info almost 2 months ago, and still no solution or even acknowledgement from Apple of the problem! Others have also submitted reports to Apple! Time to come out of denial Apple, and once and for all fix this issue!

  • Eric Hildum Level 2 (265 points)

    It may be all over the web, but that does not mean a lot of people are experiencing the problem. I have five Mac systems of various vintages, and none show this problem. The issue may be confined to just a single system type, or, more likely, some sort of odd configuration issue (and yes, this could occur on a new install). Further, the number of people complaining in discussions like these dwarfs the number that actually take the time to file a proper bug report with a reasonably complete description of the problem, logs, and diagnostic traces. It would not surprise me if Apple has only one or two reports of the problem in their database.


    The more reports that are submitted, with complete sysdiagnose traces and system configuration reports, the sooner Apple will be able to identify and fix the problem. So if you have the problem, do not post a complaint here about Apple not fixing things until you have taken 30 minutes to file as complete a bug report as you can, then given Apple time to make an update release to fix the issue. In some rare cases, Apple will reach out to issue reporters with additional questions and diagnostic procedures.


    I have filed many bug reports over the years; to date, every major bug I reported has been fixed. I even sometimes see issues reported on the web, reproduce them myself, and submit a bug report since it is clear that many people would rather complain than take the steps to help Apple identify and fix the issue. I would do so for this one, but I do not have this problem.


    By the way, if an issue does not get fixed in the next release, update the bug report with additional diagnostics on the new release - sometimes fixes are only partially successful.

  • superjones Level 1 (0 points)

    Thanks for the good PR effort, Eric. If you have joined this thread only to minimize the effects of what has been reported, I think you can consider your work done.


    If you had bothered to read through this entire thread, you would see that bugs have been reported and updated, feedback has been provided, and Apple Care has been contacted. I am not too sure what more can be done unless, like you, we have a direct line to Apple development and can get all of the "major" bugs we find fixed in the next release like you have been able to do in the past. I do not see what your posts have contributed to the conversation other than telling the rest of us that our issue needs to be reported (it has been - multiple times) and that it does not affect that many users (you are incorrect).

  • zer0ed Level 1 (20 points)

    Well said superjones!

  • me-hutch Level 1 (0 points)

    Yes Eric - thank you for the detailed comments. I'm glad you don't have the issue. I did file a bug report. My frustration is better explained below. In my limited experience the issue is obvious on 5 of 6 machines to which I have been exposed. As long as the true experts are pressing the issue thru the right channels, little more can be done.


    I respect your remarks superjones and your partly right. I did read the entire thread AND several others dating back to the original release of 10.9.1. Couldn't find any Apple acknoledgement of the issue and confirmation its being worked on. I may have missed the Apple feedback you mention. Your correct that all you can ask is confirmation they are working on the obvious problem. I also raised the issue at the genius bar locally and the comment was that they had never heard of the problem. I found that odd, particularly when 3 others at this particualr session chimed in with the same stalling open/save file dialogue box. I also filed a bug report on the issue a few weeks back.


    Apple says they don't monitor the Support Communities and that may be so. I regret if nothing was contributed by my frustrated post. My organization is small (63 employees) Having convinced my partners to simply try out only 3 new iMac's the last quarter of 2013 to blend in with the sea of Windows machines, the issue worked against my efforts. And before you say it, I realize an iMac is not a great biz machine but its baby steps for non power users. I also agreed to let one of my partners replace a Windows laptop with a MacBook Pro. When he asked me if he should upgrade to Mavericks I said "sure". He has the same problem. As does my daughter on her MacBook pro post upgrade.


    I'm glad you don't have the problem superjones. Don't diminish the issue to those that deal with it constantly.


    - hutch

  • zer0ed Level 1 (20 points)


    I don't think you meant to direct your above post at superjones!

  • Eric Hildum Level 2 (265 points)

    In my experience, Apple never acknowledges bugs in forums such as this. Further, it is rare that they make any statement about bug resolution efforts in any forum at all. About the only way I have known when Apple is working on a bug I reported is if a) they contact me asking for more information, or (less reliable) b) I see my report has been closed as a duplicate of some other report. Unfortunately with the design of the bug reporting system, in the latter case I cannot see the original bug report.


    While posting in forums such as this may allow others to make suggestions to help work around issues (as has been the case here), such postings will not help Apple identify or fix bugs.


    By the way, I do think there is a serious problem that needs to be fixed. Clearly, it is one of the hardest type to fix as it is intermittant in appearance, affecting some and not others. This makes clear, detailed reporting by those affected even more important, as they are likely the only source of information for finding and resolving the issue.

  • Eric Hildum Level 2 (265 points)

    superjones - what makes you think I have a direct line to Apple? I use the same bug reporting system as everyone else. I have just been doing it for twenty years, so perhaps have filed and seen resolved a few more bugs than average.


    I suppose could be considered a direct line….

  • zer0ed Level 1 (20 points)

    Eric: Maybe because you came on so authoritative. I myself was under the impression you worked for Apple! However, on closer examination of your responses in this thread I concluded it was more of a bull in a china closet scenario! 

  • iching6 Level 1 (0 points)

    Well said. 


    I had this issue on my iMac Mid 2007, MacBook 2008 and MacBook Pro 2012 Retina.

    This issue actually long existed in Mountain Lion version for me.  I was surprised that it is still not yet fixed in Mavericks.


    Can you try move a file from one directory to another?  Even this operation take more than 10 seconds. Ridiculous.

    I will report to Apple Care this week.  It is a serious bug and can cost Apple billion of dollars!  How can Apple ignore it?

  • verstaerker2 Level 1 (0 points)

    interesting is in my case it got "solved" by creating a new user... when using this new user everything runs fast and smoothly

    but that is no real solution as i don't want to redo all the settings

Previous 1 4 5 6 7 8 Next