Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34588 - [roundcubemail-0.9rc2-1] Error 500 with nginx

Attached to Project: Community Packages
Opened by Antoine (AntoineVe) - Wednesday, 03 April 2013, 15:26 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 16 April 2013, 14:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After updating to roundcubemail 0.9rc2, I get only a blank page. No error log in nginx, just a 500 return code on access log :

> 0000:IPv6:blah::blah::blah: - - [03/Apr/2013 17:02:04 +0200] "GET / HTTP/1.1" 500 5 "-" "Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0"

Downgrading to roundcubemail 0.8.5 resolve the problem.

*I know it maybe an upstream bug but this package have to stay in testing IMHO*

Additional info:
nginx 1.2.8 from « nginx-1.2.8-1-i686.pkg.tar.xz »
php-fpm 5.4.13 from « php-fpm-5.4.13-3-i686.pkg.tar.xz »

Steps to reproduce: Update from « roundcubemail-0.8.5-1-any.pkg.tar.xz» to « roundcubemail-0.9rc2-1-any.pkg.tar.xz ».
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 16 April 2013, 14:08 GMT
Reason for closing:  Fixed
Comment by Antoine (AntoineVe) - Wednesday, 03 April 2013, 15:34 GMT
From http://roundcube.net/download : 0.9rc2 is a beta release, while 0.8.6 is the stable version. Why not provide 0.8.6 instead of 0.9rc2 ?
Comment by Jelle van der Waa (jelly) - Friday, 05 April 2013, 08:57 GMT
It would indeed be usefull to stay with roundcube 0.9.8 as it's stable.
Comment by Sergej Pupykin (sergej) - Friday, 05 April 2013, 10:06 GMT
I put it because of sqlite3 support.

Did not use it with nginx, but it works well for me in apache.
Comment by Antoine (AntoineVe) - Friday, 05 April 2013, 17:35 GMT
I think it's more a php-fpm issue than nginx... I still trying to debug that, discussing with the upstream team.
Comment by Sergej Pupykin (sergej) - Tuesday, 16 April 2013, 14:07 GMT
Updated to 0.9 stable. Closing this bug.

Loading...