Osmc-no-secure-path edited!

fzinken · 21 January 2017 15:35

That should not have broken your PATH.

As already mentioned you are most likely faster my making a backup and start from scratch.
Alternative post the URL from this two commands and we can try to help you

history | paste-log
grab-logs -A

Schnitte · 21 January 2017 15:37

Well I’ll just try to restart from scratch with my modification of skin.confluence - and keep checking if sudo ldconfig still works.

Probably I will find there it goes wrong… I hope so.

Thanks until now.

Schnitte · 21 January 2017 15:42

http://paste.osmc.io/eqozinokap

http://paste.osmc.io/ajonuxokiy

After having reboot once and started from scratch the sudo ldconfig doesn’t work…

Schnitte · 21 January 2017 15:47

When trying to fx. “sudo apt-get dist-upgrade”

I’m getting this error.
E: Sub-process /usr/bin/dpkg returned an error code (2)

It works when I do sudo -i first, but this should be necessary? Should it?

fzinken · 21 January 2017 15:53

I am confused here, did you already do a clean reinstall and sudo ldconfig is not working on that?

Schnitte · 21 January 2017 15:54

It worked first time, but didn’t after reboot. The only thing I had installed was zsh.

fzinken · 21 January 2017 15:56

That might be the source of your problem with a none working PATH, why did you install it?

Schnitte · 21 January 2017 15:57

Why is zsh a non working path? “Getting oh-my-zsh to work in Ubuntu · GitHub”

Because I really hate to work in bash?

sam_nazarko · 21 January 2017 15:58

That is the problem.

I mentioned in an earlier post that you should check which shell is being used when you run ./build, and I specifically mentioned:

I’m not sure why you would choose to omit this, it’s quite important.

zsh is a second class citizen on Debian. If you want to use it, then you need to set PATH manually yourself. OSMC will only fully and officially support a BusyBox shell interpreter and Bash

fzinken · 21 January 2017 15:58

github.com/osmc/osmc

osmc-no-secure-path breaks sudo in clean environments

opened 01:07AM - 16 Jul 16 UTC

dekimsey

Empty shell paths aren't being reset correctly when using sudo. This is the resu…lt of the osmc-no-secure-path commit 62596e56c7bcdb959dcf2e54e616241921a2b659. From the commit message, it is unclear to me as to why disabling secure-path was set. I don't believe it should be disabled as the secure-path on jessie looks quite sane. I found this while debugging an issue with `apt-get` I ran into when using Ansible on the box. This was deemed to be a [distribution problem](https://github.com/ansible/ansible/issues/1679) on the OS. Some reference output : _error except from attempt to apt-get install a package using ansible_ ``` dpkg: warning: 'ldconfig' not found in PATH or not executable. dpkg: warning: 'start-stop-daemon' not found in PATH or not executable. ``` _current path_ ``` dekimsey@living-room:~/ansible$ ansible all -i localhost, -b -m shell -a 'echo $PATH' localhost | SUCCESS | rc=0 >> /usr/local/bin:/usr/bin:/bin:/usr/games ``` _after re-enabling securepath_ ``` dekimsey@living-room:~/ansible$ ansible all -i localhost, -b -m shell -a 'echo $PATH' localhost | SUCCESS | rc=0 >> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ```

Schnitte · 21 January 2017 16:01

Then I guess I neither won’t be able to download wiringPi??

sam_nazarko · 21 January 2017 16:01

You can set up wiringPi just fine using the default shell.

Schnitte · 21 January 2017 16:02

Well so I won’t be able to have zsh installed on my Pi?

sam_nazarko · 21 January 2017 16:03

You can use zsh on your Pi but then you must configure PATH manually.

It’s not officially supported however and may cause breakage.

Schnitte · 21 January 2017 16:05

I really doesn’t understand what that freaking “PATH” is? Is it an abbreviation for something?

joakim_s · 21 January 2017 16:14

Simply put, it’s an enviroment variable that lets the system search certain folders for executables.