[Tickets #12486] Re: Can't download attachments over ActiveSync

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Jul 30 11:39:49 UTC 2013


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12486
------------------------------------------------------------------------------
  Ticket             | 12486
  Updated By         | simon at simonandkate.net
  Summary            | Can't download attachments over ActiveSync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


simon at simonandkate.net (2013-07-30 11:39) wrote:

Being loaded in php.ini:

extension=imagick.so
extension="lzf.so"
extension="memcache.so"
extension="pam.so"
extension="ssh2.so"
extension="mongo.so"
extension="horde_lz4.so"
extension=geoip.so

Horde doesn't run without lzf.so, I assume because compression is enabled.

With all of the others remarked out, the zend_mm_heap corrupted  
messages disappear, but the segfaults remain, along with the "Cannot  
download attachment". So one of the commented out modules is causing  
the zend error but the segfault is being driven from elsewhere. I've  
commented memcache out entirely as I don't use it any more, and I  
suspect from reading that may have been the cause of the zend errors.

php.d directory loads:

-rw-r--r-- 1 root root 49 Jul 13 00:50 curl.ini
-rw-r--r-- 1 root root 47 Jul 13 00:50 dom.ini
-rw-r--r-- 1 root root 24 Jul  1  2010 facedetect.ini
-rw-r--r-- 1 root root 57 Jul 13 00:50 fileinfo.ini
-rw-r--r-- 1 root root 45 Jul 13 00:50 gd.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 imap.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 intl.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 json.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 ldap.ini
-rw-r--r-- 1 root root 23 Jul  1  2010 libpuzzle.ini
-rw-r--r-- 1 root root 57 Jul 13 00:50 mbstring.ini
-rw-r--r-- 1 root root 53 Jul 13 00:50 mcrypt.ini
-rw-r--r-- 1 root root 53 Jul 13 00:50 mysqli.ini
-rw-r--r-- 1 root root 51 Jul 13 00:50 mysql.ini
-rw-r--r-- 1 root root 47 Jul 13 00:50 pdo.ini
-rw-r--r-- 1 root root 59 Jul 13 00:50 pdo_mysql.ini
-rw-r--r-- 1 root root 59 Jul 13 00:50 pdo_pgsql.ini
-rw-r--r-- 1 root root 61 Jul 13 00:50 pdo_sqlite.ini
-rw-r--r-- 1 root root 51 Jul 13 00:50 pgsql.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 phar.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 soap.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 tidy.ini
-rw-r--r-- 1 root root 49 Jul 13 00:50 wddx.ini
-rw-r--r-- 1 root root 59 Jul 13 00:50 xmlreader.ini
-rw-r--r-- 1 root root 53 Jul 13 00:50 xmlrpc.ini
-rw-r--r-- 1 root root 59 Jul 13 00:50 xmlwriter.ini
-rw-r--r-- 1 root root 47 Jul 13 00:50 xsl.ini
-rw-r--r-- 1 root root 47 Jul 13 00:50 zip.ini

But I am uncertain which of those are not 'standard' - the same date  
on most would lead me to believe that those have come from my upgrade  
to 5.3.27...

Next step will be to try and get a core dump I guess, unless anything  
looks odd from the above?





More information about the bugs mailing list