Common c unimplemented subshell type 1 mac os

mc: subshell not working with /bin/sh

Сообщил:	sierkb@…	Владелец:
Приоритет:	Normal	Этап разработки:
Компонент:	ports	Версия:
Ключевые слова:	Копия:
Port:	mc

Описание (последним изменил «>larryv (Lawrence Velázquez) )

After upgrading from macOS 10.11 to 10.12 and reinstalling MacPorts with all the ports, I run into the following problem:

on macOS 10.12.0 (Sierra), mc throws a

Searching for this error, I’ve stumbled over similar problems/bugs relating mc on FreeBSD:

I’ve never had this problem before on macOS 10.11.x and older, and I guess, something might have changed on 10.12 relating /bin/sh resp. the shell environment. Please fix here on MacPorts with a patch or upstream, so that mc is usable again with subshell on macOS 10.12.x (Sierra).

История изменений (13)

comment:1 Changed 5 лет ago by «>mf2k (Frank Schima)

Владелец:	изменён с macports-tickets@… на mk@…
Ключевые слова:	subshell not worling with /bin/sh перемещены
Копия:	mk@… перемещён

comment:2 следующий: 4 Changed 5 лет ago by «>mkae (Marko Käning)

Tested this on Sierra just now and can’t reproduce the error.

Tell me, have you entered

in Terminal.app ‘s «Preferences/Profiles/Startup/Run command» and check-marked it?

comment:3 Changed 5 лет ago by «>larryv (Lawrence Velázquez)

Краткое описание:	mc: subshell not worling with /bin/sh → mc: subshell not working with /bin/sh
Описание:	изменено (отличие)

comment:4 в ответ на: 2 ; следующий: 5 Changed 5 лет ago by sierkb@…

Tested this on «Sierra 10.12.1 Beta» just now and can’t reproduce the error.

OK. 10.12.1 Beta. And 10.12.0? Maybe a bug in macOS 10.12.0 and fixed in 10.12.1 Beta?

in Terminal.app ‘s «Preferences/Profiles/Startup/Run command» and check-marked it?

No. I have it this way since years without problems:

Added /opt/local/bin/bash to the end of /etc/shells with

Change the user login default shell to /opt/local/bin/bash with

Verify this change in System Preferences > Users & Groups > Current User > Advanced Options (per right-click) > Login Shell > /opt/local/bin/bash

comment:5 в ответ на: 4 Changed 5 лет ago by «>mkae (Marko Käning)

Well, I can’t test on 10.12.0, unfortunately. Not sure what to do about this for now.

Re bash: OK, I see, you’ve globally set that for your user account.

comment:6 следующий: 7 Changed 5 лет ago by «>mkae (Marko Käning)

Perhaps you can contact upstream, sierkb, and report back if there is something new happening.

Alternatively I could try adapt the patch for MacPorts and attach it to this ticket so that you can test it locally on your system. Once your Sierra gets an update you can check again with the unpatched version of mc in order to verify what I am seeing here on my Beta.

comment:7 в ответ на: 6 Changed 5 лет ago by «>sierkb

Perhaps you can contact upstream, sierkb, and report back if there is something new happening.

Alternatively I could try adapt the patch for MacPorts and attach it to this ticket so that you can test it locally on your system.

Once your Sierra gets an update

Apple has released 10.12.1 update yesterday, I’ve installed it:

you can check again with the unpatched version of mc in order to verify what I am seeing here on my Beta.

Same error as before. I have no clue, why your 10.12.1 beta seems to work at that point, but not the stable 10.12.1 release on my installation. And no clue, why I’ve had no problem at the very same point with 10.11.x and lower but since 10.12.x. What has changed in 10.12.x concerning shell/subshell that effects this?

comment:8 Changed 5 лет ago by «>mkae (Marko Käning)

I have something consoling for you:

as observed on my Sierra release 10.12.1.

You know what, I think I all along missed the sudo in front of my mc call. ;-/

I’ll look into this (patch) and let you know. I hope it’s not a pressing matter for you, as I won’t be able to do this immediately. Stay tuned and patient please. 🙂

comment:9 Changed 5 лет ago by «>mkae (Marko Käning)

comment:10 следующий: 11 Changed 5 лет ago by «>mkae (Marko Käning)

Решение:	→ fixed
Состояние:	accepted → closed

So, I’ve built and ran a patched mc on Sierra (and for reference also on Mavericks) w/o seeing the above issue anymore.

Done in r154272! (Let’s hope that the buildbots will be fine with it!)

Yet, I don’t know what to make of the ​ patch source’s comment:6. Well, it’s solved for MacPorts now. If they don’t want to commit this patch they’ll surely figure out another solution.

comment:11 в ответ на: 10 Changed 5 лет ago by «>sierkb

So, I’ve built and ran a patched mc on Sierra (and for reference also on Mavericks) w/o seeing the above issue anymore.

Done in r154272! (Let’s hope that the buildbots will be fine with it!)

OK. Thanks a lot. It works for me. But this tiny patch used by you has a disadvantage (delay of 5 or 10 seconds), as also mentioned in ​ mc Ticket #3658 comment 1:

The attached patch allows mc to start without error. However, there is a 5 second delay when it starts. When trying to use the subshell, it simply shows a blank terminal, at which point any key press returns you to the normal mc file layout screen.

I guess, there seems to be a better and more sophisticated upstream patch around (hint: this mc upstream comment ​ mc doesn’t recognize shell (e.g., /bin/sh) as bash when it is a link to bash binary, comment 11), which avoids such delays and other things:

Maybe prefer this more sophisticated mc ticket 3692 patch over the quick fix mc ticket 3658 patch used by you?

Well, it’s solved for MacPorts now.

If they don’t want to commit this patch they’ll surely figure out another solution.

Maybe they prefer this mentioned ​ mc Ticket #3692 More sophisticated shell type detection method (which is targeted: Future Releases, that’s why I asked them to ship it more early rather than in any so far unnamend future release)?

comment:12 Changed 5 лет ago by «>mkae (Marko Käning)

Решение:	fixed
Состояние:	closed → reopened

OK, will look into the alternative patch. This time, though, it will take much longer. I am sorry, but please test that yourself locally, if possible.

Источник

mc: subshell not working with /bin/sh

Сообщил:	sierkb@…	Владелец:
Приоритет:	Normal	Этап разработки:
Компонент:	ports	Версия:
Ключевые слова:	Копия:
Port:	mc

Описание (последним изменил «>larryv (Lawrence Velázquez) )

After upgrading from macOS 10.11 to 10.12 and reinstalling MacPorts with all the ports, I run into the following problem:

on macOS 10.12.0 (Sierra), mc throws a

Searching for this error, I’ve stumbled over similar problems/bugs relating mc on FreeBSD:

I’ve never had this problem before on macOS 10.11.x and older, and I guess, something might have changed on 10.12 relating /bin/sh resp. the shell environment. Please fix here on MacPorts with a patch or upstream, so that mc is usable again with subshell on macOS 10.12.x (Sierra).

История изменений (13)

comment:1 Changed 5 лет ago by «>mf2k (Frank Schima)

Владелец:	изменён с macports-tickets@… на mk@…
Ключевые слова:	subshell not worling with /bin/sh перемещены
Копия:	mk@… перемещён

comment:2 следующий: 4 Changed 5 лет ago by «>mkae (Marko Käning)

Tested this on «Sierra 10.12.1 Beta» just now and can’t reproduce the error.

Tell me, have you entered

in Terminal.app ‘s «Preferences/Profiles/Startup/Run command» and check-marked it?

comment:3 Changed 5 лет ago by «>larryv (Lawrence Velázquez)

Краткое описание:	mc: subshell not worling with /bin/sh → mc: subshell not working with /bin/sh
Описание:	изменено (отличие)

comment:4 в ответ на: 2 ; следующий: 5 Changed 5 лет ago by sierkb@…

Tested this on «Sierra 10.12.1 Beta» just now and can’t reproduce the error.

OK. 10.12.1 Beta. And 10.12.0? Maybe a bug in macOS 10.12.0 and fixed in 10.12.1 Beta?

in Terminal.app ‘s «Preferences/Profiles/Startup/Run command» and check-marked it?

No. I have it this way since years without problems:

Added /opt/local/bin/bash to the end of /etc/shells with

Change the user login default shell to /opt/local/bin/bash with

Verify this change in System Preferences > Users & Groups > Current User > Advanced Options (per right-click) > Login Shell > /opt/local/bin/bash

comment:5 в ответ на: 4 Changed 5 лет ago by «>mkae (Marko Käning)

Well, I can’t test on 10.12.0, unfortunately. Not sure what to do about this for now.

Re bash: OK, I see, you’ve globally set that for your user account.

comment:6 следующий: 7 Changed 5 лет ago by «>mkae (Marko Käning)

Perhaps you can contact upstream, sierkb, and report back if there is something new happening.

Alternatively I could try adapt the patch for MacPorts and attach it to this ticket so that you can test it locally on your system. Once your Sierra gets an update you can check again with the unpatched version of mc in order to verify what I am seeing here on my Beta.

comment:7 в ответ на: 6 Changed 5 лет ago by «>sierkb

Perhaps you can contact upstream, sierkb, and report back if there is something new happening.

Alternatively I could try adapt the patch for MacPorts and attach it to this ticket so that you can test it locally on your system.

Once your Sierra gets an update

Apple has released 10.12.1 update yesterday, I’ve installed it:

you can check again with the unpatched version of mc in order to verify what I am seeing here on my Beta.

Same error as before. I have no clue, why your 10.12.1 beta seems to work at that point, but not the stable 10.12.1 release on my installation. And no clue, why I’ve had no problem at the very same point with 10.11.x and lower but since 10.12.x. What has changed in 10.12.x concerning shell/subshell that effects this?

comment:8 Changed 5 лет ago by «>mkae (Marko Käning)

I have something consoling for you:

as observed on my Sierra release 10.12.1.

You know what, I think I all along missed the sudo in front of my mc call. ;-/

I’ll look into this (patch) and let you know. I hope it’s not a pressing matter for you, as I won’t be able to do this immediately. Stay tuned and patient please. 🙂

comment:9 Changed 5 лет ago by «>mkae (Marko Käning)

comment:10 следующий: 11 Changed 5 лет ago by «>mkae (Marko Käning)

Решение:	→ fixed
Состояние:	accepted → closed

So, I’ve built and ran a patched mc on Sierra (and for reference also on Mavericks) w/o seeing the above issue anymore.

Done in r154272! (Let’s hope that the buildbots will be fine with it!)

Yet, I don’t know what to make of the ​ patch source’s comment:6. Well, it’s solved for MacPorts now. If they don’t want to commit this patch they’ll surely figure out another solution.

comment:11 в ответ на: 10 Changed 5 лет ago by «>sierkb

So, I’ve built and ran a patched mc on Sierra (and for reference also on Mavericks) w/o seeing the above issue anymore.

Done in r154272! (Let’s hope that the buildbots will be fine with it!)

OK. Thanks a lot. It works for me. But this tiny patch used by you has a disadvantage (delay of 5 or 10 seconds), as also mentioned in ​ mc Ticket #3658 comment 1:

The attached patch allows mc to start without error. However, there is a 5 second delay when it starts. When trying to use the subshell, it simply shows a blank terminal, at which point any key press returns you to the normal mc file layout screen.

I guess, there seems to be a better and more sophisticated upstream patch around (hint: this mc upstream comment ​ mc doesn’t recognize shell (e.g., /bin/sh) as bash when it is a link to bash binary, comment 11), which avoids such delays and other things:

Maybe prefer this more sophisticated mc ticket 3692 patch over the quick fix mc ticket 3658 patch used by you?

Well, it’s solved for MacPorts now.

If they don’t want to commit this patch they’ll surely figure out another solution.

Maybe they prefer this mentioned ​ mc Ticket #3692 More sophisticated shell type detection method (which is targeted: Future Releases, that’s why I asked them to ship it more early rather than in any so far unnamend future release)?

comment:12 Changed 5 лет ago by «>mkae (Marko Käning)

Решение:	fixed
Состояние:	closed → reopened

OK, will look into the alternative patch. This time, though, it will take much longer. I am sorry, but please test that yourself locally, if possible.

Источник

Common c unimplemented subshell type 1 mac os

After running numerous pkg add commands on pfSense 2.3.5 i386 I was finally able to install Midnight Commander, only to find that it would not run, giving the error

common.c: unimplemented subshell type 1
read (subshell_pty….): No error: 0 (0)

Any ideas on what I need to do to get it working?

If you pkg added a load of things it may well have overwritten something required by pfSense.

Why are you trying to install MC though? Just use SCP and some remote file system manager.

If you pkg added a load of things it may well have overwritten something required by pfSense.

Why are you trying to install MC though? Just use SCP and some remote file system manager.

MC is the app I use most and am lost without it. It’s even included in the base build of FreeNAS. If you are not familiar with it you are not aware of how powerful it is, especially for accessing the filesystem. I have it on my normal pfSense box but it is a pain to install because of all the dependencies… I’ve just noticed that pfSense contains /usr/local/etc/pkg/repos/FreeBSD.conf which has enabled: no set. If I change that to yes can I then run pkg install mc as I would on FreeBSD and automatically install all the dependencies?

There is no reason to access the filesystem on a pfSense installation, even in emergency cases you at most have to copy the config to a different storage device. So including/adding something like MC doesn’t make any sense. Use something like WinSCP on your client, if you really need a filemanager, and don’t mess up your firewall.

In case anyone else has this problem the workaround is to run mc -u

Источник