Issue 123636 - [ia2] Launching swriter.exe results in invisible, broken Writer
Summary: [ia2] Launching swriter.exe results in invisible, broken Writer
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: accessibility (show other issues)
Version: 4.1.0-dev
Hardware: PC Windows, all
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks: winA11y
  Show dependency tree
 
Reported: 2013-11-05 10:06 UTC by James Teh
Modified: 2017-05-20 10:33 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description James Teh 2013-11-05 10:06:35 UTC
Str:
1. Ensure OpenOffice is closed.
2. Open Writer by selecting OpenOffice Writer from the Start Menu or by running swriter.exe.
Expected: Writer should start and function as normal.
Actual: the main window is invisible and isn't in the alt+tab task switcher or the running applications bar (so it's impossible to switch back to Writer once you switch away). Furthermore, text cannot be accessed via the accessibility hierarchy. The menus can be accessed, though.

This does not occur if you start OpenOffice and then select Text Document.
Comment 1 Rainer Bielefeld 2013-11-05 18:17:59 UTC
NOT Reproducible with server installation of "AOO 4.1.0-Dev – German  UI / German locale - [AOO410m1(Build:9750)  -  Rev. 1537973 - 2013-11-03]" on German WIN7 Home Premium (64bit)", own separate user profile:

0. Close all soffice.xxx instances
1. Open ....\program\ folder in WIN Files Explorer
2. doubleclick on swriter.exe
   Expected: first splash screen with progress bar, then empty Writer document,
             all WIN functions as usual.
   Actual: as expected.

Looks like an installation issue.

@reporter:
unfortunately important information we will 
need to reproduce your problem is missing.
Please add all information requested in following:
a) What is the "Main Window"? Spash screen?
   <http://en.wikipedia.org/wiki/Splash_screen>
d) Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
e) if possible contribute an instruction how to create a sample document 
  from the scratch
f) add information 
  f1) Where do you see relation to Assitive Technology support?
  f3) concerning your PC 
  f4) concerning your Operating System (Version, Distribution, Language)
  f5) concerning your AOO version (with Build/revision ID if it's not a 
     public release) and localization (UI language, Locale setting)
  f6) AOO settings that might be related to your problems 
  f8) Whether your problem persists when you renamed your user profile 
     (Quit Quickstart before!) before you launch AOO (please see
     <http://www.openoffice.org/development/releases/3.4.1.html#AOO3.4.1ReleaseNotes-KnownIssues>)
  f9) Whether that worked in former OOO / AOO Versions 
  f10) Win7: what if you launch as administrator?
 
Even if you can not provide all demanded information, every little new information might bring the breakthrough.
Please do not cite these hints in your reply, but cite the items like:
c): Yes, also in CALC, not in Impress
Comment 2 James Teh 2013-11-05 20:35:21 UTC
My apologies. My understanding was that the [ia2] prefix was sufficient to communicate that bugs were specific to the ia2 branch, as suggested on the dev mailing list.

This was tested with an ia2 branch build with rev 1536988. There is a later build, but it is apparently quite broken.

It seems to only happen with assistive technology support enabled and if an assistive technology is running when you start Writer. I tested with NVDA. I suspect it isn't relevant, but for reference, I'm running Windows 7 x64.
Comment 3 V Stuart Foote 2013-11-07 03:09:30 UTC
@Rainer -- Please review current ia2 Branch development issues if you are going to apply your considerable BZ issue QA acumen, welcome to the fray so to speak as we work to make the IAccessible2 accessibility bridge ready for a 4.1 merge.

Current ia2 branch build r1538508 is available from Buildbot. And while the branch was just resyncd with trunk it has a number of aspects that are unique to running with Assistive Technology. And to work with this branch, suspect that you must install as an Administrative install will not suffice for testing the IAccessible2 interface.

Confirming Jamie's observations, working on Windows 7 sp1 64-bit. 
AOO410m1(Build:9750)  -  Rev. 1538508
Rev.1538508

Additionally, launching of Writer from Start menu or with swriter.exe, will flash oppen the start pannel, but then no wiriter window opens. 

A review of windows task manager the soffice.exe *32 --> "C:\Program Files (x86)\OpenOffice 4\program\swriter.exe" -writer
and soffice.bin *32  --> "C:\Program Files (x86)\OpenOffice 4\program\swriter.exe" "--writer" "-env:OOO_CWD_=2C:\\Program Files (x86)\\OpenOffice 4"

Killing these processes in task manager puts the ia2 branch into a document recovery notice -- abort cycle. And to recover use of OpenOffice I had to rename (or delete) the per-user profile--%APPDATA%\OpenOffice

All other launchers (Base, Calc, Draw, Impress, Math & OpenOffice) function correctly and launch respective component.
Comment 4 V Stuart Foote 2013-11-07 03:16:43 UTC
Further, verified that with AT disabled (NVDA halted) the Start menu launcher for Writer (and all other components) does fully launch component without issue.
Comment 5 James Teh 2013-11-07 04:00:02 UTC
(In reply to V Stuart Foote from comment #3)
> to work with this branch,
> suspect that you must install as an Administrative install will not suffice
> for testing the IAccessible2 interface.
Unless I'm missing something, the IA2 support no longer depends on any components being installed/registered with the system.

> Additionally, launching of Writer from Start menu or with swriter.exe, will
> flash oppen the start pannel, but then no wiriter window opens.
The window does open, but it's invisible. This is easy for a screen reader user to see, but a sighted user will need an inspection tool of some sort to see it. :)

> Killing these processes in task manager puts the ia2 branch into a document
> recovery notice -- abort cycle. And to recover use of OpenOffice I had to
> rename (or delete) the per-user profile--%APPDATA%\OpenOffice
I did find a way to avoid deleting the profile. After you kill OpenOffice after the problem occurs, if you launch with scalc.exe and cancel the recovery, Calc will then launch as normal.
Comment 6 Rainer Bielefeld 2013-11-07 05:13:09 UTC
@V Stuart
Thank you for explication, can you / someone please leave some hints  in the Wiki in QA area on <https://wiki.openoffice.org/wiki/BUGZILLA/FAQ#.5Bia2.5D>?
Comment 7 V Stuart Foote 2013-11-07 06:08:14 UTC
@Rainer,

(In reply to Rainer Bielefeld from comment #6)
> @V Stuart
> Thank you for explication, can you / someone please leave some hints  in the
> Wiki in QA area on <https://wiki.openoffice.org/wiki/BUGZILLA/FAQ#.5Bia2.5D>?

Just tried, but the stupid pick-the-cats Captcha in use will not pass a valid confirmation code for the Wiki account creation.  Sorry!

Meanwhile, the short of it is that the ia2 branch is implementing an IAccessible2 native bridge of UNO Accessibility API (UAA) events for Windows--similar to the NX Accessibility and ATK/AT-SPI bridges in place for OS X and Linux.  The native bridge replaces the Java JRE implemented Java Accessibility API that requires the Java Access Bridge to connect to UAA events.
Comment 8 Steve Yin 2013-11-07 12:51:37 UTC
I will focus on this issue. It is a little bit strange :)
Comment 9 V Stuart Foote 2013-11-12 20:32:33 UTC
On Windows 7 sp1 64-bit with NVDA 2013.2 active and
AOO410m1(Build:9750)  -  Rev. 1540658
Rev.1540658

Setting Resolved Fixed, issue is no longer producible at the r1540658 build.

Writer session fully formed when launched from Start Menu --> OpenOffice 4.1.0 --> OpenOffice Writer component launcher. Alt-TAB Window switcher moves into and out of the Writer session with out issue.  Alt-<F4> exit functions as expected.

@Steve Y. any specific commit you can site for resolution?
Comment 10 Steve Yin 2013-11-15 02:44:29 UTC
@Stuart: This issue has the same root cause with i123619. There has some lines for handling accessibility of the old sw annotation feature (PostIt in OOo3.1) in the bridge. So the new AOO version has no accessible for the annotation window. We need to re-implement it later.