Description of problem: Usage of zarafa-webaccess causes segmentation fault of httpd (via php-mapi): [Thu Feb 11 22:06:13 2010] [notice] core dump file size limit raised to 18446744073709551615 bytes [Thu Feb 11 22:06:13 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Thu Feb 11 22:06:13 2010] [notice] Digest: generating secret for digest authentication ... [Thu Feb 11 22:06:13 2010] [notice] Digest: done [Thu Feb 11 22:06:13 2010] [notice] Apache/2.2.13 (Unix) DAV/2 PHP/5.2.12 mod_ssl/2.2.13 OpenSSL/0.9.8k-fips configured -- resuming normal operations [Thu Feb 11 22:06:15 2010] [notice] child pid 15933 exit signal Segmentation fault (11), possible coredump in /tmp Version-Release number of selected component (if applicable): libmapi-6.30.10-1.fc11.x86_64 zarafa-monitor-6.30.10-1.fc11.x86_64 zarafa-server-6.30.10-1.fc11.x86_64 zarafa-ical-6.30.10-1.fc11.x86_64 php-mapi-6.30.10-1.fc11.x86_64 zarafa-6.30.10-1.fc11.x86_64 zarafa-dagent-6.30.10-1.fc11.x86_64 zarafa-debuginfo-6.30.10-1.fc11.x86_64 zarafa-spooler-6.30.10-1.fc11.x86_64 zarafa-gateway-6.30.10-1.fc11.x86_64 zarafa-utils-6.30.10-1.fc11.x86_64 zarafa-common-6.30.10-1.fc11.x86_64 zarafa-client-6.30.10-1.fc11.x86_64 zarafa-webaccess-6.30.10-1.fc11.noarch How reproducible: Everytime, see above, below and the attachment. Steps to Reproduce: 1. yum install zarafa zarafa-webaccess --enablerepo=testing 2. Configure MySQL 3. service httpd restart 4. Go to http://localhost/webaccess/ and get the error Actual results: Usage of zarafa-webaccess causes segmentation fault of httpd (via php-mapi) Expected results: No segmentation fault when php-mapi/zarafa-webaccess is used. Additional info: I'll attach a full backtrace from the core dump.
Created attachment 390353 [details] Full backtrace of the core dump
I've to correct myself: The crash happens when I try to login into webaccess. If I come then back again to the login page, the crash happens right away as it seems, because of the cookie or whatelse knows the session. A simple "cd /usr/share/zarafa-webaccess && php index.php" works fine. A simple PHP-MAPI script works (connect the Zarafa Server, fetch all calendar entries for today and show them) without crashing - and that via Apache & PHP. Looks like the login is doing something worse?!
The same is happening on Fedora 12.
Created attachment 395835 [details] Remerged changeset of Subversion Revision 18968 from 6.40.0 (trunk) to 6.30.10
zarafa-6.30.10-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.fc13
zarafa-6.30.10-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.fc12
zarafa-6.30.10-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.fc11
zarafa-6.30.10-2.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/zarafa-6.30.10-2.el5
zarafa-6.30.10-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2816
zarafa-6.30.10-2.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2010-2312
zarafa-6.30.10-2.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2010-2312
zarafa-6.30.10-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2816
zarafa-6.30.10-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2948
zarafa-6.30.10-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update zarafa'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-2958
zarafa-6.30.10-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/F11/FEDORA-2010-2958
zarafa-6.30.10-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2948
zarafa-6.30.10-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-6.30.10-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-6.30.10-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-6.30.10-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.