Ubuntu
dbus package

nvidia-settings: Couldn't connect to accessibility bus

Bug #1523274 reported by Tobias Burkard
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When trying to restore .nvidia-settings-rc by executing:

$ nvidia-settings --load-config-only --config /path/to/config

the output is:

** (nvidia-settings:6149): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection refused

the settings are not being restored. It doesn't matter if the command is executed as root or not.

I also spotted such messages in other places, for example when executing "ubuntu-bug" which lead me here:

** (apport-gtk:6236): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection refused

I am running Xubuntu 15.10 which is an upgraded installation from 15.04 which again is an upgraded installation from 14.10. I hope that's not the root of my problem.

Thanks in advance for any help!

Greetings from Germany,

Tobias Burkard

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: dbus 1.10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Dec 6 20:20:16 2015
InstallationDate: Installed on 2015-03-09 (271 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: dbus
UpgradeStatus: Upgraded to wily on 2015-11-05 (30 days ago)

See original description
Revision history for this message
Tobias Burkard (tobias-burkard) wrote :
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
Revision history for this message
David A. Desrosiers (setuid) wrote :

Can confirm, this also affects:

nvidia-settings; 396.18-0ubuntu0~gpu16.04.1
nvidia-390.48
Xenial 16.04.4 LTS

I have tried every NVIDIA driver from 390.48 direct from NVIDIA all the way back to 304 from 'main' and the graphics PPA, all with 100% failure correctly identifying or using my LCD panel or any externally connected displays.

This _just_ started happening after 1 year of correctly configured and perfect use of all 3 panels. I can't figure out what happened that broke this, but now nothing works, and I'm stuck with the default Intel driver, which only supports 1600x1080 on my 4k panel.

Booting Windows 7 on the same physical metal, all 3 panels work flawlessly, arranged correctly, at the native 4k resolution.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.