Not marking duplicate, the other bug is likely a specific crash, the log
handler is broken and we should also fix that, confirming the issue
** This bug is no longer a duplicate of bug 150471
[Gutsy] high processor activity after logging out and then logging in again
** Changed in: nautilus (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: Invalid => Triaged
--
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
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
