https://bugzilla.novell.com/show_bug.cgi?id=346987
User bryeny@mi-tech.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=346987#c10
--- Comment #10 from Bryen Yunashko 2007-12-17 08:15:57 MST ---
Let me quickly add to this so you can build an expected environment. I was
testing symptoms on a test machine Friday night, and haven't completed the task
you asked of me. But here's what is important:
1. 10.3 released with at-spi not enabled. You need to be sure the
gnome-session and Control-center2 updates are installed on the box before
accessibility is enabled. These are the only updates I have added to the
freshly installed 10.3 box.
2. I have discovered that the existence of .orca directory in ~/home is needed
for the bug to be recreated. When you first start up Orca as a user, a set of
setup questions will be asked. Those get sent to .orca hidden directory.
If I try to recreate the bug in a clean user that has never set up orca before,
then the problem does not exist. So the obvious workaround is to rename/remove
orca, which isn't a good idea.
3. As a side note, I found in interesting situation. Clicking on the yast2
icon in main-menu's recent applications section, rather than Alt-F2 or
launching yast2 on the cli, did not cause the crash. Hans suggested I install
the libbonobo update to see if I could simulate a crash afterwards, but I
haven't had a chance to yet.
So the ultimate question in all of this is... How do we ignore the existence of
orca in user's directory when launching yast modules.
Hope that helped.
I will do any further testing requested this evening, as I am unavailable for
the day today.
Thank you.
Bryen
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.