← Back to team overview

dx-packages team mailing list archive

[Bug 760769] Re: Desktop stops responding to all keyboard and mouse clicks

 

*** This bug is a duplicate of bug 762918 ***
    https://bugs.launchpad.net/bugs/762918

Lately, I've been having the same issue. My desktop mouse cursor was
responsive, but the clicks were registering or being detected.

I was able to ssh into this machine when it happened. Doing a top, I
noticed that the load was > 12 ! (Typical load is usually < 2).

Also, there were some ibus related processes hogging up gigabytes of
memory. Bizarre and a little unnerving. I killed  a couple of these ibus
related memory hogs, my system came back to normal.

So, I think the mouse clicks not being detected was a side effect of the
system being under such a heavy load that it couldn't respond in a
timely fashion to mouse clicks.

Also, as a side note, I changed my Google Chrome configuration to
disallow running in the background. It also seemed to be using up a
solid gigabyte+ of memory.

I'm going to try to remove ibus and see if the crazy load issue (I
wasn't really actively doing anything to stress the system at the time)
goes away..

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/760769

Title:
  Desktop stops responding to all keyboard and mouse clicks

Status in Compiz:
  New
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: unity

  I don't have a way to reproduce this yet, but I believe it is
  associated with Alt-tab use.  Every hour or so, my desktop just simply
  stops responding to keyboard clicks or mouse clicks.  Cursor movement
  still works, but the entire desktop is completely unresponsive.  As
  far as I can tell, window output still works (I think my IRC client is
  updating), and the machine still accepts ssh, but that's about it.  I
  have to remotely log in and reboot the machine to get it back.

  Is there a less disruptive way to kill and restart Unity remotely?
  (Assuming of course that it's Unity that's crashing here.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/760769/+subscriptions