Bug#714314: libatk-bridge2.0-0: undefined symbol: atspi_is_initialized
* What led up to the situation?
Upgrading to 2.9.3-1 with at-spi2-core 2.5.3-2
* What exactly did you do (or not do) that was effective (or
Running any program that relies on libatk-bridge-2.0.so.0 (such as
* What was the outcome of this action?
gnome-terminal: symbol lookup error: /usr/lib/i386-linux-gnu/libatk-bridge-2.0.so.0: undefined symbol: atspi_is_initialized
* What outcome did you expect instead?
Expect program to launch properly
Upgrading to at-spi2-core 2.9.3-1 fixes the problem, but the libatk-bridge2.0-0
package doesn't seem to depend on it - it says it requires libatspi2.0-0 (>=
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.8-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libatk-bridge2.0-0 depends on:
ii libatk1.0-0 2.8.0-2
ii libatspi2.0-0 2.5.3-2
ii libc6 2.17-2
ii libdbus-1-3 1.6.8-1
ii libglib2.0-0 2.36.3-2
ii multiarch-support 2.17-2
libatk-bridge2.0-0 recommends no packages.
libatk-bridge2.0-0 suggests no packages.
-- no debconf information
The contents of this message, together with any attachments, are intended only for the use of the person(s) to whom they are addressed and may contain confidential and/or privileged information. If you are not the intended recipient, immediately advise the sender, delete this message and any attachments and note that any distribution, or copying of this message, or any attachment, is prohibited.