http://bugzilla.novell.com/show_bug.cgi?id=508611 User bgmerrell@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=508611#c19 --- Comment #19 from Brian Merrell <bgmerrell@novell.com> 2009-10-11 15:01:13 MDT --- Thanks Wolfgang. I had a little time to investigate this between some recent work on security updates. I will tell you what I discovered, in case it is useful to you: The problem exists in the mozilla191 package (which I believe you and Stephen already disovered). If either gconf-backend.patch.bz2 or gecko-lockdown.patch is applied, then Firefox is no longer accessible. toolkit-ui-lockdown.patch can be applied without making Firefox inaccessible. Additionally, if the patches to xpinstall/src/nsXPInstallManager.cpp and widget/src/gtk2/nsWindow.cpp are removed from the gecko-lockdown.patch, the gecko-lockdown.patch can be applied without making Firefox inaccessible. However, if gconf-backend.patch.bz2 is also applied, Firefox will remain inaccessible. Again, I'm not sure how useful this information is to you, but I wanted to let you know what I had seen thus far. Please let me know if I can help with anything. The easiest way to tell if Firefox is accessible is to to the following: 1. Enable assistive technologies from the GNOME control panel (under the assistive technologies icon). You have to log out and log back in for the change to take affect. 2. Run Accerciser and make sure that Firefox appears in the left pane (the TreeView of applications). You should be able to expand Firefox in that pane and see several children under the Firefox application. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.