Issue 123852

Summary: Several OpenOffice apps run on Windows 2008 R2 Server via Microsoft Remote Desktop cause Ms RDP 8 client for OS X to crash
Product: General Reporter: Samuel D'Errico <samuel.derrico>
Component: uiAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: bgpublic, cthompson, issues, malcolm
Version: 4.0.1   
Target Milestone: ---   
Hardware: Mac   
OS: OS X 10.9   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
MS RDP error and crash report none

Description Samuel D'Errico 2013-12-13 21:07:01 UTC
Created attachment 82096 [details]
MS RDP error and crash report

When I try to use OpenOffice 4.0.1 installed on a Windows Server via the Ms Remote Desktop Client version 8 for OS X, the Ms RDP client crashes and even if I try to reestablish the connection it freezes and there's a never-ending series of crashes. The only way to have the connection working again is to close the OpenOffice application (most cases CALC) from the Server phisically, no other way out.
Comment 1 Charles Stephen Thompson 2014-01-08 16:59:51 UTC
This is definitely happening. Every time I open OpenOffice or attempt to log on to an MS remote client with OpenOffice already open, Remote Desktop crashes with a fairly serious EXC_BAD_ACCESS (SIGSEGV) error message.
Comment 2 Malcolm 2014-03-05 05:10:36 UTC
Same issue here as the OP. I'm using Mac OS X 10.9.2 and Microsoft Remote Desktop 8.0.24308 (v8.0.3 in app store) connecting to Windows Server 2008R2.
As soon as Open Office Writer application or the Open Office application (v4.0.1) opens it crashes the session and I have to log in with Remote Desktop Connection under a Windows machine to close the application. If the application is minimised, there is no problem, but when I open the application, it crashes. If I attempt to log on with Microsoft Remote Desktop (under OS X) after the session crash, the Microsoft Remote Desktop immediately crashes.
As others have reported on the Microsoft social.technet site, if I set Microsoft Remote Desktop to make the connection at 8 bits, there is no problem except for the ugliness of the screen ;-)
There is no warning or error in the Event logs of the server I could find. I am connecting as an administrator.
I am happy to do some followup testing/provide input if someone as some suggestions. Initial part of crash report from Remote Desktop below. I am not sure if this is a Microsoft or Open Office issue, but it does not occur with the Windows remote desktop client.

Regards,
Malcolm

Process:         Microsoft Remote Desktop [495]
Path:            /Applications/Microsoft Remote Desktop.app/Contents/MacOS/Microsoft Remote Desktop
Identifier:      com.microsoft.rdc.mac
Version:         8.0.24308 (8.0.24308)
App Item ID:     715768417
App External ID: 224042646
Code Type:       X86-64 (Native)
Parent Process:  launchd [197]
Responsible:     Microsoft Remote Desktop [495]
User ID:         501

Date/Time:       2014-03-05 15:21:16.926 +1030
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version:  11
Anonymous UUID:  E226F27D-31BE-B3EF-DC15-7AB9A51903D1


Crashed Thread:  14

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffffc

VM Regions Near 0xfffffffffffffffc:
--> shared memory          00007fffffe39000-00007fffffe3a000 [    4K] r-x/r-x SM=SHM  
    

Thread 0:: Dispatch queue: com.apple.main-thread
Comment 3 Malcolm 2014-03-19 13:01:33 UTC
Some success... May not be an issue with Open Office.

It seems to be a combination of a user and the "My Desktop" entries under Microsoft Remote Desktop client v8. I found a user that could open Open Office without crashing MS Remote Desktop.
Entries look exactly the same if opened under Edit.

I created a new entry under MS Remote Desktop v8.0.5 and worked for users that didn't work before.

It is possible that there was a bug that caused a not-visible change/corruption in the My Desktop entries. I recommend people try creating new entries.

I created a new "My Desktop" entry and changed *only* the connection IP:port , Domain\user for user name and the resolution to 1024 x 786. Then I opened the session, logged in and I could open Open Office on the desktop!
Comment 4 Brett G 2014-11-11 17:44:59 UTC
I believe that I have isolated the issue to a problem between OpenOffice and RDPClip.exe.

My understanding is that Windows uses RDPClip.exe to manage synchronization of the clipboard between the client and the RDP session.  Both OpenOffice and LibreOffice seem to have some problem with the way that RDPClip works.  In my research, they are other applications that have similar problems... so this is not a problem exclusive to Openoffice.

RDPClip runs ONLY WHEN you enable clipboard redirection, so the easy workaround is to disable clipboard redirection either on the server (affecting all RDP sessions to that connection) or within the RDP client application (where you can change the setting client-by-client).

This workaround has been effective for my systems, using Windows Server 2008 R2 and Ubuntu 12.04 LTSP clients.

If you want to confirm this is your problem, wait until next time you have a freeze-up and OpenOffice won't restart without freezing again.  Next, simply go into the task manager and kill RDPclip.   If this is your problem, OpenOffice should now restart properly, without immediately freezing.