Skip to main content ↑ ↓
Topic: iwd + dinit prevent shutdown (Read 668 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

iwd + dinit prevent shutdown

https://github.com/davmac314/dinit/issues/124

dinit + iwd prevent my system from shutdown
i never try it with other init system. but i've try it with openrc and everything works fine.
i attached a screenshot, bellow.
i can how ever, do un-graceful shutdown by using emergency shutdown sysreq.

Note: if i start iwd manually `dinitctl start iwd` then try to kill it `dinitctl stop iwd`, it stuck and i cant switch to back google chrome.
it frooze my DE.

https://github.com/davmac314/dinit/issues/124

Re: iwd + dinit prevent shutdown

Reply #1 –
Quote from: boku – on
i can how ever, do un-graceful shutdown by using emergency shutdown sysreq.
I would try with loginctl poweroff.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: iwd + dinit prevent shutdown

Reply #3 –
(Note that this turned out to be due to a kernel bug. See the issue in Dinit's github linked above for details).

Re: iwd + dinit prevent shutdown

Reply #4 –
Quote from: davmac – on
(Note that this turned out to be due to a kernel bug. See the issue in Dinit's github linked above for details).
This is not a kernel bug.
I would think about the content of the line 1326.
https://github.com/davmac314/dinit/blob/master/src/dinitctl.cc
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "
 

Re: iwd + dinit prevent shutdown

Reply #5 –
Quote from: lq – on
This is not a kernel bug.
I would think about the content of the line 1326.
https://github.com/davmac314/dinit/blob/master/src/dinitctl.cc

I don't know what you mean. This issue was caused by a kernel bug (a null pointer dereference in the wireless stack), which was reported in the kernel log (as seen by the `dmesg` command). It's not clear to me what you think the significance of line 1326 is nor what you believe is wrong with it.