/bin/udevadm should be exit 0 instead of exit 1

Bug #1646557 reported by Onno
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

if [ "$1" = "trigger" ]; then
echo "some text halt was sinnvolle oder unsinniges zum Abruch
          exit 1
fi

apt-get install rfkill
for example fails to configure

why not in /bin/udevadm end with exit 0 in case of trigger
or settle?

then apt-get install rfkill and 28 other packages can configure

Revision history for this message
Daniel Holbach (dholbach) wrote :

This seems to have nothing to do with the Ubuntu Packaging Guide. Can you file a bug on Ubuntu instead? https://help.ubuntu.com/community/ReportingBugs

Changed in ubuntu-packaging-guide:
status: New → Invalid
Revision history for this message
Onno (schiller-babsi) wrote : Re: [Bug 1646557] Re: /bin/udevadm should be exit 0 instead of exit 1

Ok in lynx I don't see that. You can't move this bug? It is terrible
with no working X oben a bug with lynx.

Am 02.12.2016 um 09:20 schrieb Daniel Holbach:
> This seems to have nothing to do with the Ubuntu Packaging Guide. Can
> you file a bug on Ubuntu instead?
> https://help.ubuntu.com/community/ReportingBugs
>
> ** Changed in: ubuntu-packaging-guide
> Status: New => Invalid
>

--
https://www.amazon.de/dp/B01F6RZJIE
Tel: +4917645531440

Revision history for this message
Daniel Holbach (dholbach) wrote :

So you're saying this is a problem in the rfkill Ubuntu package? Can you try to explain the issue a bit more? Which behaviour are you seeing? What did you expect? Which version of Ubuntu are you using?

Revision history for this message
Onno (schiller-babsi) wrote :

No, I am saying it is a bug in serveral package or in udevadm. All
packages, which call /bin/udevadm trigger or /bin/udevadm settle get a
Sigkill.

Am 03.12.2016 um 09:18 schrieb Daniel Holbach:
> So you're saying this is a problem in the rfkill Ubuntu package? Can you
> try to explain the issue a bit more? Which behaviour are you seeing?
> What did you expect? Which version of Ubuntu are you using?
>

--
https://www.amazon.de/dp/B01F6RZJIE
Tel: +4917645531440

Revision history for this message
Onno (schiller-babsi) wrote :

cat: /etc/udevadm: Datei oder Verzeichnis nicht gefunden
root@thinkpad:/bin# cat /bin/udevadm
#!/bin/sh

if [ "$1" = "trigger" ]; then
    echo "udevadm trigger is not permitted while udev is unconfigured." 1>&2
    exit 1
fi

if [ "$1" = "settle" ]; then
    echo "udevadm settle is not permitted while udev is unconfigured." 1>&2
    exit 1
fi

exec /bin/bash -c "exec -a \"\$0\" /bin/udevadm.upgrade \"\$@\"" "$0" "$@"
root@thinkpad:/bin# cat /etc/issue
Ubuntu 16.04.1 LTS \n \l

root@thinkpad:/bin# apt-get --reinstall install rfkill
E: Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource ist zur Zeit nicht verfügbar)
E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?
root@thinkpad:/bin# cat /bin/udevadm
#!/bin/sh

if [ "$1" = "trigger" ]; then
    echo "udevadm trigger is not permitted while udev is unconfigured." 1>&2
    exit 1
fi

if [ "$1" = "settle" ]; then
    echo "udevadm settle is not permitted while udev is unconfigured." 1>&2
    exit 1
fi

exec /bin/bash -c "exec -a \"\$0\" /bin/udevadm.upgrade \"\$@\"" "$0" "$@"
root@thinkpad:/bin# cat /etc/issue
Ubuntu 16.04.1 LTS \n \l

root@thinkpad:/bin# apt-get --reinstall install rfkill
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
0 aktualisiert, 0 neu installiert, 1 erneut installiert, 0 zu entfernen und 52 nicht aktualisiert.
Es müssen noch 0 B von 8.612 B an Archiven heruntergeladen werden.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
(Lese Datenbank ... 1683175 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../rfkill_0.5-1ubuntu3_amd64.deb ...
Entpacken von rfkill (0.5-1ubuntu3) über (0.5-1ubuntu3) ...
Trigger für man-db (2.7.5-1) werden verarbeitet ...
Trigger für ureadahead (0.100.0-19) werden verarbeitet ...
ureadahead will be reprofiled on next reboot
rfkill (0.5-1ubuntu3) wird eingerichtet ...
udevadm trigger is not permitted while udev is unconfigured.
dpkg: Fehler beim Bearbeiten des Paketes rfkill (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 rfkill
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
localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB

Total disk space freed by localepurge: 0 KiB

E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Onno (schiller-babsi) wrote :

Solution change udevadm or change packages if xenial change udevadm - rfkill is just an example there are more packages, which call /bin/udevadm at dpkg configure ... if you change udevadm, then

cat udevadm
#!/bin/sh

if [ "$1" = "trigger" ]; then
    echo "udevadm trigger is not permitted while udev is unconfigured." 1>&2
    exit 0
fi

if [ "$1" = "settle" ]; then
    echo "udevadm settle is not permitted while udev is unconfigured." 1>&2
    exit 0
fi

exec /bin/bash -c "exec -a \"\$0\" /bin/udevadm.upgrade \"\$@\"" "$0" "$@"

then
dpkg --configure -a
rfkill (0.5-1ubuntu3) wird eingerichtet ...
udevadm trigger is not permitted while udev is unconfigured.

but get configured, because the package didn't get a sigkill

affects: ubuntu-packaging-guide → udev (Ubuntu)
Changed in udev (Ubuntu):
status: Invalid → New
affects: udev (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.