Fixed in wicd 1.7.3
** Changed in: wicd
Importance: Undecided => High
** Changed in: wicd
Status: New => Fix Released
** Changed in: wicd
Assignee: (unassigned) => Tom Van Braeckel (tomvanbraeckel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Branch linked: lp:ubuntu/wicd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this bug go to:
https://bugs.launchpad.net/wicd/+
This bug was fixed in the package wicd - 1.7.2.4-4.1ubuntu1
---
wicd (1.7.2.4-4.1ubuntu1) trusty; urgency=low
* debian/patches/34-fix-resolv.conf_backup-restore-broken-link.patch:
allow wicd-daemon to start when /etc/resolv.conf is a broken link
(LP: #1132529)
-- chilic...@
I've taken the fix provide by tommy in bug #1193856 and prepared a merge
request for the ubuntu package and the upstream code:
https://code.launchpad.net/~chilicuil/ubuntu/trusty/wicd/fix-1132529/+merge/197998
https://code.launchpad.net/~chilicuil/wicd/wicd/+merge/198057
Hopefully one will get ac
** Also affects: wicd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this bug go to:
** Branch linked: lp:~chilicuil/ubuntu/trusty/wicd/fix-1132529
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this bug go to:
htt
@Piotr Darzyn: please do not change bug status without a CLEAR
explanation of why you did so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifica
Bug status reset to Confirmed. Importance set to Medium per a request
in #ubuntu-bugs on IRC.
** Changed in: wicd (Ubuntu)
Importance: Undecided => Medium
** Changed in: wicd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of
Hey guys I have the same versions as Martin does (with Xubuntu).
Is it possible to release the patch provided in this duplicate?
https://bugs.launchpad.net/wicd/+bug/1193856
It makes no sense if everybody has to fix it himself ...
--
You received this bug notification because you are a member o
I'm on Kubuntu 13.10, and ran into the same problem, with wicd installed
from the Saucy repositories. The fix in comment #19 worked.
The bug status was changed to "Fix committed" -- how does the process
work on this one? Will this be fixed in the next Ubuntu release, or
backported to the current o
I ran into the same bug on Xubuntu 13.10.
However I did not post because of that (apparently it'll probably be
fixed in the next release). I post because I believe you should also
make wicd give more information if and when it runs into critical
problems (for example with this backup). Critical pr
** Changed in: wicd (Ubuntu)
Status: Confirmed => New
** Changed in: wicd (Ubuntu)
Status: New => Incomplete
** Changed in: wicd (Ubuntu)
Status: Incomplete => Opinion
** Changed in: wicd (Ubuntu)
Status: Opinion => Invalid
** Changed in: wicd (Ubuntu)
Status:
Same problem, same solution as #Liam, thanks guys.
Linux Mint 15 Olivia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this bug
Same problem, same solution as @Liam, Gracias. Ubuntu 13.04 Linux
3.8.0-30-generic x86_64 GNU/Linux.
Awesome wm, not that it matters...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Hi, i'm on Linux Mint 15 and this worked for me :
rm /etc/resolv.conf
ln -s /run/resolvconf/resolv.conf
rm /var/lib/wicd/resolv.conf.orig
ln -s /run/resolvconf/resolv.conf /var/lib/wicd/resolv.conf.orig
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Robert patch "check for existing backup of symlink to resolv.conf"
listed above worked like a charm for me!
Xubuntu raring 13.04 - freshly switched from network-manager to wicd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@Liam Worked like a charm. Nice find on the broken link. Darn relative
paths!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this
@Liam thanks, your steps worked for me too. Looks like the tray icon is
gone for good now since 13.04 release ditched the systray completely out
and a new appindicator would be needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@Liam worked for me to, @bmarsh I am only using WPA and don't have any
problem, I hoped you found a fix for your problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wic
@ Liam: thanks, that worked for me, but I don't see the tray icon (I
already checked and it is enabled on the startup programs)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't sta
bmarsh, your patch provided in comment #19 fixed it for me. I did this:
rm /etc/resolv.conf
ln -s /run/resolvconf/resolv.conf
rm /var/lib/wicd/resolv.conf.orig
ln -s /run/resolvconf/resolv.conf /var/lib/wicd/resolv.conf.orig
then, launching wicd with "sudo service wicd start" work
Guys, but look what error you get. Have you tried to delete that file
(/var/lib/wicd/resolv.conf.orig)? The problem is that when you start
wicd, it tryis to copy file from a broken symlink and wicd-daemon
crashes leaving some traces in /var/lib/wicd/. Try to remove that backup
file, make sure links
Getting same error:
Traceback (most recent call last):
File "/usr/share/wicd/daemon/wicd-daemon.py", line 1859, in
main(sys.argv)
File "/usr/share/wicd/daemon/wicd-daemon.py", line 1708, in main
os.symlink(dest, backup_location)
OSError: [Errno 17] File exists
Raring release 64-bit v
Getting closer maybe.
1) I made the symlink change mentioned above but that didn't fix
anything.
2) In checking with the daemon file, I went to /var/lib/wicd and found
a similar symlink:
resolv.conf.orig --> ../run/resolvconf/resolv.conf
3) I changed that symlink to be absolute and the da
Having same wicd problem (dbus error - - logfile is empty) on
13.04-i386 with all updates applied. The symlink change didn't help at
all. And 13.04 has now been released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
ok, getting really weird again ... kernel panic and everything hanging
... it did that before my patch as well. not responsive at all, I give
up for now, after all raring is still in development.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
seems the client also hangs when started, at least it is infinitely
searching for connections
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifica
Got the wicd daemon running, but having other problems now, so far here
is a patch to get the daemon started, its a one liner
ERROR:dbus.proxies:Introspect error on :1.12:/org/wicd/daemon:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply. Possible causes i
Robert,
I applied the patch and still have those issues. 12.10 works fine
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications abou
Having the exact same Problem as Noah, on fresh installed raring (dev
branch), same arch
replacing symlinks did not fix it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start w
Is there an easy way to apply this patch to my machine?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this bug go to:
https://bu
noahc@trex:~$ sudo wicd
[sudo] password for noahc:
Traceback (most recent call last):
File "/usr/share/wicd/daemon/wicd-daemon.py", line 1859, in
main(sys.argv)
File "/usr/share/wicd/daemon/wicd-daemon.py", line 1708, in main
os.symlink(dest, backup_location)
OSError: [Errno 17] File
What happens when you run "sudo wicd"? You should get some traceback that way.
Does /run/resolvconf/resolv.conf exist on your system? Try this:
ls -lah /etc/resolv.conf
cat /etc/resolv.conf
And check what was resolv.conf before with:
ls -lah /etc/resolv.conf.backup
--
You received this bug not
I am unable to get the above solution to work:
noahc@trex:~$ lsb_release -rd
Description:Ubuntu Raring Ringtail (development branch)
Release:13.04
noahc@trex:~$ apt-cache policy wicd
wicd:
Installed: 1.7.2.4-4
Candidate: 1.7.2.4-4
Version table:
*** 1.7.2.4-4 0
500 http:
Ok- well, at least that is a temporary solution until the upstream
developers and/or Ubuntu developers can come up with a permanent
solution as I don't want to mess with the program's working too much
(I'm not a developer by trade). :P
--
You received this bug notification because you are a membe
The attachment "rmbackup.patch" of this bug report has been identified
as being a patch. The ubuntu-reviewers team has been subscribed to the
bug report so that they can review the patch. In the event that this is
in fact not a patch you can resolve this situation by removing the tag
'patch' from
Evan, that probalby works but I think it's not the right solution. I
started this bug as related to wicd but now it seems to me that it's
related to ubuntu or resolvconf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
How about this patch? I remved the symlink/backup thing althogether.
** Patch added: "rmbackup.patch"
https://bugs.launchpad.net/ubuntu/+source/wicd/+bug/1132529/+attachment/3545409/+files/rmbackup.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, just updating link fixed it for me. Long story short, just run this
2 commands:
sudo mv /etc/resolv.conf /etc/resolv.conf.backup
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
Here are some more details about this issue.
When I started wicd as root (not with init script) I got IO e
Atlantic, would just update the sym link? I am also experiencing this
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't start wicd daemon
To manage notifications about this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wicd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132529
Title:
Can't
The problem is that /etc/resolv.conf is a link to
../run/resolvconf/resolv.conf and when wicd makes the backup, relative
path ../run/... doesn't exist.
The fix is to change /etc/resolv.conf to point to
/run/resolvconf/resolv.conf (this is absolute path).
--
You received this bug notification bec
42 matches
Mail list logo
