touch-packages team mailing list archive

[Bug Watch Updater <1193236@xxxxxxxxxxxxxxxxxx>]

** Changed in: at-spi
       Status: Unknown => New

** Changed in: at-spi
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1193236

Title:
   Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-*

Status in Assistive Technology Service Provider Interface:
  New
Status in “at-spi2-core” package in Ubuntu:
  Fix Released
Status in “at-spi2-core” package in Debian:
  Unknown

Bug description:
  Since a few days, xsession-errors is fullfilled by that kind of
  errors:

  ** (nautilus:22621): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection
  refused

  ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused

  Similar errors are reported all over the net, but Debian have tried to fix it already:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517

  But some other devs seems to blame an atk-bridge:
  https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA

  And some others suggest a dbus/gdbus race; the good thing is that
  seems not disturbing that much the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
  Uname: Linux 3.9.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: i386
  Date: Fri Jun 21 08:35:40 2013
  MarkForUpload: True
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions