Bug#617663: iceweasel: Iceweasel does not save the previos settings at the next start.
Mike Hommey
mh at glandium.org
Thu Mar 10 13:27:35 UTC 2011
On Thu, Mar 10, 2011 at 07:05:14PM +0700, Sthu Deus wrote:
> Package: iceweasel
> Version: 3.5.16-5
> Severity: normal
>
> Iceweasel does not save the previos settings at the next start. For
> example, if I set on the off-line mode and quit iceweasel, then, next
> time I start it - the option is turned off. And so on.
>
> Right after update the iceweasel, at the very first start, I see a
> window stating:
>
> 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: Failed to connect to
> socket /tmp/dbus-lTnDnN2Xrg: Connection refused) 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: Failed to connect to
> socket /tmp/dbus-lTnDnN2Xrg: Connection refused) 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: Failed to connect to
> socket /tmp/dbus-lTnDnN2Xrg: Connection refused) 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: Failed to connect to
> socket /tmp/dbus-lTnDnN2Xrg: Connection refused)
>
> I run iceweasel under another user using
>
> /usr/bin/gksu -u user iceweasel %u
Then the dbus messages are not surprising. But mostly harmless. Note
that preferences are not saved through dbus/gconf, but in Iceweasel's
own configuration.
When you set Iceweasel off-line, can you go to the about:config url and
check the browser.offline value? After quitting, can you check
/home/user/.mozilla/firefox/$profile/prefs.js and see if it contains
browser.offline and its value?
Thanks
Mike
More information about the pkg-mozilla-maintainers
mailing list