"Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

General discussions about LaunchBar
PackDude
Posts: 5
Joined: Wed Jul 25, 2012 9:35 pm

"Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby PackDude » Thu Dec 14, 2017 1:35 am

After upgrading to High Sierra, whenever I try to eject external hard drives, I get the following "The disk "*******" couldn't be ejected because "LaunchBar" is using it." I'm using the latest version of LaunchBar (Version 6.9.3 (6156)). Any suggestions? Quitting the app every time I need to eject a drive is not acceptable. This just started after the upgrade to HS.

marco
Objective Development
Objective Development
Posts: 64
Joined: Mon Jul 28, 2014 3:00 pm
Location: Vienna, Austria

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby marco » Mon Dec 18, 2017 1:30 pm

Is this reproducible or just a one-off thing? It could be that LaunchBar is currently accessing the disk because it’s indexing something. Do you have any rules set up that could cause this, e.g. a Folder Indexing rule whose path points to a folder on that disk?

luckylindy
Posts: 5
Joined: Fri Dec 07, 2012 11:34 pm

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby luckylindy » Wed Apr 04, 2018 9:52 pm

I had the same issue. I think I fixed it; try this:

1. Invoke LB
2. Press command-option-i
3. On the left, select 'Mounted Volumes'
4. In the window on the right, un-check the mounted volume(s) you want to be able to eject
5. Quit LB
6. Start LB again
7. Check the index again (steps 1-3); in the right window, you should see that your unchecked setting (step 4) has 'stuck', and your mounted volume is not being indexed by LB
8. Eject the volume; it should eject

I haven't let the mounted volume sit for very long between steps 7 and 8, but I am hoping this preference survives time and reboots. I'll let you know.

Y'all do likewise!

marco
Objective Development
Objective Development
Posts: 64
Joined: Mon Jul 28, 2014 3:00 pm
Location: Vienna, Austria

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby marco » Thu Apr 05, 2018 9:38 am

luckylindy wrote:[…] and your mounted volume is not being indexed by LB

Please note that if you uncheck a volume in the “Mounted Volume” rule’s index, that does not mean that the volume’s content is not indexed. This simply means that that volume will not show up when you browse the “Mounted Volumes” rule or when you do a full index search. Also, that indexing rule never access anything on the volume, it just lists whatever volumes are currently mounted. Therefore, what you suggest should not be the root of the problem. Instead, there could be a Folder indexing rule that access the volume.

dmw
Posts: 4
Joined: Fri Nov 17, 2006 5:20 pm

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby dmw » Fri Jun 08, 2018 6:29 pm

I'm also having this problem. I have to quit LaunchBar every time I want to eject my external disk. If I quit and restart LaunchBar, I can eject the drive with LaunchBar running. Similarly, I can eject the drive with LaunchBar running if I try shortly after I mount the drive. But if I try to eject after the drive has been plugged in for some time, I invariably get the "Disk couldn't be ejected" error.

So there is something happening in LaunchBar some time after the drive has been plugged in that is causing the issue. I tried looking at the files LaunchBar had open, and none of them were on the external drive, so I'm stumped.

marco
Objective Development
Objective Development
Posts: 64
Joined: Mon Jul 28, 2014 3:00 pm
Location: Vienna, Austria

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby marco » Mon Jun 11, 2018 12:27 pm

If LaunchBar doesn’t have any files open on the external drive, but macOS is still unable to unmount it because if LaunchBar, that doesn’t make much sense to me. How did you check that LaunchBar has no files open on the volume?

This is still something I could not reproduce. And I’m frequently mounting and unmounting disks on my Mac.

rowatt
Posts: 3
Joined: Mon Sep 17, 2018 7:35 pm

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby rowatt » Mon Sep 17, 2018 7:43 pm

I recently started having the same issue. In my case, it started after I started using CCC to backup my main disk. In normal operation CCC mounts the backup disk, does the backup and then unmounts it. However, sometimes CCC can't unmount it and in every case I've tested, it is LaunchBar which is preventing the unmount.

`lsof` tells me that in every case I have checked, it's because LaunchBar has opened the X.app/Contents/Resources/Assets.car file where "X" is an application in the /Applications folder - e.g. Mail.app, Messages.app, Evernote.app.

I haven't deliberately added anything from the backup disk to LaunchBar's index - is there anything I can do to either totally exclude that drive from any indexing, or at least turn off whatever rule is opening the Assets.car files?

marco
Objective Development
Objective Development
Posts: 64
Joined: Mon Jul 28, 2014 3:00 pm
Location: Vienna, Austria

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby marco » Tue Sep 18, 2018 10:49 am

rowatt wrote:`lsof` tells me that in every case I have checked, it's because LaunchBar has opened the X.app/Contents/Resources/Assets.car file […]

That is very interesting, thank you for letting me know. LaunchBar does not itself access these paths, but the system frameworks LaunchBar uses very likely do. For example, when LaunchBar shows the icon of an app, it uses functionality in the Foundation and AppKit frameworks to load the icon from disk. And since nowadays many apps use asset catalogs where all images and icons stored in the Assets.car file, something has to read from that file. Looks like something in the system frameworks is holding on to the file for no apparent reason. We’ll investigate this further.

rowatt
Posts: 3
Joined: Mon Sep 17, 2018 7:35 pm

Re: "Disk couldn't be ejected because Launchbar is using it" after High Sierra upgrade

Postby rowatt » Tue Sep 18, 2018 11:51 am

Great - thank you.


Return to “LaunchBar General”

Who is online

Users browsing this forum: No registered users and 2 guests