[horde] Login/session problems with Horde 3, IMP4, & PHP 5.3

[Leonardo Boiko]

Thanks for the suggestions! display_errors only gives me a bunch of
deprecation warnings… And I’ve looked on apache, syslog, and horde
logs; the only thing I get is the “Login success” from imp via
imap/ssl.

I had not merged my php.ini (simply kept the old one), but I tried the
new package’s php.ini just now as well as yours, to no avail.  I also
just tried to disable SSL, thinking the http→https redirect might be
breaking the session somehow, but it also didn’t work.  Cleaning
/var/lib/php5 didn’t do anything. I’m running out of ideas :/

2012/1/5 Andrew Morgan <morgan at orst.edu>:
> On Thu, 5 Jan 2012, Leonardo Boiko wrote:
>
>> Hi,
>>
>> I’m running an installation of Horde 3.3.11 with IMP 4.3.10 in
>> production. Recently I’ve upgraded Debian from lenny to squeeze, which
>> changed PHP 5.2.6 to 5.3.3.
>>
>> After the upgrade, login stopped working.  It seems like the classic
>> session problem; I don’t get any errors in the logs, and I see a
>> successful IMAP login, but I’m silently thrown back to the login
>> screen.  I’ve already went through all the session diagnosis steps of
>> the wiki[1]; I’m using the PHP session handler, and tried disabling
>> cookies and using URL sessions; session.autostart is disabled; session
>> storage seems ok; but nothing made it work.
>>
>> If I downgrade the PHP packages back to 5.2, it works as usual.  The
>> problem only appears with PHP 5.3.  Trying to upgrade to Horde 4
>> caused other, unrelated problems, but in any case I’d like to keep
>> using Horde 3 if possible.
>>
>> Any hints on how can I further diagnose this problem? Thanks in advance.
>
>
> I am running those versions on Debian Squeeze right.  I dist-upgraded from
> Lenny back in October.  Your problem is tickling my memory, but I don't
> remember the details!  Grrr.
>
> Did you merge the new php.ini settings from Squeeze?  I have attached my
> /etc/php5/apache2/php.ini file.
>
> There might be errors in your log files, or you could temporarily turn on
> display_errors in php.ini.
>
> Sorry I can't remember what I did...
>
>        Andy