Arch Linux

fredbezies

Member

Registered: 2011-07-28

Posts: 353

[systemd] Do not upgrade to systemd 232-1 on 32bit installations

I've done this mistake.

I had to chroot using an usb key with last archlinux ISO on it to downgrade to systemd 231-4.

Bug reported : https://bugs.archlinux.org/task/51693

And upstream : https://github.com/systemd/systemd/issues/4575

Last edited by fredbezies (2016-11-06 06:59:06)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,774

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

You might ask yourself why it says it is starting 231.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

fredbezies

Member

Registered: 2011-07-28

Posts: 353

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

You might ask yourself why it says it is starting 231.

Because I did not produce a new kernel image with mkinitcpio. "starting version XXX" message is refreshed with mkinitcpio, or am I wrong ? It is the case since systemd was chosen back in october 2012. At least if I remember well

Downgrading to 231-4 fixes the problem.

Edit : tried with mkinicpio -p linux... Same bug. So it is really a systemd 232-1 bug.

Last edited by fredbezies (2016-11-04 16:15:40)

fredbezies

Member

Registered: 2011-07-28

Posts: 353

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

More infos on this bug. I cannot reproduce it on my toshiba laptop which is a 64 bit installation. 32bit only bug ? Something else ? Will try my main PC, which is a 64 bit installation... Keeping fingers crossed.

Looks like it a 32bit only bug

Last edited by fredbezies (2016-11-04 17:16:34)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

Please edit your first post and choose a title that is less histrionic and actually reflects your issue...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

fredbezies

Member

Registered: 2011-07-28

Posts: 353

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

Edit done. Sorry.

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

(Why oh why did I have to reboot this time.... totally unnecessary and those 20 minutes to fix it were damned precious!)

For anyone else running into this, you can use this workaround in the emergency shell (or downgrade by other means, whatever works best for you):

find /etc/systemd /usr/lib/systemd -name '*.service' | xargs grep -l ^RestrictAddressFamilies | xargs sed -r 's/^RestrictAddressFamilies=(.*)/#RestrictAddressFamilies=\1/' -i

Edit: yes, you're not supposed to modify stuff in /usr/lib/systemd directly ... but systemd isn't supposed to introduce major showstopper bugs like these, and the next package with the fix will overwrite the edits anyway.

Last edited by byte (2016-11-05 09:13:44)

---

1000

fredbezies

Member

Registered: 2011-07-28

Posts: 353

Re: [systemd] Do not upgrade to systemd 232-1 on 32bit installations

(Why oh why did I have to reboot this time.... totally unnecessary and those 20 minutes to fix it were damned precious!)

For anyone else running into this, you can use this workaround in the emergency shell (or downgrade by other means, whatever works best for you):

find /etc/systemd /usr/lib/systemd -name '*.service' | xargs grep -l ^RestrictAddressFamilies | xargs sed -r 's/^RestrictAddressFamilies=(.*)/#RestrictAddressFamilies=\1/' -i

Edit: yes, you're not supposed to modify stuff in /usr/lib/systemd directly ... but systemd isn't supposed to introduce major showstopper bugs like these, and the next package with the fix will overwrite the edits anyway.

Bug reported upstream : https://github.com/systemd/systemd/issues/4575

If you want to follow progress. Adding bug report to first message too.