Bug 19344

Summary:	Unable to use EConnMan for WiFi in E20
Product:	Mageia	Reporter:	aguador <waterbearer54>
Component:	RPM Packages	Assignee:	trem <tremyfr>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageiatools
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description aguador 2016-09-13 01:07:00 CEST

The Enlightenment packages install both connman and E's graphical interface EConnMan. However, one or both of these packages conflicts with Mageia's Network Center in the MCC.

If connman.service is enabled, ethernet connections seem to work fine. However, WiFi connections are impossible to configure with connman running. Network center will save a password, but fail to connect. EConnMan will fail to connect and, likewise, fail to save the password.

It is possible to connect successfully with only the Network Center.

Why is this a big deal? Because the EConnMan provides not only a lightweight, user-friendly interface, but a status indicator on the panel. This is important given the system tray issue reported in the request for a package in the repositories (Bug 19343). I will also note that in the course of two years of using EConnMan it has been stable and functional.

It would be great to find a way to have these two tools live together somehow. However, there are two obvious work arounds: 1) disable the Network Center in E (how?); 2) omit ConnMan from E (and configuring E not to, incorporating a system tray to display the network status.

Although I assume this issue is hardware independent, but the machine in question is an Asus K53S laptop with a Centrino Wireless-N 100 card. I did two installations and, curiously, the first time connman.service was enabled on installation. On the second, I had to manually enable it (and later disable it to have WiFi!).

Rémi Verschelde 2016-09-13 10:00:39 CEST

CC: (none) => mageiatools
Assignee: bugsquad => tremyfr

Comment 1 aguador 2016-10-25 00:01:55 CEST

I found this old thread on switching from drakx-net to Network Manager, but the information seems dated as I have no ~/.net-applet file.

https://forums.mageia.org/en/viewtopic.php?f=25&t=5782

However, drakx-net-applet is installed and presumably running:

$ systemctl status network.service
â network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: enabled)
   Active: active (running) since lun 2016-10-24 19:47:19 CEST; 3h 44min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1616 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/
   CGroup: /system.slice/network.service
           ââ1781 /sbin/ifplugd -I -b -i enp5s0
           ââ1855 /usr/sbin/wpa_supplicant -B -i wlp3s0 -c /etc/wpa_supplicant.c
           ââ1857 /sbin/ifplugd -I -b -i wlp3s0
           ââ2165 dhclient -1 -q -lf /var/lib/dhclient/dhclient--wlp3s0.lease -p

Since drakx-net and connman are in conflict, I am assuming that either drakx-net-applet needs to be excluded from the E package, or instructions added on how to disable it.

At least for testing purposes, would /etc/rc.d/init.d/network need to deleted or can drakx-net-applet now be found and disabled elsewhere?

Since the network is brought up with an init script, am I correct in assuming that not running the script is enough to disable the service and no "systemctl disable" command is needed before enabling the connman service?

Comment 2 aguador 2017-10-13 19:56:37 CEST

As a result of a discussion on the dev list, it is clear that the problem is systemd.networkd which is now on by default (who knew?!?), not net-applet which does not even load in by default in E.

Disabling systemd.networkd and .resolved allows connman to work for wired connections. However, connman, while showing available wifi signals, will not connect, aborting when attempting to enter a password in either econnman or connmanctl. The latter shows simply a "connection failed" followed by "Operation aborted".

Comment 3 aguador 2017-12-31 15:26:15 CET

I have had connman working my Cauldon system (E22), but have still not managed it on Mga6 (E21) where it worked once, but not before or after. See this forum thread: https://forums.mageia.org/en/viewtopic.php?f=25&t=12074

Comment 4 aguador 2020-04-22 09:56:23 CEST

Old bug report and, while the problem continues with E22 and E23, will close for now pending more research. This is likely a wpa_supplicant configuration issue.

Status: NEW => RESOLVED
Resolution: (none) => OLD