gconf-editor

Bug #292852 reported by rext

This bug report was converted into a question: question #49976: gconf-editor.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gconf-editor (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gconf-editor

Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite habilitar TCP/IP en ORBit, o que tiene bloqueos de NFS de una caída de sistema. Vea http://www.gnome.org/projects/gconf/(Detalles - 1: Falló al obtener la conexión con la sesión: 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.)
Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite habilitar TCP/IP en ORBit, o que tiene bloqueos de NFS de una caída de sistema. Vea http://www.gnome.org/projects/gconf/(Detalles - 1: Falló al obtener la conexión con la sesión: 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.)
Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite habilitar TCP/IP en ORBit, o que tiene bloqueos de NFS de una caída de sistema. Vea http://www.gnome.org/projects/gconf/(Detalles - 1: Falló al obtener la conexión con la sesión: 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.)
Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite habilitar TCP/IP en ORBit, o que tiene bloqueos de NFS de una caída de sistema. Vea http://www.gnome.org/projects/gconf/(Detalles - 1: Falló al obtener la conexión con la sesión: 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.)
Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite habilitar TCP/IP en ORBit, o que tiene bloqueos de NFS de una caída de sistema. Vea http://www.gnome.org/projects/gconf/(Detalles - 1: Falló al obtener la conexión con la sesión: 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.)
Falló al contactar con el servidor de configuraciones; algunas de las posibles causas son que necesite habilitar TCP/IP en ORBit, o que tiene bloqueos de NFS de una caída de sistema. Vea http://www.gnome.org/projects/gconf/(Detalles - 1: Falló al obtener la conexión con la sesión: 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.)

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gconf-editor
NonfreeKernelModules: nvidia
Package: gconf-editor 2.24.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_MX.UTF-8
SourcePackage: gconf-editor
Uname: Linux 2.6.27-7-generic x86_64

Tags: apport-bug
Revision history for this message
rext (tropi78) wrote :
Changed in gconf-editor:
importance: Undecided → Low
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.