[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Synaptic

El dom, 07-06-2009 a las 18:11 -0400, Tony Baldwin escribió:
> Miguel Angel wrote:
> > Buenas tardes, quisiera preguntar si es normal el que no pueda ver el
> > punto de menú para mi synaptic, ya que después de una actualización de
> > paquetes ya no he podido acceder synaptic a través del menú de sistema.
> > Pueden decirme si esto es algo normal o ocurrió un problema al haber
> > actualizado los paquetes?
> > 
> > 
> 
> Puede ser que lo has borrado por error mientras hiciste las actualizaciones.
> 
> ¿Has intentado buscarlo o prender por terminal?
> $ gksu synaptic # para iniciarlo

El error que sale al ejecutar este comando es:

GConf Error: 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: 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.)

GConf Error: 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: 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.)

GConf Error: 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: 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.)

> /tony
> 
> -- 
> http://www.baldwinsoftware.com
> free/open source software
> tcl yer os with a feather...
> 
>
Reply to: