Hai cercato la traduzione di corba da Inglese a Malese

corba factory
kilang corba

custom corba poa
poa corba suai

corba error: %s
ralat corba: %s

corba cosnaming service.
perkhidmatan cosnaming corba.

provides a corba scripting interface
membekal antaramuka pengskripan corba

couldn't interpret corba value for list element
tak dapat mentafsirkan nilai corba bag unsur senarai

the item could not be deleted due to a corba error
item tidak dapat dihapuskan disebabkan oleh ralat corba

a corba error occurred whilst accessing the address book.
terdapat ralat terjadi apabila corba sementara mengakses buku alamat.

the event could not be deleted due to a corba error
peristiwa tidak dapat dihapuskan disebabkan oleh ralat corba

adding client to server's list failed, corba error: %s
penambahan klien ke senarai pelayan gagal, ralat corba: %s

couldn't make sense of corba value received in set request for key `%s'
tidak dapat nilai corba yang munasabah diterima dalam permintaan set kekunci '%s'

unable to store a value at key '%s', as the configuration server has no writable databases. there are some common causes of this problem: 1) your configuration path file %s/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so nfs file locking doesn't work in your home directory or 4) your nfs client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. if you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. if you have stale locks, remove ~/.gconf*/*lock. perhaps the problem is that you attempted to use gconf from two machines at once, and orbit still has its default configuration that prevents remote corba connections - put "orbiiopipv4=1" in /etc/orbitrc. as always, check the user.* syslog for details on problems gconfd encountered. there can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
tidak boleh menyimpan nilai pada kekunci '%s', sebagai pelayan konfigurasi yang tidak mempunyai pengkalan data boleh tulis. terdapat beberapa nilai umum bagi masalah ini: 1)fail laluan konfigurasi anda %s/path tidak mengandungi sebarang pengkalan data atau tidak ditemui 2) kadangkala kami tersalah cipta dua proses gconfd 3) sistem operasi anda tersalah konfigur jadi penguncian fail nfs tidak berfungsi didalam direktori rumah anda atau 4) mesin klien nfs anda mengalami kerosakan dan tidak maklumkan pelayan dengan betul semasa but semula fail yang patut dilepaskan. jika anda mempunyai dua proses gconfd (atau mempunyai dua pada saat dilancarkan), penfaftaran keluar, mematikan semua salinan gconfd, dan pendaftaran kembali mungkin boleh membantu. jika anda mempunyai penguncian lapuk, buang ~/.gconf*/*lock. kemungkinan masalahnya anda cuba gunakan gconf dari dua mesin pada masa yang sama, dan orbit masih mempunyai konfigurasi lalai yang mana ia menghalang sambungan corba jauh - jadi masukkan "orbiiopipv4=1" didalam /etc/orbitrc. seperti kebiasaannya, semak user.*syslog untuk perincian masalah gconfd hadapi. hanya satu gconfd setiap direktori rumah, dan ia mesti memiliki lockfile didalam ~/.gconfd dan juga lokasi storan lockfile seperti ~/.gconf