Bring OS X Error Message window to the front











up vote
5
down vote

favorite
4












In OS X, when an application crashes, a window with an error report will appear. That window is by default unreachable by Command+Tab nor does it appear in the Dock. Of course, if by error or on purpose one clicks another window, the error report will go to the background and hide behind the other windows.



This is really annoying, because in order to see it, I will have to use Exposé and scan through 20+ Windows in order to find it. (Not to say, that I don’t like Exposé anymore since Snow Leopard made the window sizes all confusingly equal.)



Any ideas on how to make the error reports Command+Tabbable?










share|improve this question
























  • I assume you mean Command-Tab, rather than Option-Tab.
    – Lawrence Velázquez
    Dec 6 '09 at 15:52






  • 1




    Related question with some possible answers: superuser.com/questions/45649/dismiss-ical-alarm-without-mouse
    – Doug Harris
    May 7 '10 at 19:06















up vote
5
down vote

favorite
4












In OS X, when an application crashes, a window with an error report will appear. That window is by default unreachable by Command+Tab nor does it appear in the Dock. Of course, if by error or on purpose one clicks another window, the error report will go to the background and hide behind the other windows.



This is really annoying, because in order to see it, I will have to use Exposé and scan through 20+ Windows in order to find it. (Not to say, that I don’t like Exposé anymore since Snow Leopard made the window sizes all confusingly equal.)



Any ideas on how to make the error reports Command+Tabbable?










share|improve this question
























  • I assume you mean Command-Tab, rather than Option-Tab.
    – Lawrence Velázquez
    Dec 6 '09 at 15:52






  • 1




    Related question with some possible answers: superuser.com/questions/45649/dismiss-ical-alarm-without-mouse
    – Doug Harris
    May 7 '10 at 19:06













up vote
5
down vote

favorite
4









up vote
5
down vote

favorite
4






4





In OS X, when an application crashes, a window with an error report will appear. That window is by default unreachable by Command+Tab nor does it appear in the Dock. Of course, if by error or on purpose one clicks another window, the error report will go to the background and hide behind the other windows.



This is really annoying, because in order to see it, I will have to use Exposé and scan through 20+ Windows in order to find it. (Not to say, that I don’t like Exposé anymore since Snow Leopard made the window sizes all confusingly equal.)



Any ideas on how to make the error reports Command+Tabbable?










share|improve this question















In OS X, when an application crashes, a window with an error report will appear. That window is by default unreachable by Command+Tab nor does it appear in the Dock. Of course, if by error or on purpose one clicks another window, the error report will go to the background and hide behind the other windows.



This is really annoying, because in order to see it, I will have to use Exposé and scan through 20+ Windows in order to find it. (Not to say, that I don’t like Exposé anymore since Snow Leopard made the window sizes all confusingly equal.)



Any ideas on how to make the error reports Command+Tabbable?







macos window






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 6 '09 at 22:24

























asked Dec 6 '09 at 15:22









Debilski

1,2381013




1,2381013












  • I assume you mean Command-Tab, rather than Option-Tab.
    – Lawrence Velázquez
    Dec 6 '09 at 15:52






  • 1




    Related question with some possible answers: superuser.com/questions/45649/dismiss-ical-alarm-without-mouse
    – Doug Harris
    May 7 '10 at 19:06


















  • I assume you mean Command-Tab, rather than Option-Tab.
    – Lawrence Velázquez
    Dec 6 '09 at 15:52






  • 1




    Related question with some possible answers: superuser.com/questions/45649/dismiss-ical-alarm-without-mouse
    – Doug Harris
    May 7 '10 at 19:06
















I assume you mean Command-Tab, rather than Option-Tab.
– Lawrence Velázquez
Dec 6 '09 at 15:52




I assume you mean Command-Tab, rather than Option-Tab.
– Lawrence Velázquez
Dec 6 '09 at 15:52




1




1




Related question with some possible answers: superuser.com/questions/45649/dismiss-ical-alarm-without-mouse
– Doug Harris
May 7 '10 at 19:06




Related question with some possible answers: superuser.com/questions/45649/dismiss-ical-alarm-without-mouse
– Doug Harris
May 7 '10 at 19:06










2 Answers
2






active

oldest

votes

















up vote
3
down vote













Fun question. Short answer:




sudo defaults write "/System/Library/CoreServices/Problem Reporter.app/Contents/Info" LSUIElement -bool false




That should cause Problem Reporter to show up in the Dock the next time it is run.



How I arrived at the answer: When a crash occurs, /System/Library/CoreServices/ReportCrash is run by launchd according to one of the com.apple.ReportCrash*.plist files in /System/Library/Launch{Daemons,Agents}/. This is responsible for generating the crash report you'll find in [~]/Library/Logs/CrashReporter/ or [~]/Library/Logs/DiagnosticReports.



It looks like ReportCrash might be able to initiate display of a dialog similar the "Problem Report for APP" dialog – it contains the string "/System/Library/PrivateFrameworks/CrashReporterSupport.framework", which is what contains the resources used to localize the text displayed in the dialog window. It also contains calls to the CFUserNotification API. But the ReportCrash process exits after a while, while the dialog continues to display. (The CFUserNotification approach is most likely a fallback in case _CROpenProblemReport, which has the CrashReporterSupport private framework open the application you're seeing, fails.)



Guess what keeps running? /System/Library/CoreServices/Problem Reporter.app. If you open this file, the problem report dialog comes to the fore. The reason you can't see this in the Dock or the Cmd-Tab list is because its Info.plist file contains the entry LSUIElement = 1.



I bet you can make it so you can see it in the Dock and Cmd-Tab to it by changing the value of the LSUIElement to <false/> in /System/Library/CoreServices/Problem Reporter.app/Contents/Info.plist.






share|improve this answer























  • You should add your discovery to blacktree's Secrets.
    – cregox
    Apr 1 '11 at 15:16


















up vote
0
down vote













Based on the first answer, I found out that these sets of steps on High Sierra bring an existing Problem Reporter to the front.



The GUI way:




  1. Press Command+Space to start Spotlight Search

  2. Search for /System/Library/CoreServices/Problem Reporter.app and wait for the result to show up

    (a search for just Problem Reporter.app will not reveal it!)
    enter image description here

  3. Press Enter

  4. Now the "Problem Reporter" windows is in the front and has focus


The Terminal way:




  1. Open a Terminal window or tab

  2. Run open -a /System/Library/CoreServices/Problem Reporter.app

  3. Now the "Problem Reporter" windows is in the front and has focus






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f79516%2fbring-os-x-error-message-window-to-the-front%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    3
    down vote













    Fun question. Short answer:




    sudo defaults write "/System/Library/CoreServices/Problem Reporter.app/Contents/Info" LSUIElement -bool false




    That should cause Problem Reporter to show up in the Dock the next time it is run.



    How I arrived at the answer: When a crash occurs, /System/Library/CoreServices/ReportCrash is run by launchd according to one of the com.apple.ReportCrash*.plist files in /System/Library/Launch{Daemons,Agents}/. This is responsible for generating the crash report you'll find in [~]/Library/Logs/CrashReporter/ or [~]/Library/Logs/DiagnosticReports.



    It looks like ReportCrash might be able to initiate display of a dialog similar the "Problem Report for APP" dialog – it contains the string "/System/Library/PrivateFrameworks/CrashReporterSupport.framework", which is what contains the resources used to localize the text displayed in the dialog window. It also contains calls to the CFUserNotification API. But the ReportCrash process exits after a while, while the dialog continues to display. (The CFUserNotification approach is most likely a fallback in case _CROpenProblemReport, which has the CrashReporterSupport private framework open the application you're seeing, fails.)



    Guess what keeps running? /System/Library/CoreServices/Problem Reporter.app. If you open this file, the problem report dialog comes to the fore. The reason you can't see this in the Dock or the Cmd-Tab list is because its Info.plist file contains the entry LSUIElement = 1.



    I bet you can make it so you can see it in the Dock and Cmd-Tab to it by changing the value of the LSUIElement to <false/> in /System/Library/CoreServices/Problem Reporter.app/Contents/Info.plist.






    share|improve this answer























    • You should add your discovery to blacktree's Secrets.
      – cregox
      Apr 1 '11 at 15:16















    up vote
    3
    down vote













    Fun question. Short answer:




    sudo defaults write "/System/Library/CoreServices/Problem Reporter.app/Contents/Info" LSUIElement -bool false




    That should cause Problem Reporter to show up in the Dock the next time it is run.



    How I arrived at the answer: When a crash occurs, /System/Library/CoreServices/ReportCrash is run by launchd according to one of the com.apple.ReportCrash*.plist files in /System/Library/Launch{Daemons,Agents}/. This is responsible for generating the crash report you'll find in [~]/Library/Logs/CrashReporter/ or [~]/Library/Logs/DiagnosticReports.



    It looks like ReportCrash might be able to initiate display of a dialog similar the "Problem Report for APP" dialog – it contains the string "/System/Library/PrivateFrameworks/CrashReporterSupport.framework", which is what contains the resources used to localize the text displayed in the dialog window. It also contains calls to the CFUserNotification API. But the ReportCrash process exits after a while, while the dialog continues to display. (The CFUserNotification approach is most likely a fallback in case _CROpenProblemReport, which has the CrashReporterSupport private framework open the application you're seeing, fails.)



    Guess what keeps running? /System/Library/CoreServices/Problem Reporter.app. If you open this file, the problem report dialog comes to the fore. The reason you can't see this in the Dock or the Cmd-Tab list is because its Info.plist file contains the entry LSUIElement = 1.



    I bet you can make it so you can see it in the Dock and Cmd-Tab to it by changing the value of the LSUIElement to <false/> in /System/Library/CoreServices/Problem Reporter.app/Contents/Info.plist.






    share|improve this answer























    • You should add your discovery to blacktree's Secrets.
      – cregox
      Apr 1 '11 at 15:16













    up vote
    3
    down vote










    up vote
    3
    down vote









    Fun question. Short answer:




    sudo defaults write "/System/Library/CoreServices/Problem Reporter.app/Contents/Info" LSUIElement -bool false




    That should cause Problem Reporter to show up in the Dock the next time it is run.



    How I arrived at the answer: When a crash occurs, /System/Library/CoreServices/ReportCrash is run by launchd according to one of the com.apple.ReportCrash*.plist files in /System/Library/Launch{Daemons,Agents}/. This is responsible for generating the crash report you'll find in [~]/Library/Logs/CrashReporter/ or [~]/Library/Logs/DiagnosticReports.



    It looks like ReportCrash might be able to initiate display of a dialog similar the "Problem Report for APP" dialog – it contains the string "/System/Library/PrivateFrameworks/CrashReporterSupport.framework", which is what contains the resources used to localize the text displayed in the dialog window. It also contains calls to the CFUserNotification API. But the ReportCrash process exits after a while, while the dialog continues to display. (The CFUserNotification approach is most likely a fallback in case _CROpenProblemReport, which has the CrashReporterSupport private framework open the application you're seeing, fails.)



    Guess what keeps running? /System/Library/CoreServices/Problem Reporter.app. If you open this file, the problem report dialog comes to the fore. The reason you can't see this in the Dock or the Cmd-Tab list is because its Info.plist file contains the entry LSUIElement = 1.



    I bet you can make it so you can see it in the Dock and Cmd-Tab to it by changing the value of the LSUIElement to <false/> in /System/Library/CoreServices/Problem Reporter.app/Contents/Info.plist.






    share|improve this answer














    Fun question. Short answer:




    sudo defaults write "/System/Library/CoreServices/Problem Reporter.app/Contents/Info" LSUIElement -bool false




    That should cause Problem Reporter to show up in the Dock the next time it is run.



    How I arrived at the answer: When a crash occurs, /System/Library/CoreServices/ReportCrash is run by launchd according to one of the com.apple.ReportCrash*.plist files in /System/Library/Launch{Daemons,Agents}/. This is responsible for generating the crash report you'll find in [~]/Library/Logs/CrashReporter/ or [~]/Library/Logs/DiagnosticReports.



    It looks like ReportCrash might be able to initiate display of a dialog similar the "Problem Report for APP" dialog – it contains the string "/System/Library/PrivateFrameworks/CrashReporterSupport.framework", which is what contains the resources used to localize the text displayed in the dialog window. It also contains calls to the CFUserNotification API. But the ReportCrash process exits after a while, while the dialog continues to display. (The CFUserNotification approach is most likely a fallback in case _CROpenProblemReport, which has the CrashReporterSupport private framework open the application you're seeing, fails.)



    Guess what keeps running? /System/Library/CoreServices/Problem Reporter.app. If you open this file, the problem report dialog comes to the fore. The reason you can't see this in the Dock or the Cmd-Tab list is because its Info.plist file contains the entry LSUIElement = 1.



    I bet you can make it so you can see it in the Dock and Cmd-Tab to it by changing the value of the LSUIElement to <false/> in /System/Library/CoreServices/Problem Reporter.app/Contents/Info.plist.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 1 '11 at 15:41









    cregox

    3,72454160




    3,72454160










    answered Dec 2 '10 at 15:28









    Jeremy W. Sherman

    58829




    58829












    • You should add your discovery to blacktree's Secrets.
      – cregox
      Apr 1 '11 at 15:16


















    • You should add your discovery to blacktree's Secrets.
      – cregox
      Apr 1 '11 at 15:16
















    You should add your discovery to blacktree's Secrets.
    – cregox
    Apr 1 '11 at 15:16




    You should add your discovery to blacktree's Secrets.
    – cregox
    Apr 1 '11 at 15:16












    up vote
    0
    down vote













    Based on the first answer, I found out that these sets of steps on High Sierra bring an existing Problem Reporter to the front.



    The GUI way:




    1. Press Command+Space to start Spotlight Search

    2. Search for /System/Library/CoreServices/Problem Reporter.app and wait for the result to show up

      (a search for just Problem Reporter.app will not reveal it!)
      enter image description here

    3. Press Enter

    4. Now the "Problem Reporter" windows is in the front and has focus


    The Terminal way:




    1. Open a Terminal window or tab

    2. Run open -a /System/Library/CoreServices/Problem Reporter.app

    3. Now the "Problem Reporter" windows is in the front and has focus






    share|improve this answer

























      up vote
      0
      down vote













      Based on the first answer, I found out that these sets of steps on High Sierra bring an existing Problem Reporter to the front.



      The GUI way:




      1. Press Command+Space to start Spotlight Search

      2. Search for /System/Library/CoreServices/Problem Reporter.app and wait for the result to show up

        (a search for just Problem Reporter.app will not reveal it!)
        enter image description here

      3. Press Enter

      4. Now the "Problem Reporter" windows is in the front and has focus


      The Terminal way:




      1. Open a Terminal window or tab

      2. Run open -a /System/Library/CoreServices/Problem Reporter.app

      3. Now the "Problem Reporter" windows is in the front and has focus






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        Based on the first answer, I found out that these sets of steps on High Sierra bring an existing Problem Reporter to the front.



        The GUI way:




        1. Press Command+Space to start Spotlight Search

        2. Search for /System/Library/CoreServices/Problem Reporter.app and wait for the result to show up

          (a search for just Problem Reporter.app will not reveal it!)
          enter image description here

        3. Press Enter

        4. Now the "Problem Reporter" windows is in the front and has focus


        The Terminal way:




        1. Open a Terminal window or tab

        2. Run open -a /System/Library/CoreServices/Problem Reporter.app

        3. Now the "Problem Reporter" windows is in the front and has focus






        share|improve this answer












        Based on the first answer, I found out that these sets of steps on High Sierra bring an existing Problem Reporter to the front.



        The GUI way:




        1. Press Command+Space to start Spotlight Search

        2. Search for /System/Library/CoreServices/Problem Reporter.app and wait for the result to show up

          (a search for just Problem Reporter.app will not reveal it!)
          enter image description here

        3. Press Enter

        4. Now the "Problem Reporter" windows is in the front and has focus


        The Terminal way:




        1. Open a Terminal window or tab

        2. Run open -a /System/Library/CoreServices/Problem Reporter.app

        3. Now the "Problem Reporter" windows is in the front and has focus







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 25 at 11:01









        Jeroen Wiert Pluimers

        1,51483151




        1,51483151






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f79516%2fbring-os-x-error-message-window-to-the-front%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Сан-Квентин

            Алькесар

            Josef Freinademetz