Mixing
Revert killall -KILL Dock
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I'm playing around with Dock and until now I was using killall Dock command to relaunch it.
Now I used killall -KILL Dock and my Dock went down without relaunching itself. I tried restarting my mac but it did not help.
I tried to open also /System/Library/CoreServices/Dock/Contents/MacOS/Dock but all I'm getting is:
2018-08-18 22:05:31.276 Dock[1061:44244] -[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb
2018-08-18 22:05:31.277 Dock[1061:44244] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb'
Is there any way I can get my Dock back :(?
macos finder dock
asked Aug 18 at 20:06
Ancinek
1388
add a comment |Â
up vote
1
down vote
favorite
I'm playing around with Dock and until now I was using killall Dock command to relaunch it.
Now I used killall -KILL Dock and my Dock went down without relaunching itself. I tried restarting my mac but it did not help.
I tried to open also /System/Library/CoreServices/Dock/Contents/MacOS/Dock but all I'm getting is:
2018-08-18 22:05:31.276 Dock[1061:44244] -[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb
2018-08-18 22:05:31.277 Dock[1061:44244] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb'
Is there any way I can get my Dock back :(?
macos finder dock
asked Aug 18 at 20:06
Ancinek
1388
Check to see if the Dock is hiding, press ⌥⌘D (Option-Command-D), Also, in Terminal, runpgrep Dockand if it doesn't return thePID, then runopen -a Dockand let us know what happens.
– user3439894
Aug 18 at 20:21
The shortcut does not work at all.pgrep Dockreturns a PID andopen -a Dockdoes nothing too. Also doingkillall DockreturnsNo matching processes belonging to you were found
– Ancinek
Aug 18 at 20:22
I've just updated my comment above
– Ancinek
Aug 18 at 20:23
Anther update. I didkillall Finderthenopen -a Dockand nowkillall Dockdoes not return anything at all - so it seems that it should be working, but it is not :( And after doing nothing at all in terminal and trying to dokillall Dockagain it returns the error :/
– Ancinek
Aug 18 at 20:27
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm playing around with Dock and until now I was using killall Dock command to relaunch it.
Now I used killall -KILL Dock and my Dock went down without relaunching itself. I tried restarting my mac but it did not help.
I tried to open also /System/Library/CoreServices/Dock/Contents/MacOS/Dock but all I'm getting is:
2018-08-18 22:05:31.276 Dock[1061:44244] -[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb
2018-08-18 22:05:31.277 Dock[1061:44244] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb'
Is there any way I can get my Dock back :(?
macos finder dock
asked Aug 18 at 20:06
Ancinek
1388
I'm playing around with Dock and until now I was using killall Dock command to relaunch it.
Now I used killall -KILL Dock and my Dock went down without relaunching itself. I tried restarting my mac but it did not help.
I tried to open also /System/Library/CoreServices/Dock/Contents/MacOS/Dock but all I'm getting is:
2018-08-18 22:05:31.276 Dock[1061:44244] -[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb
2018-08-18 22:05:31.277 Dock[1061:44244] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber stringByExpandingTildeInPath]: unrecognized selector sent to instance 0xe5cdf6a4f4b8bcfb'
Is there any way I can get my Dock back :(?
macos finder dock
asked Aug 18 at 20:06
Ancinek
1388
asked Aug 18 at 20:06
Ancinek
1388
asked Aug 18 at 20:06
Ancinek
1388
asked Aug 18 at 20:06
Ancinek
1388
1388
Check to see if the Dock is hiding, press ⌥⌘D (Option-Command-D), Also, in Terminal, runpgrep Dockand if it doesn't return thePID, then runopen -a Dockand let us know what happens.
– user3439894
Aug 18 at 20:21
The shortcut does not work at all.pgrep Dockreturns a PID andopen -a Dockdoes nothing too. Also doingkillall DockreturnsNo matching processes belonging to you were found
– Ancinek
Aug 18 at 20:22
I've just updated my comment above
– Ancinek
Aug 18 at 20:23
Anther update. I didkillall Finderthenopen -a Dockand nowkillall Dockdoes not return anything at all - so it seems that it should be working, but it is not :( And after doing nothing at all in terminal and trying to dokillall Dockagain it returns the error :/
– Ancinek
Aug 18 at 20:27
add a comment |Â
Check to see if the Dock is hiding, press ⌥⌘D (Option-Command-D), Also, in Terminal, runpgrep Dockand if it doesn't return thePID, then runopen -a Dockand let us know what happens.
– user3439894
Aug 18 at 20:21
The shortcut does not work at all.pgrep Dockreturns a PID andopen -a Dockdoes nothing too. Also doingkillall DockreturnsNo matching processes belonging to you were found
– Ancinek
Aug 18 at 20:22
I've just updated my comment above
– Ancinek
Aug 18 at 20:23
Anther update. I didkillall Finderthenopen -a Dockand nowkillall Dockdoes not return anything at all - so it seems that it should be working, but it is not :( And after doing nothing at all in terminal and trying to dokillall Dockagain it returns the error :/
– Ancinek
Aug 18 at 20:27
Check to see if the Dock is hiding, press ⌥⌘D (Option-Command-D), Also, in Terminal, run
pgrep Dock and if it doesn't return the PID, then run open -a Dock and let us know what happens.– user3439894
Aug 18 at 20:21
Check to see if the Dock is hiding, press ⌥⌘D (Option-Command-D), Also, in Terminal, run
pgrep Dock and if it doesn't return the PID, then run open -a Dock and let us know what happens.– user3439894
Aug 18 at 20:21
The shortcut does not work at all.
pgrep Dock returns a PID and open -a Dock does nothing too. Also doing killall Dock returns No matching processes belonging to you were found– Ancinek
Aug 18 at 20:22
The shortcut does not work at all.
pgrep Dock returns a PID and open -a Dock does nothing too. Also doing killall Dock returns No matching processes belonging to you were found– Ancinek
Aug 18 at 20:22
I've just updated my comment above
– Ancinek
Aug 18 at 20:23
I've just updated my comment above
– Ancinek
Aug 18 at 20:23
Anther update. I did
killall Finder then open -a Dock and now killall Dock does not return anything at all - so it seems that it should be working, but it is not :( And after doing nothing at all in terminal and trying to do killall Dock again it returns the error :/– Ancinek
Aug 18 at 20:27
Anther update. I did
killall Finder then open -a Dock and now killall Dock does not return anything at all - so it seems that it should be working, but it is not :( And after doing nothing at all in terminal and trying to do killall Dock again it returns the error :/– Ancinek
Aug 18 at 20:27
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
So, fortunately I found where the problem was - it was the desktoppicture.db file. Probably a corrupted one. Removing it made the macOS replaced it automagically with a new one :)
answered Aug 18 at 20:50
Ancinek
1388
1
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
add a comment |Â
up vote
1
down vote
I would try ⌥⌘D first. If that doesn't work go to Apple Support Downloads, then search for, download, and run the combo 10.13.6 update (or the latest combo update available for your system version). That's may be the simplest, fastest way to fix something like this.
answered Aug 18 at 20:27
Trellis
35718
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
accepted
So, fortunately I found where the problem was - it was the desktoppicture.db file. Probably a corrupted one. Removing it made the macOS replaced it automagically with a new one :)
answered Aug 18 at 20:50
Ancinek
1388
1
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
add a comment |Â
up vote
3
down vote
accepted
So, fortunately I found where the problem was - it was the desktoppicture.db file. Probably a corrupted one. Removing it made the macOS replaced it automagically with a new one :)
answered Aug 18 at 20:50
Ancinek
1388
1
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
So, fortunately I found where the problem was - it was the desktoppicture.db file. Probably a corrupted one. Removing it made the macOS replaced it automagically with a new one :)
answered Aug 18 at 20:50
Ancinek
1388
So, fortunately I found where the problem was - it was the desktoppicture.db file. Probably a corrupted one. Removing it made the macOS replaced it automagically with a new one :)
answered Aug 18 at 20:50
Ancinek
1388
edited Aug 18 at 22:17
answered Aug 18 at 20:50
Ancinek
1388
answered Aug 18 at 20:50
Ancinek
1388
answered Aug 18 at 20:50
Ancinek
1388
1388
1
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
add a comment |Â
1
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
1
1
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
Please accept your answer. This will stop it from coming back to the front page every so often in the future.
– Harald Hanche-Olsen
Aug 19 at 6:51
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
@HaraldHanche-Olsen I will do it as soon as I can - still one day before I can accept it :)
– Ancinek
Aug 19 at 9:12
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
Good. I keep forgetting the various time limits around here. 8-)
– Harald Hanche-Olsen
Aug 19 at 9:45
add a comment |Â
up vote
1
down vote
I would try ⌥⌘D first. If that doesn't work go to Apple Support Downloads, then search for, download, and run the combo 10.13.6 update (or the latest combo update available for your system version). That's may be the simplest, fastest way to fix something like this.
answered Aug 18 at 20:27
Trellis
35718
add a comment |Â
up vote
1
down vote
I would try ⌥⌘D first. If that doesn't work go to Apple Support Downloads, then search for, download, and run the combo 10.13.6 update (or the latest combo update available for your system version). That's may be the simplest, fastest way to fix something like this.
answered Aug 18 at 20:27
Trellis
35718
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I would try ⌥⌘D first. If that doesn't work go to Apple Support Downloads, then search for, download, and run the combo 10.13.6 update (or the latest combo update available for your system version). That's may be the simplest, fastest way to fix something like this.
answered Aug 18 at 20:27
Trellis
35718
I would try ⌥⌘D first. If that doesn't work go to Apple Support Downloads, then search for, download, and run the combo 10.13.6 update (or the latest combo update available for your system version). That's may be the simplest, fastest way to fix something like this.
answered Aug 18 at 20:27
Trellis
35718
answered Aug 18 at 20:27
Trellis
35718
answered Aug 18 at 20:27
Trellis
35718
answered Aug 18 at 20:27
Trellis
35718
35718
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f334077%2frevert-killall-kill-dock%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Check to see if the Dock is hiding, press ⌥⌘D (Option-Command-D), Also, in Terminal, run
pgrep Dockand if it doesn't return thePID, then runopen -a Dockand let us know what happens.– user3439894
Aug 18 at 20:21
The shortcut does not work at all.
pgrep Dockreturns a PID andopen -a Dockdoes nothing too. Also doingkillall DockreturnsNo matching processes belonging to you were found– Ancinek
Aug 18 at 20:22
I've just updated my comment above
– Ancinek
Aug 18 at 20:23
Anther update. I did
killall Finderthenopen -a Dockand nowkillall Dockdoes not return anything at all - so it seems that it should be working, but it is not :( And after doing nothing at all in terminal and trying to dokillall Dockagain it returns the error :/– Ancinek
Aug 18 at 20:27