First impression on 14.10
Daniel van Vugt
daniel.van.vugt at canonical.com
Wed Oct 8 01:47:57 UTC 2014
Joseph,
There is another way to gather information from a spinning process less
destructively. Attach gdb to it (from a remote login, 2nd machine
required) and get a backtrace ("bt") that way. I have a script I can
provide you to do that if you open a bug.
As for the keystrokes, I think there's already a bug for that:
https://bugs.launchpad.net/xmir/+bug/1295851
Also, I just noticed you say "14.04". Mir on 14.04 is effectively
unsupported and now very out of date. As it's under heavy development we
can only fix Mir issues on the development release (14.10).
- Daniel
On 08/10/14 06:56, Joseph Rushton Wakeling wrote:
> On 06/10/14 03:36, Daniel van Vugt wrote:> Joseph,
>> We would like to get to the bottom of your high CPU problem and fix
>> it. Can you
>> by any chance force a core dump of the spinning process when it's
>> happening?...
>> Like with:
>> kill -ABRT <process ID>
>>
>> If that fails to generate a problem report, then please log it here:
>> https://bugs.launchpad.net/xmir/+filebug
>
> OK, I've reinstalled ubuntu-desktop-mir on my 14.04 system. No sign of
> any 100% CPU issues so far, so I may have misremembered and the problem
> Cemil observed on 14.10 may be new.
>
> What _does_ happen on 14.04, which I recall as the principal reason I
> uninstalled ubuntu-desktop-mir, is that the system seems quite
> unresponsive to key strokes -- not cripplingly so, but certainly very
> irritatingly so.
More information about the Mir-devel
mailing list