http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c1 --- Comment #1 from Hannes Reinecke --- Verified; calling export NO_AT_BRIDGE=1 emacs makes the warning go away. So why do I have to set this? Why isn't it set per default? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c2 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chcao@suse.com Flags| |needinfo?(chcao@suse.com) --- Comment #2 from Dr. Werner Fink --- And why this have become an emacs bug? GNU Emacs simply uses the bus that's it. It does not configure nor start this bus. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c4 --- Comment #4 from Hannes Reinecke --- I never said it's emacs fault ... It's just that I've been triggering this bug by starting emacs, that's all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c6 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #6 from Frederic Crozat --- I'm assuming the mesasge is displayed after becoming root in a terminal using su ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c8 --- Comment #8 from Frederic Crozat --- (In reply to Hannes Reinecke from comment #7)

No. The message is displayed when starting 'emacs' in an xterm.

which graphical environment are you using ? I'm not getting this on leap using GNOME3 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c10 --- Comment #10 from Dr. Werner Fink --- (In reply to Frederic Crozat from comment #8) I see this messages with fvwm2 .. guess: the GNOME API always expects a GNOME session manager and default of emacs with X11 is gtk aka GNOME. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c12 --- Comment #12 from Dr. Werner Fink --- I'd like to suggest to extend the file /etc/profile.d/at-spi2.sh suse/werner> rpm -qf /etc/profile.d/at-spi2.sh at-spi2-atk-common-2.16.0-2.2.x86_64 as well as o add a csh variant for this. That is not only to test for # currently there is no proper accessibility forwarding through SSH # so abort loading the module in an SSH session to avoid warnings if test -n "$SSH_TTY" -a -n "$SSH_CLIENT" ; then export NO_AT_BRIDGE=1 fi but also to a GNOME variable -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c14 --- Comment #14 from Dr. Werner Fink --- OK ... then we have for bourne shell (not only bash) cat /etc/profile.d/at-spi2.sh _gnome_toolkit=$(gsettings get org.gnome.desktop.interface toolkit-accessibility) if test -z "$_gnome_toolkit" -o "$_gnome_toolkit" = false ; then NO_AT_BRIDGE=1 export NO_AT_BRIDGE fi unset _gnome_toolkit and fot tcsh cat /etc/profile.d/at-spi2.csh set _gnome_toolkit=`gsettings get org.gnome.desktop.interface toolkit-accessibility` if ( ${%_gnome_toolkit} == 0 || $_gnome_toolkit == false ) setenv NO_AT_BRIDGE 1 unset _gnome_toolkit btw: Why does this the API of the GNOME libraries do not on their own? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c16 Michael Gorse changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@suse.com Flags|needinfo?(mgorse@suse.com) |needinfo?(hare@suse.com) --- Comment #16 from Michael Gorse --- Do you have at-spi-bus-launcher running? If so, is it owned by the user running emacs? We were intending to phase out the use of toolkit-accessibility and have accessibility be available on demand, but it also needs not to cause problems where it is not needed. Anyway, gtk+ no longer checks the key, and the intent was that other applications would ultimately stop relying on it once they confirmed that removing the check would not lead to performance issues, although I believe that firefox still checks the key. Anyway, orca sets the key, but I don't believe that the focusCaretTracker code does, for instance (so we may have a bug there, where the focus caret tracker does not work in firefox unless the key is set). Setting NO_AT_BRIDGE would also mean that, if the screen reader is started, then existing gtk applications would not have accessibility enabled until the desktop is restarted. As far as I know, the only bug being noticed is that we're getting a console warning. If we need to eliminate it, then my preference would be to patch AT-SPI to remove the warning, or only display it if toolkit-accessibility is set. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=957295 http://bugzilla.suse.com/show_bug.cgi?id=957295#c18 Tomáš Chvátal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #18 from Tomáš Chvátal --- This is automated batch bugzilla cleanup. The openSUSE 42.1 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -- You are receiving this mail because: You are on the CC list for the bug.