You are not logged in.
Pages: 1
Since a recent update I get this error when starting firefox (even with a fresh new profile):
An error occurred while loading or saving configuration information for firefox. Some of your configuration settings may not work properly.
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon
)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon
)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon
)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon
)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: EOF in dbus-launch reading address from bus daemon
)
Offline
https://bugs.launchpad.net/musca/+bug/341219
System update with -Syu?
Offline
Yes, updated with -Syu. Maybe firefox needs rebuilding, as suggested in the bug report?
Offline
I have the same issue. I can't connect to dbus as a normal user. If i run dbus-daemon as user i get a segmentation fault, so dbus launch receives an EOF in dbus-launch reading address from bus daemon.
I tried reinstaling libstdc++5, coreutils, filesystem, expat, dbus, and dbus-core. Problem persists. The problem started after the last update, yesterday morning.
Offline
i found that running dmesg an error appears with libGL.so, so i tried removing nvidia drivers and now seems to work fine. Still, it is strange that it works for root but it doesn't as a regular user.
Offline
this is what i get in dmesg:
dbus-daemon[4205]: segfault at 6fdda5e0 ip b7e4d30c sp bfff1540 error 4 in libGL.so.185.18.31[b7e26000+80000]
mtrr: no MTRR for e0000000,10000000 found
mtrr: no MTRR for e0000000,10000000 found
mtrr: no MTRR for e0000000,10000000 found
dbus-daemon[7520]: segfault at c ip b7f475da sp bfaab9f0 error 4 in dbus-daemon (deleted)[b7f17000+46000]
dbus-daemon[25656]: segfault at 6ff545e0 ip b7f0a30c sp bfce1780 error 4 in libGL.so.185.18.31[b7ee3000+80000]
dbus-daemon[25785]: segfault at 6fda45e0 ip b7e3230c sp bfbd1730 error 4 in libGL.so.185.18.31[b7e0b000+80000]
dbus-daemon[25832]: segfault at 6ff325e0 ip b7ef930c sp bfd74a10 error 4 in libGL.so.185.18.31[b7ed2000+80000]
Offline
I tried switching back to the previous version of the nvidia drivers but nothing changed.
Offline
People on freedesktop gave me the answer. I had
export LD_PRELOAD=/usr/lib/libGL.so.1
in my .bashrc to fix the fullscreen bug that when switching flash content to fullscreen.
Offline
Pages: 1