Ok, these are the results of the test in a notebook where is fairly reproducible the issue described: the infamous Dell M3800 -yes, the same one I talked about a year ago in http://forums.bodhil...upport/?p=94997, although we had observed the Moksha restart issue sporadically on some other computers (desktop and notebooks).
The .e/ directory in all the computers is the custom configuration included in Escuelas Linux 5.0. That custom configuration was created from scratch in the previous 3.2.0 Bodhi version, in which there were no Moksha restart issues in the few computers were we installed it as a pilot, with the idea to deploy it as default when Bodhi 4.0 were released (which we actually did in Escuelas Linux 5.0).
Using the default .e/ included in Escuelas Linux on the M3800. Dragging around Terminology and PcmanFM. In less than a minute, the expected behavior: Moksha restarted.
Closing session. Press CTRL-ALT-F1 to open a Terminal, and from that place, deleted .e/ directory. Exit terminal and ALT-F7 to return to Login Screen, access the system. The default Moksha Desktop appears.
Open PCManFm and dragged it around the screen and... to my disappointment, Mosksha restarts... I was expecting that in the default Moksha configuration this would not happen :-(
So, the same behavior was observed with our custom .e/ config, and with the freshly created .e/ Moksha default config.
Some more info just in case it could be useful: the notebook has installed the nvidia-367 package, but the tests were done using its Intel GPU. I currently use the Intel GPU not only for better battery duration, but because I had a bad experience using the Nvidia GPU using the previous Escuelas Linux 4.5 (based in Bodhi 3.2). In a formal conference I had active the Nvidia one, and found to my dismay that GPU does not work well with an HDMI to VGA adapter: the screen in the laptop showed a slide, while in the projection didn't. I had to turn back and forth on each slide to refresh the external display, and when opening apps, with the Nvidia GPU I had to drag around the app window in order to be make it visible on the projector. Aside from the embarrassment, now I stick with the Intel GPU, which does not have that behavior...
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
02:00.0 3D controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev ff)