Bring OS X Error Message window to the front
up vote
5
down vote
favorite
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
add a comment |
up vote
5
down vote
favorite
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
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
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
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
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
macos window
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
add a comment |
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
add a comment |
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
.
You should add your discovery to blacktree's Secrets.
– cregox
Apr 1 '11 at 15:16
add a comment |
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:
- Press
Command
+Space
to start Spotlight Search
- Search for
/System/Library/CoreServices/Problem Reporter.app
and wait for the result to show up
(a search for justProblem Reporter.app
will not reveal it!)
- Press
Enter
- Now the "Problem Reporter" windows is in the front and has focus
The Terminal way:
- Open a Terminal window or tab
- Run
open -a /System/Library/CoreServices/Problem Reporter.app
- Now the "Problem Reporter" windows is in the front and has focus
add a comment |
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
.
You should add your discovery to blacktree's Secrets.
– cregox
Apr 1 '11 at 15:16
add a comment |
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
.
You should add your discovery to blacktree's Secrets.
– cregox
Apr 1 '11 at 15:16
add a comment |
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
.
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
.
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
add a comment |
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
add a comment |
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:
- Press
Command
+Space
to start Spotlight Search
- Search for
/System/Library/CoreServices/Problem Reporter.app
and wait for the result to show up
(a search for justProblem Reporter.app
will not reveal it!)
- Press
Enter
- Now the "Problem Reporter" windows is in the front and has focus
The Terminal way:
- Open a Terminal window or tab
- Run
open -a /System/Library/CoreServices/Problem Reporter.app
- Now the "Problem Reporter" windows is in the front and has focus
add a comment |
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:
- Press
Command
+Space
to start Spotlight Search
- Search for
/System/Library/CoreServices/Problem Reporter.app
and wait for the result to show up
(a search for justProblem Reporter.app
will not reveal it!)
- Press
Enter
- Now the "Problem Reporter" windows is in the front and has focus
The Terminal way:
- Open a Terminal window or tab
- Run
open -a /System/Library/CoreServices/Problem Reporter.app
- Now the "Problem Reporter" windows is in the front and has focus
add a comment |
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:
- Press
Command
+Space
to start Spotlight Search
- Search for
/System/Library/CoreServices/Problem Reporter.app
and wait for the result to show up
(a search for justProblem Reporter.app
will not reveal it!)
- Press
Enter
- Now the "Problem Reporter" windows is in the front and has focus
The Terminal way:
- Open a Terminal window or tab
- Run
open -a /System/Library/CoreServices/Problem Reporter.app
- Now the "Problem Reporter" windows is in the front and has focus
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:
- Press
Command
+Space
to start Spotlight Search
- Search for
/System/Library/CoreServices/Problem Reporter.app
and wait for the result to show up
(a search for justProblem Reporter.app
will not reveal it!)
- Press
Enter
- Now the "Problem Reporter" windows is in the front and has focus
The Terminal way:
- Open a Terminal window or tab
- Run
open -a /System/Library/CoreServices/Problem Reporter.app
- Now the "Problem Reporter" windows is in the front and has focus
answered Nov 25 at 11:01
Jeroen Wiert Pluimers
1,51483151
1,51483151
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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