Category Archives: MacOS

MacOS Yosemite: Apps still in Launchpad after removal

Recently I have removed some apps from my Macbook Air, as I’ve noticed that is definitely not a gaming PC. In concrete I am talking about Steam, the Gaming Platform and two games. Neither the Mac Book Air is designed for games, nor the small SSD can handle too much data.

So what I did was the following:

  • I removed the Games from Steam
  • I pulled Steam into the Trash
  • Empty the trash

After doing this I noticed that the games and the Steam app still appears on the launchpad.

Following some research on the internet, I have tried to reset my launchpad with the following commands following Nick Man [1]:

defaults write ResetLaunchPad -bool true; killall Dock

But actually when I did this, the “ghost” apps still existed. In addition to that the whole order of my apps – grouping them over years to make it personally usable for me – has been vanished. Apple has now rearanged my apps in their order. Big Dislike!

Also the remove and rebuild of the Dock as described in [2] with the following command did not work out:

rm ~/Library/Application\ Support/Dock/*.db; killall Dock

After some time, when I got used to the “ghost apps”, I ended up in a Finder folder, where suddenly the “ghost apps” showed up.

Screenshot at März 25 17-04-00

And believe it or not – removing them from this folder, I finally got rid of my “ghost apps”. So two things I have learned from this lesson:

  • There are user-specific applications existing in ~/Applications
  • Sometimes the solution for a problem is easier than expected.

[1], Ultimative Guide to Fixing and Resetting OSX Yosemite LaunchPad 

[2], Reset LaunchPad to fix persistent empty folder bug 

OS X 10.10 – Yosemite Beta 4

I have just downloaded the OS X 10.10 – Yosemite Beta 4, and at first sight most of my reported issues seems to be gone by now. Still a bit questionable is the information provided with the update. Once again  – 850 MB update with the information “recommended for all users” is a bit too less information, but maybe the majority feels happy with it.

So from my previous post [1] the issue with the empty help menu is gone – there is now help where you need it. The search function in my Calendar and in Mail is still not working – whatever I enter, I do not get any search results back. The issue with Mail, where I was not able to write any text was fixed by an previous update already.

From the first test report [2] I think most of the bugs are fixed. Quite annoying for me is the thing with  VmWare, as through the upgrade I am kind of forced to buy a new licence for VmWare 7.

Testing other applications I recently found a reproducible bug in iBooks Author [3]. Trying to add some additional text to the classical layout with the made-up text, the iAuthor application crashes as you can see.

Schnappschuss (2014-09-30 22.20.00)#

There has been done a lot recently and many things improved, but still there is some way to go for the final release of Mac OS X 10.10. Beyond the open bugs there are also some features I would like to see. For example since upgrading my iPhone to iOS 8, I still do not see the level of integration I expected to see – but that might come up in the next releases.

[1], OS X 10.10 Yosemite – Testing Part 2

[2], OS X 10.10 Yosemite – Testing Part 1

[3] Apple, iBooks Author

OS X 10.10 Yosemite – Testing Part 2

Following my testing of OS X 10.10 Yosemite [1], today I have downloaded the following two updates from Apple for the Mac OS X 10.10 Yosemite:

  • OS X Yosemite Developer Preview 7
  • OS X Beta Recovery Update

First of all it would be helpful to provide some more details in regards to the context of the update. An “this update is recommended for all users” with an 1.6 GB package is a bit questionable. Unfortunately directly after the installation I was not able to use Mail anymore. Trying to write a new mail, I’ve been able to define the recipients, to attach a file, but actually not to write any text.

Schnappschuss (2014-09-16 17.09.07)

Then I wanted to create an bug report with the Apple Feedback tool. As far as I remember it was possible to report it via the Help menu. When I looked there, actually the help was somehow missing. I’ve check on other apps – e.g. Safari, but the help menu points are missing there as well.


Actually the menu points are there and can be selected, but the labels are missing.

I am just wondering if there will be another patch when iOS8 is going to be released 2014/09/17 following [2]. Anyway that is going to be interesting how the integration with Yosemite works.

[2014/09/21] Update: Furthermore I’ve noticed that the search function in the Calendar does not work correctly. I searched for “PPL-KURS”, where I should have at least 10 entries in the future, but it gave me “No results found”.

Schnappschuss (2014-09-22 08.47.33)


[1], OS X 10.10 Yosemite – Testing Part 1

[2], iOS-8 10 Thins we want to see



How to stop a failed FileVault encryption (at least partly)

With the upgrade to the second public beta version of OS X 10.10 Yosemite [1], I took the decision to enable FileVault to encrypt my disk. Setting the checkbox on the installation didn’t ring any bell in my head, so I went forward without thinking what such a simple click might do. Who needs backups? Who cares about installed software and licences? Who needs a laptop to work?

Anyway, this click resulted that after the installation of the new beta version, the operating system started to encrypt my hard drive. It started and actually never stopped – showing my over 1000 days left for the encryption. So how to check the actual status? Searching through the internet provided me some feedback to crosscheck what might be the real status. Here the command and the output (with the main messages highlighted in bold):

firebird: jvr$ diskutil cs list
 CoreStorage logical volume groups (1 found)
 +-- Logical Volume Group 84A81CB4-5CF5-4870-A328-D5F95B4C6FC7
 Name: Macintosh HD
 Status: Online
 Size: 250140434432 B (250.1 GB)
 Free Space: 1413611520 B (1.4 GB)
 +-< Physical Volume 0D11C48B-24FF-4B1F-8145-D2B175A086F2 | ---------------------------------------------------- | Index: 0 | Disk: disk0s2 | Status: Online | Size: 250140434432 B (250.1 GB) | +-> Logical Volume Family FB0D79FD-CC02-4C94-9D6E-49237DE99976
 Encryption Status: Unlocked
 Encryption Type: AES-XTS
 Conversion Status: Converting
 Conversion Direction: forward
 Has Encrypted Extents: Yes
 Fully Secure: No
 Passphrase Required: Yes
 +-> Logical Volume 19FF468D-62F8-4818-828F-EE8F6160F450
 Disk: disk1
 Status: Online
 Size (Total): 248391270400 B (248.4 GB)
 Conversion Progress: Failed
 Revertible: No
 LV Name: Macintosh HD
 Volume Name: Macintosh HD
 Content Hint: Apple_HFS


In addition to the failed encryption, the process seems that he doesn’t want to stop. By running in the background he consumed around 20% of my CPU usage resulting into a constantly running cooler, while holding a hot MacBook Air in your hand and watching the battery level going down quite rapidly.

Ok, what did we learn about this issue? Do backups and think twice enabling a check-box under a beta version of an operating system.

Not being able to find any acceptable fixes for my problem (all somehow recommend to restore from the backup) I felt left alone with my laptop.

So scanning for the according process turned out that corestoraged was causing the high load. Giving it a 50/50 chance to fix it or to destroy my system completely I had an idea how to fix it. So first I tried to simply kill the process. That worked but after a few seconds the process reappeared – so it must have been started from another daemon. It turned out that actually the launchd is kicking off this process. So either to go through the whole tutorial [2] I decided to do a quick fix/trial. So my idea was to move the daemon binary and than to kill the process. So I did the following:

firebird:~ jvr$ mv /usr/libexec/corestoraged /usr/libexec/corestoraged.old
firebird:~ jvr$ killall corestoraged

And suprisingly the load dropped, while my operating system was still working. Please note that this is highly risky and I would not recommend to do it unless you don’t see any other options.

It should be also noted that there is definitely a better solution in place related to the launchd configuration. Neither the less Apple should get their FileVault running stable, especially since it has to be considered as a core service.

[2014/09/09] Update: Already giving up my hope to fix the issue permanently, I started to backup my MacBook and prepare for a re-installation. Even if the above workaround resolved the CPU usage & power consumption issue, I did not feel comfortable moving around core processes, where I was not 100% sure what they are doing. So I backed up everything and started cleaning my machine.
Having everything done so far I decided to start the Mac in Recovery mode and try one more time the disk repair functionality (especially the fix permissions). After doing this, I thought I give it one more last try. Booted up, moved the corestoraged back and checked in the FileVault progress screen within the Security Settings.
And suddenly I saw that the encryption process was working again. This time I did not touch the machine anymore until the encryption was finished.

And what I have learned from this lesson – do backups. And the second lesson I’ve learned: never go the easy way and start reinstalling your operating system.


[1], OS X 10.10 Yosemite – Test

[2] A launchd Tutorial