Bug 1148402 - wicd-gtk "ERROR: Unable to communicate with wicd daemon."
Summary: wicd-gtk "ERROR: Unable to communicate with wicd daemon."
Keywords:
Status: CLOSED DUPLICATE of bug 1074315
Alias: None
Product: Fedora
Classification: Fedora
Component: wicd
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-01 11:50 UTC by Rob
Modified: 2014-11-25 16:17 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-11-25 16:17:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
systemctl output (4.11 KB, text/plain)
2014-10-01 11:50 UTC, Rob
no flags Details

Description Rob 2014-10-01 11:50:59 UTC
Created attachment 943026 [details]
systemctl output

Description of problem:

I recently updated to Fedora 20 (from 19) using the fedup network process and all seems to be ok with the exception of wicd-gtk, which throws the error below:

> wicd-gtk
Has notifications support True
ERROR: Unable to communicate with wicd daemon.

Be sure the wicd service is enabled and running:
systemctl enable wicd.service
systemctl start wicd.service

NOTE: NetworkManager and other network device daemons must be disabled.
>


NetworkManager has been completely uninstalled and the system rebooted. systemctl shows wicd as active and running and the network is active. But wicd-gtk still cannot connect. Nothing that I can see in /var/log/wicd/wicd.log and/or /var/log/messages or dmesg shows any error that suggests anything out of the ordinary. Systemctl output reports: "abrt-watch-log -F BUG: WARNING: ... recursive locking..." 

Version-Release number of selected component (if applicable):

Linux xxxx 3.16.3-200.fc20.x86_64 #1 SMP Wed Sep 17 22:34:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

wicd Version:

rpm -qi wicd-common
Name : wicd-common
Version : 1.7.2.4
Release : 11.fc20
Architecture: noarch
Install Date: Tue 30 Sep 2014 11:26:18 AM BST
Group : System Environment/Base
Size : 1535161
License : GPLv2+
Signature : RSA/SHA256, Wed 02 Jul 2014 08:01:24 PM BST, Key ID 2eb161fa246110c1
Source RPM : wicd-1.7.2.4-11.fc20.src.rpm
Build Date : Wed 02 Jul 2014 04:48:41 PM BST
Build Host : arm02-builder15.arm.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http wicd.sourceforge.net/
Summary : Wicd common files
Description :
This package provides the main wicd daemon and the wicd-cli front-end.

rpm -qi wicd-gtk
Name : wicd-gtk
Version : 1.7.2.4
Release : 11.fc20
Architecture: noarch
Install Date: Tue 30 Sep 2014 11:26:20 AM BST
Group : Applications/Internet
Size : 555605
License : GPLv2+
Signature : RSA/SHA256, Wed 02 Jul 2014 07:59:31 PM BST, Key ID 2eb161fa246110c1
Source RPM : wicd-1.7.2.4-11.fc20.src.rpm
Build Date : Wed 02 Jul 2014 04:48:41 PM BST
Build Host : arm02-builder15.arm.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http wicd.sourceforge.net/
Summary : GTK+ client for wicd
Description :
Client program for wicd that uses a GTK+ interface.



How reproducible:
Repeatable - every time.

Steps to Reproduce:
1. Stop & disable network.service via systemctl 
2. Uninstall NetworkManager
3. Enable & start wicd.service
4. Start wicd-gtk

Actual results:

Has notifications support True
ERROR: Unable to communicate with wicd daemon.

Be sure the wicd service is enabled and running:
    systemctl enable wicd.service
    systemctl start wicd.service

NOTE: NetworkManager and other network device daemons must be disabled.


Expected results:

No error and tray icon.


Additional info:

Comment 1 jan 2014-10-04 21:20:59 UTC
I've had this problem for a week now, after doing an update of F20. wicd-gtk no longer is able to talk to the running daemon, wicd-curses works fine.

Comment 2 Vagabond 2014-10-15 23:46:22 UTC
I have this problem as well. wicd-curses and wicd-cli works fine and I am able to successfully connect with them.
It looks like /usr/share/wicd/gtk/wicd-client.py is the culprit. At the end is
a check to see if "wireless" was found in the dbus interface. If not then the error that is posted appears. The problem is that the dbus interface hasn't been checked at that point so the error always appears.

Getting rid of that check ( so that just main(sys.argv) is called ) works for me.

Comment 3 Jerther 2014-11-22 17:42:26 UTC
Removing the check fixed the problem for me too.

Comment 4 David Cantrell 2014-11-25 16:17:12 UTC

*** This bug has been marked as a duplicate of bug 1074315 ***


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