[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#732618: marked as done (libatspi2.0-0: warning "Couldn't register with accessibility bus")

Your message dated Mon, 25 Aug 2014 01:58:43 +0200
with message-id <20140824235842.GA809@xvii.vinc17.org>
and subject line Re: Bug#732618: WARNING: Couldn't register with accessibility bus
has caused the Debian Bug report #732618,
regarding libatspi2.0-0: warning "Couldn't register with accessibility bus"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
732618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732618
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: emacs24
Version: 24.3+1-2
Severity: normal

Each time I start Emacs with its own interface, including with
"emacs -Q", I get a warning like:

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

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages emacs24 depends on:
ii  emacs24-bin-common   24.3+1-2
ii  gconf-service        3.2.6-1
ii  libasound2           1.0.27.2-3
ii  libatk1.0-0          2.10.0-2
ii  libc6                2.17-97
ii  libcairo-gobject2    1.12.16-2
ii  libcairo2            1.12.16-2
ii  libdbus-1-3          1.6.18-2
ii  libfontconfig1       2.11.0-2+local1
ii  libfreetype6         2.5.1-2
ii  libgconf-2-4         3.2.6-1
ii  libgdk-pixbuf2.0-0   2.28.2-1+b1
ii  libgif4              4.1.6-11
ii  libglib2.0-0         2.36.4-1
ii  libgnutls26          2.12.23-8
ii  libgomp1             4.8.2-10
ii  libgpm2              1.20.4-6.1
ii  libgtk-3-0           3.8.6-1
ii  libice6              2:1.0.8-2
ii  libjpeg8             8d-2
ii  libm17n-0            1.6.4-2
ii  libmagickcore5       8:6.7.7.10-6
ii  libmagickwand5       8:6.7.7.10-6
ii  libotf0              0.9.13-1
ii  libpango-1.0-0       1.36.0-1+b1
ii  libpangocairo-1.0-0  1.36.0-1+b1
ii  libpng12-0           1.2.49-5
ii  librsvg2-2           2.40.0-1
ii  libselinux1          2.2.1-1
ii  libsm6               2:1.2.1-2
ii  libtiff4             3.9.7-3
ii  libtinfo5            5.9+20130608-1
ii  libx11-6             2:1.6.2-1
ii  libxft2              2.3.1-1
ii  libxml2              2.9.1+dfsg1-3
ii  libxpm4              1:3.5.10-1
ii  libxrender1          1:0.9.8-1
ii  zlib1g               1:1.2.8.dfsg-1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.3+1-1

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,

On 2014-08-24 23:34:00 +0200, Samuel Thibault wrote:
> Vincent Lefevre, le Thu 19 Dec 2013 14:19:18 +0100, a écrit :
> > Control: reassign -1 libatspi2.0-0 2.10.2-1
> > Control: retitle -1 libatspi2.0-0: warning "Couldn't register with accessibility bus"
> 
> When reassigning a bug, always Cc the maintainer of the new package,
> otherwise he doesn't even get a mail about the bug being reassigned.

Sorry, this should really be done automatically.

> > > > Each time I start Emacs with its own interface, including with
> > > > "emacs -Q", I get a warning like:
> > > > 
> > > > ** (emacs:4601): 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.
> 
> Does that still happen?

No, and I tried to reproduce it, but I couldn't. So I'm closing the bug.

> Does at-spi2-registryd get started along the way?

Currently, it is started automatically when I log in.

> Which desktop environment are you using?

No desktop environment, just fvwm as my window manager.

> Do you have something in the $GTK_MODULES environment variable?

No, there was something in the past:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562202

but I don't know since when it was no longer set.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

--- End Message ---
Reply to: