Re: gconf gconf2 problem with Sarge

From: Paul Morgan (paulswm_at_earthlink.net)
Date: 11/29/03

  • Next message: Florian Ernst: "Re: Any news about python errors in unstable?"
    To: debian-user@lists.debian.org
    Date: Sat, 29 Nov 2003 14:33:52 -0500
    
    

    On Sat, 29 Nov 2003 12:22:36 -0600, Glen Snyder wrote:

    > I've had a few hiccups lately with Sarge (on a linux box named tracer),
    > that seem to be related to gconf and gconf2 which I first noticed when
    > trying to start Galeon.
    >
    > Any suggestions would be greatly appreciated.
    > Thanks,
    > Glen
    >
    > Both gconf processes seem to be running:
    >
    > tracer:/home/glen# ps jaxwww | grep gconf
    > 1 431 402 402 ? -1 S 1000 0:01
    > /usr/lib/gconf2/gconfd-2 13
    > 2895 2966 2965 2792 ttyp0 2965 R 0 0:00 grep gconf
    >
    >
    > Here's whatI get in /var/log/messages/
    >
    > Nov 29 11:22:57 tracer gconfd (glen-2764): starting (version 2.4.0.1),
    > pid 2764 user 'glen'
    > Nov 29 11:22:57 tracer gconfd (glen-2764): Failed to get lock for
    > daemon, exiting: Failed to lock '/tmp/gconfd-glen/lock/ior': probably
    > another process has the lock, or your operating system has NFS file
    > locking misconfigured (Resource temporarily unavailable)
    > Nov 29 11:29:08 tracer gconfd (root-2866): starting (version 2.4.0.1),
    > pid 2866 user 'root'
    > Nov 29 11:29:08 tracer gconfd (root-2866): Resolved address
    > "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config
    > source at position 0
    > Nov 29 11:29:08 tracer gconfd (root-2866): Resolved address
    > "xml:readwrite:/root/.gconf" to a writable config source at position 1
    > Nov 29 11:29:08 tracer gconfd (root-2866): Resolved address
    > "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config
    > source at position 2
    > Nov 29 11:35:08 tracer gconfd (root-2866): GConf server is not in use,
    > shutting down.
    >
    > Also, if I try: "tracer:/home/glen# gconftool-1 --shutdown" I get:
    > Shutdown error: Failed to contact configuration server (a likely cause
    > of this is that you have an existing configuration server (gconfd)
    > running, but it isn't reachable from here - if you're logged in from two
    > machines at once, you may need to enable TCP networking for ORBit)

    This has been discussed in here the last few days, you should find the
    thread with a few minutees' browsing. Basically, Galeon is no longer in
    Sarge. I myself converted my bookmarks and moved to Firebird (I posted in
    here how to do that if you don't have Galeon running). There is also a
    post in here describing how to salvage the situation by having both gconfs
    running; as long as you don't remove Galeon expecting to be able to
    install it again (which is what I did) you should be OK.

    You say in your mail that both gconfs appear to be running, but the output
    from your ps shows only gconf2.

    -- 
    ....................paul
    "The average lifespan of a Web page today is 100 days. This is no way to
    run a culture."
    Internet Archive Board Chairman
    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Florian Ernst: "Re: Any news about python errors in unstable?"

    Relevant Pages

    • Re: Broken Galeon in Sarge
      ... claiming that it can't find a gconf ... I followed the instructions in the Galeon FAQ, ... reinstalling schema doesn't work. ... and also fixed some gconf problems with metacity and themes. ...
      (Debian-User)
    • Re: Broken Galeon in Sarge
      ... > It seems that the gconf2 I pulled from testing yesterday broke Galeon. ... gnome libs i don't use. ...
      (Debian-User)