nautilus (1:2.20.0-0ubuntu8) hardy; urgency=low * debian/patches/18_disable_signal_handler.patch: - Don't use the logging code signal handler it's buggy and makes nautilus being stuck and eat cpu on crash (LP: #150471)
--- Is there any way this will be ported to Gutsy? I have a hard time believing this is a "low" urgency, as I have the same result in multiple live X/LTSP servers, which slows the powerful machines to a crawl when nautilus misbehaves (daily)... -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs