Hi Geoff On Fri, 30 Nov 2001 17:28:01 +0000, Geoff wrote:
Just checking ... by "didn't change anything" you mean that dampsquib still reports "Gtk-WARNING **: cannot open display" - correct?
I think that was my mistake. I was assuming that # would rem lines out. When I removed all the # lines it did not re appear.
It seems that ip-up is never completing, even when we move the firestarter stuff into the ip-up.local script - which is not entirely surprising if there is some problem starting firestarter from the script. The easy test for the correctness of that is to try to log on to your ISP when ip-up.local has failed. Presumably you can't and also presumably running ifconfig does not reveal the presence of ppp0.
Assuming that when Firestarter is called from local and does not start is a failure, then the connection proceeds and is firewalled. As I understand it, it falls back to the Suse firewall. When F/s loads it replaces Suse.
Who owns the firestarter executable? ls-l /full/path/to/firestarter should give the answer (second column of the output). If it is root then you could, as root,
. That should allow other users to run it. If the owner is not root, then and then .
ls-l /full/path/to/firestarter That gives command not found, however I would expect it to be root since you cannot access Firestarter from user. In the file properties from Konqueror it show Ownership as root for User and Group.
I don't suppose that there is any harm in reinstallation - though the cynical money is on it making no difference.
You are probably right, but sometimes it works. Have you ever taken items apart when they don't work - can't find anything wrong, but start it and it works.
Keep smiling, there *is* a way to do this.
Yes, I've got it selotaped in position :) Thanks Regards, David