Re: [gnome-db]Problem running gnomedb-mgr



>>I have installed gnome-db on two helix gnome Linux boxes (one RH7 and one
>>heavily upgraded RH6.2), and both exhibit the same problem.  The packages
>>install OK,  but attempt to run gnomedb-mgr (which is the GUI configuration
>>tool, yes?) simply hang.  It displays no messages and will sit there
>>forever. I'm stumped.
>>open("/tmp/orbit-adam/reg.IDL:OAF_ObjectDirectory:1.0-local", O_RDONLY) = -1
>>ENOENT (No such file or directory)
>>open("/tmp/orbit-adam/reg.IDL:OAF_ObjectDirectory:1.0", O_RDONLY) = -1
>>ENOENT (No such file or directory)
>I'm not sure, but i suppose there are two possibilities:
>- Your oaf installation is broken

I did a "--force" reinstall of the oaf RPM.  Situtation has not changed.

>You need to reinstall oaf, possibly oaf dependent software.
>- The .oafinfo files of libgda/gnome-db have been installed into a
>directory other than those of your oaf installation
>If you are sure your oaf-installation is o.k. (e.g. other oaf based 
>applications work), 

Nautilus PR3 works,  I got the oaf RPM from their site.

>simply locate e.g. OAF_naming-service.oaf and

Hmmm,  I can't find a file with that name anywhere..

>move/copy all gda .oaf/.oafinfo files into the dir where you've found it.

the gda RPM doesn't contain any *.oaf* files,  all the ones I can find come from
gnome-db.  Is this normal?  They are in /usr/share/oaf along with the
Nautilus*.oaf files.

open("/tmp/orbit-adam/oaf-register.lock", O_RDONLY|O_CREAT, 0700) = 9
fcntl64(9, F_SETFD, FD_CLOEXEC)         = 0
getpid()                                = 12393
fcntl64(9, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=1}) = 0
brk(0x809d000)                          = 0x809d000
open("/tmp/orbit-adam/reg.IDL:OAF_ObjectDirectory:1.0-local", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/tmp/orbit-adam/reg.IDL:OAF_ObjectDirectory:1.0", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/tmp/orbit-adam/reg.IDL:OAF_ActivationContext:1.0-local", O_RDONLY) = 10

This section of strace indicates that it opens
"/tmp/orbit-adam/reg.IDL:OAF_ActivationContext:1.0-local", but that
"reg.IDL:OAF_ObjectDirectory:1.0-local" and "reg.IDL:OAF_ObjectDirectory:1.0"
fail.  Are these diffrent possible names for the same file or do
-ObjectDirectory- files and -ActivationContext- files have diffrent purposes?

Systems and Network Administrator
Morrison Industries
1825 Monroe Ave NW.
Grand Rapids, MI. 49505




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