Error installing policykit-gnome due to gconf schema issue

Drake, Richard R rrdrake at sandia.gov
Fri Oct 22 10:22:47 PDT 2010


Hello,

I've been trying to install policykit-gnome from scratch for a while now and
for the last few weeks, get an error.  I wonder if someone knows a fix. Here
is what I do:

 % sudo port -f uninstall installed
 % sudo port selfupdate
 % sudo port install policykit-gnome

It gets all through the dependencies but fails activating policykit-gnome.
Here is the error:

...
--->  Building gconf
--->  Staging gconf into destroot
--->  Installing gconf @2.28.1_0
--->  Activating gconf @2.28.1_0
--->  Cleaning gconf
--->  Installing policykit-gnome @0.96_0
--->  Activating policykit-gnome @0.96_0
Error: Target org.macports.activate returned: shell command failed
Log for policykit-gnome is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.
org_release_ports_gnome_policykit-gnome/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>


The end of the log file shows

:debug:activate activating directory:
/opt/local/share/locale/zh_TW/LC_MESSAGES
:debug:activate activating file:
/opt/local/share/locale/zh_TW/LC_MESSAGES/polkit-gnome-1.mo
:debug:activate Executing
proc-post-org.macports.activate-activate-0:info:activate I/O warning :
failed to load external entity
"/opt/local/etc/gconf/schemas/*.schemas":info:activate Failed to open
`/opt/local/etc/gconf/schemas/*.schemas': No such file or directory
:info:activate shell command "export GCONF_CONFIG_SOURCE=`gconftool-2
--get-default-source` &&  gconftool-2 --makefile-install-rule
/opt/local/etc/gconf/schemas/*.schemas" returned error 1
:error:activate Target org.macports.activate returned: shell command failed
:debug:activate Backtrace: shell command failed
    while executing
"$post $targetname"
:info:activate Warning: the following items did not execute (for
policykit-gnome): org.macports.activate
:notice:activate Log for policykit-gnome is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.
org_release_ports_gnome_policykit-gnome/main.log


Anybody have ideas?  It seems like the trac ticket system requires an
account now, so I don't know how to inform the package maintainers of a
problem.

Thanks,

-rich




More information about the macports-users mailing list