Comment 155 for bug 1297849
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #155 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
If you need to do anything more than 'killall nm-applet' and starting nm-applet again, then it's quite unlikely that this patch really fixes the issue -- I did notice this issue *once* on my system yesterday and logged off and back in, from there the agent could be detected. This doesn't seem to me like either shell version detection or something related to upgrading (given I wasn't doing an upgrade at all).
Since then, I've tried to kill off my VPN or terminate it normally, neither method works to reproduce the problem: I can immediately start it again, and I do get the authentication dialog and I am able to reconnect normally.
Anyone can add further information on this bug, or can verify that without the patch, stopping nm-applet and restarting it will make things work again, or can make things work without needing to reboot (only restarting nm-applet, with the patch applied)?
There's still a branch for 0.9.10, 0.9.8, etc. It would be best if someone was to report the bug upstream or otherwise contact upstream developers to get a review of the patch.