Bug#691718: marked as done (AT-spi upgrade breaks Gnome-shell accessibility)
Your message dated Mon, 29 Oct 2012 10:17:34 +0000
with message-id <E1TSmPW-0005NM-NS@franck.debian.org>
and subject line Bug#691718: fixed in at-spi2-atk 2.5.3-4
has caused the Debian Bug report #691718,
regarding AT-spi upgrade breaks Gnome-shell accessibility
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.)
--
691718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691718
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libatk-adaptor
Version: 2.5.3-3
Priority: important
I am running Sid with everything up to date, including atk-adaptor 2.5.3-3.
Upon starting a Gnome session, I am unable to access gnome-shell and the
following error messages appear in ~/.xsession-errors:
** (gnome-shell:20547): WARNING **: Accessibility: org.a11y.atspi schema not found. Are you sure that at-spi or at-spi2 is installed on your system?
** (gnome-shell:20547): WARNING **: Accessibility: invalid module path (NULL)
** (gnome-shell:20547): WARNING **: Accessibility: error loading the atk-bridge. Although the accessibility on the system is enabled and clutter accessibility is also enabled, accessibility support on GNOME She
ll will not work
According to the changelog, the schema was removed as redundant in
the latest at-spi upload, but Gnome-shell is evidently still looking for it,
not finding it and therefore not loading the ATK bridge.
--- End Message ---
--- Begin Message ---
Source: at-spi2-atk
Source-Version: 2.5.3-4
We believe that the bug you reported is fixed in the latest version of
at-spi2-atk, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 691718@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Thibault <sthibault@debian.org> (supplier of updated at-spi2-atk package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 29 Oct 2012 11:07:04 +0100
Source: at-spi2-atk
Binary: libatk-adaptor libatk-adaptor-dbg libatk-adaptor-data libatk-bridge2.0-0 libatk-bridge2.0-dev libatk-bridge2.0-0-dbg
Architecture: source amd64
Version: 2.5.3-4
Distribution: unstable
Urgency: low
Maintainer: Debian Accessibility Team <debian-accessibility@lists.debian.org>
Changed-By: Samuel Thibault <sthibault@debian.org>
Description:
libatk-adaptor - AT-SPI 2 toolkit bridge
libatk-adaptor-data - AT-SPI 2 toolkit bridge - data
libatk-adaptor-dbg - AT-SPI 2 toolkit bridge - debugging symbols
libatk-bridge2.0-0 - AT-SPI 2 toolkit bridge - shared library
libatk-bridge2.0-0-dbg - AT-SPI 2 toolkit bridge - debugging symbols
libatk-bridge2.0-dev - Development files for the AT-SPI 2 toolkit bridge
Closes: 691718
Changes:
at-spi2-atk (2.5.3-4) unstable; urgency=low
.
* libatk-adaptor-data.install: Revert previous change: keep schema
installed, it is actually needed. (Closes: #691718)
Checksums-Sha1:
1ab5b9ff7c835875bf1623923774879116170161 1863 at-spi2-atk_2.5.3-4.dsc
db3f302590e51965c87c745946bc13b43f14eecc 8900 at-spi2-atk_2.5.3-4.debian.tar.gz
547b1ef8e65240aa65e1f56b9d8283ee4141cc61 6028 libatk-adaptor_2.5.3-4_amd64.deb
0a2b5a72e4eb72961fc7b1d4f10e2258e043a63d 6414 libatk-adaptor-dbg_2.5.3-4_amd64.deb
2be8e8645d93399f77954cadc4a00badffa2a12f 21612 libatk-adaptor-data_2.5.3-4_amd64.deb
a5379c3c90f27ca4c7e5cea219ad90df56581100 62010 libatk-bridge2.0-0_2.5.3-4_amd64.deb
bb4bf1a4a066536dd762a0f4eca1c2cb30555350 4428 libatk-bridge2.0-dev_2.5.3-4_amd64.deb
a72f02d593907bd563b9e52436906c5783e3ec5e 90282 libatk-bridge2.0-0-dbg_2.5.3-4_amd64.deb
Checksums-Sha256:
2a8039a935efc021ecdc7ca06d3ee2e6071e6f76b2296a3039c269eccb275327 1863 at-spi2-atk_2.5.3-4.dsc
d6899327cb03629ea2cd8ca3714c02e8bf31b7c0c83f26e8284f136f845a0c82 8900 at-spi2-atk_2.5.3-4.debian.tar.gz
f6ec6fd6bdcd1ed031a39ec872b0276c91cd146ad851a7e1ade54ded01b5b7b5 6028 libatk-adaptor_2.5.3-4_amd64.deb
027fbeac07ca1c9a2fdbe14f27188fde12b5af324ea089d28694aeb2bb63cd38 6414 libatk-adaptor-dbg_2.5.3-4_amd64.deb
4c6cffb75d81fe44dc977c1e267f7e49bade7d84137b378fd02c0ce0ac9c6270 21612 libatk-adaptor-data_2.5.3-4_amd64.deb
17d9d9b212142b077806aa269783b53d972d37c572ab76ae4b23c98fd79c7070 62010 libatk-bridge2.0-0_2.5.3-4_amd64.deb
b17992f3e29f71e439d5bd3368b60af2aac5e8f4518fb9cab11e4db94599c71b 4428 libatk-bridge2.0-dev_2.5.3-4_amd64.deb
ed65277d90c4d9e98856391bbfa6ec234db843482b79ed7f6232c81c3de35dab 90282 libatk-bridge2.0-0-dbg_2.5.3-4_amd64.deb
Files:
4834827ccbd1ac0247f27a9d76f33ced 1863 misc optional at-spi2-atk_2.5.3-4.dsc
3ff23de3828f2d96715ec7f729bf6895 8900 misc optional at-spi2-atk_2.5.3-4.debian.tar.gz
b2f2c41f1817319131b1ffa8e4fcfd3c 6028 misc optional libatk-adaptor_2.5.3-4_amd64.deb
eec46ee1137cd7e500176a5d0d2b10c4 6414 debug extra libatk-adaptor-dbg_2.5.3-4_amd64.deb
93889861d394c5db3897f5c687e37a36 21612 misc optional libatk-adaptor-data_2.5.3-4_amd64.deb
846653d8823a0c7d759497471efa9626 62010 libs optional libatk-bridge2.0-0_2.5.3-4_amd64.deb
b0f7c1ec88cbf92cc6f210f37766708a 4428 libdevel optional libatk-bridge2.0-dev_2.5.3-4_amd64.deb
a90712cadae18fbc4169f397d8a6332d 90282 debug extra libatk-bridge2.0-0-dbg_2.5.3-4_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iF4EAREKAAYFAlCOVoAACgkQ2y9P4eIpzVCUTQD+LWYtKNqSqz3KZGtoI7jRUqhq
vCFv7Fuem6HffHTDEg0A/R2SQQaqzxYDghhF77KNopgoW0WAagO27gXPH38gM1Gq
=WQfV
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: