Error: unsupported compressor 8

[Andrew J]

Hi,

When I start up the command line tools under High Sierra 10.13 with Bbedit 12, I sometimes see messages like the following:

$ bbedit .

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8

/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'

This error does not always occur and seems to depend on what directory I am in, and so perhaps on the filetypes that Bbedit is trying to display? I do see similar entries in the console:

Oct 16 10:49:20 mekon BBEdit[38338]: /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8

Oct 16 10:49:20 mekon BBEdit[38338]: /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.1.1/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'

Everything seems to be running, but it's a bit annoying...

Andrew

[Rich Siegel]

On 10/16/17 at 6:05 AM, a.h....@gmail.com (Andrew J) wrote:

>Hi,
>
>When I start up the command line tools under High Sierra 10.13
>with Bbedit 12, I sometimes see messages like the following:

These log entries are the result of a bug in the OS. They're
harmless and don't indicate a problem, although they do pollute
Terminal output when they appear while using the `bbedit` tool.

Because the log entries only occur when BBEdit is started, the
best workaround for now is to leave BBEdit running.

We have reported this issue to Apple, and if you have a
developer account, we would be grateful if you did likewise.

R.
--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they
sedate me.

[Andrew J]

Hi Rich, 

Done: Reported on https://bugreport.apple.com/ -- and marked as a duplicate. So at least they are paying some attention...

Andrew

[Rich Siegel]

On 10/26/17 at 5:24 AM, a.h....@gmail.com (Andrew J) wrote:

> Done: Reported on https://bugreport.apple.com/ -- and marked as a
> duplicate. So at least they are paying some attention...

Great. Also, 12.0.1 contains a workaround.

Enjoy,

[Br. Bill]

Is the workaround still good? I'm running 12.5 on Mojave 10.14.1 and the problem still exists.

-----

Br.Bill

DevOops

[Rich Siegel]

On 11/19/18 at 3:44 PM, bocto...@gmail.com (Br. Bill) wrote:

>Is the workaround still good? I'm running 12.5 on Mojave 10.14.1 and
>the problem still exists.

You have an old version of the command-line tools installed; use
"Install Command Line Tools" from the BBEdit menu to update them.

[Br. Bill]

I installed the latest, but it didn't change anything.

Then I upgraded BBEdit to 12.5.1 and then installed latest command line tools again, and presto-fixo.

-----

Br.Bill

DevOops