Problem: My Debian (Jessie) Linux laptop has issues with juggling a secondary screen and sleeping at the same time. More specifically, it seems:

It seems if you come out of sleep with a secondary screen connected, even if you put the laptop to sleep with “it” (o.k., not the same “it”, just spec-wise the equivalent FULL HD LCD screen on VGA – being able to easily move the laptop to work in multiple places is kind of the point of having one in the first place), the primary laptop screen seems to remain asleep completely. FN keys to switch primary and secondary screen on laptop have no effect.

If you disconnect the secondary screen, Linux does fall back onto the primary screen, however, “forgets” to turn the backlight on. FN keys to up brightness have no effect

have not found a reliable way avoiding the issue – maybe always disconnecting secondary screen before putting laptop to sleep? If you don’t want to have to do this, or forget, try to use this:

Workaround:

While I could get to the tty shell on secondary screen using CTRL+ALT+F1, but using xrandr --auto gave can't open display.

However, try installing this utility which I found recommended in a different context:

Sleep takes out your primary screen and you are not good at blind starting, finding and typing into your Konsole? Right-click on the desktop of your secondary scree, “Run command”, and issue the same command line.

I seem to be getting a lot of hits on this post for Windows 7 where the globalized language features are still limited to Enterprise and Ultimate SKU (and especially not available in Home and Home basic which most language learning users will work with).

We have conflicting needs for a language technology software environment: diversity, simplicity, quality, manageability. We use of software configuration management tools like TEM. However, we are sitting between an extremely diverse user base (supporting 17 languages) in our unit and a central IT support with a diverse base of units to support.

this is for us a great time saver, compared with maintaining subsets of software on subsets of faculty computers that are as similar to the configuration of the subset software on LRC computers as possible,

while for faculty at the same time a realistic test bed what it will be like to operate LRC computers during class.

We provide access to a subset (which is easily set and edited in the RDG file loaded into Remote Desktop Connection Manager, which is stored on a shared network drive so that we can update the connection files without disruption of faculty access should there be network changes) since we teach faculty not to log out currently logged in users when they try to connect, but rather choose another computer from the subset that is free to not. We exclude computers used in classes where we frequently have high-stakes exams. We also have high-stakes assignments (using Respondus Lockdown browser)

we put a shortcut to the Remote Desktop Connection Manager on the start menu or desktop.

Our computer numbering scheme is simple enough for faculty to navigate – besides, since we connect only to the uniform LRC PC environment, it does not matter.

MSTSC’ing from the remote computer simply fails with a non-descriptive error message.

However, if you get as far as the remote computer login screen, you get a valuable hint: Your 2nd Microsoft account has not been added to the Remote Desktop Users Group (presumably this happens by default when you create your first Microsoft account).

To fix this, log in as admin on your Windows 8 machine (either locally or remotely with an account which is in the Remote Desktop Users Group), windows key+f, “users”, click on “settings”, and use the direct shortcut to “remote desktop users group” to add the user in question (with the Microsoft account email) to the permitted users group.

Adding what I believed was the local account equivalent of the 2nd Microsoft account via desktop / windows-ley x/ “computer management” / “users and groups” to the “remote desktop users group” did not work.