Description of problem: I installed Mageia 4.1 with Enlightenment as desktop choice (i.e. in the installer, at the desktop choice screen I chose "Custom Desktop", then I selected E17 instead of KDE, without changing anything at the individual package level. In this configuration EConnMan is not present. I also haven't been able to find a rpm package which contains it. It is however configured to be loaded by E17 (as a module), and by default the EConnMan gadget is present in the task (which doesn't work, because the module does not exist). I also noticed that this is cause for frequent crashes of E17 at login. Removing the EConnMan moddule from E17 also makes the crashes go away. Steps to Reproduce: 1. Install Mageia with Enlightenment Desktop instead of KDE 2. Login to E17 3. EConnMan gadget is not working: exclamation mark is displayed, clicking on Settings will trigger an error message, that EConnMan is missing. There is a forum post on this topic as well: https://forums.mageia.org/en/viewtopic.php?f=7&t=5161 If EConnMan is not supposed to be used in Mageia, then default configuration of E17 should be changed so that the module is not loaded by default (maybe also removed from the list?) and the gadget should not be in the taskbar. Reproducible: Steps to Reproduce:
Assignee: bugsquad => tremyfr
I've requested the push of python-efl (updated to 1.11) and task-enlightenment (add python-efl, dbus-x11 and econnman). It should fix this issue on cauldron.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Is it EconnMan (the module) that is missing or connman the network service? Having recently attempted an installation of Enlightenment in Mageia 5 I had the E module, EConnMann (the graphical module to configure the network service) . . . which crashed because it could not find connman (the network service itself). This is actually normal because Enlightenment is installed via a network connection which needs a network service enabled and running to connect and download install files. This is usually handled by Network Manager (although I do not remember with certainty from my recent installation except that it is NOT connman). After completing installation, whatever network service was running during installation will still be enabled in systemd, so even if connman is installed, it will not start. To solve, make sure you have connman installed, then you simply disable the active network service and enable connman. So: 1) Verify that connman is installed with with the MCC or open Terminology or another terminal and check as follows: # rpm -qa | grep 'connman' 2) Having installed or verified the presence of connman, determine which network service is running: $ systemctl list-units -t service 3) Disable the running network service (NetworkManager used as an example): $ systemctl disable NetworkManager.service 4) Enable connman: $ systemctl enable connman.service On reboot the network should be active and EConnMan running normally. If E is the only desktop you are running, you can then, of course, uninstall the other network manager simply to have a cleaner installation.
CC: (none) => waterbearer54
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD