There is a bug on this specific version, it has been fixed already, the ebuild just need a version bump. References: Upstream: https://bugs.launchpad.net/wicd/+bug/993912 Arch: https://bugs.archlinux.org/task/29709 Arch Forum topic discussing the bug: https://bbs.archlinux.org/viewtopic.php?id=140928 I could replicate the log described in the post with my home AP. Since the bug is recognized by upstream and this is just a version bump request, I guess it doesn't need my emerge --info, does it? I'm running ~amd64, btw.
Created attachment 312243 [details] emerge --info I had an emerge --info hanging around from another bug reported yesterday. No harm is done.
(In reply to comment #0) > There is a bug on this specific version, it has been fixed already, the > ebuild just need a version bump. > > References: > Upstream: https://bugs.launchpad.net/wicd/+bug/993912 > Arch: https://bugs.archlinux.org/task/29709 Thanks for the note. I added the patch to 1.7.2.4-r1. + 21 May 2012; Thomas Kahle <tomka@gentoo.org> + +files/wicd-1.7.2.4-fix-dbus-error.patch, +wicd-1.7.2.4-r1.ebuild: + -r1 bump to fix bug 416579
*** Bug 429738 has been marked as a duplicate of this bug. ***