LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices


Reply
  Search this Thread
Old 12-22-2014, 11:50 AM   #1
dr_berta
Member
 
Registered: Sep 2005
Location: Carpi (Modena) - Italy
Distribution: Ubuntu 20.04_x86_64 LTS; Slackware 13 64bit; Gentoo, Fedora, Yocto
Posts: 77

Rep: Reputation: 1
Error message after login: Couldn't connect to accessibility bus


Hi all,
few days ago my desktop with Ubuntu 14.04 x86_64 started to send a strange message just after the login (see attached image - sorry but it is in italian). I tried to investigate the reason of the problem and I found that the .xsession-errors file had the following content (translated from italian):
Code:
** (zenity:10227): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-k79ZmNDcyI: Connection refused
sudo: no tty present and no password request program specified
sudo: no tty present and no password request program specified
openConnection: connect: File o directory not existing
cannot connect to brltty at :0
init: Process main of job indicator-application terminated, regenerating
init: Process main of job indicator-application terminated, regenerating
init: indicator-application is regenerating too fast, stopped
Also the syslog file is reporting strange messages (see attached file)
Finally even the dmesg has errors:
Code:
[   10.332081] EXT4-fs (sdb1): INFO: recovery required on readonly filesystem
[   10.332085] EXT4-fs (sdb1): write access will be enabled during recovery
[   11.614154] EXT4-fs (sdb1): recovery complete
[   11.617760] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[   25.779118] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   25.982981] systemd-udevd[343]: starting version 204
[   26.629629] wmi: Mapper loaded
[   26.657812] ATK0110 ATK0110:00: EC enabled
[   26.672428] device-mapper: multipath: version 1.6.0 loaded
[   26.714403] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SBRG.ASOC.SMRG 1 (20131115/utaddress-251)
[   26.714408] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   26.775167] MCE: In-kernel MCE decoding enabled.
[   26.783665] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
[   26.783725] sp5100_tco: PCI Revision ID: 0x42
[   26.783754] sp5100_tco: Using 0xfed80b00 for watchdog MMIO address
[   26.783764] sp5100_tco: Last reboot was not triggered by watchdog.
[   26.783799] sp5100_tco: initialized (0xffffc90010c8cb00). heartbeat=60 sec (nowayout=0)
[   26.861535] lp: driver loaded but no devices found
[   26.880717] it87: Found IT8721F chip at 0x290, revision 1
[   26.880758] ACPI Warning: 0x0000000000000295-0x0000000000000296 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SIOR.ECRE 1 (20131115/utaddress-251)
[   26.880763] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   26.892747] EDAC MC: Ver: 3.0.0
[   26.924391] type=1400 audit(1419245957.906:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=425 comm="apparmor_parser"
[   26.924397] type=1400 audit(1419245957.906:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=425 comm="apparmor_parser"
[   26.924400] type=1400 audit(1419245957.906:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=425 comm="apparmor_parser"
[   26.924764] type=1400 audit(1419245957.906:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=425 comm="apparmor_parser"
[   26.924769] type=1400 audit(1419245957.906:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=425 comm="apparmor_parser"
[   26.924959] type=1400 audit(1419245957.906:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=425 comm="apparmor_parser"
[   26.937037] [drm] Initialized drm 1.1.0 20060810
[   26.970622] ppdev: user-space parallel port driver
[   26.974486] AMD64 EDAC driver v3.4.0
[   26.974510] EDAC amd64: DRAM ECC disabled.
[   26.974514] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
[   26.974514]  Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
[   26.974514]  (Note that use of the override may cause unknown side effects.)
[   27.015354] kvm: Nested Virtualization enabled
[   27.015357] kvm: Nested Paging enabled
[   27.579694] Bluetooth: Core ver 2.17
[   27.579713] NET: Registered protocol family 31
[   27.579714] Bluetooth: HCI device and connection manager initialized
[   27.579722] Bluetooth: HCI socket layer initialized
[   27.579724] Bluetooth: L2CAP socket layer initialized
[   27.579727] Bluetooth: SCO socket layer initialized
[   27.915826] usbcore: registered new interface driver btusb
[   28.809993] nvidia: module license 'NVIDIA' taints kernel.
[   28.809997] Disabling lock debugging due to kernel taint
[   28.817945] nvidia: module verification failed: signature and/or  required key missing - tainting kernel
[   28.822576] vgaarb: device changed decodes: PCI:0000:05:00.0,olddecodes=io+mem,decodes=none:owns=none
[   28.822797] [drm] Initialized nvidia-drm 0.0.0 20140818 for 0000:05:00.0 on minor 0
[   28.822808] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  304.125  Mon Dec  1 19:58:28 PST 2014
[   28.961086] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[   29.025576] Linux video capture interface: v2.00
[   29.041314] hda-intel 0000:00:14.2: Using LPIB position fix
[   29.044765] hda-intel 0000:00:14.2: Enable sync_write for stable communication
[   29.086887] autoconfig: line_outs=1 (0x1c/0x0/0x0/0x0/0x0) type:line
[   29.086890]    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   29.086892]    hp_outs=1 (0x1d/0x0/0x0/0x0/0x0)
[   29.086893]    mono: mono_out=0x0
[   29.086893]    dig-out=0x20/0x21
[   29.086894]    inputs:
[   29.086895]      Rear Mic=0x1a
[   29.086896]      Front Mic=0x1e
[   29.086897]      Line=0x1b
[   29.093036] input: HDA ATI SB Line Out as /devices/pci0000:00/0000:00:14.2/sound/card0/input8
[   29.093100] input: HDA ATI SB Line as /devices/pci0000:00/0000:00:14.2/sound/card0/input7
[   29.093150] input: HDA ATI SB Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input6
[   29.529996] usb_audio: Warning! Unlikely big volume range (=6144), cval->res is probably wrong.
[   29.530000] usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 768/6912/1<6>[   29.530175] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0819)
[   29.530176] usbcore: registered new interface driver snd-usb-audio
[   29.544602] input: UVC Camera (046d:0819) as /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/input/input9
[   29.544676] usbcore: registered new interface driver uvcvideo
[   29.544679] USB Video Class driver (1.1.1)
[   29.722834] Bluetooth: RFCOMM TTY layer initialized
[   29.722844] Bluetooth: RFCOMM socket layer initialized
[   29.722849] Bluetooth: RFCOMM ver 1.11
[   29.754136] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.754139] Bluetooth: BNEP filters: protocol multicast
[   29.754144] Bluetooth: BNEP socket layer initialized
[   29.979093] type=1400 audit(1419245960.958:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=760 comm="apparmor_parser"
[   29.979100] type=1400 audit(1419245960.958:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=760 comm="apparmor_parser"
[   29.979460] type=1400 audit(1419245960.958:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=760 comm="apparmor_parser"
[   30.301858] init: cups main process (761) killed by HUP signal
[   30.301866] init: cups main process ended, respawning
[   30.793555] init: failsafe main process (702) killed by TERM signal
[   31.075191] type=1400 audit(1419245962.050:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/share/gdm/guest-session/Xsession" pid=893 comm="apparmor_parser"
[   31.936605] audit_printk_skb: 177 callbacks suppressed
[   31.936609] type=1400 audit(1419245962.910:71): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cups-browsed" pid=1128 comm="apparmor_parser"
[   31.980423] type=1400 audit(1419245962.954:72): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=1132 comm="apparmor_parser"
[   31.984587] init: gdm main process (1057) killed by TERM signal
[   32.042350] init: samba-ad-dc main process (957) terminated with status 1
[   32.726469] r8169 0000:01:00.0 eth0: link down
[   32.726482] r8169 0000:01:00.0 eth0: link down
[   32.726509] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   32.726733] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   34.292370] r8169 0000:01:00.0 eth0: link up
[   34.292378] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   34.489379] r8169 0000:01:00.0 eth0: link down
[   34.489395] r8169 0000:01:00.0 eth0: link down
[   34.489405] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   34.490007] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   35.897357] init: smbd main process (690) killed by TERM signal
[   36.181980] r8169 0000:01:00.0 eth0: link up
[   36.181988] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   53.423150] NVRM: Your system is not currently configured to drive a VGA console
[   53.423154] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   53.423156] NVRM: requires the use of a text-mode VGA console. Use of other console
[   53.423157] NVRM: drivers including, but not limited to, vesafb, may result in
[   53.423158] NVRM: corruption and stability problems, and is not supported.
[   53.698124] init: plymouth-upstart-bridge main process ended, respawning
[   53.731551] init: plymouth-upstart-bridge main process (1829) terminated with status 1
[   53.731559] init: plymouth-upstart-bridge main process ended, respawning
[   60.124766] type=1400 audit(1419245990.327:73): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2487 comm="apparmor_parser"
[   60.124774] type=1400 audit(1419245990.327:74): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2487 comm="apparmor_parser"
[   60.125141] type=1400 audit(1419245990.327:75): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2487 comm="apparmor_parser"
[   64.400163] Guest personality initialized and is inactive
[   64.400206] VMCI host device registered (name=vmci, major=10, minor=57)
[   64.400207] Initialized host personality
[   64.437416] NET: Registered protocol family 40
[   65.375271] init: plymouth-stop pre-start process (3227) terminated with status 1
[  282.856431] systemd-hostnamed[4338]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 1205.314517] usb 1-2: new high-speed USB device number 3 using ehci-pci
[ 1205.454401] usb 1-2: New USB device found, idVendor=04b8, idProduct=084f
[ 1205.454413] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1205.454421] usb 1-2: Product: USB2.0 MFP(Hi-Speed)
[ 1205.454426] usb 1-2: Manufacturer: EPSON
[ 1205.454431] usb 1-2: SerialNumber: 4C41324B3033353783
[ 1205.460901] usb-storage 1-2:1.2: USB Mass Storage device detected
[ 1205.461083] scsi9 : usb-storage 1-2:1.2
[ 1205.614339] WARNING! power/level is deprecated; use power/control instead
[ 1205.742450] usblp 1-2:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x084F
[ 1205.742477] usbcore: registered new interface driver usblp
[ 1206.463032] scsi 9:0:0:0: Direct-Access     EPSON    Stylus Storage   1.00 PQ: 0 ANSI: 2
[ 1206.463818] sd 9:0:0:0: Attached scsi generic sg7 type 0
[ 1206.475164] sd 9:0:0:0: [sdg] Attached SCSI removable disk
[ 1228.873060] usblp0: removed
[ 1271.471435] usblp 1-2:1.1: usblp0: USB Bidirectional printer dev 3 if 1 alt 0 proto 2 vid 0x04B8 pid 0x084F
[22444.308785] systemd-hostnamed[8329]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
I read on the web that there is a bug about the DBUS, but I didn't understand if there is a fix.

So, any suggestion about how I could try to fix my problem?
Thanks

Claudio
Attached Thumbnails
Click image for larger version

Name:	2014-12-19 08.41.44.jpg
Views:	223
Size:	102.7 KB
ID:	17184  
Attached Files
File Type: txt syslog.txt (123.7 KB, 82 views)
 
Old 01-08-2015, 11:15 PM   #2
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Hi:

I did several searches and I found, just like you that this is a bug.
https://bugs.launchpad.net/ubuntu/+s...s/+bug/1363355

In this thread the member made a change to his rc.conf file. Maybe try it and see if it helps.
https://bbs.archlinux.org/viewtopic.php?id=93840

Update to the most current version of dbus and see if that works.
http://www.freedesktop.org/wiki/Software/dbus/

This member solved the dbus problem by reinstalling his distriubution.
I would put that as the last thing on the to do list.
http://ubuntuforums.org/showthread.php?t=1831509

DBUS session bus needs to write into ~/.dbus (because it is a session bus)
http://www.linuxquestions.org/questi...em-4175420825/

The last article I was able to find is that if 'dbus is owned by root' that can be a possible problem.
http://askubuntu.com/questions/13557...install-or-fix

I hope that helps.-
 
Old 01-10-2015, 02:06 AM   #3
dr_berta
Member
 
Registered: Sep 2005
Location: Carpi (Modena) - Italy
Distribution: Ubuntu 20.04_x86_64 LTS; Slackware 13 64bit; Gentoo, Fedora, Yocto
Posts: 77

Original Poster
Rep: Reputation: 1
Thanks Ztcoracat for your help.

I've finally solved the problem. I found that the dbus problem was a consequence of the real problem.
The origin of the problem was a usb driver of a peripheral requiring a new compilation after a kernel upgrade. In the past it never required a new compilation, but with one of the last kernel upgrades something has been changed creating an incompatibility with the driver.

So, I can put solved the thread.

Claudio
 
1 members found this post helpful.
Old 01-10-2015, 12:22 PM   #4
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by dr_berta View Post
Thanks Ztcoracat for your help.

I've finally solved the problem. I found that the dbus problem was a consequence of the real problem.
The origin of the problem was a usb driver of a peripheral requiring a new compilation after a kernel upgrade. In the past it never required a new compilation, but with one of the last kernel upgrades something has been changed creating an incompatibility with the driver.

So, I can put solved the thread.

Claudio
Your Welcome-

What was the indication that made you suspicious of the driver and compilation or should I say; re-compilation was necessary?
 
Old 01-10-2015, 05:36 PM   #5
dr_berta
Member
 
Registered: Sep 2005
Location: Carpi (Modena) - Italy
Distribution: Ubuntu 20.04_x86_64 LTS; Slackware 13 64bit; Gentoo, Fedora, Yocto
Posts: 77

Original Poster
Rep: Reputation: 1
I reviewed the problem from the beginning.
So, I saw that the error was starting just after the login, but the message was saying that there was a problem with password... strange.
Then I tried to access to the system without the graphic, but in this case, just after the login, I received a double request of password from sudo.
At this point I tried to identify what was requiring a root permission to work and finally I identified a script that, after the login, was starting the usb driver of a peripheral.
The idea to rebuild the driver has been suggested me by the VMware virtual machines behavior: every time the kernel changes you have to rebuild it (but in this case it is done automatically).

Basically the error message was saying correctly the place of the problem (the scrpit was located in /etc/profile), but was indicating a wrong reason for the error. This created some confusion instead to help me.

Claudio
 
Old 01-10-2015, 06:34 PM   #6
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
every time the kernel changes you have to rebuild it (but in this case it is done automatically).
Right, I agree.

I see where the error created confusion. Sorry you had to go through that.

Glad that everything is working correctly now.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Gnome Terminal 3.14 - Couldn't Register with Accessibility Bus zetrotrack000 Linux - General 1 10-12-2014 03:09 AM
Had an error message that something couldn't start because the tmp file was full..... steve513 Mandriva 5 08-06-2009 12:08 PM
ubuntu login error accessibility app error exception during registry activatin from a jennyund Linux - Newbie 1 06-22-2009 08:35 PM
i couldn't figure out error message hibudd Linux - Software 1 03-26-2007 10:26 AM
fluxbox Error: couldn't connect to xserver Furlinastis Slackware 4 09-22-2005 07:20 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop

All times are GMT -5. The time now is 06:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration