MacOS – After Mavericks 10.9.2 Update, problems running Keepass/Mono

macosmonox11xquartz

I have a rMBP 13" late 2013 model and just updated Mavericks today to 10.9.2 (Software OS X 10.9.2 (13C64))

I have been using the OSX package of keepass from here (Openix) without any issues before updating.

After updating, if I try to open keepass, the laptop hangs (i get the beachball of doom) and the mono process uses upwards of 98% of the cpu untill I kill it.

I have the mono runtime (version 3.2.7) and XQuartz 2.7.5 (xorg-server 1.14.4), installed. I am not very knowledgable as to how to troubleshoot to see if there is mono or x11 issue, I just installed them to be able to use keepass on my macbook.

IS there anyone else experiencing this same issue?

What steps could I take to begin troubleshooting this?

Best Answer

A useful troubleshooting tool for any OS X application is opensnoop which lets you see file activity on your system. If you run sudo opensnoop -v | grep mono-sgen before launching KeePass you'll be able to watch which files it is opening as it launches.

I ran this to troubleshoot another question about KeePass problems and on my system the first launch of KeePass generates a lot of activity where Mono is opening and caching the fonts on the system in ~/.cache/fontconfig. While it is doing this the application appears to be doing nothing, as the UI doesn't appear until this task is complete which takes minutes on my system. Luckily it only seems to want to do this once, as subsequent starts are about what I'd expect.

And this is only guesswork but upgrading Mono, XQuartz or KeePass or installing other fonts might prompt Mono to regenerate this cache, resulting in another one off slow application launch. Just something to be aware of.

Related Solutions

MacOS – Running .NET binary with mono

See this link

Basically what you have to do is to use one of the Mono tools (mkbundle is a generic one while macpack is designed to work on Mac OS X) to link all your application executables, resources and dll in a single executable file that can be later run as a single app.

From the macpack doc:

macpack is a tool that must be used to bundle Cocoa# applications into Double-Clickable, Finder friendly, bundles on Mac OS X. It bundles static libraries and resources, as well as generates a basic info.plist into the .app bundle.

For example the following commands are used to build the CurrencyConverter.exe into an application bundle:

$ mcs -g -debug+ CurrencyConverter.cs -out:CurrencyConverter.exe -pkg:cocoa-sharp
$ rm -rf CurrencyConverter.app
$ macpack -m:2 -o:.  -r:/Library/Frameworks/Mono.framework/Versions/Current/lib/    
  libCocoaSharpGlue.dylib -r:CurrencyConverter.nib -n:CurrencyConverter 
  -a:CurrencyConverter.exe

The resulting CurrencyConverter.app is just another Mac OS X application as far as the Finder is concerned, and can be opened from Finder, or launched from Terminal using the open -a CurrencyConverter command.

MacOS – External monitor stopped working after 10.9.2 update

I've just managed to workaround the problem by disabling DisplayPort 1.2 within the Dell OSD.

To do this, you might need to use a bit of a workaround, which is to get the monitor to bring up the input select and then hold down the green tick for ~8 seconds when the (mini-)DisplayPort option is selected. This will bring up a new menu that enables you to enable/disable DisplayPort 1.2 mode. (Green tick to enable/red to disable, etc.)

Whilst I suspect this is just a temporary fix, it at least means that I can use the monitor until Apple fix their seemingly problematic 10.9.2 release.

UPDATE

As an minor update, my bug report has been closed as a duplicate and due to the nature of Apple's "closed" bug tracking system I've no means of viewing the other ticket. However, at least this is a known issue that will presumably be addressed in a successive release.

Best Answer

Related Solutions

MacOS – Running .NET binary with mono

MacOS – External monitor stopped working after 10.9.2 update

Related Question