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

[Liam Proven]

On 18 November 2013 16:22, Colin Law <clanlaw at googlemail.com> wrote:
> I think the point about making a new bug report using the method
> indicated is so that the logs and such like are made available for
> analysis i the hope of getting further information.  This happens
> occasionally to me also, I am just waiting for it to happen again then
> I will report it.
>
> Not sure what you mean by "no action in 2 months" as there seems to be
> quite a lot of activity on them, one was only reported today


But nothing is crashing or abending. The problem is that the
network-manager daemon is not responding appropriately to system
resume, but it is still running. It is visible in nm-applet but
restarting that does not help. I am guessing it is caused by a kernel
interaction.

When I say "no action", the problem has been reported since August. It
was present before release and still is, unfixed, 2 months later.

I have left a similar comment on the most-subscribed version of this bug, FWIW.


-- 
Liam Proven • Profile: http://lproven.livejournal.com/profile
Email: lproven at cix.co.uk • GMail/G+/Twitter/Flickr/Facebook: lproven
MSN: lproven at hotmail.com • Skype/AIM/Yahoo/LinkedIn: liamproven
Tel: +44 20-8685-0498 • Cell: +44 7939-087884