https://bugzilla.novell.com/show_bug.cgi?id=346987 Bryen Yunashko changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bryeny@mi-tech.com Keywords| |accessibility Status Whiteboard| |gnome-accessibility -- 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.

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#c2 Bryen Yunashko changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hpj@novell.com Status|NEEDINFO |NEW Info Provider|doheiligh@novell.com | --- Comment #2 from Bryen Yunashko 2007-12-10 20:21:06 MST --- (In reply to comment #1 from Cyril Hrubis)

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!

Hi Cyril, I'm helping Darragh with collecting symptoms, so I'll post the logs here. I have identified an interesting difference in behavior. In the above first report, that is generated when you do: 1. Command line to start Orca 2. Start Yast2 in Gnome. 3. In this case, it is the module that crashes and generates the error mentioned above. 4. The yast2log is attached as y2log-826 (indicating it happened at 8:26 p.m.) I tried recreating this in a different method by: 1. Command line to start Orca 2. In a second gnome-terminal window, start yast2 from the command line. 2a. The following output occurs on the yast2 gnome-terminal window: (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (y2controlcenter-gnome:4026): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed 2b. Yast2 does start up and everything is fine. 2c. However, going back to the first gnome-terminal where Orca was started on the command line: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/orca/atspi.py", line 700, in __init__ self.accessible.ref() COMM_FAILURE Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/orca/atspi.py", line 700, in __init__ self.accessible.ref() COMM_FAILURE Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/orca/atspi.py", line 700, in __init__ self.accessible.ref() COMM_FAILURE 3. Selected a module (in this case Software Repositories) 3a. Accessing the Package Management Failed: Another process is accessing the package database. Package management cannot be used now." 4. Despite these errors, Orca is still running. It is only Yast2 that does not continue. The log report in this case is y2log-917 (because it occurred at 9:17 p.m.) Please let us know if we can provide any further information. -- 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.

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#c4 --- Comment #4 from Bryen Yunashko 2007-12-10 20:25:20 MST --- Created an attachment (id=186733) --> (https://bugzilla.novell.com/attachment.cgi?id=186733) second y2log file -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mmeeks@novell.com -- 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.

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#c7 --- Comment #7 from Bryen Yunashko 2007-12-14 09:09:26 MST --- (In reply to comment #6 from Ricardo Cruz)

Hi, Could you try the following version which has our custom accessibility hooks disabled: svn checkout http://svn.opensuse.org/svn/yast/trunk/gtk/unstable/ yast-gtk

That'd be great. To compile it: make -f Makefile.cvs make sudo make install

Just make sure that the necessary -devel packages are installed. They are listed on README.

Could you explain what is expected from trying this out? If we are dependent on accessibility tools and you say the custom accessibility hooks are disabled for the version you link to, what exactly are we expected to do/see? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c9 --- Comment #9 from Michael Meeks 2007-12-17 07:35:59 MST --- Hi Ricardo; to test is simple enough; from the Control Center select "Assistive Technology" and hit "Enable assistive technologies". Then log out / in again - everything should be instrumented now. Then you need to run accerciser or 'at-poke' to be able to see the apps running & what they expose. OTOH - I forget what the story is wrt. 'root' owned applications in this space: AFAIR there was some socket/privilege problem there. Hans Peter may know more (?) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User doheiligh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c11 Darragh O Heiligh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |doheiligh@novell.com --- Comment #11 from Darragh O Heiligh 2008-01-10 04:20:14 MST --- Any update on this? After Bryan's help, I don't see anything else. Please do not hesitate to contact me at doheiligh@novell.com if you require any testing. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User rpmcruz@alunos.dcc.fc.up.pt added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c13 Ricardo Cruz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #13 from Ricardo Cruz 2008-01-17 04:09:16 MST --- I guess we can close this now? Tell me if you need it functional for a 10.3 box. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c15 JP Rosevear changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpr@novell.com --- Comment #15 from JP Rosevear 2008-01-17 13:53:52 MST --- How hard is this to back port to the 10.3 version Ricardo? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User doheiligh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c17 --- Comment #17 from Darragh O Heiligh 2008-01-18 09:29:20 MST --- Hello, I have tested the latest version of Yast2-gtk from SVN however I am sorry to report that I am still encountering this bug. You can test this by following the below instructiosn: 1. Start Gnome. 2. Go into a terminal: alt F2 ----- gnome-terminal 3. Su to root. su 4. Launch Orca with root access. orca --no-setup --disable main-window 5. Keep the console open and go to Yast2. Click on Gnome menu, system / yast2. 6. Try starting one of the modules. You will notice that an error window is shown. Note: you may need to run Orca as a normal user and run through it's set up process before following these instructions. A log out is also required to enable accessibility for the Gnome Desktop. Thanks -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User doheiligh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c19 --- Comment #19 from Darragh O Heiligh 2008-02-27 03:52:54 MST --- Yes. error is the same. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User doheiligh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c21 Darragh O Heiligh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|doheiligh@novell.com | --- Comment #21 from Darragh O Heiligh 2008-03-06 03:48:02 MST --- Morning, A few updates. Ok, after a fresh installation of OpenSuSE 10.3, I used the svn repository mentioned in comment 16. Accessibility seems to be fine now and the modules are showing correctly. A few issues have arisen. 1. When closing a module, yast hangs. Yast logs are attached. 2. my screen reader, Orca, reads buttons but the static text in the dialogues is not accessible. I really don't know a better way of explaining this. I should be able to use a function called flat review mode in Orca to read the labels of error and warning dialogues. This works everywhere else in Gnome in GTK plus applications. Thanks for your help. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User doheiligh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c23 --- Comment #23 from Darragh O Heiligh 2008-03-07 11:05:55 MST --- Created an attachment (id=199578) --> (https://bugzilla.novell.com/attachment.cgi?id=199578) yast 2 logs. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c25 Michael Meeks changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sh@novell.com --- Comment #25 from Michael Meeks 2008-04-16 02:29:33 MST --- So - in fact this is a mix of an ORBit2 bug, and (perhaps) a Yast UI bug. Here is the problem: To be backwards compatible with single threaded apps; we have the concept of a "main thread" (which sucks). It is on this thread that we execute incoming requests - to be certain that we don't create threading issues. Anyhow - all is well with yast2 - we initialize this thread as the "UI thread" in yast2, and everything goes swimmingly until shutdown. On shutdown yast2's UI core (apparently) kills the UI thread; and then proceeds to destroy all windows from the main (ie. non-UI) thread: Stefan - is that an easy thing to fix ?: Thread 1 (Thread 0xb78966d0 (LWP 10696)): .. #20 0xb65c7691 in ~YGDialog (this=0x80a2cd8) at YGDialog.cc:127 #21 0xb691c610 in YDialog::deleteAllDialogs () from /usr/lib/libyui.so.3 #22 0xb68f6e07 in YUI::~YUI () from /usr/lib/libyui.so.3 #23 0xb65c54bb in ~YGUI (this=0x80a2c88) at YGUI.h:42 #24 0xb69752d9 in YUIComponent::result () from /usr/lib/YaST2/plugin/libpy2UI.so.2 #25 0xb7ecd253 in main () from /usr/lib/liby2.so.2 #26 0xb7a4d5f6 in __libc_start_main (main=0x80484b8 , argc=3, ubp_av=0xbfb8cbd4, init=0x80485c0 <__gmon_start__@plt+232>, fini=0x80485b0 <__gmon_start__@plt+216>, rtld_fini=0xb8081650 <_dl_fini>, stack_end=0xbfb8cbcc) at libc-start.c:220 #27 0x08048511 in ?? () ie. I would expect that to be happening in Thread 2 ... :-) Of course - ORBit2 can do better here; we don't handle this case as elegantly as we can; but I'd prefer a belt & braces fix really. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c27 --- Comment #27 from Stefan Hundhammer 2008-04-16 06:09:48 MST --- Please also note that with that latest version of yast2-libyui event ownership changed - YDialog now handles that. Simply get rid of all calls to "delete event". The compiler should complain at those places. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=346987 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=346987#c29 --- Comment #29 from Michael Meeks 2008-06-03 09:06:26 MDT --- OTOH - a11y doesn't work running as root; reading the strace - it seems that the root user manages to connect just fine to the main user's CORBA sockets - and send & recieve useful events from the registryd. The problem comes (obviously) when the user-space orca process wants to connect to a root-owned socket, and start remote-controlling a process running as root: as expected, the sockets are secure, and can't be connected to. A simple 'chown -R michael /tmp/orbit-root' (while the app is running) lets ORCA connect beautifully to a root yast2; So - on the whole, it's not transparently obvious what to do here; clearly there are risks running any app using a GUI toolkit as the root user - those are clearly magnified by allowing the user to connect to a process running as root and start tweaking it intimately. I guess, one approach would be to make the ORB detect this mode: and get it to create a socket in /tmp/linc-$USER instead of /tmp/orbit-$USER with that user's permissions. OTOH - it's not totally clear to me how to reliably detect what the master user is [ though we could perhaps steal that from grokking profiles in the IOR on the root window ] - urgh. -- 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.