Bug#614717: Installation hangs at 'gconf-schemas --register-all --no-signal'

Francesco Poli invernomuto at paranoici.org
Fri Apr 15 19:57:29 UTC 2011


On Wed, 23 Feb 2011 00:43:57 +0000 Ben Hutchings wrote:

> I'm trying to rebuild shotwell, for which gconf2 is a build-dep.
> I really don't think installation is supposed to take this long:
> 
>  2785 root      20   0  7756  3972  1936 R 99.0  0.2  4:21.79 /usr/bin/python /usr/sbin/gconf-schemas --register-all --no-signal


Hello!

FWIW, I wasn't able to reproduce this bug.

I tried 

  # aptitude install gconf2

inside an updated sid chroot (managed by pbuilder).

Then I tried on a (real) wheezy machine, where gconf2 was pulled in as a
dependency of another package I was installing.

In both cases, the installation completed in very short times, without
anything strange.
Both cases were on amd64 architecture.

I hope my little contribution may be of help...
Bye.


-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20110415/5eaa9039/attachment-0001.pgp>


More information about the pkg-gnome-maintainers mailing list