macvim-dev / macvim-dev/macvim

kCFURLVolumeIsAutomountedKey missing, from Time Machine

Open
#889 25 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
7.9k
Forks
691
PR merge metrics
No merged PRs in 30d

Description

when I launch mvim from the command line, then I am seeing messages throughout the day stream to the terminal that look like this:

2019-04-29 02:00:00.308 MacVim[25865:2008397] kCFURLVolumeIsAutomountedKey missing for file:///Volumes/ccc/: Error Domain=NSCocoaErrorDomain Code=257 "The file “ccc” couldn’t be opened because you don’t have permission to view it." UserInfo={NSURL=file:///Volumes/ccc/, NSFilePath=/Volumes/ccc, NSUnderlyingError=0x7fd205d05aa0 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}}

2019-04-29 03:00:15.539 MacVim[25865:2016017] kCFURLVolumeIsAutomountedKey missing for file:///Volumes/timemachine/: Error Domain=NSCocoaErrorDomain Code=257 "The file “timemachine” couldn’t be opened because you don’t have permission to view it." UserInfo={NSURL=file:///Volumes/timemachine/, NSFilePath=/Volumes/timemachine, NSUnderlyingError=0x7fd2072289d0 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}}

These seem to coincide time wise with when my Time Machine and/or Carbon Copy Cloner backups are timed to auto mount SMB shares in order to run backups. No idea why this would cause macvim to complain. I don't remember this happening before, but its quite annoying to have my terminal clutter up. Mvim seems to run ok otherwise.

Detailed steps to reproduce the behavior:

  1. Run mvim from the command line
  2. Wait for Timemachine to run a backup over network

Vim Version 8.1.950
OSX sierra 10.12.6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running mvim from the command line on macOS Sierra and reproducing the warning when Time Machine or Carbon Copy Cloner mounts the SMB backup shares. Trace which MacVim entry point emits the kCFURLVolumeIsAutomountedKey message and determine what behavior should change without affecting normal use. Done means the repeated terminal warnings no longer appear during backup mounts while mvim continues to run normally.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, vim
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.