Eject All and Mavericks

[macwish]

Eject All has been working without a hitch for me - except, since installing Mavericks, after completing ejecting all of my external drive partitions successfully, I get the following crash notification: "UnmountAssistantAgent has crashed unexpectedly." The crash does not seem to cause any lasting problems, because Eject All works the next time. I assume this is a problem of Apple's UnMountAssistantAgent (Version 4.0) and not an Alfred problem. Has anyone seen this?

 

What you were doing when the issue happened: run Eject All in Alfred

Whether you were able to replicate it a second time by performing the same action: Happens every time since upgrading to OS X 10.9 (Mavericks). Did not happen with Snow Leopard or Mountain Lion.

Include any screenshots that might help us: see attached

Include the Alfred version & build number you are using: 2.1 (218)

Include your OS X version: OS X 10.9 on MacBook Pro (Early 2011)

 

 

I can email you the crash report if it would be helpful.

[Andrew]

 

Eject All has been working without a hitch for me - except, since installing Mavericks, after completing ejecting all of my external drive partitions successfully, I get the following crash notification: "UnmountAssistantAgent has crashed unexpectedly." The crash does not seem to cause any lasting problems, because Eject All works the next time. I assume this is a problem of Apple's UnMountAssistantAgent (Version 4.0) and not an Alfred problem. Has anyone seen this?

 

What you were doing when the issue happened: run Eject All in Alfred

Whether you were able to replicate it a second time by performing the same action: Happens every time since upgrading to OS X 10.9 (Mavericks). Did not happen with Snow Leopard or Mountain Lion.

Include any screenshots that might help us: see attached

Include the Alfred version & build number you are using: 2.1 (218)

Include your OS X version: OS X 10.9 on MacBook Pro (Early 2011)

 

 

I can email you the crash report if it would be helpful.

 

 

I've been unable to reproduce this issue - I'm going to move it into the help forum to see if anybody else is seeing this issue.

 

It could be some corruption in Finder somewhere.

 

Cheers,

Andrew