Bug 3521 - WICD network control does not work
Summary: WICD network control does not work
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
Depends on:
Reported: 2011-11-28 14:15 CET by Alberto Girlando
Modified: 2012-12-02 14:31 CET (History)
4 users (show)

See Also:
Source RPM: wicd-1.7.0-4.mga1
Status comment:


Description Alberto Girlando 2011-11-28 14:15:36 CET
I recently installed Mageia on a netbook (replacing Mandriva), and I want to use WICD rather than the distro net-applet, because the wifi is unstable and disconnets often: In these cases WICD is better because immediately reconnects, without action on my side.

So I installed WICD, but in launching I have the following message:
"Could not connect to WICD's D-bus interface. Check the wicd log for error
message."  The log. massage is: An exit code of 1 was returned
from wicd-gtk --no-tray. There are no other messages.

The problem is reproduces always, also in the test installation of Mageia
I am running on VirtualBox
Comment 1 Manuel Hiebel 2011-11-28 19:23:29 CET
If i'am not wrong, there is a daemon to start.
/etc/init.d/wi [tab] start

(or use drakxservices)

Keywords: (none) => NEEDINFO
Source RPM: (none) => wicd

Comment 2 Alberto Girlando 2011-11-29 09:58:35 CET
Yes you are right, I forgot that, but just in the last test on the virtual machine that I made before submitting the bug. Now the test complete goes as that:
the wicd daemon start automatically at login, but that the message "could not connect... etc" appears. When I close, another message telling me that the daemon has shut down appears: "The wicd daemon has shut down. The UI will not work properly until is restarted." By checking the system services, however, the wicd daemon is given as running. If I make a restart by the command line, as you suggests, it gives the daemon as running, then starting wicd-gtk repeat the error.
I also avoided the mageia net-applet to start at login (although having both net-applet and wicd-gtk running did not give conflict in Mandriva) but the error repeats again.
Comment 3 Marja Van Waes 2012-01-19 16:54:04 CET
no maintainer for wicd, cc'ing two committers of the package (in Mdv)

Keywords: NEEDINFO => (none)
CC: (none) => fundawang, marja11, misc

Comment 4 Marja Van Waes 2012-04-13 17:24:43 CEST
Still no maintainer, and the same version of wicd in cauldron.

Shouldn't we drop this package if no one wants to maintain it?

Source RPM: wicd => wicd-1.7.0-4.mga1

Comment 5 Alberto Girlando 2012-04-14 10:42:03 CEST
Probably yes. In addition the latest version of net-applet in mageia works well, and I haven't observed the problems of falling conncetions anymore.
Comment 6 Marja Van Waes 2012-06-10 18:18:18 CEST
There is a request to remove the wicd package: bug 5926
Comment 7 Alberto Girlando 2012-06-11 08:09:29 CEST
(In reply to comment #6)
> There is a request to remove the wicd package: bug 5926
Comment 8 Alberto Girlando 2012-06-11 08:10:56 CEST
(In reply to comment #6)
> There is a request to remove the wicd package: bug 5926

Ok for what is of my concern.
Comment 9 Dave Hodgins 2012-06-12 00:48:59 CEST
In the initial bug report, wicd was mentioned as having been

During qa testing of a recent security update for the wicd
package, a problem was found, which shows that the package
that was included in both Mageia 1 final release, and the
Mageia 2 final release can not work.

As the package also conflicts with the two methods of handling
network configuration that are supported by the Mageia installer,
and requires a lot of manual configuration, that is not handled
by any of our network configuration tools, Mageia will be dropping
the package wicd from Mageia 3, and will not fix problems with
the package in Mageia 1 or 2.

So basically, the answer is don't use it.  If you have already
installed wicd, please uninstall it, so it doesn't cause any
problems with the network tools that do work.

CC: (none) => davidwhodgins

Comment 10 Manuel Hiebel 2012-11-05 16:51:53 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and 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.

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.

Mageia Bugsquad
Comment 11 Manuel Hiebel 2012-12-02 14:31:43 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Mageia Bugsquad

Resolution: (none) => WONTFIX

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