Ubuntu MATE 16.04.3
Reproduced the issue in caja using the test case described by tsimonq2.
Installed gvfs/1.28.2-1ubuntu1~16.04.2 (gvfs/xenial-proposed)
Ran killall caja to reload caja and its components.
Attempted to reproduce the bug after reload: could not reproduce the bug.
The proposed pack
Tested the POC against version 2.24.30-1ubuntu1.16.04.2 from xenial-proposed.
Updated package fixes the bug.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Tested the POC against version 2.24.31-1ubuntu1.1 from zesty-proposed.
Updated package fixes the bug.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gt
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1641912
Title:
Please backport two recent-manager patches
To manage
This used to happen to me while running Ubuntu MATE 16.04 Beta 2.
I killed the process, it respawned and resumed eating one of my cores.
I killed it again, it respawned again.
I forgot to kill it, and it somehow ran for a while, then stopped. Haven't seen
that happen in a while now.
--
You recei
