On Thu, Jun 25, 2009 at 01:58:44PM -, stevux wrote:
> Saw the same thing, but i _do_ think this is a pidgin issue, as I see
> the process in status 'TASK_UNINTERRUPTABLE' causing kill not to have
> (the desired) effect.
This means that it is stuck in a kernel call, thus it is a kernel bug.
i
Saw the same thing, but i _do_ think this is a pidgin issue, as I see
the process in status 'TASK_UNINTERRUPTABLE' causing kill not to have
(the desired) effect.
Attaching output for 'ps', lsof and apt-cache.
-
r...@primerib:~# uname -a
Linux primerib 2.6.24-24-generic #1 SMP Fri Jun 5 10:34
On Mon, Jun 15, 2009 at 11:24:27PM -, Leann Ogasawara wrote:
> Reassigning to pidgin.
>
> ** Package changed: linux (Ubuntu) => pidgin (Ubuntu)
>
If it cannot be killed with kill -9, it is NOT a pidgin bug, it is a
kernel bug.
--
HARDY -- Pidgin uses 100% CPU, cannot be killed with kill -9
Reassigning to pidgin.
** Package changed: linux (Ubuntu) => pidgin (Ubuntu)
--
HARDY -- Pidgin uses 100% CPU, cannot be killed with kill -9
https://bugs.launchpad.net/bugs/373273
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
This is not a bug in the linux-meta package, moving to the linux
package.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
HARDY -- Pidgin uses 100% CPU, cannot be killed with kill -9
https://bugs.launchpad.net/bugs/373273
You received this bug notification because you are a member o
