After upgrading to Ubuntu 16.04, whenever atom is started from within a virtualenv, there is either no display of the new instance or a heavily pixelated depiction. Some times, the entire screen of my workstation freezes (besides mouse cursor movement) to the point that I have to hard reboot the machine.
The problem seems to be say, non-deterministic cause after some reboots it occasionally goes away, atom executes correctly and I am able to work from within the virtualenv.
Has anybody encountered this issue?
edit - update: After leaving the instance hanging with the pixalated display, I got the following error in my command line from where I tried to run atom after activating my virtualenv
(venv_p35) > /usr/bin/atom: line 115: 3995 Killed nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1 App load time: 388ms
p.s. here is an example of what I am talking about