Andrei, et al -- ...and then Andrei Borzenkov said... % % 17.02.2019 3:52, David T-G ??????????: % > % > ...and then Carlos E. R. said... % > % % > % On 16/02/2019 13.05, David T-G wrote: % > % % > % > I tried this, and it failed because a fatal signal was delivered. Hmmph. % > % > Apparently my NetworkManager is suddenly broken. % > % % > % The exact output you got here would be interesting. % > % > From my laptop to a screen grab to a thumb drive to my tablet to you :-) % > ... % > davidtg@wench:~> sudo rcnetwork restart % > Job for NetworkManager.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. % > davidtg@wench:~> % > davidtg@wench:~> % > davidtg@wench:~> sudo systemctl status NetworkManager.service ... % > Process: 9722 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=dumped, signal=BUS) % > Main PID: 9722 (code=dumped, signal=BUS) % > % > Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=7/BUS % % You may try check some external conditions that could result in SUGBUS % (like no space on FS/RAM pressure): % % https://stackoverflow.com/questions/2089167/debugging-sigbus-on-x86-linux Thanks for the link! I'll give that a shot, although the obvious ones look fine and the problem persists through multiple reboots. % % It may be faulty hardware as well. Or it may be mixed repositories % resulting in errors during execution. I'm more hopeful of the latter, for sure! But hardware has to go at some point, so I'll also check with a thumb drive boot. % % In any case you should be able to switch to wicked while you % troubleshoot NM problem. Oooh! Yes, please! Sooooo... How? TIA again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org