Bug 7873 - NM does not work as installed in KDE
Summary: NM does not work as installed in KDE
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 7557
  Show dependency treegraph
 
Reported: 2012-10-22 18:39 CEST by Frank Griffin
Modified: 2019-02-20 00:20 CET (History)
3 users (show)

See Also:
Source RPM: networkmanager plasma-network-management
CVE:
Status comment:


Attachments
screenshot of kcm entry for networkmanager (75.70 KB, image/png)
2012-10-29 19:21 CET, John Balcaen
Details

Description Frank Griffin 2012-10-22 18:39:48 CEST
If you do a fresh install on a laptop with wireless, selecting both KDE and GNOME, and go through adding the wireless interface with drakconnect, selecting Use NetworkManager, the interface will not start.

Apparently, NM requires extra configuration to be able to control a wireless interface.  Without it, you get syslog messages like the following:

**********************************************************************
Oct 22 07:15:19 localhost draknetcenter[10231]: modified file /etc/sysconfig/network-scripts/ifcfg-eth1
Oct 22 07:15:19 localhost draknetcenter[10231]: modified file /etc/sysconfig/network-scripts/ifcfg-eth1
Oct 22 07:15:19 localhost draknetcenter[10231]: changed mode of /etc/sysconfig/network-scripts/ifcfg-eth1 to 755
Oct 22 07:15:19 localhost draknetcenter[10231]: written eth1 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth1
Oct 22 07:15:19 localhost draknetcenter[10231]: running: /sbin/ifdown eth1 daemon
Oct 22 07:15:19 localhost draknetcenter[10231]: running: /sbin/ifup eth1 daemon
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ...
Oct 22 07:15:20 localhost NetworkManager[999]: <warn> failed to allocate link cache: (-10) Operation not supported
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh:     error: Missing SSID
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-eth1.
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ...
Oct 22 07:15:20 localhost NetworkManager[999]: <warn> failed to allocate link cache: (-10) Operation not supported
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh:     error: Missing SSID
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ...
Oct 22 07:15:20 localhost NetworkManager[999]: <warn> failed to allocate link cache: (-10) Operation not supported
Oct 22 07:15:20 localhost NetworkManager[999]:    ifcfg-rh:     error: Missing SSID
*********************************************************************

Supposedly, the plasma-applet-networkmanagement package is required for this, but NM does not require it and KDE does not install it by default.  Even so, after installing it, the above messages continue to appear, and I can't find any way in the KDE system settings to execute it.  The closest I can come is in "Information Sources", where NM is already selected.

However, if you log into the GNOME 3 desktop, and use its applet to start the interface, you get messages like the following:

***********************************************************************
Oct 22 07:18:52 localhost NetworkManager[999]:    ifcfg-rh:     read connection 'NETGEAR-2.4-G'
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) starting connection 'NETGEAR-2.4-G'
Oct 22 07:18:52 localhost NetworkManager[999]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Oct 22 07:18:52 localhost NetworkManager[999]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1/wireless): connection 'NETGEAR-2.4-G' requires no security.  No secrets needed.
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Config: added 'ssid' value 'NETGEAR-2.4-G'
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Config: added 'scan_ssid' value '1'
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Config: added 'key_mgmt' value 'NONE'
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Oct 22 07:18:52 localhost NetworkManager[999]: <info> Config: set interface ap_scan to 1
Oct 22 07:18:52 localhost NetworkManager[999]: <info> (eth1): supplicant interface state: inactive -> scanning
Oct 22 07:18:53 localhost wpa_supplicant[1210]: ioctl[SIOCSIWAP]: Device or resource busy
Oct 22 07:18:53 localhost NetworkManager[999]: <info> (eth1): supplicant interface state: scanning -> associating
Oct 22 07:18:53 localhost NetworkManager[999]: <info> (eth1): supplicant interface state: associating -> completed
Oct 22 07:18:53 localhost NetworkManager[999]: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'NETGEAR-2.4-G'.
Oct 22 07:18:53 localhost NetworkManager[999]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 22 07:18:53 localhost NetworkManager[999]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Oct 22 07:18:53 localhost NetworkManager[999]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 22 07:18:53 localhost NetworkManager[999]: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 22 07:18:53 localhost NetworkManager[999]: <info> dhclient started with pid 15016
Oct 22 07:18:53 localhost NetworkManager[999]: <info> Activation (eth1) Beginning IP6 addrconf.
Oct 22 07:18:53 localhost avahi-daemon[1027]: Withdrawing address record for fe80::c2f8:daff:fe85:7188 on eth1.
Oct 22 07:18:53 localhost NetworkManager[999]: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
***********************************************************************

and the interface comes up just fine.

I'm sure there are several arguments to be put forth, such as "we don't enable NM by default through drakconnect so why should plasma-applet-networkmanagement be installed by default", but the bottom line is that for our default desktop and what is rapidly becoming our default network management tool, this doesn't work out-of-the-box, and if it can even work at all from KDE, it is anything but obvious how to get it to work.

Marking this as "major" (at least), if only based on the number of bugs here and countless man-months of dialog in them of the type "NM doesn't work with my wireless" and "of course it must, it works fine with mine".  IMO it should be a release-blocker.
Comment 1 Frank Griffin 2012-10-25 22:25:03 CEST
I have found that the plasma-network-management applet is installed by urpmi, but not activated.  To activate it, you  must explicitly add it using the KDE desktop GUI.  

If you do that, and then execute it and select the wireless interface and specify NM, the needed files are created and the interface comes up.

At least in my opinion, it is not acceptable to expect garden-variety users to figure this out.  Especially when GNOME handles it all without a murmur.
Comment 2 Manuel Hiebel 2012-10-26 22:32:27 CEST
something that you can do kde team *?

CC: (none) => balcaen.john, lmenut
Assignee: bugsquad => nicolas.lecureuil
Source RPM: NetworkManager => networkmanager plasma-network-management

Comment 3 John Balcaen 2012-10-27 05:31:51 CEST
Adding by default plasma-network-management will pull by default networkmanager.
Since nm is not the default on mageia, i don't see while we should enforce the installation of it.
Also there's not « need » to activate the plasma-applet in the taskbar to configure your network with nm, you can simply configure it using systemsettings (the kcm files are packaged with the plasma applet).

So in short until nm is the default i don't think it's a good idea to enforce the use of nm on every user(for the record i'm not against nm since i'm using it since mga1 without problem but *without* the ifcfg module using the native keyfile module instead)
Comment 4 Frank Griffin 2012-10-27 15:34:24 CEST
Well, my idea was rather the reverse: have NM pull in plasma-network-management if KDE is installed and add it to the default panel.  I agree that until NM is the default, it shouldn't be pulled in for everyone.

>Also there's not « need » to activate the plasma-applet in the taskbar to
configure your network with nm, you can simply configure it using
systemsettings (the kcm files are packaged with the plasma applet).

Could you give the details of this, please ?  I couldn't find anything in the systemsettings network dialog that had anything to do with configuring NM.

Further, several bug reports have indicated that if NM is started at bootup, it interferes with wireless even if the interface indicates that it is not controlled by NM.  So, if NM is installed, but is not the default, netapplet may need to do the NM configuration even if NM is not responsible for the interface.
Comment 5 Frank Griffin 2012-10-27 20:21:53 CEST
I suppose the lynchpin issue here is whether having NM running in the system still interferes with non-NM wireless interfaces.

If it does not, then the applet isn't needed.

If it does, then if NM is going to be active (and it will get re-enabled for every refresh of the package), it has to be used for the wireless in KDE.

Manuel, since you have a tracker bug for NM, is there an easy way to post a single comment to all of the tracked bugs to see if manually installing the applet, launching it, and configuring the wireless interface that way makes NM work for everyone who reported problems with NM and wireless ?

If that's true, then all we would need is a way for drakconnect, maybe nmcli wifi connect, to do the configuration the applet does if the user checks the NM box, and we could just add something to the errata to say that if you have NM installed because of GNOME, you may have to configure your wireless as NM-controlled (or activate it for the first time in GNOME) to get it to work.
Comment 6 Manuel Hiebel 2012-10-27 22:07:17 CEST
(In reply to comment #5)
> Manuel, since you have a tracker bug for NM, is there an easy way to post a
> single comment to all of the tracked bugs to see if manually installing the
> applet, launching it, and configuring the wireless interface that way makes NM
> work for everyone who reported problems with NM and wireless ?

yep as with all other search or list of bugs: 

https://bugs.mageia.org/buglist.cgi?bug_id=7317,7249,6675,1138,7358,6936,3782,7551,865,3928,7498,7873&tweak=1

Blocks: (none) => 7557

Comment 7 Frank Griffin 2012-10-27 22:20:57 CEST
(In reply to comment #6)
> (In reply to comment #5)
> > Manuel, since you have a tracker bug for NM, is there an easy way to post a
> > single comment to all of the tracked bugs to see if manually installing the
> > applet, launching it, and configuring the wireless interface that way makes NM
> > work for everyone who reported problems with NM and wireless ?
> 
> yep as with all other search or list of bugs: 
> 
> https://bugs.mageia.org/buglist.cgi?bug_id=7317,7249,6675,1138,7358,6936,3782,7551,865,3928,7498,7873&tweak=1

Yes, I knew about getting the list so that I could post separately to each.  I was wondering if there was some magic way to post the same comment to a list of bugs, like Claire or Marja did with the mass ping.

If not, I'll do the posts separately.
Comment 8 Manuel Hiebel 2012-10-27 22:24:50 CEST
check all of them and add a comment at the below of the page :)
Comment 9 John Balcaen 2012-10-28 09:49:42 CET
(In reply to comment #4)
> Well, my idea was rather the reverse: have NM pull in plasma-network-management
> if KDE is installed and add it to the default panel.  I agree that until NM is
> the default, it shouldn't be pulled in for everyone.
Hum this solution is not really easy with urpmi (or i'm probably missing some functionnality in urpmi) & the only current workaround i can find so far would be something like that :
1) nm is installed by default
2) nm requiring a « gui » configuration tool (something virtualprovides such as nm-gui) which would be also provided by the plasma-applet
3) have kde requiring the plasma-applet so we can « prefer » the kde app instead of the gtk's one.


> >Also there's not « need » to activate the plasma-applet in the taskbar to
> configure your network with nm, you can simply configure it using
> systemsettings (the kcm files are packaged with the plasma applet).
> 
> Could you give the details of this, please ?  I couldn't find anything in the
> systemsettings network dialog that had anything to do with configuring NM.

Systemsettings/Networkconnections
In this section you can add/remove/edit your nm configuration.

> 
> Further, several bug reports have indicated that if NM is started at bootup, it
> interferes with wireless even if the interface indicates that it is not
> controlled by NM. 
NM was not started by default initially but i guess it was changed due to the switch either to systemd by default or to gnome3 which requires nm.

> So, if NM is installed, but is not the default, netapplet
> may need to do the NM configuration even if NM is not responsible for the
> interface.
not easy i guess :/
the installer should probably drop a configuration file to disable the wifi interface in the networkmanager configuration.
Something for blino or tv i guess :p
Comment 10 Frank Griffin 2012-10-29 13:10:23 CET
>Systemsettings/Networkconnections
In this section you can add/remove/edit your nm configuration

This makes no mention of NM.  Are you sure this writes the same NM conf files that the plasma applet does ?  If KDE isn't using NM by default, why would it ?
Comment 11 Frank Griffin 2012-10-29 13:24:05 CET
Please refer to the discussion in bug#7873 and bug#2160 and see if your problems with NM go away if you either allow GNOME (if you have it installed) to activate it or you install plasma-network-management under KDE, add it to your panel, and use it to configure your SSID.

For NM to handle wireless correctly, it needs to create SSID-specific files of its own by parsing the ifcfg files produced by drakconnect.  GNOME's nm-applet does this automatically, since it has no option to *not* use NM, but since NM isn't the default yet for other desktops, it doesn't happen automatically there.  

You'll need to install NM and let it start, and recreate your wireless interface with drakconnect specifying "Allow NM to control this interface".

Please test and post your results, as whether NM works for all the chips involved when it's properly configured will have a significant impact on how it needs to be handled for non-GNOME desktops in MGA3.
Comment 12 Frank Griffin 2012-10-29 13:29:07 CET
>Systemsettings/Networkconnections
In this section you can add/remove/edit your nm configuration

This makes no mention of NM.  Are you sure this writes the same NM conf files that the plasma applet does ?  If KDE isn't using NM by default, why would it ?
Comment 13 Frank Griffin 2012-10-29 13:30:06 CET
(In reply to comment #8)
> check all of them and add a comment at the below of the page :)

Cool.  I learn something new every day, thanks.
Comment 14 John Balcaen 2012-10-29 14:38:48 CET
(In reply to comment #12)
> >Systemsettings/Networkconnections
> In this section you can add/remove/edit your nm configuration
> 
> This makes no mention of NM.  Are you sure this writes the same NM conf files
> that the plasma applet does ? 
i am because i'm using it & it's showing my nm configuration network.
I'll add a screenshot later once i' get back @ home.
The plasma applet is just an applet. When you're editing the configuration files you simply popup the adequat kcm entries.
And yes there's no mention of nm in this kcm configuration tool.
Comment 15 John Balcaen 2012-10-29 19:21:12 CET
Created attachment 3009 [details]
screenshot of kcm entry for networkmanager

Attached is the screenshot of the kcm entry from systemsettings.
You can trigger it from the console using for example:
kcmshell4 kcm_networkmanagement

Regards,
Comment 16 Frank Griffin 2012-10-29 19:29:10 CET
OK, thanks John.  Originally, when I opened Network, it displayed my SSID in the Wireless tab.  I selected it and clicked Edit, and all of the details were correct.

Does the fact that the interface appeared at all mean that the NM files have been written ?  If not, will it write them when I close it even though I haven't modified anything ?
Comment 17 John Balcaen 2012-10-30 00:44:54 CET
(In reply to comment #16)
> Does the fact that the interface appeared at all mean that the NM files have
> been written ? 
Yes.

> If not, will it write them when I close it even though I
> haven't modified anything ?
Well it should not (i hope) wrote anything at all if nothing was changed.
Comment 18 Marja Van Waes 2015-03-31 23:35:11 CEST
@ Frank

Is this bug still valid?

Please close if it isn't

Thanks :-)

CC: (none) => marja11
Keywords: (none) => NEEDINFO

Comment 19 Frank Griffin 2015-04-01 01:49:40 CEST
Well, installing KDE still doesn't install the plasma network applet by default, so NM won't work under KDE by default.  In addition, NM is not systemd-enabled even if GNOME is installed, 

The original impetus for this bug report was that net-applet wasn't working for a lot of wireless devices, so there was really no option except NM, and if you were using KDE, NM wouldn't work without the plasma applet.  

If net-applet has been fixed to the extent that people don't need NM, then I guess it doesn't matter that NM doesn't work under KDE.  But since NM doesn't seem to get enabled even if installed, the fact that pulling in the plasma network applet also pulls in NM shouldn't really matter, but I still think it would be nice if KDE users had some way out-of-the-box to use NM if they want to.
Comment 20 Marja Van Waes 2015-04-01 07:06:21 CEST
Thx for the feedback, Frank

Keywords: NEEDINFO => (none)

Samuel Verschelde 2016-08-25 16:24:06 CEST

Assignee: mageia => kde

Luc Menut 2016-08-25 16:42:24 CEST

CC: lmenut => (none)

Comment 21 Nicolas Lécureuil 2017-04-17 13:19:44 CEST
is it still valid ? ( i have not tested ).

CC: (none) => mageia

Comment 22 Frank Griffin 2017-04-17 14:33:30 CEST
As far as I know this is still valid.  All my installs install every desktop, including GNOME, but NM is not enabled (I'm not even sure if it gets installed, as I have post-install scripts that install it).  I still have to manually install the plasma applet.

It's been a while since I did a fresh install, but my recollection is that I had to use nmcli to activate the wifi initially.
Comment 23 Frank Griffin 2017-04-25 17:59:40 CEST
I've just done a new fresh install, and here's how it stands in current cauldron:

Specifying all desktops in Custom, NM *is* installed but it is *not* enabled, so it doesn't start at boot.  plasma-applet-nm is not installed, but if you start NM and install the applet it automatically detects and connects the wifi.

I'm guessing that GNOME detects that NM isn't started and starts it automatically.

I think that standard policy is to enable any service when it's installed, so I'm not sure why that doesn't happen with NM.

Also, if NM is installed, it would make sense to pull in plasma-applet-nm to make it accessible to plasma.  If NM isn't running, the applet will tell you that if you attempt to use it.
Comment 24 Frank Griffin 2019-02-20 00:20:14 CET
Where are we with this ?  NM is more mainstream MGA than it was when I entered this.  What is the preferred relationship between NM and Plasma, considering that they are supposed to coexist now ?

Note You need to log in before you can comment on or make changes to this bug.