stakanov, et al -- ...and then stakanov said... % % In data sabato 16 febbraio 2019 03:39:20 CET, David T-G ha scritto: % > % > II have had some problems with network when I go from one location ... % > and even failing to find my RJ45 interface at all. Where did it go?!? % > I used to have a little wifi icon in my KDE notification area but it % > has also gone away. ... % > :-D % I have another user with a PC (running up to now network manager) that had the % very same problem after a recent update. It would be very useful if you could % recall which update exactly you did perform prior to the issue. I haven't approved any updates recently, in fact. I just checked my Software Updates notification and it reports (as well as that I am offline, of course) that my last check was 13+ days ago. I did install new Xerox printer software and add a new printer through YaST, but that's been up and happy for at least a week and maybe two or three. The days have run together with all of the tax return prep (including printing) we've been doing. % That said: I am convinced hat you have already network manager running, but % that it does not "see" any of the network cards. Hmmmmm... I'm not so sure of that now. Read on... % You can try to do the following: % sudo ifup % on a terminal should tell you if your network is still managed by network This does, indeed, tell me that the network is managed by NetworkManager.service and skips. So far, so good. % manager. I suppose that you have tried to restart the network before. % (terminal: sudo rcnetwork restart) I tried this, and it failed because a fatal signal was delivered. Hmmph. Apparently my NetworkManager is suddenly broken. From there I tried systemctl status and it apparently did activate, giving me a PID in a process tree, but that PID is no longer running. I also ran journalctl -xe and got tons of output including a complaint about the lock file for a recently-deceased printer and something about a DBus error because of no reply related to my audio card ... I think. I didn't notice anything about NetworkManager, though. But it doesn't appear to be running and ifconfig still shows me no IP on wlan0 and no RJ45 instance at all. % BTW: if I am not mistaken you are going to find a file called /etc/netconfig. % Please let me know if that file is present. Thank you. It is, indeed. My devices are all jus dashes, though. Thanks 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

Carlos, et al -- ...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 ifup <13>Feb 16 19:43:26 davidtg: Network is managed by 'NetworkManager.service' -> skipping davidtg@wench:~> davidtg@wench:~> 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 Ï NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Sat 2019-02-16 19:43:35 EST; 2s ago 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 Feb 16 19:43:35 wench systemd[1]: Failed to start Network Manager. Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Unit entered failed state. Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart. Feb 16 19:43:35 wench systemd[1]: Stopped Network Manager. Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Start request repeated too quickly. Feb 16 19:43:35 wench systemd[1]: Failed to start Network Manager. Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Unit entered failed state. Feb 16 19:43:35 wench systemd[1]: NetworkManager.service: Failed with result 'start-limit'. davidtg@wench:~> % % For example, I get this on a working *15.0* machine with NetworkManager % % ??? NetworkManager.service - Network Manager ... % CGroup: /system.slice/NetworkManager.service % ?????? 1598 /usr/sbin/NetworkManager --no-daemon % ??????16854 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlan1.pid -lf /var/lib/NetworkManager/dhclient-...-wlan1.lease -cf /var/lib/NetworkManager/dhclient-wlan1.conf w> [snip] Curiously, I recall getting a PID tree earlier, but this time I didn't. Not sure what's different... Thanks for the debugging help. Send more :-) 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

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

Carlos, et al -- ...and then Carlos E. R. said... % % On 18/02/2019 13.32, David T-G wrote: % % > 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. I got a chance to do this; WiFi came right up and RJ45 worked ... once I swapped out the dead cable! But it still didn't work back under 42.3. % % You could attach the result of this: % % zypper lr --details > repolist.txt % % and we can investigate your list of repositories. % % (note: file attach better than pasting result in an email because it has % long lines that would wrap making reading difficult) Understood, although at least my message source wouldn't do that :-) It's attached. % % % % > % In any case you should be able to switch to wicked while you % > % troubleshoot NM problem. % > % > Oooh! Yes, please! Sooooo... How? % % Just fire up yast, network module, there should be a button to switch % mode. Then fill up the form... Oh! Son of a gun... The last time I tried it, which was under the GUI, I'm sure I didn't see that as an option. Now, under the CLI text version, I see Wicked. OK; I'll try it and report. % % Of course, wicked is complicated if you move the machine to another WiFi % Access Point, because IIRC you have to redo the configuration. But, in % your case... Yeah; something is better than nothing, and I almost never go anywhere else anyway. % % -- % Cheers / Saludos, Thanks again & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

On 18/02/2019 17.07, David T-G wrote:

Carlos, et al --

...and then Carlos E. R. said... % % On 18/02/2019 13.32, David T-G wrote: % % > 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.

I got a chance to do this; WiFi came right up and RJ45 worked ... once I swapped out the dead cable! But it still didn't work back under 42.3.

% % You could attach the result of this: % % zypper lr --details > repolist.txt % % and we can investigate your list of repositories. % % (note: file attach better than pasting result in an email because it has % long lines that would wrap making reading difficult)

Understood, although at least my message source wouldn't do that :-) It's attached.

The only /suspicious/ repo is "network", not knowing why you added it or when. Everything else seems right to me. I notice that you use an adobe repo. Is that for acroread? you will need to do some hoolahop jumping on Leap 15.0. Ask later, there is an old thread that explains, perhaps a wiki page. I have to do the same thing on this computer.

% > % In any case you should be able to switch to wicked while you % > % troubleshoot NM problem. % > % > Oooh! Yes, please! Sooooo... How? % % Just fire up yast, network module, there should be a button to switch % mode. Then fill up the form...

Oh! Son of a gun... The last time I tried it, which was under the GUI, I'm sure I didn't see that as an option. Now, under the CLI text version, I see Wicked. OK; I'll try it and report.

% % Of course, wicked is complicated if you move the machine to another WiFi % Access Point, because IIRC you have to redo the configuration. But, in % your case...

Yeah; something is better than nothing, and I almost never go anywhere else anyway.

Right. [...] I see your other post. Curious! nm -> wicked -> nm and works! For a while. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Carlos, et al -- ...and then Carlos E. R. said... % % On 17/02/2019 01.52, David T-G wrote: % > ... % > From my laptop to a screen grab to a thumb drive to my tablet to you :-) % > ... % > 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) % % Oh :-( Yeah. That certainly explains why I have no network. Now to figure out why I have no NetworkManager... % ... % > Curiously, I recall getting a PID tree earlier, but this time I didn't. % > Not sure what's different... % % That in your case NetworkManager crashes and dumps core (signal=BUS). I No, I realize that :-) I'm not sure what's different on MY machine from run to run. % have never seen this. This is not something that can be solved with % configuration files that has gone lost, this is more serious. % % See Andrei Borzenkov advice. Yep. Thanks. % % As you can see, the exact error text is crucial. Well, yeah... Of course. Knowing what to type to get to the error is pretty good, too, and I'm just fumbling around here! :-) Thanks 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