ufw problem (certainly down to gconf)

3xp10r3r|X13 · 10-16-2011, 02:43 PM

Hello there,
I shortly switched from slackware to debian, because I got really fed up with the not existing package manager. Surely, you can live with downloading everything manually and either extracting it or transforming it into a tgz package, but it's just not what I want. A great thing was the ability to sort of "build your own system".

But back to my current problem. I was looking for a nice stable distribution with a decent package manager and still room to do the stuff you want. Debian caught my I and I went on installing it. - No problem at all (way simpler than the slackware and arch installation process)

Well, after getting into the terminal and living out my desire to finally use a package manager again, I thought of setting up a firewall. Installing the program went well, as usual, but running it got me some trouble.

It doesn't really matter if I try to run firestarter of ufw (relating to ufw I went for the gufw). However I'm getting the following error messages:

ufw:

Code:

GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: 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.)

it gives me something similar, when I try to run firestarter.
What's wrong with the d-bus deamon? Or is it down to some other issue.

(just a bit upset, because everywhere I looked for debian, people said it would be damn stable etc.) - as I said, everything else is running fine...

I hope this is not a common issue. If so, please just forward me to the existing thread (I couldn't find a lot with google - the gconf thing though seems to be quite common but not relating to ufw. The firestarte error didn't give me any hits)

Every advice, suggestion or if possible the solution to this thread is very appreciated.

jschiwal · 10-16-2011, 04:40 PM

Quote:

after getting into the terminal

Are you logged into a terminal at the computer, or connected remotely? I think you chose a firewall configuration program with a graphical interface. Are you logged into gnome?

3xp10r3r|X13 · 10-17-2011, 01:00 PM

great, somebody answered!!!
well, as mentioned, I am using graphical interfaces in both cases (just launching them using the terminal) and yes, I am running gnome. No, I am not logged in remotely or something.

It is a fresh intall of Debian 6-something on a usual pc. Distributions, which ran just fine: Fedora, Opensuse, Arch-Linux, Slackware and probably most relating to Debian: Ubuntu.

It is a gnome issue isn't it? (because of the gconf error? )

again: I am trying to run firestarter and gufw (the graphical interface of the well known ufw)
If there is still additional information needed, please just ask. I am happy to answer anything to help you coming up with a solution.

jschiwal · 10-19-2011, 02:04 AM

It sounds like you are installing two firewall config tools. The Linux firewall is the kernel's Netfilter. It is configured with iptables commands. Firestarter and other web or GUI tools make it easier to define these rules. They often create a script on the fly based on networking values, such as from using DHCP or network manager. Two firewall tools may compete rather than complement each other, replacing the other tool's script.

Try launching the tool from the menu. The dbus is used for interprocess communication. Between programs, as well as well Policy Kit. The message about the dbus not running, I've seen after ssh'ing into my desktop, and the dbus related variables weren't set. Starting some graphical root programs may fail because root doesn't have access to the display. Using gnomesu may work. It may also exchange cookies or set environmental variables that X11, Policy or GConf need.

On my ssh problem in KDE, I added bash code in my .bashrc script to check for an ssh session and start a dbus session.