Page 1 of 1

D-Bus error suddenly started appearing

Posted: 2017/02/17 17:20:04
by cosmicjohn
I am using Centos 7

Code: Select all

uname -a
Linux MRT-des1 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I wasn't having any problems running KDE apps from a remote laptop. All of a sudden, after a reboot every KDE app starts showing a D-BUS error. I can get past it by using dbus-launch, but I am trying to figure out what set this off in the first place and how to fix it. The error I see is

Code: Select all

# konsole &
# unnamed app(10856): KUniqueApplication: Cannot find the D-Bus session server:  "Failed to connect to socket /tmp/dbus-KWEue9OGmU: Connection refused" 

unnamed app(10855): KUniqueApplication: Pipe closed unexpectedly.
I haven't changed anything in the system configuration, haven't added any new software, done any updates or anything. All I did was poweroff the machine one day, reboot it the next day and lo and behold this issue.

Any help would be highly appreciated.

Re: D-Bus error suddenly started appearing

Posted: 2017/02/17 18:04:06
by TrevorH
What's the output from ls -ld /tmp ?

You're not running the latest CentOS - your kernel is from sometime in 7.2 and 7.3 is current and has been for about 3 months. You should yum update everything sooner rather than later as no fixes have been produced for 7.2 since 7.3 came out at the start of December.

Re: D-Bus error suddenly started appearing

Posted: 2017/02/17 18:17:05
by cosmicjohn

Code: Select all

]# ls -ld /tmp
drwxrwxrwt. 10 root root 4096 Feb 17 12:58 /tmp
I guess I could update the install, but its a bit of a hassle. We're Department of Defense contractors and a "yum update" is a nightmare because these machines aren't connected to the external world. Even getting a CD or DVD into the lab poses security nightmares after a machine is certified. I could load up a new machine, have it certified and such - that takes a little bit less than an act of Congress.

The real question is why did this start happening all of a sudden, and only on the one machine?