http://bugzilla.novell.com/show_bug.cgi?id=548605 http://bugzilla.novell.com/show_bug.cgi?id=548605#c3 --- Comment #3 from Harald Koenig <koenig@linux.de> 2009-11-19 23:23:49 UTC --- (In reply to comment #2)
Isn't this just the non-delayed suseconfig problem?
gconftool-2 sucks especially if it is executed for each gnome package being installed. openSUSE avoids this in CD installation (in YaST, more precisely) by setting YAST_IS_RUNNING env. variable, and packages are hacked to avoid runing suseconfig (which in turn runs gconftool). Then YaST executes suseconfig only once, at the end of installation.
my update was started via boot from NET-CD and yast did the update (totally standard)! YAST_IS_RUNNING is not evaluated at all in compiz scripts: rpm -q --scripts compiz | grep YAST_IS_RUNNING "rpm -qa --scripts" shows YAST_IS_RUNNING being used for some SuSEconfig.fonts calls and other stuff, but I can't find any flagged calls to gconftool-2 am I missing something, or is that YAST_IS_RUNNING flag missing for gconftool-2 issues ?
In the meantime, use the workaround described at http://en.opensuse.org/Upgrade/Supported#Known_Issues (the one with YAST_IS_RUNNING) if needed (and vote for the feature in fate :O).
thanks for this pointer, I'll keep it in mind for "zypper dup", but in my case yast *was* running! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.