Issue 42429 - Office freezes on accessible desktop with gtk file picker
Summary: Office freezes on accessible desktop with gtk file picker
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: nospam4obr
QA Contact: issues@framework
URL:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2005-02-10 14:24 UTC by nospam4obr
Modified: 2005-04-08 15:20 UTC (History)
6 users (show)

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


Attachments
Selective stack trace (6.58 KB, text/txt)
2005-02-11 14:44 UTC, nospam4obr
no flags Details
proposed patch (1.06 KB, patch)
2005-02-14 18:18 UTC, caolanm
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description nospam4obr 2005-02-10 14:24:24 UTC
On an accessible GNOME desktop, the office freezes as soon as the user tries to
open the gtk-file picker.

To reproduce, open gconf-editor and activate
desktop/gnome/interface/accessibility checkbox, log out and back in and run the
office.
Comment 1 nospam4obr 2005-02-10 14:25:14 UTC
Added accessibility keyword.
Comment 2 caolanm 2005-02-10 15:09:21 UTC
I'm not seeing this myself yet with accessibility enabled, what versions of gtk
and ooo is this ? http://bugzilla.gnome.org/show_bug.cgi?id=161604 looks
suspicious, but maybe unrelated.
Comment 3 nospam4obr 2005-02-10 15:22:24 UTC
I have this problem on a GNOME 2.6 with an m78. Since you're not seeing this: is
the gtk file picker accessible ?
Comment 4 caolanm 2005-02-10 15:38:57 UTC
cmc->mmeeks/raul: you seeing something like this with the file dialog ?
Comment 5 mmeeks 2005-02-10 15:52:20 UTC
Not really tried it - is there a stack-trace available of this freeze ?
Comment 6 rsiddhartha 2005-02-11 09:30:41 UTC
Havent been to try m78 yet, but m76 seems to be fine with GNOME 2.6.
Comment 7 nospam4obr 2005-02-11 14:44:42 UTC
Created attachment 22474 [details]
Selective stack trace
Comment 8 nospam4obr 2005-02-11 14:52:33 UTC
The machine I have this problem on runs Solaris 10 x86. I left out all the Java
threads which should not have anything to do with the problem.

BTW: I noticed that with the gtk plugin there appear two frames in at-poke - one
from the Java bridge and one from atk. I am not sure whether this will confuse
Gnopernicus or GOK. Any ideas how to disable the accessibility in the gtk plugin ?
Comment 9 mmeeks 2005-02-11 14:58:12 UTC
So - considering carefully - you're right - I've no idea how this can possibly
work. There's no way to get the native gtk+ a11y to talk nicely with the OO.o
a11y unless both bridge to atk ( work we have planned, but not done ).

I think the only/best soln' is to just disable the native file-picker when a11y
is enabled.
Comment 10 caolanm 2005-02-14 18:18:16 UTC
Created attachment 22601 [details]
proposed patch
Comment 11 caolanm 2005-02-14 18:19:31 UTC
*sigh*, so I propose doing something like this then once I have "fpicker3" created.
Comment 12 caolanm 2005-02-15 11:02:56 UTC
I'll try this patch in fpicker3
Comment 13 caolanm 2005-02-15 14:31:45 UTC
reopen to reassign
Comment 14 caolanm 2005-02-15 14:32:37 UTC
installset at:
http://ooomisc.services.openoffice.org/pub/OpenOffice.org/cws/upload/fpicker3/

cmc->obr: perhaps you can see if that installset works around the problem for
us. Though its linux intel only unfortunately.
Comment 15 caolanm 2005-02-15 14:32:49 UTC
.
Comment 16 nospam4obr 2005-02-17 14:29:19 UTC
You seem to build without ENABLE_GNOMEVFS, at least there is no
openofficeorg-gnome-integration package in the fpicker3 install set.

Without this package, OOo no longer activates accessibility, so that your fix
did not work as expected in the first place.

However, copying the library libfps_gnome.so into an Hamburg RE m78 build did
fix the problem (-> verified), but you should consider building with
ENABLE_GNOMEVFS set.
Comment 17 mmeeks 2005-03-08 11:28:14 UTC
*** Issue 43665 has been marked as a duplicate of this issue. ***
Comment 18 nospam4obr 2005-04-08 15:20:11 UTC
Checked again in m91.