Okay, the patch is being applied with a significant offset but it still looks like it's going to the right place. I see that we're calling killall -TERM instead of killall -HUP in the patch. That seems non-optimal (since it means we'll keep shutting down the gconfd server instead of letting it use it's 30second timeout) But that shouldn't cause the problem we're seeing unless something's drastically wrong in the SIGTERM signal handler. The patch also doesn't invoke killall when makefile-uninstall-rule is invoked but that shouldn't be as much of an issue (just leaves unused data in the gconf server until it reloads.) It also shouldn't cause this issue. Anyone know why we haven't seen progress on the upstream bug? No one's raised any philosophical blockers with doing this: http://bugzilla.gnome.org/show_bug.cgi?id=328697 Colin, if no one's looking into fixing this bug there's two ways to workaround this bug: Change macros.gconf2 to run killall after the schemas are installed or uninstalled. This requires an update of the GConf2 package. We don't know which Fedora versions this affects yet (the guake update was for F13) Restore the packaging guideline suggestion to run killall -HUP gconfd-2 Since we don't know which versions this affects, we'd need to recommend it on all Fedora releases. What do you prefer? -Toshio
Attachment:
pgpc3sjM5tcPs.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
