Just did some testing again. It's worse. If I have chromium started and chromium IS NOT loading any pages AND it's NOT starting (starting up the program chromium), I get NO freez. I only get the freez when: chromium is loading a page OR I just pressed the button to start chromium and it's starting up. If I press mod4+s during one of this two situations, it freezed always. I can reproduce it how many times I want. Since I know it's about loading pages or staring up, I tried to get a freeze with out chromium starting or loading. I couldn't. So I think it's pretty clearly defined when it freezes and when it doesn't. I hope this helps, to fix the bug.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561105 Title: xsession freez, and later crash when using mod4+s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352-updates/+bug/1561105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
