To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=60696
------- Additional comments from [EMAIL PROTECTED] Tue Oct 30 20:52:52 +0000 2007 ------- I was able to successfully install and run the topten QATESTTOOL tests on both the Windows and Linux Unxsplash2 CWS builds without any issues. Below are the builds I used for my testing: http://termite.go-oo.org/install_sets/O3-build-328-unxsplash2-install_set.zip http://termite.go-oo.org/install_sets/Win-XP-143-unxsplash2-install_set.zip I was also able to successfully start soffice (which on Linux exercised oosplash) under the following conditions: xnest window (DISPLAY=:22.0) vnc session (DISPLAY=127.0.0.1:1.0) Windows XP using 16 bit color Windows XP using 24 bit color openSUSE 10.3 GNOME session using 15 bit color openSUSE 10.3 GNOME session using 24 bit color Under the openSUSE 10.3 Linux system I tested to make sure that the following commands worked correctly when no soffice.bin process was running as well as when an existing process was already running: soffice -writer soffice -calc soffice -impress soffice -dbase soffice -minimized soffice -invisible soffice -norestore soffice -quickstart soffice -nologo soffice -nolockcheck soffice -nodefault soffice -headless soffice -help soffice -h soffice -? soffice -o soffice -n soffice -display soffice -view soffice -show The commandline options that failed for me when no soffice processes was already running were: soffice -p <document> soffice -pt <printername> <document> I also ran into problems with the application not starting on the correct DISPLAY only when I had the same user logged into two sessions at the same time (ie a vnc and xnest sessions). Once OpenOffice was opened and started from one of the sessions, any attempts from the other session would result in the OOo application starting up in the first session. However, I did notice the same behavior using the upstream OOo 2.3 (OOo_2.3.0_LinuxIntel_install_wJRE_en-US.tar.gz) downloaded from here: http://openoffice.bouncer.osuosl.org/?product=OpenOffice.org&os=linuxintelwjre&lang=en-US&version=2.3.0 So I do not believe this is an issue behavior that was introduced in this CWS. While reading the previous comments in this issue, I realized that I may not have tested all of the command line or headless test environments for this CWS. I'm not exactly sure what other scenarios the upstream developers believe will break with this CWS. Besides having kendy look into the printing failure, could one of the upstream developers help explain to me what other tests should be exercise if any before we nominate this CWS? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
