evolution-alarm-notifty crash: Failed to connect to socket

Asked by Juan Simón on 2009-04-24

Binary package hint: evolution

Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite activar TCP/IP en ORBit, o que tiene bloqueos de NFS debidos a una caída de sistema. Consulte http://www.gnome.org/projects/gconf/ para más información. (Detalles - 1: Falló al obtener la conexión con la sesión: Failed to connect to socket /tmp/dbus-gUWrap2KvL: Conexión rechazada)

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: evolution 2.26.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux 2.6.28-11-server i686

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu evolution Edit question
Assignee:
No assignee Edit question
Solved by:
Juan Simón
Solved:
2009-04-24
Last query:
2009-04-24
Last reply:
2009-04-24
Juan Simón (simonbcn) said : #1
Sebastien Bacher (seb128) said : #2

the description is not in english changing to a question

Juan Simón (simonbcn) said : #3

That's the original error message of my Ubuntu.

Traduction (Google Traductor):

Failed to contact server configurations, some of the possible causes are that you need to enable TCP/IP in ORBit or it have NFS locks due to a system drop. See http://www.gnome.org/projects/gconf/ for more information. (Details - 1: Failed to get connection to session: Failed to connect to socket / tmp/dbus-gUWrap2KvL: Connection refused)

Better now?

Sebastien Bacher (seb128) said : #4

it seems to indicate an user configuration issue and not a bug now, changing back to a question

Juan Simón (simonbcn) said : #5

configuration issue!!??
It worked fine until a few days ago due to some actualization.

Juan Simón (simonbcn) said : #6

Thanks for nothing!

Juan Simón (simonbcn) said : #7

Solved.
Is it not an error when a program is updated and doesn't check for configuration to avoid this errors?