Issue 65852 - atk: crash in a11y leter wizard
Summary: atk: crash in a11y leter wizard
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0.4
Assignee: nospam4obr
QA Contact: issues@gsl
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2006-05-29 12:07 UTC by caolanm
Modified: 2008-06-12 12:54 UTC (History)
4 users (show)

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


Attachments
fix (627 bytes, patch)
2006-05-29 12:07 UTC, caolanm
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description caolanm 2006-05-29 12:07:32 UTC
1. Enable accessibility
2. Start oowriter
3. File->Wizards->Letter Wizard...
4. Click "Next >" on each page
5. Click Finish
6. Dialog appears "This document already exists"; click "yes"
7. Mouseover the new window

-> crash, patch attached to avoid
Comment 1 caolanm 2006-05-29 12:07:57 UTC
Created attachment 36770 [details]
fix
Comment 2 nospam4obr 2006-05-29 14:08:46 UTC
Patch commited in CWS vcl59.
Comment 3 nospam4obr 2006-06-02 09:35:24 UTC
Still crashes for me on my old 1,8 GHz P4: VCLEVENT_BUTTON_CLICK is propagated
an already destroyed WindowEventListener.

We really need to clean up the CallEventListeners mess either by making the
listener interface reference-counted or by avoiding to copy the listeners list.
Comment 4 nospam4obr 2006-08-02 10:12:14 UTC
Since the patch does not fix the problem (at least for me), removing the PATCH
flag and re-target to 2.x.
Comment 5 nospam4obr 2007-11-26 12:44:11 UTC
We should try to fix this for 3.0.
Comment 6 nospam4obr 2008-03-14 12:13:46 UTC
Just tested again with DEV300_m2 on Solaris Nevada (77): trying to launch the
Letter Wizard already fails, here is the console output:

com.sun.star.lang.IllegalArgumentException: 
        at com.sun.star.bridges.jni_uno.JNI_proxy.dispatch_call(Native Method)
        at com.sun.star.bridges.jni_uno.JNI_proxy.invoke(JNI_proxy.java:183)
        at $Proxy19.invoke(Unknown Source)
        at com.sun.star.wizards.common.Resource.getStringList(Resource.java:76)
        at com.sun.star.wizards.letter.LocaleCodes.<init>(LocaleCodes.java:15)
        at
com.sun.star.wizards.letter.LetterWizardDialogImpl.initializeNorms(LetterWizardDialogImpl.java:895)
        at
com.sun.star.wizards.letter.LetterWizardDialogImpl.startWizard(LetterWizardDialogImpl.java:125)
        at
com.sun.star.wizards.letter.CallWizard$WizardImplementation.trigger(CallWizard.java:95)

obr->es: can you reproduce this ?
Comment 7 caolanm 2008-03-14 12:20:32 UTC
That could be (yet another case of) the hardcoded value in 
wizards/com/sun/star/wizards/letter/LocaleCodes.java in getStringList of e.g.
16298 falling out of sync with the value it is supposed to match in
svtools/inc/svtools/svtools.hrc. "STR_SVT_JAVAERROR_END" now I think
Comment 8 eric.savary 2008-03-14 15:16:21 UTC
Confirmed (nothing happens + console output) on snv_79 with DEV300_m2.

But... in m238 I cannot confirm neither crash (first description: when
completing the wizard while a letter doc already exists) nor the console output.

Hope this helps to find the regression time.
Comment 9 nospam4obr 2008-06-10 05:55:24 UTC
With DEV300_m15 I can neither reproduce the problem of the wizard not starting
nor do I get the crash again that made me re-open this issue => fixed.

If anyone can still reproduce the original crash, please re-open again.
Comment 10 mdxonefour 2008-06-12 12:54:19 UTC
MD: closing now