Need to Relaunch Finder (Spinning Wheel) Every Few Clicks (MacOS Sierra)

[trevor25220]

 

[Slydude]

Is this (first screenshot) how Activity Monitor looks when everything is going well or when the computer is "acting up"? If this is when things are normal we need to see what it looks like when things aren't normal.

 

[pm-r]

Hmmm…??? That DesktopServicesHelper process sure seems to be overly active whatever it does.

And are you using OSXFuse or FUSE for macOS by chance?





- Patrick
======

 

[trevor25220]

Don't have FUSE. Bit it does seem to be linked to Desktopserviceshelper ...

Others have asked about DSH but nobody answers.

https://osxfuse.github.io/2015/09/25/OSXFUSE-2.8.1.html

 

[harryb2448]

Download the OS X.6.8 Combo Updater and run it Trevor and see if that helps. If no joy maybe a boot from your SL DVD and do a format and clean install, after backing up of course. Suggest not doing a migration until ascertaining if the new install works well.

Also see if this from Apple Discussions is any help regarding quitting a program such as Audio that seems to cause this problem:-


https://discussions.apple.com/thread/6668392?start=0&tstart=0

 

[trevor25220]

https://discussions.apple.com/thread/7703294?start=0&tstart=0

1. Close Finder if it's open.

2. Open an Applications > Utilities > Terminal window and paste the following commands:

rm ~/Library/Preferences/com.apple.finder.plist
rm ~/Library/Preferences/com.apple.preferences.extensions.FinderSync.plist

3. Then reboot.

This thread gives 2 lines of Terminal code. Enter one by one and reboot. Seems to have stabilised the Finder constantly crashing! Advisor stated:

"The problem was corrupt preference files and those commands removed them. Finder then created new ones, so you may have to customise your preferences for Finder again."

This is a novel solution which I shall certainly keep to hand in case of any repeat.

 

[Slydude]

I'm going to go put on my dunce cap now and sit in the corner. I should have mentioned that. For the benefit of others reading the thread I should mention that this can be done without resorting to Terminal commands if you have a bootable clone of your system. Boot from the clone then go to your internal drive, find those preference files and delete them, then reboot the mac from your internal drive.

The Finder, which I am not using, apparently crashes every few random mouse clicks

I should have mentioned this earlier simply as a correction: If your Mac is running you are using the Finder. Most, and perhaps all, of the file operations (copying, moving deleting, etc) run through the Finder at some point. Unless of course they are being completed through the Terminal.

Edit: This includes tasks which the user did not specifically initiate that run in the background such as checking to see what peripherals (hard drives etc( are still attached to the Mac.

 

[pm-r]

I'm going to go put on my dunce cap now and sit in the corner.

I think I better join you Slydude as I overlooked the old tried and true System fix as well.

It used to be a pretty standard fix for all kinds of maladies some years and Mac Systems ago.





- Patrick
======

 

[trevor25220]

System remains stable. The Terminal commands sound less scary than performing a clone boot and searching for those files.

 

[Slydude]

System remains stable. The Terminal commands sound less scary than performing a clone boot and searching for those files.

The boot from another drive is accomplished rather simply by holding down the Option key during bootup. Assuming one has a bootable device/copy which I think everyone should have just for emergencies.

As far as finding the files goes they are in the path given by the Terminal commands. Doing something via Terminal is sometimes necessary but it has tremendous potential for errors that can cause havoc on the system. I have no problem with someone using Terminal if:

1. There is no other means of accomplishing what needs to be done.
2. The user understands Terminal commands enough to use them properly and know what is supposed to happen.

I think issue number one is particularly important. If I'm not mistaken there have been instances of people posting potentially damaging Terminal commands on the net just to see how many people would use them without understanding what the commands do.

 

[MacInWin]

The Terminal commands sound less scary than performing a clone boot and searching for those files.

They may seem less scary because you don't fully understand how badly you can muck up the system with the rm command.

 

[trevor25220]

Associated Printer Crash, Necessitating Resetting of Printer System (via Preferences) Every Day

Rather than start a fresh thread, I would like to ask about another niggling fault, possibly linked to my MacOS Sierra upgrade from Mavericks (originally Snow Leopard). I run a Canon Pixma MG7751 Multifunction Printer (2016) which is a fantastic little machine for the price but my MacBook Pro 13" (2011) is forever 'Searching for printer' when I start work each day, even though it had only had the lid closed overnight and the power switched off (sometimes it shuts down by itself if battery low).

Can never get the print queue to resume without a full reset and install in the preferences pane! Rebooting the Mac or printer or recycling the printer-cable USB still doesn't get a waiting print job going, nor does the printer dialog box 'pause - resume'. I have to reset the printing system via preferences at the start of every day -- then it's good for one day. I have tried re-installing the drivers from Canon's site but that doesn't help.

The drivers always remain on the system to be added back on the printer preferences pane but, curiously, two different 'Printers' (both named Canon 7700 Series) are selectable in the print dialog box. Let's call them 'old' and 'new'. I prefer the 'old' because the 'new' will not print 'High' quality on plain paper. I don't use wifi or anything wireless.

Any suggestions? Thank you.

 

[MacInWin]

Trevor, you would be much better served by starting a new thread. Maybe a Moderator can cut this post out and start a new thread with it. The title of the thread is an important thing for those who are searching to both find answers and to help and burying a second topic in a thread is a great way to get ignored.

 

[pm-r]

Trevor, you would be much better served by starting a new thread. Maybe a Moderator can cut this post out and start a new thread with it. The title of the thread is an important thing for those who are searching to both find answers and to help and burying a second topic in a thread is a great way to get ignored.

+1 !!!!






- Patrick
======

 

[pm-r]

They may seem less scary because you don't fully understand how badly you can muck up the system with the rm command.

Such a huge constructive understatement Jake!!!

And one that many a user should have known about or heeded.






- Patrick
======