There haven't been any more reports of this since the fix above landed in 13.10.0+13.10.20130911.3-0ubuntu1.
Since it was being reported so frequently before the release, I think it's safe to mark this as fixed.
There haven't been any more reports of this since the fix above landed in 13.10.0+ 13.10.20130911. 3-0ubuntu1.
Since it was being reported so frequently before the release, I think it's safe to mark this as fixed.