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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jan Djärv <jan.h.d <at> swipnet.se>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#15188: closed (message should say what the accessibility bus is)
Date: Mon, 26 Aug 2013 15:53:02 +0000

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

Your message dated Mon, 26 Aug 2013 17:52:00 +0200
with message-id <03D996F2-30A4-4AF6-A551-28F7BFCB89FA <at> swipnet.se>
and subject line Re: bug#15154: 24.3; Various GTK warnings on debian jessie/sid
has caused the debbugs.gnu.org bug report #15154,
regarding message should say what the accessibility bus is
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
15154: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15154
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Subject: message should say what the accessibility bus is
Date: Sun, 25 Aug 2013 21:32:22 +0800

This message should say what the accessibility bus is. Some bus for old people?

     # su - nobody -c 'HOME=/tmp emacs -f w3m ~jidanni/jidanni.org/location/directions/index.html'
     No directory, logging in with HOME=/

     ** (emacs:3345): 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.

Also the URL it is trying to reach, if any should be revealed.

[Message part 3 (message/rfc822, inline)]

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.