| Summary: | "Network" advises "the system network services are not compatible with this version" | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ben McMonagle <westel> |
| Component: | RPM Packages | Assignee: | Joseph Wang <joequant> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | isobuild, joequant, mageia, mageiatools, marja11 |
| Version: | Cauldron | Keywords: | 6RC |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | cinnamon | CVE: | |
| Status comment: | |||
| Attachments: |
report.bug.xz
journal.txt |
||
|
Description
Ben McMonagle
2017-03-20 08:37:37 CET
Created attachment 9120 [details]
report.bug.xz
Ben McMonagle
2017-03-20 08:39:12 CET
Keywords:
(none) =>
6sta2
Tbh, I don't know which tool gets started when you click on "Network" in the Cinnamon application menu launcher.
Do you know?
Please attach journal.txt that is the result from running as root, after clicking on "Network",
journalctl -ab > journal.txt
and tell at what time you clicked on "Network"
It might be a red herring, but in report.bug.xz, there are 15 lines with both "network" and "no packages match" in them:
[marja@localhost Downloads]$ xzcat 20533report.bug.xz | grep network | grep "no packages match" | wc -l
15
[marja@localhost Downloads]$
(3 times about netprofile-plugin-network, the others are about 12 different networkmanager-* packages)
CC'ing Cinnamon maintainer and the isobuild and mageiatools maintainer groups.
====> Btw, I don't know whether the March 14 iso that Ben used, contained the meta-task (rpmsrate) changes that are now reverted.... did it? <====Keywords:
(none) =>
NEEDINFO (In reply to Marja van Waes from comment #2) > Tbh, I don't know which tool gets started when you click on "Network" in the > Cinnamon application menu launcher. It's a shortcut to the Network section of the Cinnamon System Settings tool (/usr/share/cinnamon/cinnamon-setting). It's working here in my fully updated cauldron system. You'll get the error message Ben reports if the NetworkManager service isn't running. > ====> Btw, I don't know whether the March 14 iso that Ben used, contained > the meta-task (rpmsrate) changes that are now reverted.... did it? <==== Yes it did. CC:
(none) =>
mageia (In reply to Martin Whitaker from comment #3) Thanks for the answers, Martin. @ Ben Did networking already work, or did you start the "Network" tool to set up your connection? Since, as Martin explained, when NetworkManager.service isn't active & running you'll get the "the system network services are not compatible with this version" error, do please, apart from the requested journalctl output, also attach the output of: systemctl status NetworkManager.service and after that try whether restarting the service solves the problem: systemctl restart NetworkManager.service If it doesn't help, then please run systemctl status NetworkManager.service again and attach its output. <maybe unrelated>systemd thinks, still or again, that network.service failed when it didn't, see bug 11102</maybe unrelated> Created attachment 9131 [details]
journal.txt
(In reply to Marja van Waes from comment #2) > Tbh, I don't know which tool gets started when you click on "Network" in the > Cinnamon application menu launcher. > > Do you know? no > > Please attach journal.txt that is the result from running as root, after > clicking on "Network", > > journalctl -ab > journal.txt > > and tell at what time you clicked on "Network" timestamp : Mar 21 22:14 I tried 3 times but this does not show (In reply to Marja van Waes from comment #4) > > systemctl status NetworkManager.service sorry, lost the output somewhere, said network manager not running > > > and after that try whether restarting the service solves the problem: > > systemctl restart NetworkManager.service that fixes it upon reboot, it has forgotten to restart "NetworkManager.service"
conveniently I can now give: systemctl status NetworkManager.service
$ systemctl status NetworkManager.service
â NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; ven
Active: inactive (dead)
Docs: man:NetworkManager(8)
lines 1-4/4 (END)
(In reply to ben mcmonagle from comment #5) > Created attachment 9131 [details] > journal.txt Mar 21 22:14:06 localhost.localdomain systemd[1]: Starting Network Service... Mar 21 22:14:06 localhost.localdomain systemd[1]: Network Manager is not active. Mar 21 22:14:06 localhost.localdomain systemd[1]: Dependency failed for Network Manager Wait Online. Mar 21 22:14:06 localhost.localdomain systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Mar 21 22:14:06 localhost.localdomain systemd[1]: Started Network Service. (In reply to ben mcmonagle from comment #7) > > $ systemctl status NetworkManager.service > â NetworkManager.service - Network Manager > Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; > ven > Active: inactive (dead) > Docs: man:NetworkManager(8) > lines 1-4/4 (END) To me that looks as if your system doen't want to use NetworkManager.... the above looks exactly like on my system, where drakx-net handles the network cards. If there's anything in the `configureNetwork' step in report.bug.xz that tells whether NetworkManager is allowed or not to control the network card, then I fail to see it :-( What does draknetcenter say, when you click on the configure button and scroll down... is allowing Network Manager to control the interface set to "Automatic" or to something else? (In reply to Marja van Waes from comment #8) > To me that looks as if your system doen't want to use NetworkManager.... the > above looks exactly like on my system, where drakx-net handles the network > cards. I think that you either need to run systemctl enable NetworkManager.service or check the respective "On boot" checkbox in drakxservices (which does the same thing). In my experience you also need to disable network.service, as the two services fight each other for control of the network interface. > What does draknetcenter say, when you click on the configure button and > scroll down... is allowing Network Manager to control the interface set to > "Automatic" or to something else? Again in my experience, it doesn't seem to matter what you set that option to. Maybe someone started to add support for NetworkManager in drakxtools, but never finished the job. valid for Mageia-6-rc-i586-DVD.iso DATE.txt: Fri Apr 7 23:11:51 CEST 2017 maybe remove this launcher?
Ben McMonagle
2017-04-10 09:34:24 CEST
Keywords:
(none) =>
6RC (In reply to Marja van Waes from comment #8) > > What does draknetcenter say, when you click on the configure button and > scroll down... is allowing Network Manager to control the interface set to > "Automatic" or to something else? automatic (sorry for delay in reply) (In reply to Martin Whitaker from comment #3) > (In reply to Marja van Waes from comment #2) > > Tbh, I don't know which tool gets started when you click on "Network" in the > > Cinnamon application menu launcher. > > It's a shortcut to the Network section of the Cinnamon System Settings tool > (/usr/share/cinnamon/cinnamon-setting). It's working here in my fully > updated cauldron system. You'll get the error message Ben reports if the > NetworkManager service isn't running. > Assigning to the Cinnamon maintainer. Maybe, if that tool can't work with drakx-net and as long as we don't use NetworkManager by default in Cinnamon, it is possible and OK to replace the "the system network services are not compatible with this version" message with e.g. the following?: "This tool needs a running NetworkManager.service". Assignee:
bugsquad =>
joequant long resolved Resolution:
(none) =>
FIXED |