Bug 75662

I use LibreOffice 4.x on Windows 7 Professional for x86-32 on incubus, my primary desktop computer at my residence.  When I am at my residence, I use the video console of incubus.  At my employer’s shop, I use a different desktop computer, succubus, which runs Windows 8 Enterprise RTM for x86-32.  incubus and succubus are both on the same Hamachi Virtual LAN.  When I am at my employer’s shop, I use succubus as an RDP client to control incubus over the Hamachi Virtual LAN.  If only LibreOffice Writer 4.x is running when I switch between using the video console and RDP session, LibreOffice Writer 4.x is still functional after the switch.  However, if LibreOffice Base 4.x is running when I switch between using the video console and RDP session, then all of LibreOffice 4.x hangs after the switch:  the windows of the LibreOffice 4.x applications stop responding, which forces me to terminate LibreOffice 4.x .  I usually have only LibreOffice Writer 4.x running in addition to LibreOffice Base 4.x when switching between the video console and RDP session:  I know that LibreOffice Writer 4.x hangs in addition to LibreOffice Base 4.x if LibreOffice Base 4.x is running when switching but I do not know if other LibreOffice 4.x applications will hang too if LibreOffice Base 4.x is running when switching.  I expect that the other LibreOffice 4.x applications will hang too.  Of those applications, I expect that Calc is most likely for me to leave running in addition to Writer and Base.

I need all of LibreOffice 4.x to remain functional when switching between the video console and RDP session even if LibreOffice Base 4.x is running when switching.  IIRC, I did not have this problem with LibreOffice 3.x but I cannot currently test with LibreOffice 3.x because I no longer have LibreOffice 3.x installed on incubus.

I have some other configuration details that may not be relevant but I will mention them in case they are relevant:

1. Both my residence and my employer’s shop use a Wired LAN (Ethernet over twisted pair cable) using only Ethernet switches, no Ethernet hubs.  Both sites have a Wireless LAN too but both incubus and succubus use only the Wired LAN.  At both sites, the physical Wired LAN and the physical Wireless LAN are a single logical Virtual LAN using a MAC bridge.  At both sites, the wired gateway runs DD-WRT and uses Telus ADSL service for its uplink (to the WAN).

2. Both incubus and succubus are dual-head with a 21-inch Trinitron CRT computer display at 1600×1200 at 85 Hz on the left and a 27-inch Samsung SyncMaster 275T Plus (for incubus) or Samsung SyncMaster 275T (plain 275T, not 275T Plus;  for succubus) at 1920×1200 on the right.  For both incubus and succubus, the CRT is the primary display and the LCD is the secondary display.

3. succubus uses a stock kernel with crippled support for the Physical Address Extension (PAE) capability of the x86 CPU because succubus has only 4 GiB of main memory, which seems to suffice for my usage because succubus usually runs much less at once than incubus.  However, incubus uses an unofficially patched kernel to undo Microsoft’s intentional crippling of the PAE support in the client editions of Windows NT for x86-32 because incubus has 8 GiB of main memory because incubus always runs a lot of software at once, which usually uses more than 4 GiB of physical RAM.  I mention this unofficially patched kernel because the Windows 7 kernel is from Windows 7 RTM but most of the rest of the Windows 7 installation is from Windows 7 SP1.  This unusual software configuration usually seems to work well but Microsoft says that they intentionally crippled the PAE support to limit access to only the first 4 GiB of RAM because some third-party device drivers have not been tested with memory addresses above 4 GiB:  Microsoft says that such faulty device drivers can corrupt memory if the kernel uses the PAE to access more than 4 GiB of RAM.  I guess I should try to test with the stock crippled Windows 7 kernel but rebooting incubus to switch kernels is very inconvenient for me and can be done only when I am physically at my residence.  I cannot use Windows NT for x86-64 because I need specific backward compatibility that only Windows NT for x86-32 provides.

Please tell me if you need any more information from me.