Bug#664880: php-apc: APC not working very well under 5.4 (at least using mpm-itk)

Package: php-apc Version: 3.1.9-0.1+b1 Severity: grave Justification: renders package unusable My system just got the PHP 5.4.0 upgraded packages. After which, a lot of unhappiness ensued with APC. Disabling APC entirely clears up my problems. I'm getting a lot of these: --- *** glibc

Bug#664895: squirrelmail: completely broken with PHP 5.4

Package: squirrelmail Version: 2:1.5.1-5 Severity: grave Justification: renders package unusable With the upgrade to PHP 5.4.0 coming down the pipeline, SquirrelMail has been rendered unusable. Commenting out the session_(un)register functions get things working somewhat again, but SM is

Bug#664895: Info received (squirrelmail: completely broken with PHP 5.4)

I should say that the version of SM in testing/unstable (2:1.4.22-1) actually works much better even than the experimental version and only requires hex2bin to be fixed. A patch for that looks like it's already been submitted upstream: ---

Bug#656500: xkb-data: XF86_Ungrab and XF86_ClearGrab security hole upstream

Package: xkb-data Version: 2.3-2 Severity: grave Tags: security upstream Justification: user security hole As originally reported at: --- http://gu1.aeroxteam.fr/2012/01/19/bypass-screensaver-locker-program-xorg-111-and-up/ and further syndicated by: ---

Bug#572525: php-apc: install 3.1.3p1 via pecl CLI

Package: php-apc Version: 3.0.19-2 Severity: normal I had similar issues with a complex internal application when upgrading from PHP 5.2 to 5.3 (in Debian). Removing php-apc fixed all the weird problems we were seeing. Upgrading using the pecl CLI installed with php-pear to php-apc

Bug#520941: nagios3-common: missing then statement on conditional

Package: nagios3-common Severity: normal If this is the same bug as what I just saw trying to remove nagios3-common, I got the following upon removal: --- /var/lib/dpkg/info/nagios3-common.prerm: line 23: syntax error near unexpected token `fi' because the if statement is missing a then

Bug#323902: same file in both libafterimage0 and libafterstep1

Package: libafterimage0 Version: 2.1.2-1 Severity: grave Justification: renders package unusable I received the following while updating: --- Unpacking libafterimage0 (from .../libafterimage0_2.1.2-1_i386.deb) ... dpkg: error processing

Bug#321562: zsh-static: libc version problem indeed

Package: zsh-static Version: 4.2.5-11 Followup-For: Bug #321562 Yep, looks right. I rebuilt locally with 4.2.5-10 and the segfaults quit. I also just upgraded to 4.2.5-11 from incoming (not built locally) and it's fixed there also. So I guess you can close this one. Thanks for

Bug#321562: zsh-static: /bin/zsh4-static segfaults immediately

Package: zsh-static Version: 4.2.5-10 Severity: grave Justification: renders package unusable Nothing much to say other than my root shell was set to /bin/zsh4-static and after an update earlier tonight (which may or may not have included zsh-static=4.2.5-10), I couldn't log in as root