OK...after installing debug version of gnome-session (from Chris Coulson's PPA) and looking at the syslog generated, there is something that occurs on gnome-session process due to an interaction between gnome-session and amarok (amarokcollectionscanner)
Maybe gnome-session got overloaded due to abusive request from amarok and got overflowed in some way. I decided to turn off amarok (exit the program from the task manager pannel) from night-to-day lock-screen and definitely this bug didn't happen again, everything is OK, gnome-session is working in a correct manner. Here are attached my syslog and xsession-errors logs. They are tar.gz'ed since syslog are almost a mega or two ;) Thanks again for the support! Raine ** Attachment added: "tar.gz'ed syslog and xsession-errors log files" http://launchpadlibrarian.net/24001932/bug-341730.tar.gz -- gnome-session process goes berzek in cpu after a night-to-day unlock screen https://bugs.launchpad.net/bugs/341730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
