Comment 72 for bug 1748565
Revision history for this message
|
|
#72 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
The "last event is not cmd complete" is in most/all cases a red herring, so please don't focus on that. There's a patch in mainline that will remove it for all valid situations (i.e. when the command completed with command status instead of command complete): https:/
It seems like this issue has probably lots of different bugs mixed into it, all incorrectly attributing themselves to this misleading warning message, when in fact there's something unrelated going wrong. Those that are experiencing issues even after applying the patch I referred to, please open new issues, especially if the "last event is not cmd complete" message goes away for you with the patch. This one can probably be closed since the misleading message should now be gone.