Bug 915046
| Summary: | Newly installed schema values are not visible until gconfd-2 is restarted | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | darton <temp-2009-09-09> |
| Component: | GConf2 | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | bnocera, cfergeau, gatlinsullivan, justin, luzemail, mstuff, phinaliumz, raul_chirea, rodd, rstrode, stickster, thughes, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:5ff793d8aa2e5b06e19182b8c1bad1ff8cee15fa | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 755954 | Environment: | |
| Last Closed: | 2013-04-25 00:43:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
darton
2013-02-24 11:58:03 UTC
The problem is still present in Fedora 18. I confirm, after doing fresh install of Fedora 18, with LXDE as desktop, sound-juicer crashes on first run with baseuri_changed_cb: Process /usr/bin/sound-juicer was killed by signal 11 (SIGSEGV) However, after rebooting sound-juicer works fine. Its definetly Fedora bug, I tried both upstream tar.gz and Fedora package, both crash on first run, I also tried installing the same upstream version (3.5) to another Linux distro, and it didn't crash there. I commented earlier that after reboot sound-juicer works fine. One doesn't need to reboot, just logout/login is enough. Sound-juicer crashes on SIGSEGV, because GConfEntry *entry on sj-main.c:1855 is NULL before reboot/logout. If one adds checks in each of gconf notify functions (baseuri_changed_cb, device_changed_cb, open_changed_cb etc, sj-main.c:1704-1713) about *entry being NULL, that fixes this problem. However, thats not very elegant fix. This problem affects both i686 and x86_64. I don't know (atleast not yet) enough about GConf or C to fix this, any help? (In reply to comment #3) > Sound-juicer crashes on SIGSEGV, because GConfEntry *entry on sj-main.c:1855 > is NULL before reboot/logout. If one adds checks in each of gconf notify > functions (baseuri_changed_cb, device_changed_cb, open_changed_cb etc, > sj-main.c:1704-1713) about *entry being NULL, that fixes this problem. > However, thats not very elegant fix. > > This problem affects both i686 and x86_64. I don't know (atleast not yet) > enough about GConf or C to fix this, any help? These entries should never be NULL as they are defined in sound-juicer schema. However, for some reason, even though the installation of the schema in sound-juicer.spec, gconftool-2 -a /schemas/apps/sound-juicer is empty after installing the package :( *** Bug 890193 has been marked as a duplicate of this bug. *** When installing sound-juicer on a machine where it has never been installed, "gconftool -a /schemas/apps/sound-juicer" is empty until a "killall -SIGUSR2 gconfd-2". Since sound-juicer expects these values to be set as they are in the gconf schema, this causes it to crash at startup. This used to be handled by http://pkgs.fedoraproject.org/cgit/GConf2.git/tree/GConf-2.18.0.1-reload.patch?h=f14 which has been dropped. Rebuilding GConf 3.2.5 with this patch applied makes thing work as expected. The SIGTERM causes gconfd-2 to restart, while it seems SIGUSR2 is enough and causes gconfd-2 to see the new schemas entries, no idea why though as I couldn't find doc/code to support that claim. In short, please readd http://pkgs.fedoraproject.org/cgit/GConf2.git/tree/GConf-2.18.0.1-reload.patch?h=f14 to GConf2 in all branches. GConf2-3.2.6-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/GConf2-3.2.6-4.fc19 Package GConf2-3.2.6-4.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing GConf2-3.2.6-4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5686/GConf2-3.2.6-4.fc19 then log in and leave karma (feedback). GConf2-3.2.6-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/GConf2-3.2.6-2.fc18 Package GConf2-3.2.6-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing GConf2-3.2.6-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5943/GConf2-3.2.6-2.fc18 then log in and leave karma (feedback). GConf2-3.2.6-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Took me a bit of time to test, but the -2 package is indeed working as I expect with sound-juicer schemas, thanks! GConf2-3.2.6-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/GConf2-3.2.6-6.fc19 GConf2-3.2.6-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |