← Back to team overview

touch-packages team mailing list archive

[Bug 1378802] [NEW] update-manager Couldn't connect to accessibility bus

 

Public bug reported:

** (update-manager:7750): WARNING **: Couldn't connect to accessibility
bus: Failed to connect to socket /tmp/dbus-GxEtj3txBA: Connection
refused

Always happens when using update-manager..   System originally installed from Trusty media, upgraded to Utopic.   Happened in both.
Amongst kernels used are: 3.15, 3.16.0.20, 3.17.   Same error.   Current kernel:

Linux ps01lnx 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Description:	Ubuntu Utopic Unicorn (development branch)
Release:	14.10

dbus:
  Installed: 1.8.8-1ubuntu2
  Candidate: 1.8.8-1ubuntu2
  Version table:
 *** 1.8.8-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: dbus 1.8.8-1ubuntu2
Uname: Linux 3.17.0-031700-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
Date: Wed Oct  8 08:28:33 2014
InstallationDate: Installed on 2014-07-01 (98 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.dbus.log: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

** Affects: dbus (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  update-manager Couldn't connect to accessibility bus

Status in “dbus” package in Ubuntu:
  New

Bug description:
  ** (update-manager:7750): WARNING **: Couldn't connect to
  accessibility bus: Failed to connect to socket /tmp/dbus-GxEtj3txBA:
  Connection refused

  Always happens when using update-manager..   System originally installed from Trusty media, upgraded to Utopic.   Happened in both.
  Amongst kernels used are: 3.15, 3.16.0.20, 3.17.   Same error.   Current kernel:

  Linux ps01lnx 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  Description:	Ubuntu Utopic Unicorn (development branch)
  Release:	14.10

  dbus:
    Installed: 1.8.8-1ubuntu2
    Candidate: 1.8.8-1ubuntu2
    Version table:
   *** 1.8.8-1ubuntu2 0
          500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: dbus 1.8.8-1ubuntu2
  Uname: Linux 3.17.0-031700-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  Date: Wed Oct  8 08:28:33 2014
  InstallationDate: Installed on 2014-07-01 (98 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.dbus.log: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1378802/+subscriptions


Follow ups

References