Issue 100773 - Display Issue (invalid context) w/ OS X Server over VNC (when no physical monitor attached)
Summary: Display Issue (invalid context) w/ OS X Server over VNC (when no physical mon...
Status: CONFIRMED
Alias: None
Product: porting
Classification: Code
Component: MacOSX (show other issues)
Version: OOo 3.0.1
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-02 01:14 UTC by minimal11
Modified: 2013-07-30 02:15 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Screenshot #1 (470.52 KB, text/plain)
2009-04-02 01:15 UTC, minimal11
no flags Details
Screenshot #2 (252.07 KB, image/png)
2009-04-02 01:16 UTC, minimal11
no flags Details
Screenshot #3 (331.47 KB, image/png)
2009-04-02 01:16 UTC, minimal11
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description minimal11 2009-04-02 01:14:22 UTC
- You cannot use OpenOffice.org on OS X Server via Remote Desktop or VNC ('RD/VNC')

(you can use RD/VNC to use OpenOffice.org on OS X (standard/client))
(If you have a physical monitor connected to the OS X Server machine, OO.org works fine.)

I am running OS X Server 10.5.6 on an XServe 2.8GHz Quad-Core Xeon with 6GB RAM.  The machine is 
running at 1024x768.

When you launch OO form the command line to capture standard out/error with 
/Applications/OpenOffice.org.app/Contents/MacOS/soffice
the following is output (truncated, but a very long repeating series of):
soffice[75506] <Error>: CGContextSetFillColor: invalid context
soffice[75506] <Error>: CGContextSetStrokeColor: invalid context
soffice[75506] <Error>: CGContextSetFillColor: invalid context
soffice[75506] <Error>: CGContextSetStrokeColor: invalid context
soffice[75506] <Error>: CGContextSetFillColor: invalid context
soffice[75506] <Error>: CGContextSetStrokeColor: invalid context
soffice[75506] <Error>: CGContextSetFillColor: invalid context
soffice[75506] <Error>: CGContextSetStrokeColor: invalid context
soffice[75506] <Error>: CGContextSetFillColor: invalid context
soffice[75506] <Error>: CGContextSetStrokeColor: invalid context

I have tried reinstalling OS X Server from scratch with a fresh copy of OO.org, with the same result.

Interestingly, or perhaps obviously, OO.org will still function as expected if you call it using the API to 
do document conversion etc, although it has intermittent font issues, presumably connected with the 
windowing problems.

The welcome to OO window does not display, but if you use the keyboard to input a return character 
and thus open a blank document, you get some strange results.  I've uploaded some screen shots to 
illustrate:

http://node3.nirvanix.com/Recall%20Media/recall.media/tmp/Picture1.png
http://node3.nirvanix.com/Recall%20Media/recall.media/tmp/Picture2.png
http://node3.nirvanix.com/Recall%20Media/recall.media/tmp/Picture3.png

(You will see two instances of OO.org running - one is in headless mode for conversion.  The same 
thing happens with only one instance running.)
Comment 1 minimal11 2009-04-02 01:15:21 UTC
Created attachment 61348 [details]
Screenshot #1
Comment 2 minimal11 2009-04-02 01:16:36 UTC
Created attachment 61349 [details]
Screenshot #2
Comment 3 minimal11 2009-04-02 01:16:59 UTC
Created attachment 61350 [details]
Screenshot #3
Comment 4 philipp.lohmann 2009-04-02 12:49:44 UTC
maybe this is related to issue 99100; although in this case OOo seems to get a
lot further before failing.
Comment 5 philipp.lohmann 2009-04-03 16:10:47 UTC
set hdu on CC list; he may be interested.
Comment 6 hdu@apache.org 2009-04-06 09:47:47 UTC
The screen resolution seems to get calculated wrongly
Comment 7 lohmaier 2009-08-11 23:12:04 UTC
not reproducible with buildbot-mac1.services.openoffice.org machine  - runs OSX
Server, but very likely has a monitor attached, don't know. VNC server used on
that machine is Vine Server (formerly known as OSX Vnc)
http://sourceforge.net/projects/osxvnc/ (better performance and less keyboard
problems than with apple's vnc)
Comment 8 lohmaier 2009-08-19 13:12:17 UTC
Turns out that the buildbot-mac1 didn't have a monitor connected in the last
couple of days. While I had no problem with launching and using OOo, you could
only switch users once, then Apple's VNC server would stop working, would
disconnect immediately, thus not allowing new logins. 

Also desktop-backgrounds were different than what they were configured to (and
couldn't be changed.

Conclusion is: Mac without a monitor attached sucks pretty badly.

found this blog that offers a workaround:
http://blackfriarsinc.com/blog/2007/04/how-to-keep-headless-mac-mini-happy
Didn't try myself though.
Comment 9 philipp.lohmann 2009-08-25 14:22:28 UTC
target
Comment 10 Rob Weir 2013-07-30 02:15:30 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.