Re: Cannot get gimp app running
On Sat, Nov 1, 2014 at 8:07 PM, Gregory Seidman gsslist+macpo...@anthropohedron.net wrote: This is a known, upstream bug: https://trac.macports.org/ticket/45309 --Greg On Sat, Nov 01, 2014 at 06:45:55PM -0500, Eric A. Borisch wrote: Are you able to open something that uses a plugin, like a png? My gimp starts up, but none of the plugins (required for most file types) are working. - Eric I am aware. I was trying to determine if David's was somehow working (including plugins.) Turns out it was not (same boat everyone else is in.) - Eric ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
The crazy thing I did to fix Yosemite performance
Hi, So after much frustration, much stress, and of course, I broke my Mac in the process. Backed up my user folder from single-user mode (since my mac would not boot all the way). Then I wiped and reinstalled Mavericks, upgraded to Yosemite, and then restored my user folder. Back story: In an attempt to figure out why the services mds and mdworker were running away with my CPU. Nothing I did resolved this, including putting every single folder except /Applications in the exception list for Spotlight. This is where I started editing LaunchDaemons and LaunchAgents and where breakage occurred. So... This literally resolved all of the performance issues I saw reported from many others besides myself about the performance of Yosemite via the standard upgrade path. On to MacPorts... - Broken link checks - Binary database updates Both go within seconds, except for the binary database initial creation, which took a couple of minutes. After which, everything is running like new. I know it is and was a pain in the rear to have to do all of this, but if there is one thing Apple has done correct it is that restoring a backed up user folder to a fresh install, puts all configurations, accounts, and other customizations right back to where they were with no hassle. I hope this gives some insight on a sure fire way of resolving Yosemite performance issues. Good Luck, Jeff ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: The crazy thing I did to fix Yosemite performance
On Sunday November 02 2014 12:06:35 Jeff Singleton wrote: Back story: In an attempt to figure out why the services mds and mdworker were running away with my CPU. Nothing I did resolved this, including putting every single folder except /Applications in the exception list for Spotlight. This is where I started editing Did that include switching off indexing for the whole (boot) disk (mdutil -i off) followed by a reboot? That ought to have wiped your spotlight folder, presuming that the most likely performance culprit would be updating an existing (huge) database file ... R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: The crazy thing I did to fix Yosemite performance
On Nov 2, 2014, at 1:57 PM, René J.V. Bertin rjvber...@gmail.com wrote: On Sunday November 02 2014 12:06:35 Jeff Singleton wrote: Back story: In an attempt to figure out why the services mds and mdworker were running away with my CPU. Nothing I did resolved this, including putting every single folder except /Applications in the exception list for Spotlight. This is where I started editing Did that include switching off indexing for the whole (boot) disk (mdutil -i off) followed by a reboot? That ought to have wiped your spotlight folder, presuming that the most likely performance culprit would be updating an existing (huge) database file ... This problem (runaway MDs/MDWorker jobs) was also true in Mavericks. I don't know how Apple updates the Spotlight database, but it is pretty clear that following a major upgrade, that database needs to be purged of all the old records which are basically duplicated by the new. Using Apple's methodology, this update apparently takes days. Virtually all of the fixes involved trashing that Spotlight database in some fashion. A disk-wipe and re-install, is clearly one, which also has the benefit of trashing all of the various Cache databases created by various apps, as User/Library/Caches is not backed-up. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: The crazy thing I did to fix Yosemite performance
On 11/2/14 12:57 PM, René J.V. Bertin wrote: On Sunday November 02 2014 12:06:35 Jeff Singleton wrote: Back story: In an attempt to figure out why the services mds and mdworker were running away with my CPU. Nothing I did resolved this, including putting every single folder except /Applications in the exception list for Spotlight. This is where I started editing Did that include switching off indexing for the whole (boot) disk (mdutil -i off) followed by a reboot? That ought to have wiped your spotlight folder, presuming that the most likely performance culprit would be updating an existing (huge) database file ... R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users Trust me. I tried everything. Resetting the SMC, PRAM, permissions, manually deleting the .Spotlight folder from /. Anything I could find on any Apple related blog/forum, I tried it. Even going so far as to exclude lots of folders from my home Library folder, the same for System Library folder, my external drive, Bootcamp partition...none of it mattered. The only thing that had any affect was to stop the mdworker services and the syslogd service. That is the only time the CPU usage dropped and the fans started slowing. Of course, right after I rebooted, they started back up again. Somewhere in the middle of all that I probably forgot to revert an edit on one of the plist files and thats when it stopped booting to the GUI. Single-user mode was the only way, which required manually mounting my external drives and copying my user folder to it. Booted to my Mavericks USB installer, completely wiped the main drive, installed Mavericks, and upgraded to Yosemite. Then booted to single-user again, and restored my user home folder. From that point, mdworker did its initial indexing, and then dropped down to normal usage. Now the fans only spin up when I am actually doing something like compiling something under MacPorts. Jeff ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: The crazy thing I did to fix Yosemite performance
Your user folder from your original installation will include a lot of settings, preferences and the like from applications that were part of your older OS install. Potentially that might not be what you want, I don't really know. Recent versions of OS X hide your ~/Library folder in the Finder, but you can get into it with: $ cd ; open Library There is a lot of stuff in there, put there by Apple or by third-party App developers. I don't think it's such a good idea that the Library folder is completely hidden, as most users won't know it's there, won't know to back it up and so on. But of course Apple figures everyone just uses Spotlight. :-/ I don't use Spotlight, I have grey hair, my face is getting wrinkled so I drop .tar.gzs onto USB sticks. Mike Michael David Crawford mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. On Sun, Nov 2, 2014 at 4:54 PM, Jeff Singleton gvib...@gmail.com wrote: On 11/2/14 12:57 PM, René J.V. Bertin wrote: On Sunday November 02 2014 12:06:35 Jeff Singleton wrote: Back story: In an attempt to figure out why the services mds and mdworker were running away with my CPU. Nothing I did resolved this, including putting every single folder except /Applications in the exception list for Spotlight. This is where I started editing Did that include switching off indexing for the whole (boot) disk (mdutil -i off) followed by a reboot? That ought to have wiped your spotlight folder, presuming that the most likely performance culprit would be updating an existing (huge) database file ... R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users Trust me. I tried everything. Resetting the SMC, PRAM, permissions, manually deleting the .Spotlight folder from /. Anything I could find on any Apple related blog/forum, I tried it. Even going so far as to exclude lots of folders from my home Library folder, the same for System Library folder, my external drive, Bootcamp partition...none of it mattered. The only thing that had any affect was to stop the mdworker services and the syslogd service. That is the only time the CPU usage dropped and the fans started slowing. Of course, right after I rebooted, they started back up again. Somewhere in the middle of all that I probably forgot to revert an edit on one of the plist files and thats when it stopped booting to the GUI. Single-user mode was the only way, which required manually mounting my external drives and copying my user folder to it. Booted to my Mavericks USB installer, completely wiped the main drive, installed Mavericks, and upgraded to Yosemite. Then booted to single-user again, and restored my user home folder. From that point, mdworker did its initial indexing, and then dropped down to normal usage. Now the fans only spin up when I am actually doing something like compiling something under MacPorts. Jeff ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
