Folks, let me remind you that there is a temporary but helpful solution to the problem which has been given in this forum by James N. I quote him below:
******************** Assuming you use gdm for login, open the file /etc/gdm/PostSession/Default and add the 'killall nautilus' or 'sudo killall nautilus' (I used 'pkill nautilus') before the exit statement in that script. That way nautilus will be killed as your session is exiting, and the cpu will not be eaten up when you are just sitting there at the login screen. Also, switch user / login as someone else / re-login works normally for me now. ******************** By the way, I don't think tracker has something to do with this bug, although I saw that some problems arrived when both trackerd and beagled were started. -- [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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
