Hello all,

i had finished, or so I thought, installing Squeeze and all components and suddenly iceweasel stopped working properly.

The only thing I did, is that i closed my laptop (which should have it hibernate) without closing iceweasel. Later when I reopened the laptop it seems that it shut down for some reason (battery power was OK). And now when I launch iceweasel (console or other) only part of a web page appear and I cannot do anything. That's if I am logged as normal user.

When I do the same as root, iceweasel works. Although I get another kind of problem with the following error message:

%%%%%%%%%%%%%%%%%%%
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.)
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.)
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.)
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.)
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.)
%%%%%%%%%%%%%%%%%

I reinstalled iceweasel and it still does the same...

any idea of what is wrong. I must mention that I have the feeling that the screen is not lit properly as if running on battery since that time.

I have a testing suggestion:

Create a new user, then log in as the new user and test Iceweasel.

If it works, that indicates that the problem is likely in the hidden Iceweasel files in your home folder, which I think are in ~/.mozilla.

The next step would be to login as your normal user, rename that hidden directory (.mozilla.old would be my choice), start Iceweasel and see if it works.

If it does, it will create a new ~/.mozilla directory. If you really want to nail down the cause of the problem, you could close Iceweasel, move ONE file back from the old directory to the new one, restart Iceweasel, and continue this one file at a time until you identify the culprit.

1 members found this post helpful.

Have you tried restarting dbus?

Thanks for your comments,

so I had reinstalled Dbus, I removed a link (following a post I read somewhere), and god I can't remember which link now but it was in one of the /.mozilla directory. And it works almost well... when I start iceweasel from the terminal and I get this message repeatedly:

%%%%%
(firefox-bin:3467): Gdk-WARNING **: XID collision, trouble ahead
%%%%%

because I have a terminal in the background, it's annoying and I have to open another terminal to do it so as to avoid these error messages on the screen.

So, I am now going to look at this error message!

Thanks for your comments they were helpful. If you have any idea for that gdk warning...


Best,

Googling on Gdk-WARNING **: XID collision, trouble ahead turns up a slew of bug reports. Most are for Ubuntu, but several also refer to Debian.