Command exits with 127 on Babun, but works on Cygwin #225

Closed
kehak opened this Issue Jan 11, 2015 · 11 comments

Comments

Projects
None yet
9 participants
@kehak

kehak commented Jan 11, 2015

Running smartctl on Babun exits silently with error code 127, however running the same binary from a vanilla Cygwin installation works.

» pact install smartmontools
(...)
» /usr/sbin/smartctl -A /dev/sda ~127
» bash /usr/sbin/smartctl -A /dev/sda ~125
/usr/sbin/smartctl.exe: /usr/sbin/smartctl.exe: cannot execute binary file

Same problem when running the Cygwins smartctl from Babun, even though the reverse works (running Babuns smartctl from Cygwin).

» ls -l /usr/sbin/smartctl.exe ~
-rwxr-xr-x+ 1 Kehak None 0 Jan 11 18:06 /usr/sbin/smartctl.exe
» file /usr/sbin/smartctl.exe ~
/usr/sbin/smartctl.exe: PE32 executable (console) Intel 80386, for MS Windows

Tried running Babun as administrator, no difference.

@darinkes

This comment has been minimized.

Show comment
Hide comment
@darinkes

darinkes Jan 20, 2015

Contributor

Just a wild guess: see Issue #222
Maybe pact is also not running postinstall scripts while installing smartmontools.
(Didn't check if smartmontool has any)

Contributor

darinkes commented Jan 20, 2015

Just a wild guess: see Issue #222
Maybe pact is also not running postinstall scripts while installing smartmontools.
(Didn't check if smartmontool has any)

@darinkes

This comment has been minimized.

Show comment
Hide comment
@darinkes

darinkes Jan 20, 2015

Contributor

Yes, seems to be the same problem:

Package smartmontools installed
{ ~ }  » ls -l /etc/postinstall/*.sh
-rwxrwxr-x+ 1 user Kein 274 Sep  7 18:21 /etc/postinstall/smartmontools.sh
Contributor

darinkes commented Jan 20, 2015

Yes, seems to be the same problem:

Package smartmontools installed
{ ~ }  » ls -l /etc/postinstall/*.sh
-rwxrwxr-x+ 1 user Kein 274 Sep  7 18:21 /etc/postinstall/smartmontools.sh
@tombujok

This comment has been minimized.

Show comment
Hide comment
@tombujok

tombujok Feb 4, 2015

Contributor

Will be fixed soon, there's a PR waiting for merge.

Contributor

tombujok commented Feb 4, 2015

Will be fixed soon, there's a PR waiting for merge.

@tombujok tombujok added the bug label Feb 4, 2015

@NobbZ

This comment has been minimized.

Show comment
Hide comment
@NobbZ

NobbZ Feb 16, 2015

ruby and emacs seem to be affected by this too.

Is there a way to install from pullrequest until it is merged and a working version deployed?

NobbZ commented Feb 16, 2015

ruby and emacs seem to be affected by this too.

Is there a way to install from pullrequest until it is merged and a working version deployed?

@tombujok

This comment has been minimized.

Show comment
Hide comment
@tombujok

tombujok Mar 30, 2015

Contributor

Fixed in 1.1.0.
Release status: #266

Contributor

tombujok commented Mar 30, 2015

Fixed in 1.1.0.
Release status: #266

@tombujok tombujok closed this Mar 30, 2015

@masaeedu

This comment has been minimized.

Show comment
Hide comment
@masaeedu

masaeedu Jan 24, 2017

Still seeing a similar issue with the python binary, although I'm using babun 1.2.0

Still seeing a similar issue with the python binary, although I'm using babun 1.2.0

@aeroreyna

This comment has been minimized.

Show comment
Hide comment
@aeroreyna

aeroreyna Feb 27, 2017

Still same problem

Still same problem

@henriklewander

This comment has been minimized.

Show comment
Hide comment
@henriklewander

henriklewander Mar 2, 2017

Same problem for me, but there are no *.sh files, only *.sh.done

henriklewander commented Mar 2, 2017

Same problem for me, but there are no *.sh files, only *.sh.done

@henriklewander

This comment has been minimized.

Show comment
Hide comment
@henriklewander

henriklewander Mar 2, 2017

OK, it seems info in last post #222 actually fixed it:

Run update.bat from the .babun directory after exiting all babun instances and after updating everything it works.

OK, it seems info in last post #222 actually fixed it:

Run update.bat from the .babun directory after exiting all babun instances and after updating everything it works.

@TomyLobo

This comment has been minimized.

Show comment
Hide comment
@TomyLobo

TomyLobo May 7, 2017

To everyone reading the above comment by @henriklewander:
Make absolutely sure you are running this as admin and you are NOT interrupting it!
That's what I did and it fried my babun installation.
Ran without admin rights, noticed the errors, cancelled the installation and everything was gone.
That included mintty and wget and possibly bash.

TomyLobo commented May 7, 2017

To everyone reading the above comment by @henriklewander:
Make absolutely sure you are running this as admin and you are NOT interrupting it!
That's what I did and it fried my babun installation.
Ran without admin rights, noticed the errors, cancelled the installation and everything was gone.
That included mintty and wget and possibly bash.

@axellejamous

This comment has been minimized.

Show comment
Hide comment
@axellejamous

axellejamous May 15, 2017

Executing the update.bat located in .babun did not do anything for me. The only difference is that now instead of just seeing the '127' at the end I also get '130' and a line when i try to run python saying 'zsh: command not found: python'

If you're a noob like me and you're wondering where to find the .babun dir to run update.bat it's in your User's folder

axellejamous commented May 15, 2017

Executing the update.bat located in .babun did not do anything for me. The only difference is that now instead of just seeing the '127' at the end I also get '130' and a line when i try to run python saying 'zsh: command not found: python'

If you're a noob like me and you're wondering where to find the .babun dir to run update.bat it's in your User's folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment