Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: melmarker on 2018/07/28, 18:53:30
-
Hi,
until now it would be the best of all ideas not to upgrade login and util-linux.
Reasons:
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904775 (kind of solved)
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904832
The second bug is possible introduced by the file move from login to util-linux.
^^^ Icke spare mir ne Übersetzung, einfach Füsse stillhalten - wenn das Kind schon in den Brunnen gefallen ist, einfach abwarten 8)
-
Thank you
----
Danke
-
The fixed packages should hit the mirrors with the next sync cycle
-
Greetings.
I'm not sure if this is related or not, but I think I've been bitten badly by this. After the last apt upgrade (which involved these two packages). I seem to have lost functionality in root (I use su -c rather than sudo), and apt/dpkg seems to be hosed as well. Can anyone help. I've google around and got all sorth of answers involving reconfiguring my $PATH, but nothing seems to work.
Any command I attempt to execute under root gives me something like this;
zshprompt % su -c "rmmod pcspkr"
Password:
bash: rmmod: command not found
or
zsh prompt % vpn-connect
Password:
[!] Error: openvpn is not installed. Install `openvpn` package to continue.
The above is an alias I use for a script to launch my vpn (under root). openvpn is installed (I double checked with apt-cache policy), so I have no idea what's up here. This was actually when I first noticed something was wrong after the update/apgrade.
Also, any new upgrade fails with this message;
zsh prompt % su -c "apt update && apt upgrade"
Password:
Hit:1 http://ftp.debian.org/debian sid InRelease
Hit:2 http://aptosid.com/debian sid InRelease
Hit:3 http://debian.ipacct.com/deb-multimedia unstable InRelease
Hit:4 https://liquorix.net/debian sid InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libapparmor1
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/92.4 kB of archives.
After this operation, 0 B of additional disk space 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
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB
Total disk space freed by localepurge: 0 KiB
E: Sub-process /usr/bin/dpkg returned an error code (2)
su -c "apt update && apt upgrade" 6.67s user 1.22s system 39% cpu 20.027 total
Is this related to the two mentioned packages in the thread title? Because if it is, I'm afraid I won't even be able to perform an upgrade to get the fixed packages when they hit, due to these dpkg errors. Is my system hosed, or is there any way to clean up this mess?
-
congrats - you are bitten by this bug - fortunately it is fixed and will go into the mirrors this or the next dsync.
Please note: su, su $foo works just fine - su - $foo not. There was a few files not moved when moving the su command to it's new place. once you are root you can upgrade and all is fine again. if you are really desperate about this bug you could use the buildd's to upgrade your system. To be true i would recommend to wait a few hours.
-
It's possible to fix this temporarily this way:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-
Is the fix relly in the repos now? Safe to d-u?
-
After this post https://forum.siduction.org/index.php?topic=7282.0 I am not sure if it is fixed now.
-
I made a dist-upgrade with init 3, apt full-upgrade, then apt autoremove, autoclean and init 5 && reboot.
On two computer all works fine, no problems with login.
-
Please can you post your versions of login and util-linux? I do have four machines running siduction (3 64bit and one 32bit) and all do have the problems up to now. Not dramatically problem - fixable by editing PATH variable - but still present. If I remove my "PATH-additions" I am unable to access binaries in /sbin, /usr/sbin and /usr/local/sbin. Here are my versions:
login:
Installiert: 1:4.5-1.1
Installationskandidat: 1:4.5-1.1
Versionstabelle:
*** 1:4.5-1.1 500
500 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
util-linux:
Installiert: 2.32-0.3
Installationskandidat: 2.32-0.3
Versionstabelle:
*** 2.32-0.3 500
500 http://httpredir.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
-
Note the difference between "su" and "su -"
chris@sid:~$ su
Password:
root@sid:/home/chris# echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib/jvm/java-9-oracle/bin:/usr/lib/jvm/java-9-oracle/db/bin
root@sid:/home/chris# exit
exit
chris@sid:~$ su -
Password:
root@sid:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/java-9-oracle/bin:/usr/lib/jvm/java-9-oracle/db/bin
root@sid:~#
-
hmmmmm..... very interesting! Same behaviour here. Additionally username "root" is coloured red when I logged in using "su -". Is this behaviour new intended from now on - two different "root"?? One "less dangerous" and one "more dangerous"?
So one "root for beginners" :o ?
-
man su will tell you about the difference. Has behaviour changed since d-u?
-
yes. Befor d-u all paths are complete when only use "su".
-
@df8oe
apt-cache policy login util-linux
login:
Installiert: 1:4.5-1.1
Installationskandidat: 1:4.5-1.1
Versionstabelle:
*** 1:4.5-1.1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
util-linux:
Installiert: 2.32-0.3
Installationskandidat: 2.32-0.3
Versionstabelle:
*** 2.32-0.3 500
500 https://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
Now i have at boot some acpi errors.
-
I had boot errors like that but the latest kernel 4.17.11-towo.2-siduction-amd64 x86_64 solved that problem. I think it was just the one kernel that caused it.
-
ACPI Errors are gone. All works fine for me.
-
hi,
util-linux (2.32-0.4) unstable; urgency=medium
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.
[...]
So there is no bug or similar!
greetz hendrikL
-
- su '' (empty user string) used to give root, but now returns an error.
I'm not seeing an error using "su" (empty user string), it seems to work, for me, just as it did before the update.
-
"su" without arguments works - but it misses to set the PATHs to
/sbin
/usr/sbin
/usr/local/sbin
Everything else is as before.
Greetings
DF8OE
-
Must have missed this, but I thought using su without the "-" would use the current path? The "-" is required for the default root directory path, like I said must have missed something. :-[
-
"su" without arguments works - but it misses to set the PATHs to
/sbin
/usr/sbin
/usr/local/sbin
Everything else is as before.
Greetings
DF8OE
Confirmed, same here.
-
I think I have the same, but maybe worse...
If I open a konsole, login as root with su, I cannot install wit apt, dpkg or make a DU:
Changelogs werden gelesen... Fertig
Extrahiere Vorlagen aus Paketen: 100%
Vorkonfiguration der Pakete ...
dpkg: Warnung: »ldconfig« wurde im PATH nicht gefunden oder ist nicht ausführbar
dpkg: Warnung: »start-stop-daemon« wurde im PATH nicht gefunden oder ist nicht ausführbar
dpkg: Fehler: 2 erwartete Programme nicht im PATH gefunden oder nicht ausführbar
Beachten Sie: PATH von root sollte normalerweise /usr/local/sbin, /usr/sbin und /sbin enthalten
E: Sub-process /usr/bin/dpkg returned an error code (2)
How can I install the new versions?
-
su -
Edit:fixed typo, added space between su and -!
-
it works with su -
läuft, danke
-
Once again su "to who" normally su is used to become another user that's why a name of which user but you are still in your current path. That's why the " - " is used to tell the shell to use the root path, guess I didn't miss something earlier. ;)