GNU bug report logs - #15154
24.3; Various GTK warnings on debian jessie/sid

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 15154 in the body.
You can then email your comments to 15154 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tim Van Holder <tim.vanholder <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3; Various GTK warnings on debian jessie/sid
Date: Wed, 21 Aug 2013 19:01:25 +0200

[Message part 1 (text/plain, inline)]

I typically run emacs via a ssh (PuTTY) session, using the
Cygwin X server.
Emacs was built from sources (24.3 release tarball), with GTK2
auto-selected as X toolkit (even though it apparently uses GTK3).

Starting emacs (-Q or otherwise), results in:

  ** (emacs:<pid>): WARNING **: Couldn't connect to accessibility bus:
     Failed to connect to socket /tmp/dbus-OfJcFmA1Hb: Connection
     refused

Given that I explicitly disabled DBus stuff (to avoid dbus-launch
processes that would prevent a clean ssh exit) when building emacs, this
is already a bit odd. There is no such entry in /tmp (in fact there are
no /tmp/dbus-* files at all), nor is there any envvar containing
OfJcFmA1Hb.


Also on startup, the minibuffer is higher that I would expect; this
fixes itself the first time the minibuffer becomes the active buffer.
This may be due to the initial rendering of the resize handle.


When customizing something, even when not actually changing anything,
pressing "State>Set for current session" or clicking twice on the
"Custom" menu (to open and close the pop-up menu) results in one or
two cases of:

  (emacs:17279): Gdk-CRITICAL **: gdk_device_get_source: assertion
  `GDK_IS_DEVICE (device)' failed


In addition, I frequently got

  (emacs:<pid>): Gtk-WARNING **: Failed to parse menu bar accelerator
  'VoidSymbol'

which seemed to happen when autocompleting in the minibuffer, but which
I can't now reproduce. If I see it again and can reproduce it reliably,
I'll file
a separate report.


All fairly harmless things, but if you start emacs via a plain "emacs&",
all those messages do start to pollute the terminal.


In GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2)
 of 2013-08-14 on leeloo
Windowing system distributor `The Cygwin/X Project', version 11.0.11402000
System Description:     Debian GNU/Linux testing (jessie)

Configured using:
 `configure '--with-wide-int' '--without-dbus' '--without-gconf'
 '--without-gsettings''

Important settings:
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  show-paren-mode: t
  delete-selection-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  size-indication-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
M-x r e p <tab> o <tab> r <tab> <tab> <return>

Recent messages:
Loading /home/tim.vanholder/.custom.el (source)...done
Loading whitespace...done
For information about GNU Emacs and the GNU system, type C-h C-a.
Quit
GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.8.2) of
2013-08-14 on leeloo
Making completion list...
Quit
scroll-bar-toolkit-scroll: End of buffer
scroll-bar-toolkit-scroll: Beginning of buffer
Making completion list... [3 times]

Load-path shadows:
/usr/local/share/emacs/site-lisp/global/dictionaries-common/flyspell hides
/usr/local/share/emacs/24.3/lisp/textmodes/flyspell
/usr/local/share/emacs/site-lisp/global/dictionaries-common/ispell hides
/usr/local/share/emacs/24.3/lisp/textmodes/ispell

Features:
(shadow sort mail-extr emacsbug message format-spec rfc822 mml mml-sec
mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils
mailheader sendmail rfc2047 rfc2045 ietf-drums help-mode easymenu
whitespace zastai jka-compr uniquify advice help-fns cl-lib
advice-preload paren gnus gnus-ems nnheader gnus-util mail-utils mm-util
mail-prsvr wid-edit delsel cus-start cus-load time-date tooltip
ediff-hook vc-hooks lisp-float-type mwheel x-win x-dnd tool-bar dnd
fontset image regexp-opt fringe tabulated-list newcomment lisp-mode
register page menu-bar rfn-eshadow timer select scroll-bar mouse
jit-lock font-lock syntax facemenu font-core frame cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev
minibuffer loaddefs button faces cus-face macroexp files text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process dynamic-setting
font-render-setting move-toolbar gtk x-toolkit x multi-tty emacs)

[Message part 2 (text/html, inline)]

Message #8 received at 15154 <at> debbugs.gnu.org (full text, mbox):

From: michael.albinus <at> gmx.de
To: Tim Van Holder <tim.vanholder <at> gmail.com>
Cc: 15154 <at> debbugs.gnu.org
Subject: Re: bug#15154: 24.3; Various GTK warnings on debian jessie/sid
Date: Thu, 22 Aug 2013 12:22:25 +0200

Tim Van Holder <tim.vanholder <at> gmail.com> writes:

> I typically run emacs via a ssh (PuTTY) session, using the
> Cygwin X server.
> Emacs was built from sources (24.3 release tarball), with GTK2
> auto-selected as X toolkit (even though it apparently uses GTK3).
>
> Starting emacs (-Q or otherwise), results in:
>
> ** (emacs:<pid>): WARNING **: Couldn't connect to accessibility bus:
> Failed to connect to socket /tmp/dbus-OfJcFmA1Hb: Connection
> refused
>
> Given that I explicitly disabled DBus stuff (to avoid dbus-launch
> processes that would prevent a clean ssh exit) when building emacs,
> this
> is already a bit odd. There is no such entry in /tmp (in fact there
> are
> no /tmp/dbus-* files at all), nor is there any envvar containing
> OfJcFmA1Hb.

That's not because of Emacs and its D-Bus integration. Linked GTK try to
connect to at-spi (Assistive Technology Service Provider Interface).

Check your Gnome configuration how to disable it. I suspect you must
disable /desktop/gnome/interface/at-spi-dbus, but I don't know it for
sure. You might check your settings with 

# gconftool-2 --get /desktop/gnome/interface/at-spi-dbus

Best regards, Michael.

Message #11 received at 15154 <at> debbugs.gnu.org (full text, mbox):

From: Tim Van Holder <tim.vanholder <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 15154 <at> debbugs.gnu.org
Subject: Re: bug#15154: 24.3; Various GTK warnings on debian jessie/sid
Date: Mon, 26 Aug 2013 10:40:14 +0200

[Message part 1 (text/plain, inline)]

Neither
  gconftool-2 --set "/desktop/gnome/interface/accessibility" --type bool
false
(which, as I understand it, should disable all accessibility support), nor
  gconftool-2 --set "/desktop/gnome/interface/at-spi-dbus" --type bool false
had any effect (perhaps they only matter for a desktop session setup?).

Then I found

http://askubuntu.com/questions/227515/terminal-warning-when-opening-a-file-in-gedit
and I have now added
  export NO_AT_BRIDGE=1
to my .profile to avoid the startup warning.

1 message down, 1 to go :-)



On 22 August 2013 12:22, <michael.albinus <at> gmx.de> wrote:

> Tim Van Holder <tim.vanholder <at> gmail.com> writes:
>
> > I typically run emacs via a ssh (PuTTY) session, using the
> > Cygwin X server.
> > Emacs was built from sources (24.3 release tarball), with GTK2
> > auto-selected as X toolkit (even though it apparently uses GTK3).
> >
> > Starting emacs (-Q or otherwise), results in:
> >
> > ** (emacs:<pid>): WARNING **: Couldn't connect to accessibility bus:
> > Failed to connect to socket /tmp/dbus-OfJcFmA1Hb: Connection
> > refused
> >
> > Given that I explicitly disabled DBus stuff (to avoid dbus-launch
> > processes that would prevent a clean ssh exit) when building emacs,
> > this
> > is already a bit odd. There is no such entry in /tmp (in fact there
> > are
> > no /tmp/dbus-* files at all), nor is there any envvar containing
> > OfJcFmA1Hb.
>
> That's not because of Emacs and its D-Bus integration. Linked GTK try to
> connect to at-spi (Assistive Technology Service Provider Interface).
>
> Check your Gnome configuration how to disable it. I suspect you must
> disable /desktop/gnome/interface/at-spi-dbus, but I don't know it for
> sure. You might check your settings with
>
> # gconftool-2 --get /desktop/gnome/interface/at-spi-dbus
>
> Best regards, Michael.
>

[Message part 2 (text/html, inline)]

Message #16 received at 15154 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: jidanni <at> jidanni.org
Cc: jan.h.d <at> swipnet.se, 15188 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca,
 15154 <at> debbugs.gnu.org
Subject: Re: bug#15188: message should say what the accessibility bus is
Date: Mon, 26 Aug 2013 11:39:09 +0200

jidanni <at> jidanni.org writes:

> No it's not a GTK warning. Compare:
>
> ** (emacs:8668): WARNING **: Couldn't register with accessibility bus:
> Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network
> connection was broken.
>
> (midori:8504): Gtk-WARNING **: Error loading theme icon 'bookmark-new' for stock: Icon 'bookmark-new' not present in theme
>
> OK if it is a GTK warning (that is missing its Gtk- (BUG!))  please tell me which package to report the bug
> against.

I believe this message comes rather from atk (but gtk):

As Tim Van Holder has found out, one could suppress this with
"export NO_AT_BRIDGE=1". See <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15154#11>.

Best regards, Michael.

Message #21 received at 15154-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: Tim Van Holder <tim.vanholder <at> gmail.com>
Cc: 15154-done <at> debbugs.gnu.org
Subject: Re: bug#15154: 24.3; Various GTK warnings on debian jessie/sid
Date: Mon, 26 Aug 2013 17:52:00 +0200

21 aug 2013 kl. 19:01 skrev Tim Van Holder <tim.vanholder <at> gmail.com>:

> 
>   ** (emacs:<pid>): WARNING **: Couldn't connect to accessibility bus:
>      Failed to connect to socket /tmp/dbus-OfJcFmA1Hb: Connection
>      refused

As others have pointed out, it is an atk-bridge message.  Several bug reports exists, for Ubuntu there is https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1193236.

> Also on startup, the minibuffer is higher that I would expect; this
> fixes itself the first time the minibuffer becomes the active buffer.
> This may be due to the initial rendering of the resize handle.

File a separate bug for that.

> When customizing something, even when not actually changing anything,
> pressing "State>Set for current session" or clicking twice on the
> "Custom" menu (to open and close the pop-up menu) results in one or
> two cases of:
> 
>   (emacs:17279): Gdk-CRITICAL **: gdk_device_get_source: assertion
>   `GDK_IS_DEVICE (device)' failed

This is a gtk bug: https://bugzilla.gnome.org/show_bug.cgi?id=696756. The title says w32, but it also affects X.

> 
> In addition, I frequently got
> 
>   (emacs:<pid>): Gtk-WARNING **: Failed to parse menu bar accelerator
>   'VoidSymbol'
> 
> which seemed to happen when autocompleting in the minibuffer, but which
> I can't now reproduce. If I see it again and can reproduce it reliably, I'll file
> a separate report.

To reproduce: click on the menu bar so a menu is open, then press a key.
I have checked in a fix for this.

	Jan D.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.