Bug 699116
Summary: | wicd shuts down when started by systemd | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Guillaume Pasquet <etenil> |
Component: | wicd | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | andrey.henneberg, bug, dcantrell, dswegen, fabio.dieguez, me, oxyfodu, perchibald |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | wicd-1.7.0-9.fc15 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-23 04:34:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Guillaume Pasquet
2011-04-23 09:15:54 UTC
Can you try this as a /lib/systemd/system/wicd.service unit file: [Unit] Description=Wicd a wireless and wired network manager for Linux Requires=syslog.target After=syslog.target Conflicts=NetworkManager-wait-online.service NetworkManager.service [Service] Type=dbus BusName=org.wicd.daemon ExecStart=/usr/sbin/wicd ExecStop=/usr/sbin/wicd -k [Install] WantedBy=multi-user.target Then try 'systemctl start wicd.servce' and see if wicd starts up. does not work daemon starts but connection fails wicd 1.7.0 systemd 26-8 I'm currently building a test update to fix this problem. Looks the systemd unit file for wicd was basically broken. I fixed that up so that systemd properly starts wicd and controls it. I think you'll have to enable it if you want it started up at each boot. I modeled it after the NetworkManager unit files. Also missing was the D-Bus path or property or bus name definition file, whatever D-Bus calls it. Again, modeled after NetworkManager so I think the wicd package fulfills the need there. Lastly, the D-Bus connection policy for wicd was not exactly ideal. wicd seems to encourage you to set up a group specifically for users who can control wicd. I changed this to allow users who meet the at_console requirement for D-Bus to have full control of wicd. I'm open to suggestions here. If you guys think a special wicd group is better, I'll do that. But I think at_console is sufficient. There will be a notice here once I push the test update. Please give it a try and let me know if wicd successfully starts, if the clients can connect (wicd-gtk and wicd-curses), and so on. The work here will flow in to a wicd update for F-16 as the package there is identical to the one in F-15 right now, but it won't go out in the main release for F-16. wicd-1.7.0-9.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/wicd-1.7.0-9.fc15 Package wicd-1.7.0-9.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wicd-1.7.0-9.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/wicd-1.7.0-9.fc15 then log in and leave karma (feedback). it works thanks *** Bug 723554 has been marked as a duplicate of this bug. *** *** Bug 712936 has been marked as a duplicate of this bug. *** wicd-1.7.0-9.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. It seems like the x86_64 package from Fedora 16 repository is still affected by this bug. Was it supposed to be updated aswell? I'm running the installed version is 1.7.0-9.fc16. I've followed the instructions in this report, but the problem persists. There's also no update candidate on updates-testing. |