Awn

Failed to connect to socket /tmp/dbus - segmentation fault

Asked by craigyjack

This message appears when i try to launch avant. It was working fine one moment, then the next time i rebooted this appeared and I can't get it to work. I uninstalled it, and recompiled it (the repo isnt working anymore, so i compiled), and I still get this message.

This is almost exact to Question #22358, but that was marked as solved, so I didn't know if anyone would read the message I added to it, so I thought I would oopen a new question, because on that question he solved the problem himself and so I don't know what to do to solve this issue, or why it even happened.

Could someone let me know what I can do to solve this. I have no idea.

craig@craig-ubuntu:~$ avant-window-navigator

** (avant-window-navigator:18041): WARNING **: Failed to make connection to session bus: Failed to connect to socket /tmp/dbus-2Nv1V4hBd7: Connection refused

** (avant-window-navigator:18041): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

** (avant-window-navigator:18041): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

** (avant-window-navigator:18041): WARNING **: There was an error requesting the name:

** (avant-window-navigator:18041): CRITICAL **: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Segmentation fault (core dumped)
craig@craig-ubuntu:~$

Thanks,
Craig

Question information

Language:
English Edit question
Status:
Solved
For:
Awn Edit question
Assignee:
No assignee Edit question
Solved by:
craigyjack
Solved:
Last query:
Last reply:
Revision history for this message
Mark Lee (malept) said : 		#1

(Copied from the other question)

It means that there is no D-Bus daemon running for your desktop session,
or the D-Bus environment variable hasn't been updated. I've gotten this
because I run Awn via a GNU screen terminal, and when my X session
crashes and I re-login to X, a new D-Bus daemon is started, so I have to
update the DBUS_SESSION_BUS_ADDRESS environment variable to whatever the
new value is (I retrieve it by opening a new terminal window and running
`env | grep DBUS`).

Revision history for this message
craigyjack (craigyjack) said : 		#2

Thanks, but how do I set the BDUS_SESSION_BUS_ADDRESS environment variable back. and the value returned from the grep and the avant error message are the same /tmp/dbus-....... values there.

Revision history for this message
Mark Lee (malept) said : 		#3

did you open a totally new terminal?

Also, make sure that there's a dbus-daemon process running as your user. If there's no dbus-daemon with that constraint, I'd restart your X session (it's the cleanest way to get it working).

I find it odd that no other programs are being affected. Do you use pidgin, gnome-power-manager, or any other application that uses D-Bus?

Revision history for this message
craigyjack (craigyjack) said : 		#4

Another reboot got it working again. my computer was having some other problems unrelated to this as well (graphics hardware problems). But yeah, the gnome-settings-daemon was affected by that too. i hadnt booted up any other programs yet. but its all better now. my computer has been acting weird the past day, but i think she is all healed up now and not acting funky :)

Thanks guys.

Revision history for this message
craigyjack (craigyjack) said : 		#5

restarting my X session was crashing my whole computer :) but that related to the graphic hardware problem i believe. I got both of them fixed and after about the 15th turning off and on of my comptuer tonight everything looks good now