GNOME Bugzilla – Bug 648961
In Ubuntu's Unity, sound preferences opens speech-dispatcher infinite loop with Orca v3
Last modified: 2011-05-01 23:35:59 UTC
Im running into a problem apparently from gnome-orca in Ubuntu 11.04. Original reported on launchpad here https://bugs.launchpad.net/gnome-orca/+bug/773450 When I open sound preferences a terminal opens itself and a choppy voice says "Welcome ______ current desktop environment is unity" The blank sounds like my nickname used in empathy nearby people. If I close the terminal it reopens and talks again. In the sound preferences under the applications tab speech-dispatcher appears. By muting this application the voice will stop. There appears to be no way to permanently close the terminal without logging out. I was able to prevent this problem by removing gnome-orca.
Any chance this is a dup of bug 647117? i.e. if you were to reinstall your downstream gnome-orca package could you see if (re)moving the autostart file makes the problem go away? If so, does that file contain the change made to fix bug 647117? Thanks!
Your right if I remove Visual Assistance (gnome-at-visual -s) from startup applications with gnome-orca installed this problem does not occur. I don't know how to tell if my version has the change that fixed it but the commit in bug 647117 was made after the feature freeze for Ubuntu 11.04 so I think its likely my package does not include it. Does that make this a duplicate of bug 647117 that has been fixed?
(In reply to comment #2) > Your right if I remove Visual Assistance (gnome-at-visual -s) from startup > applications with gnome-orca installed this problem does not occur. That's a good sign. It looks to me like the patch was included by Luke, but that doesn't mean you have it on your particular system. Take a look at: /etc/xdg/autostart/orca-autostart.desktop and see if it has a line which reads: OnlyShowIn=GNOME; Also, do you have accessibility enabled for your session? Finally, are you comfortable building Orca from upstream master? To make a long story short, because of gnome 3 versus unity, and gnome 3 versus gnome 2, we've been advising users and anyone else who will listen to NOT use Orca from the gnome-3-0 branch if they are not in gnome 3. (You are not in gnome 3.) We're keeping Orca's master branch free of gnome 3 stuff for now so that everyone (Unity, gnome 2) can still have the latest features and fixes in Orca even without gnome shell. The package Luke seems to be providing for gnome-orca appears to be a properly-patched version of gnome-3-0's Orca. Which is a logical approach. But what I suspect is happening is that there's something gnome-3-0ish which is failing to get undone. I'll try to figure out what that might be. And we could rule that in/out if you were to re-enable the autostart but use Orca from master rather than from the gnome-3-0 branch.
An additional thought/theory: This is a variant of bug 647117. However, KDE knows it is not GNOME. Unity perhaps thinks it is GNOME, thus that work-around ain't gonna solve it.
Other stuff I would like to know: The output from each of these when the bug is manifesting itself: gsettings get org.gnome.desktop.interface toolkit-accessibility gsettings get org.gnome.desktop.a11y.applications screen-reader-enabled gconftool-2 --get /desktop/gnome/interface/accessibility I cannot reproduce this problem to save my life, on a fully updated Natty, running Unity, and using the official gnome-orca packages. Anyhoo.... For me, the values for the above are: false, false, true respectively.
I've got "OnlyShowIn=GNOME;" How do I tell if I have accessibility enabled? Building is new territory for me but Ill give it a shot if you point me in the right direction. Ill work on the output of those. thanks for the help
I'm getting false false false.
(In reply to comment #7) > I'm getting false false false. And if I set the last one to false I still cannot reproduce this bug. BTW, the falses (at least the first and last) mean that you don't have accessibility enabled. What the xdg autostart file does -- or is supposed to do -- is set the condition to only autostart if gsettings get org.gnome.desktop.a11y.applications screen-reader-enabled is true. When that condition is met, the resulting action is "launch Orca." That the value is false, but the session is going ahead and launching Orca, sounds to me like something in some other package is getting confused. The use of gsettings and the screen-reader-enabled key are gnome 3 things. They don't make sense in a Unity (gnome 2, gconf) world. Downstream should remove that autostart file.
So this is a downstream issue. gnome-session 2.32 (which is what Natty ships) apparently doesn't have the smarts to deal properly with gsettings-based autostart conditions. Compare: http://git.gnome.org/browse/gnome-session/tree/gnome-session/gsm-autostart-app.c http://git.gnome.org/browse/gnome-session/tree/gnome-session/gsm-autostart-app.c?h=gnome-2-32 I am still pondering whether or not to remove the autostart file from master, leaving it only in the gnome-3-0 branch. In the meantime, since this is a downstream issue being addressed downstream by Luke, I'm closing this bug out as NOTGNOME.