Cannot use both zlib.output_compression and output_handler together!!

I've observed this same problem. There's discussion on the forums about it, and a suggestion that it's related to an old bug being re-introduced. See here: http://ubuntuforums.org/showthread.php?t=1067968

My computer:
2.6.24-23-generic x86_64 GNU/Linux
Ubuntu 8.04.2

Version of PHP installed:
php5-common (5.2.4-2ubuntu5.5)
php5-cli (5.2.4-2ubuntu5.5)
libapache2-mod-php5 (5.2.4-2ubuntu5.5)
php-pear (5.2.4-2ubuntu5.5)

Version of mythweb installed:
mythweb (0.21.0+fixes16)

I've tried enabling and disabling output_compression and output_handler options in my php.ini file to no avail. The relevant configuration in my php.ini is:

output_buffering = Off
;output_handler =
zlib.output_compression = Off
;zlib.output_compression_level = -1
;zlib.output_handler =
implicit_flush = Off

Relevant config for mythweb in the apache config (default from installation except for additional memory limit):

php_value safe_mode 0
php_value memory_limit 64M
php_value register_globals 0
php_value magic_quotes_gpc 0
php_value file_uploads 0
php_value allow_url_fopen On
php_value zlib.output_handler Off
php_value output_handler NULL
php_flag output_handler "NULL"

have fun()
mike

I have a correction to make to the above, commenting out these lines in the mythweb apache config file (ie: /etc/apache2/sites-available/mythweb.conf ) will make mythweb work, although I'm not able to verify if it breaks anything else:

php_value zlib.output_handler Off
php_value output_handler NULL
php_flag output_handler "NULL"

I'm not sure why that works, or if it is a suitable workaround.

have fun()
mike

the above workaround fixed the problem for me too. I had to comment out only these two lines:

php_value output_handler NULL
php_flag output_handler "NULL"

Kim

KimKulak's two lines worked like a charm for me. Thank you!

KimKulak's workaround worked for me also.

Ubuntu 8.04.
$ cat /etc/issue
Ubuntu 8.04.2 \n \l

Mythweb worked fine before an update today:
Preparing to replace php5-mysql 5.2.4-2ubuntu5.4 (using .../php5-mysql_5.2.4-2ubuntu5.5_i386.deb) ...
Unpacking replacement php5-mysql ...
Preparing to replace libapache2-mod-php5 5.2.4-2ubuntu5.4 (using .../libapache2-mod-php5_5.2.4-2ubuntu5.5_i386.deb) ...
Unpacking replacement libapache2-mod-php5 ...
Preparing to replace php5-common 5.2.4-2ubuntu5.4 (using .../php5-common_5.2.4-2ubuntu5.5_i386.deb) ...
Unpacking replacement php5-common ...
Preparing to replace libpq5 8.3.5-0ubuntu0.8.04 (using .../libpq5_8.3.6-0ubuntu8.04_i386.deb) ...
Unpacking replacement libpq5 ...
Preparing to replace php5 5.2.4-2ubuntu5.4 (using .../php5_5.2.4-2ubuntu5.5_all.deb) ...
Unpacking replacement php5 ...

Thanks

Very peculiar...

I had the same problem, however the above fix did not fix it. I had to do this:

# php_value zlib.output_compression 16384
# php_value zlib.output_compression_level 4

However, this means that I now have the opposite of the intended config (no compression, but output_handler enabled). It might be my perception, but I think mythweb took a perfomance hit in doing this.

I'm running LTS server.

Oh wait, I got it!

I edited the /var/www/mythweb/.htaccess file (has the same config lines). I had to make the change in /etc/apache2/sites-available/mythweb.conf and restart apache. All good now.

The above does not work for me.

Ignore that, edited wrong config-file. A real solution would be nice though.

I can confirm this bug going from intrepid's 5.2.6-2ubuntu4 to 5.2.6-2ubuntu4.1.

For the moment, this seems to be related to only very old installs of mythweb that contain a left-over copy of /etc/mythtv/mythwweb-htaccess file (it should be renamed to something else). The php5 update changes the security of what's allowed in htaccess files, so this mythweb packaging bug only became visible after the update.

FWIW this seems to have happened to me after installing phpmyadmin.

Ok, that's because installing phpmyadmin installed php5. Never mind. Nothing to see here. Move along...

Kees Cook wrote:
> ...old installs of mythweb that contain a left-over copy of
> /etc/mythtv/mythwweb-htaccess file (it should be renamed to something else)

So to clarify, this changes the steps to implement the workaround. I reverted the changes I had made to /etc/apache2/sites-available/mythweb.conf (per the prior comments), restarted apache, confirmed the problem was still present, then ran:

# mv /etc/mythtv/mythweb-htaccess /etc/mythtv/mythweb-htaccess.obsolete
# /etc/init.d/apache2 restart

and that also worked to resolve the problem.

Presumably mythweb-htaccess can then be deleted.

The fix above worked perfectly. Thanks Tom.

You don't need to restart apache, just the move is sufficient. Thanks.

I've had a MythTV box setup for a while (over a year) and have been just doing the occasional (every month or two) updates. Did updates about a week ago and saw the same blank page as described above when going to the mythweb url.

I did what Tom Metro suggested and it worked fine. (with the addition of sudo)
sudo mv /etc/mythtv/mythweb-htaccess /etc/mythtv/mythweb-htaccess.obsolete
sudo /etc/init.d/apache2 restart

This has worked for me.

I am running mythbuntu distro on the same box for more than 1 year now. As described above iterative upgrades (from 7.10 release up to 8.04.2) produced such problem. Thank you for the fix.

Scott Merrilees solution of mv'ing mythweb-htaccess did the trick. I did not have to restart apache. Thanks.

Upgraded systems appear to be likely to run into this. My system did (which originated as a 7.10 system and was upgraded to 8.04.1).

Had the same problem after upgrade.
I did as Tom Metro suggested 14# with super user ( sudo ) and it worked for me.
Thank you, I was missing being able to brows and stream.

Mythbuntu 8.04 poweredge 2500

Marking incomplete as this release isn't supported anymore. Can anyone confirm that this issue is still present on a supported Mythbuntu/MythTV release?