Getting action on a known, identified, reproducible bug in Saucy

[Tom H]

On Mon, Nov 18, 2013 at 4:00 PM, Liam Proven <lproven at gmail.com> wrote:
>
> What can one do?
>
> I have a problem with Saucy, fully updated.
>
> It is not a new problem & it affects others. It is accurately
> described by the following open bugs in Launchpad:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235864
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212199
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1247468
>
> https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121
>
> AFAICS these are all duplicates of the same issue.
>
> I have subscribed to these. There has been no action in 2 months; all
> I am getting is what looks like boilerplate requests to open a *new*
> bug.
>
> Why is this? How will that help when there are at least 4 outstanding
> at the moment?

I _think_ that I've hit this a few times. I didn't think of it as a
bug (I guess that I should!). All that I did was "stop
network-manager" followed by "start network-manager" to reconnect.