Kolab 2.2RC1 PHP segfaults reading email with Horde

[Fabio Pietrosanti (naif)]

Today i installed a binary kolab distribution from:
http://ftp.belnet.be/packages/kolab/server/development-2.2/current/ix86-debian4.0

When i try to login in Horde something crash and the logs i have are the 
following:
==> apache-access.log <==
X - - [02/Mar/2008:17:34:06 +0100] "GET /horde/ HTTP/1.1" 302 26
X - - [02/Mar/2008:17:34:10 +0100] "GET 
/horde/login.php?Horde=df3cdcc1cd99396211bb8a6ca7be9364 HTTP/1.1" 200 2551
X - - [02/Mar/2008:17:34:10 +0100] "GET 
/horde/js/horde.js?Horde=df3cdcc1cd99396211bb8a6ca7be9364 HTTP/1.1" 200 4089
X - - [02/Mar/2008:17:34:10 +0100] "GET /horde/themes/screen.css 
HTTP/1.1" 200 16217
X - - [02/Mar/2008:17:34:10 +0100] "GET 
/horde/themes/graphics/locked.png HTTP/1.1" 200 505
X - - [02/Mar/2008:17:34:10 +0100] "GET 
/horde/themes/bluewhite/screen.css HTTP/1.1" 200 3042
X - - [02/Mar/2008:17:34:10 +0100] "GET 
/horde/themes/graphics/horde-power1.png HTTP/1.1" 200 2259
X - - [02/Mar/2008:17:34:11 +0100] "GET /horde/themes/safari.css 
HTTP/1.1" 200 307

==> apache-error.log <==
[Sun Mar 02 17:34:23 2008] [notice] child pid 5097 exit signal 
Segmentation fault (11)

I am not ever able to see any horde interface component, immediately 
after the log-in it crash.

This running on a Debian Etch inside a XEN machine (was a sarge, 
upgraded to etch).

Fabio

Troy Carpenter wrote:
> I have now tried a reinstall from scratch of Kolab 2.2RC1, and I am getting 
> the same results as before with php segfaults while reading some emails.
>
> This is from a clean source install of the openpkg version of Kolab.  My 
> machine is a 64bit Ubuntu Gutsy server.  There are no modified PHP/Apache 
> packages on the system.
>
> As before, when reading certain emails, firefox pops up a window wanting to 
> download a .php file.  Apache error log shows messages like this:
>
> [Thu Feb 28 01:33:47 2008] [notice] child pid 11230 exit signal Segmentation 
> fault (11)
> zend_mm_heap corrupted
>
> I don't know if it is something in the emails that is causing the problem, 
> whether that would be the character set or the email structure.
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>