Sponsored Content
Top Forums UNIX for Beginners Questions & Answers D-Bus: Failed to connect to socket Post 302960374 by Azrael on Saturday 14th of November 2015 01:53:08 PM
Old 11-14-2015
D-Bus: Failed to connect to socket

I'm trying a new distro called KaliBang. After the install I noticed this error is having problems letting multiple applications I have work:

Code:
(nm-applet:3674): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


** (nm-applet:3674): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Here are the current dbus packages I have installed:

Code:
# dpkg -l | grep dbus
ii  at-spi2-core                              2.5.3-2                            i386         Assistive Technology Service Provider Interface (dbus core)
ii  dbus                                      1.6.8-1+deb7u6                     i386         simple interprocess messaging system (daemon and utilities)
ii  dbus-x11                                  1.6.8-1+deb7u6                     i386         simple interprocess messaging system (X11 deps)
ii  libaudclient2:i386                        3.2.4-1                            i386         audacious dbus remote control library
ii  libdbus-1-3:i386                          1.6.8-1+deb7u6                     i386         simple interprocess messaging system (library)
ii  libdbus-glib-1-2:i386                     0.100.2-1                          i386         simple interprocess messaging system (GLib-based shared library)
ii  libdbusmenu-qt2                           0.9.0-1                            i386         Qt implementation of the DBusMenu protocol
ii  libnet-dbus-perl                          1.0.0-1+b1                         i386         Extension for the DBus bindings
ii  libqt4-dbus:i386                          4:4.8.2+dfsg-11                    i386         Qt 4 D-Bus module
ii  libqtdbus4:i386                           4:4.8.2+dfsg-11                    i386         Qt 4 D-Bus module library
ii  padbuster                                 0.3.3-1kali1                       all          Script for performing Padding Oracle attacks
ii  python-dbus                               1.1.1-1                            i386         simple interprocess messaging system (Python interface)
ii  python-dbus-dev                           1.1.1-1                            all          main loop integration development files for python-dbus
ii  qdbus                                     4:4.8.2+dfsg-11                    i386         Qt 4 D-Bus tool

I tried reinstalling X as one forum suggest worked for others. That just seem to break X for me though. The /var/run/dbus is present, but empty:

Code:
ls -la /var/run/dbus/
total 0
drwxr-xr-x  2 messagebus messagebus  40 Nov 14 01:37 .
drwxr-xr-x 12 root       root       340 Nov 14 01:37 ..

Tried a few other suggestions online, but nothing so far has worked. Any suggestions welcome.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Connect failed: No Devices Available

After installing an internal fax modem I get the message above when using the cu -l /dev/tty1A command. Any help would be most appreciated to the cu command to work again. Thanks. (3 Replies)
Discussion started by: cfaiman
3 Replies

2. Programming

connect() function in C++ socket programming

Hello All, I have a problem using connect(...) function in C++. I am using SSH from my windows system to connect it to linux server. The program works fine if I run it directly in Linux machine but I need it to run through windows machine. The function returns -1 and so my program terminates. ... (3 Replies)
Discussion started by: smdhd3
3 Replies

3. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

4. Programming

connect() socket API

Is there any relation between the connect() socket API and the TCP's Transmission Control Block. Also how does connect detect that a socket is in use i.e., EADDRINUSE (1 Reply)
Discussion started by: sunaina
1 Replies

5. Solaris

Error message : socket failed...

Dear All, I have server with SunOS 5.10 Generic_127111-06 sun4v sparc SUNW,SPARC-Enterprise-T5120, always coming out error message like this : May 25 10:37:26 sshd: fatal: Read from socket failed: Connection reset by peer So what happend with my server..??? Best Regards Bejo :D (2 Replies)
Discussion started by: mbah_jiman
2 Replies

6. UNIX for Dummies Questions & Answers

fatal: Read from socket failed: Connection reset by peer

I get this error when I log in through console: "fatal: Read from socket failed: Connection reset by peer". Can you tell me what this is and why it happens, and how to stop it? Thank you. (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

7. UNIX for Dummies Questions & Answers

Cannot connect to socket

solaris client report "cannot to socket(code 25)" while trying to backup on veritas netbackup 6.5.5 server (1 Reply)
Discussion started by: EUGINIAM
1 Replies

8. Programming

Looping connect call for a non blocking socket

will there be any unexpected results on looping connect call for a non blocking socket to determine the connection based on error code. I am getting connection unsuccessful intermittently and so wondering whether is the timeout 500 millisec not sufficient or looping connect cause any unexpected. ... (7 Replies)
Discussion started by: satish@123
7 Replies

9. UNIX for Advanced & Expert Users

Fatal: Read from socket failed: Connection reset by peer [preauth]

Hello, I have recently updated my AIX machine from version 6.1.7.5 to 6.1.9.1 and i noticed that the errpt of the server is full of ssh messages like the one below: sshdprocess_id>]: fatal: Read from socket failed: Connection reset by peer Does anyone knows if this a known bug of the ssh... (15 Replies)
Discussion started by: omonoiatis9
15 Replies
dbus-send(1)							   User Commands						      dbus-send(1)

NAME
dbus-send - Send a message to a message bus SYNOPSIS
dbus-send [--system | --session] [--dest=name] [--help] [--print-reply] [--type=type] destination_object_path message_name [contents...] DESCRIPTION
The dbus-send command is used to send a message to a D-Bus message bus. There are two standard message buses: o systemwide message bus - Disabled and not supported on Solaris, but installed on many systems as the "messagebus" init service. o per-user-login-session message bus - Enabled and supported on Solaris, and started each time a user logs in. The --system and --session options direct dbus-send to send messages to the system or session buses respectively. If neither is speci- fied, dbus-send sends to the session bus. Nearly all uses of dbus-send must provide the --dest argument which is the name of a connection on the bus to send the message to. If --dest is omitted, no destination is set. See http://www.freedesktop.org/software/dbus/ for more information. OPTIONS
The following options are supported: --dest=name Specify the name of the connection to receive the message. --help Show help information on standard output and exit. --print-reply Block for a reply to the message sent, and print any reply received. --session Send to the session message bus (this is the default). --system Send to the system message bus. The system bus is disabled and unsupported on Solaris. --type=type Specify "method_call" or "signal" (defaults to "signal"). OPERANDS
The following operands are supported: destination_object_path The object path of the message to send must always be specified. message_name The name of the message to send must always be specified. contents Following arguments, if any, are the message contents (message arguments). These are given as a type name, a colon, and then the value of the argument. The possible type names are: string, int32, uint32, double, byte, bool- ean. (D-Bus supports more types than these, but dbus-send currently does not.) EXAMPLES
Example 1: How to use dbus-send with a sh-compatible shell to start the per-session bus daemon example% dbus-send --dest='org.freedesktop.ExampleName /org/freedesktop/sample/object/name org.freedesktop.ExampleInterface.ExampleMethod int32:47 string:'hello world' double:65.32 Note that the interface is separated from a method or signal name by a dot, though in the actual protocol the interface and the interface member are separate fields. EXIT STATUS
The following exit values are returned: 0 Application exited successfully >0 Application exited with failure FILES
The following files are used by this application: /usr/bin/dbus-send Executable for dbus-send ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWdbus | +-----------------------------+-----------------------------+ |Interface stability |Volatile | +-----------------------------+-----------------------------+ SEE ALSO
dbus-cleanup-sockets(1), dbus-daemon(1), dbus-launch(1), dbus-monitor(1), dbus-uuidgen(1), libdbus-glib-1(3), attributes(5) NOTES
For authorship information refer to http://www.freedesktop.org/software/dbus/doc/AUTHORS. Updated by Brian Cameron, Sun Microsystems Inc., 2007. dbus-send was written by Philip Blundell. Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/ SunOS 5.11 19 Nov 2007 dbus-send(1)
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy