Peter, would you consider re-formatting your disk with recent btrfs-
tools, and using a 3.18+ Linux kernel? I think it's fair to assume that
or try if the problem would be resolved. And that would help you move
forward as well.
Consider how unstable older versions are warned to be:
"WARNING! - Bt
** Changed in: wicd
Status: New => Incomplete
** Changed in: wicd
Importance: Undecided => Medium
** Changed in: wicd
Assignee: (unassigned) => Tom Van Braeckel (tomvanbraeckel)
** Changed in: wicd
Status: Incomplete => Invalid
--
You received this bug
This works fine for me, with wicd on Ubuntu Utopic.
Actually, I don't see why someone (justin parker?) marked wicd as being
affected, because I don't see anyone mentioning wicd in this report, and
neither in https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262 and neither in any of
This works fine for me, with wicd on Ubuntu Utopic.
Actually, I don't see why someone (justin parker?) marked wicd as being
affected, because I don't see anyone mentioning wicd in this report, and
neither in https://bugs.launchpad.net/ubuntu/+source/systemd-
shim/+bug/1184262 and neither in any of
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 Ub
** Changed in: wicd
Milestone: 1.7.3 => 1.7.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1084380
Title:
let the user set timeout and maximum connection attempts
To manage notificatio
