Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #198341 > unrolled thread

Please help with error message

Back to article view | Back to linux.debian.user

Contents

  Please help with error message Rodolfo Medina <rodolfo.medina@gmail.com> - 2018-08-07 09:10 +0200
    Re: Please help with error message Reco <recoverym4n@gmail.com> - 2018-08-07 10:00 +0200
      Re: Please help with error message Rodolfo Medina <rodolfo.medina@gmail.com> - 2018-08-07 10:10 +0200
        Re: Please help with error message Stephan Seitz <stse+debian@fsing.rootsland.net> - 2018-08-07 10:20 +0200
          Re: Please help with error message Rodolfo Medina <rodolfo.medina@gmail.com> - 2018-08-07 10:40 +0200
            Re: Please help with error message deloptes <deloptes@gmail.com> - 2018-08-07 13:20 +0200
              Re: Please help with error message Rodolfo Medina <rodolfo.medina@gmail.com> - 2018-08-07 19:00 +0200
                Re: Please help with error message deloptes <deloptes@gmail.com> - 2018-08-08 00:00 +0200
          Re: Please help with error message mick crane <mick.crane@gmail.com> - 2018-08-07 13:50 +0200
            Re: Please help with error message mick crane <mick.crane@gmail.com> - 2018-08-07 14:10 +0200
          Re: Please help with error message mick crane <mick.crane@gmail.com> - 2018-08-07 13:50 +0200
        Re: Please help with error message Reco <recoverym4n@gmail.com> - 2018-08-07 11:40 +0200
          Re: Please help with error message Stephan Seitz <stse+debian@fsing.rootsland.net> - 2018-08-07 12:10 +0200
            Re: Please help with error message Reco <recoverym4n@gmail.com> - 2018-08-07 12:30 +0200
              Re: Please help with error message Stephan Seitz <stse+debian@fsing.rootsland.net> - 2018-08-07 12:50 +0200
                Re: Please help with error message Reco <recoverym4n@gmail.com> - 2018-08-07 15:20 +0200
              Re: Please help with error message Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-07 14:20 +0200
    Re: Please help with error message Erik Christiansen <dvalin@internode.on.net> - 2018-08-07 10:10 +0200
      Re: Please help with error message Rodolfo Medina <rodolfo.medina@gmail.com> - 2018-08-07 10:20 +0200
    Re: Please help with error message Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2018-08-07 10:10 +0200
      Re: Please help with error message Rodolfo Medina <rodolfo.medina@gmail.com> - 2018-08-07 10:20 +0200

Page 1 of 2  [1] 2  Next page →

#198341 — Please help with error message

Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
trying to install new packages, the following message appears:

# aptitude install alsaplayer-alsa pulseaudio 
pulseaudio is already installed at the requested version (12.0-1)
pulseaudio is already installed at the requested version (12.0-1)
The following NEW packages will be installed:
  alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
Do you want to continue? [Y/n/?] y
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Please help...  I'm not expert.

Thanks in advance,

Rodolfo

[toc] | [next] | [standalone]

#198342

	Hi.

On Tue, Aug 07, 2018 at 09:05:28AM +0200, Rodolfo Medina wrote:
> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
> trying to install new packages, the following message appears:
> 
> # aptitude install alsaplayer-alsa pulseaudio 
> pulseaudio is already installed at the requested version (12.0-1)
> pulseaudio is already installed at the requested version (12.0-1)
> The following NEW packages will be installed:
>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
> Do you want to continue? [Y/n/?] y
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> E: Sub-process /usr/bin/dpkg returned an error code (2)
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> 
> Please help...  I'm not expert.

Your installation lacks /sbin/ldconfig and /sbin/start-stop-daemon from
"libc-bin" and "dpkg" packages respectively. Or root's $PATH lack
"/sbin" somehow.
Either way it's not normal, it's a little wonder that you're able to
boot or run any binary executable.


I'd start fixing this mess by checking root's $PATH:

echo $PATH

It literally should have this value:

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Next I'd try this:

apt-get install --reinstall dpkg libc-bin

Reco

[toc] | [prev] | [next] | [standalone]

#198345

Reco <recoverym4n@gmail.com> writes:

> On Tue, Aug 07, 2018 at 09:05:28AM +0200, Rodolfo Medina wrote:
>> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
>> trying to install new packages, the following message appears:
>> 
>> # aptitude install alsaplayer-alsa pulseaudio 
>> pulseaudio is already installed at the requested version (12.0-1)
>> pulseaudio is already installed at the requested version (12.0-1)
>> The following NEW packages will be installed:
>>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
>> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
>> Do you want to continue? [Y/n/?] y
>> dpkg: warning: 'ldconfig' not found in PATH or not executable
>> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
>> dpkg: error: 2 expected programs not found in PATH or not executable
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
>> E: Sub-process /usr/bin/dpkg returned an error code (2)
>> dpkg: warning: 'ldconfig' not found in PATH or not executable
>> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
>> dpkg: error: 2 expected programs not found in PATH or not executable
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
>> 
>> Please help...  I'm not expert.
>
> Your installation lacks /sbin/ldconfig and /sbin/start-stop-daemon from
> "libc-bin" and "dpkg" packages respectively. Or root's $PATH lack
> "/sbin" somehow.
> Either way it's not normal, it's a little wonder that you're able to
> boot or run any binary executable.
>
>
> I'd start fixing this mess by checking root's $PATH:
>
> echo $PATH
>
> It literally should have this value:
>
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> Next I'd try this:
>
> apt-get install --reinstall dpkg libc-bin


Thanks...  I'm afraid it's bad...:

$ echo $PATH
/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
rodolfo@sda6-acer:~$ su
Password: 
root@sda6-acer:/home/rodolfo# apt-get install --reinstall dpkg libc-bin
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-3.16.0-4-686-pae linux-image-4.11.0-2-686-pae linux-image-4.12.0-1-686-pae linux-image-4.12.0-2-686-pae linux-image-4.9.0-3-686-pae
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/2,952 kB of archives.
After this operation, 0 B of additional disk space will be used.
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)


Thanks,

Rodolfo

[toc] | [prev] | [next] | [standalone]

#198349

[Multipart message — attachments visible in raw view] — view raw

On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:
>$ echo $PATH
>/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>rodolfo@sda6-acer:~$ su
>Password:

You are using testing/unstable, aren’t you?

The su binary was replaced with another one, and now Debian is breaking 
user space again. :-(
Now su alone doesn’t change the path but keeps the user path. You have to 
use „su -”.

  The util-linux implementation of /bin/su is now used, replacing the
  one previously supplied by src:shadow (shipped in login package), and
  bringing Debian in line with other modern distributions. The two
  implementations are very similar but have some minor differences (and
  there might be more that was not yet noticed ofcourse), e.g.

  - new 'su' (with no args, i.e. when preserving the environment) also
    preserves PATH and IFS, while old su would always reset PATH and IFS
    even in 'preserve environment' mode.
  - su '' (empty user string) used to give root, but now returns an error.
  - previously su only had one pam config, but now 'su -' is configured
    separately in /etc/pam.d/su-l

  The first difference is probably the most user visible one. Doing
  plain 'su' is a really bad idea for many reasons, so using 'su -' is
  strongly recommended to always get a newly set up environment similar
  to a normal login. If you want to restore behaviour more similar to
  the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.

Shade and sweet water!
	
	Stephan

-- 
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |

[toc] | [prev] | [next] | [standalone]

#198350

Stephan Seitz <stse+debian@fsing.rootsland.net> writes:

> On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:
>>$ echo $PATH
>>/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>rodolfo@sda6-acer:~$ su
>>Password:
>
> You are using testing/unstable, aren’t you?
>
> The su binary was replaced with another one, and now Debian is breaking user
> space again. :-(
> Now su alone doesn’t change the path but keeps the user path. You have to use
> „su -”.
>
>  The util-linux implementation of /bin/su is now used, replacing the
>  one previously supplied by src:shadow (shipped in login package), and
>  bringing Debian in line with other modern distributions. The two
>  implementations are very similar but have some minor differences (and
>  there might be more that was not yet noticed ofcourse), e.g.
>
>  - new 'su' (with no args, i.e. when preserving the environment) also
>    preserves PATH and IFS, while old su would always reset PATH and IFS
>    even in 'preserve environment' mode.
>  - su '' (empty user string) used to give root, but now returns an error.
>  - previously su only had one pam config, but now 'su -' is configured
>    separately in /etc/pam.d/su-l
>
>  The first difference is probably the most user visible one. Doing
>  plain 'su' is a really bad idea for many reasons, so using 'su -' is
>  strongly recommended to always get a newly set up environment similar
>  to a normal login. If you want to restore behaviour more similar to
>  the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.


Yes, if becoming root with with `su -' the error about what is the present
thread disappears...

Rodolfo

[toc] | [prev] | [next] | [standalone]

#198359

Rodolfo Medina wrote:

> Yes, if becoming root with with `su -' the error about what is the present
> thread disappears...

I guess sudo is always better to use

[toc] | [prev] | [next] | [standalone]

#198420

deloptes <deloptes@gmail.com> writes:

> Rodolfo Medina wrote:
>
>> Yes, if becoming root with with `su -' the error about what is the present
>> thread disappears...
>
> I guess sudo is always better to use


I'd always thought that `su' was Debian's and `sudo' was Ubuntu's...  :-)

Rodolfo

[toc] | [prev] | [next] | [standalone]

#198437

Rodolfo Medina wrote:

> I'd always thought that `su' was Debian's and `sudo' was Ubuntu's...  :-)

No - both are linux and sudo is for the use to be able to use specific
commands. So in general I add sudo rule for my use for bash and it is done.
Alternatively add user to sudo group and you can use the factory rule

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

There is nothing like ubuntu or debian relationship here.

regards

[toc] | [prev] | [next] | [standalone]

#198372

On 2018-08-07 09:18, Stephan Seitz wrote:
> On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:
>> $ echo $PATH
>> /home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>> rodolfo@sda6-acer:~$ su
>> Password:
> 
> You are using testing/unstable, aren’t you?
> 
> The su binary was replaced with another one, and now Debian is
> breaking user space again. :-(
> Now su alone doesn’t change the path but keeps the user path. You have
> to use „su -”.
> 
>  The util-linux implementation of /bin/su is now used, replacing the
>  one previously supplied by src:shadow (shipped in login package), and
>  bringing Debian in line with other modern distributions. The two
>  implementations are very similar but have some minor differences (and
>  there might be more that was not yet noticed ofcourse), e.g.
> 
>  - new 'su' (with no args, i.e. when preserving the environment) also
>    preserves PATH and IFS, while old su would always reset PATH and IFS
>    even in 'preserve environment' mode.
>  - su '' (empty user string) used to give root, but now returns an 
> error.
>  - previously su only had one pam config, but now 'su -' is configured
>    separately in /etc/pam.d/su-l
> 
>  The first difference is probably the most user visible one. Doing
>  plain 'su' is a really bad idea for many reasons, so using 'su -' is
>  strongly recommended to always get a newly set up environment similar
>  to a normal login. If you want to restore behaviour more similar to
>  the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.
> 
> Shade and sweet water!
> 
> 	Stephan

so where is user's path kept these days as it seems I might have set 
user PATH to root PATH ?
and I should probably put it back as it was.
mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#198379

On 2018-08-07 12:47, mick crane wrote:
> On 2018-08-07 09:18, Stephan Seitz wrote:
>> On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:
>>> $ echo $PATH
>>> /home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>> rodolfo@sda6-acer:~$ su
>>> Password:
>> 
>> You are using testing/unstable, aren’t you?
>> 

> so where is user's path kept these days as it seems I might have set
> user PATH to root PATH ?
> and I should probably put it back as it was.
> mick

OK seems set $PATH after su does change root PATH so things are as they 
were

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#198374

On 2018-08-07 09:18, Stephan Seitz wrote:
> On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:
>> $ echo $PATH
>> /home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>> rodolfo@sda6-acer:~$ su
>> Password:
> 
> You are using testing/unstable, aren’t you?
> 
> The su binary was replaced with another one, and now Debian is
> breaking user space again. :-(
> Now su alone doesn’t change the path but keeps the user path. You have
> to use „su -”.
> 
>  The util-linux implementation of /bin/su is now used, replacing the
>  one previously supplied by src:shadow (shipped in login package), and
>  bringing Debian in line with other modern distributions. The two
>  implementations are very similar but have some minor differences (and
>  there might be more that was not yet noticed ofcourse), e.g.
> 
>  - new 'su' (with no args, i.e. when preserving the environment) also
>    preserves PATH and IFS, while old su would always reset PATH and IFS
>    even in 'preserve environment' mode.
>  - su '' (empty user string) used to give root, but now returns an 
> error.
>  - previously su only had one pam config, but now 'su -' is configured
>    separately in /etc/pam.d/su-l
> 
>  The first difference is probably the most user visible one. Doing
>  plain 'su' is a really bad idea for many reasons, so using 'su -' is
>  strongly recommended to always get a newly set up environment similar
>  to a normal login. If you want to restore behaviour more similar to
>  the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.
> 
> Shade and sweet water!
> 
> 	Stephan

Ah, Ok that explains why /sbin wasn't in what I thought was root's $PATH 
when su to find why ldconfig wasn't found for something or other.

cheers

mick






-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#198351

	Hi.

On Tue, Aug 07, 2018 at 10:08:06AM +0200, Rodolfo Medina wrote:
> Reco <recoverym4n@gmail.com> writes:
> 
> > On Tue, Aug 07, 2018 at 09:05:28AM +0200, Rodolfo Medina wrote:
> >> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
> >> trying to install new packages, the following message appears:
> >> 
> >> # aptitude install alsaplayer-alsa pulseaudio 
> >> pulseaudio is already installed at the requested version (12.0-1)
> >> pulseaudio is already installed at the requested version (12.0-1)
> >> The following NEW packages will be installed:
> >>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
> >> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> >> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
> >> Do you want to continue? [Y/n/?] y
> >> dpkg: warning: 'ldconfig' not found in PATH or not executable
> >> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> >> dpkg: error: 2 expected programs not found in PATH or not executable
> >> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> >> E: Sub-process /usr/bin/dpkg returned an error code (2)
> >> dpkg: warning: 'ldconfig' not found in PATH or not executable
> >> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> >> dpkg: error: 2 expected programs not found in PATH or not executable
> >> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> >> 
> >> Please help...  I'm not expert.
> >
> > Your installation lacks /sbin/ldconfig and /sbin/start-stop-daemon from
> > "libc-bin" and "dpkg" packages respectively. Or root's $PATH lack
> > "/sbin" somehow.
> > Either way it's not normal, it's a little wonder that you're able to
> > boot or run any binary executable.
> >
> >
> > I'd start fixing this mess by checking root's $PATH:
> >
> > echo $PATH
> >
> > It literally should have this value:
> >
> > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> >
> > Next I'd try this:
> >
> > apt-get install --reinstall dpkg libc-bin
> 
> 
> Thanks...  I'm afraid it's bad...:

No, it's a honest mistake on your part, not a misconfigured system.


> $ echo $PATH
> /home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> rodolfo@sda6-acer:~$ su

Don't. Do. That. Ever.

'su' without arguments preserves your current environment.
$PATH suffers from this (which is annoying or overall bad in this case),
but unforeseen side effects (including root-owned files in your $HOME)
start with a single X client that you'll run as root.

It's called 'su -'. Use it instead.

Reco

[toc] | [prev] | [next] | [standalone]

#198353

[Multipart message — attachments visible in raw view] — view raw

On Di, Aug 07, 2018 at 12:35:32 +0300, Reco wrote:
>> rodolfo@sda6-acer:~$ su
>Don't. Do. That. Ever.

That’s bullshit. I did it all the time until Debian decided to break 
things.

I never had your mentioned problems.

„su” doesn’t change the working directory. So if you compile software as 
a user you can then type „make install” after su. Now it is simpler to 
compile as root user.

If you need to run an X11 program as root su preserved the DISPLAY 
variable.

Luckily you can switch back to the old behaviour, but this should be the 
default. As Linus would say: „Don’t break user behaviour! Give them an 
option to switch to a new one.”.

Shade and sweet water!

	Stephan

-- 
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |

[toc] | [prev] | [next] | [standalone]

#198354

	Hi.

On Tue, Aug 07, 2018 at 12:01:02PM +0200, Stephan Seitz wrote:
> On Di, Aug 07, 2018 at 12:35:32 +0300, Reco wrote:
> > > rodolfo@sda6-acer:~$ su
> > Don't. Do. That. Ever.
> 
> That’s bullshit. I did it all the time until Debian decided to break things.

It never hurts to check an appropriate manpage *before* calling BS.
In this case:

The su command is used to become another user during a login session.
Invoked without a username, su defaults to becoming the superuser. The
optional argument - may be used to provide an environment similar to
what the user would expect had the user logged in directly.


> I never had your mentioned problems.

Either you have /sbin in your user's path, or you haven't run a single
apt-get all these years. There are other possibilities, of course,
though less flattering.


> „su” doesn’t change the working directory. So if you compile software as a
> user you can then type „make install” after su.

True. But this tidbit does not relate to this particular problem at all.


> Now it is simpler to compile as root user.

It was always 'simpler'. But not 'smarter'.


> If you need to run an X11 program as root su preserved the DISPLAY variable.

And it also preserves $HOME. So any changed configuration file will be
owned by root. Not a big deal if you never try to run the program in
question as your user.


> Luckily you can switch back to the old behaviour, but this should be the
> default.

Care to provide a Debian bug number that you filled on this particular
issue? Because rants on debian-user do not transform to patches by
themselves.


> As Linus would say: „Don’t break user behaviour! Give them an
> option to switch to a new one.”.

A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ.
Two notable behaviour changes without any way to disable them.

Reco

[toc] | [prev] | [next] | [standalone]

#198355

[Multipart message — attachments visible in raw view] — view raw

On Di, Aug 07, 2018 at 01:18:59 +0300, Reco wrote:
>> I never had your mentioned problems.
>Either you have /sbin in your user's path, or you haven't run a single
>apt-get all these years. There are other possibilities, of course,
>though less flattering.

Bullshit again. You didn’t read the thread, did you?
This is new behaviour in testing because Debian switched the source for 
the su binary.

Debian 9:
stse@fsing:~$ echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
stse@fsing:~$ su
Passwort:
root@fsing /home/stse # echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Testing:
[stse@osgiliath]: echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
[stse@osgiliath]: su
Passwort:
osgiliath:/home/stse# echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin

Testing with „ALWAYS_SET_PATH yes” in login.defs:
[stse@osgiliath]: echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
[stse@osgiliath]: su
Passwort:
osgiliath:/home/stse# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

I hope you see the difference.

>> „su” doesn’t change the working directory. So if you compile software 
>> as a user you can then type „make install” after su.
>True. But this tidbit does not relate to this particular problem at all.

It does. Depending on your needs you could use „su” or „su -”.

>> Now it is simpler to compile as root user.
>It was always 'simpler'. But not 'smarter'.

Doesn’t matter, security is always a compromise. If it gets to much work 
it will be reduced.

>> If you need to run an X11 program as root su preserved the DISPLAY 
>> variable.
>And it also preserves $HOME. So any changed configuration file will be
>owned by root. Not a big deal if you never try to run the program in

Only if the file never existed.

>> Luckily you can switch back to the old behaviour, but this should be 
>> the default.
>Care to provide a Debian bug number that you filled on this particular
>issue? Because rants on debian-user do not transform to patches by
>themselves.

Which patches?

>> As Linus would say: „Don’t break user behaviour! Give them an
>> option to switch to a new one.”.
>A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ.
>Two notable behaviour changes without any way to disable them.

Are these security changes? Then Linus permits it if there is no other 
way. By the way, what are these changes that are breaking user space?

Shade and sweet water!

	Stephan

-- 
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |

[toc] | [prev] | [next] | [standalone]

#198398

	Hi.

On Tue, Aug 07, 2018 at 12:45:51PM +0200, Stephan Seitz wrote:
> On Di, Aug 07, 2018 at 01:18:59 +0300, Reco wrote:
> > > I never had your mentioned problems.
> > Either you have /sbin in your user's path, or you haven't run a single
> > apt-get all these years. There are other possibilities, of course,
> > though less flattering.
> 
> Bullshit again. You didn’t read the thread, did you?

Tsk-tsk. Personal attacks on debian-user, and it's not even a Friday.

> This is new behaviour in testing because Debian switched the source for the
> su binary.
> 
> Debian 9:
> stse@fsing:~$ echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> stse@fsing:~$ su
> Passwort:
> root@fsing /home/stse # echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> 
> Testing:
> [stse@osgiliath]: echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
> [stse@osgiliath]: su
> Passwort:
> osgiliath:/home/stse# echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
> 
> Testing with „ALWAYS_SET_PATH yes” in login.defs:
> [stse@osgiliath]: echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
> [stse@osgiliath]: su
> Passwort:
> osgiliath:/home/stse# echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> 
> I hope you see the difference.

So once again Debian aligned its behaviour with RHEL. Not the first
time, not the last. A interesting change, but a minor one.
All of us using 'su -' all these years are not affected.
Users of ordinary 'su' may suffer though.


> 
> > > „su” doesn’t change the working directory. So if you compile
> > > software as a user you can then type „make install” after su.
> > True. But this tidbit does not relate to this particular problem at all.
> 
> It does. Depending on your needs you could use „su” or „su -”.

And you're telling me to read the thread. How exactly apt-get's
behaviour depends on cwd?


> > > If you need to run an X11 program as root su preserved the DISPLAY
> > > variable.
> > And it also preserves $HOME. So any changed configuration file will be
> > owned by root. Not a big deal if you never try to run the program in
> 
> Only if the file never existed.

Or program's developer is trying being smart and writes changed
configuration in a different file followed by rename(2).

> 
> > > Luckily you can switch back to the old behaviour, but this should be
> > > the default.
> > Care to provide a Debian bug number that you filled on this particular
> > issue? Because rants on debian-user do not transform to patches by
> > themselves.
> 
> Which patches?

You're expressing a strong dislike of a certain change, but you're doing
so in a wrong place. An appropriate place for such dislikes is called
bugs.debian.org, and all the changes of behaviour are accepted in the
form of patches to source packages theres.


> > > As Linus would say: „Don’t break user behaviour! Give them an
> > > option to switch to a new one.”.
> > A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ.
> > Two notable behaviour changes without any way to disable them.
> 
> Are these security changes? Then Linus permits it if there is no other way.
> By the way, what are these changes that are breaking user space?

Too lazy to read the changelog, eh?
Fix for CVE-2018-13405 breaks directory permissions.
Fix for CVE-2018-5390 changes TCP stack.

Reco

[toc] | [prev] | [next] | [standalone]

#198385

On Tue, Aug 07, 2018 at 01:18:59PM +0300, Reco wrote:
> On Tue, Aug 07, 2018 at 12:01:02PM +0200, Stephan Seitz wrote:
> > On Di, Aug 07, 2018 at 12:35:32 +0300, Reco wrote:
> > > > rodolfo@sda6-acer:~$ su
> > > Don't. Do. That. Ever.
> > 
> > That’s bullshit. I did it all the time until Debian decided to break things.

> Either you have /sbin in your user's path, or you haven't run a single
> apt-get all these years. There are other possibilities, of course,
> though less flattering.

No, Stephan is correct.  In Debian stable, "su" with no arguments
changes PATH.  It has done so for years.  Decades, if I'm not mistaken.

Here, watch:

wooledg:~$ echo "$PATH"
/home/wooledg/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
wooledg:~$ su
Password: 
root@wooledg:/home/wooledg# echo "$PATH"
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

If testing/unstable has changed this behavior, then that's going to be
a HUGE thing to adjust to.  Has a bug been filed for it yet?

[toc] | [prev] | [next] | [standalone]

#198344

On 07.08.18 09:05, Rodolfo Medina wrote:
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Looks like your root $PATH is mangled. Could you post the output from:

# echo $PATH

Here I have:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

That's consistent with what you read:

> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin
> and /sbin

If setting up a proper root $PATH isn't the simple fix, then we need:

# type ldconfig

Here I have:   ldconfig is /sbin/ldconfig
which will be found in root's PATH.

If "type" returns a full path to ldconfig, then we need the output of:

$ ls -l /sbin/ldconfig     # Or wherever your's finds it.

Does it have execute permission for root?

If that doesn't hit any paydirt, it would be interesting to see if you
have an ldconfig anywhere at all:

$ locate ldconfig

Erik

[toc] | [prev] | [next] | [standalone]

#198348

Erik Christiansen <dvalin@internode.on.net> writes:

> On 07.08.18 09:05, Rodolfo Medina wrote:
>> dpkg: warning: 'ldconfig' not found in PATH or not executable
>> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
>> dpkg: error: 2 expected programs not found in PATH or not executable
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
>
> Looks like your root $PATH is mangled. Could you post the output from:
>
> # echo $PATH
>
> Here I have:
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> That's consistent with what you read:
>
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin
>> and /sbin
>
> If setting up a proper root $PATH isn't the simple fix, then we need:
>
> # type ldconfig
>
> Here I have:   ldconfig is /sbin/ldconfig
> which will be found in root's PATH.

# type ldconfig
bash: type: ldconfig: not found

Thanks

Rodolfo

[toc] | [prev] | [next] | [standalone]

#198346

Rodolfo Medina, Di 07 Aug 2018 09:05:28 CEST:

> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
> trying to install new packages, the following message appears:
> 
> # aptitude install alsaplayer-alsa pulseaudio 
> pulseaudio is already installed at the requested version (12.0-1)
> pulseaudio is already installed at the requested version (12.0-1)
> The following NEW packages will be installed:
>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
> Do you want to continue? [Y/n/?] y
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> E: Sub-process /usr/bin/dpkg returned an error code (2)
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Did you check the value of PATH - as the message suggests?
Did you check that (/sbin/)ldconfig and (/sbin/)start-stop-daemon exist
and they are executable?

> Please help...  I'm not expert.

In that case, you shouldn't use sid...

-- 
Regards
  mks

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web