Why was the status of this bug changed to opinion?
I though it was expected that changes of status were accompanied by a
comment explaining why the change was made?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
One more, hopefully the last, multiarch-related patch is attached, for
various graphics libraries.
** Patch added: graphics-libs-are-multiarch.patch
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/739977/+attachment/1935549/+files/graphics-libs-are-multiarch.patch
--
You received this
debdiff will follow once this builds and I test it a little.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/739977
Title:
PHP5 FTBFS in Natty
--
Ubuntu-server-bugs mailing list
Ahem... spoke too soon. The configure script now runs to completion but
the link step fails.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/739977
Title:
PHP5 FTBFS in Natty
--
Ah, that would be nice --- I thought I'd missed something; if you are
correct I can claim my patches are fine and libgd2 was the culprint :)
Regarding your earlier comment:
(It's unfortunate that we don't have time to convert the entire system in one
cycle;
if all of PHP5's build-deps were
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/739977
Title:
PHP5 FTBFS in Natty
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
Confirmed. Attempting to build php5 5.3.5-1ubuntu4 on Natty by running
debuild in a local VM resulted in the attached script output.
** Attachment added: debuild output showing FTBS issue
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/739977/+attachment/1929157/+files/debuild.txt
**
The way php5 does its library presence checks is unusual. Apparently
someone recreated autotools functionality themselves, in a way that
breaks the multiarch work being done for Natty.
In reality, noone is likely to rework an 85K (non-empty) line configure
script! So a smaller cheaper fix needs
** Patch added: libdb4-is-multiarch.patch
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/739977/+attachment/1929301/+files/libdb4-is-multiarch.patch
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in
Note that changing configure parameter --with-
libdir=lib/${DEB_HOST_MULTIARCH} does not work, because this is used for
finding both header files and actual libraries.
So (unless others have better ideas) it seems that patching the various
config*.m4 files for each such test is the best we can
Setting back to New status because bug submitter kindly supplied the
requested vsftpd.conf
** Changed in: vsftpd (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in ubuntu.
Setting anonymous_enable to YES enables identified login (aknaff), but
(obviously) disables anonymous (ftp) login
Unless I am very confused, the YES in that final sentence in the bug
description was probably intended to be NO :)
--
You received this bug notification because you are a member of
OK. Do we have a test case for which my patch fails?
If the remaining issue is that my patch contains a closing '}', that is
easily solved, because the {} around the variable name are only there
for style reasons, and are not required.
Here is a modified patch without the {} . Is there a test
It seems to me a patch to /etc/logrotate.d/apache2 is the simplest
solution.
The attached diff tries to solve the issue and also be more readable,
breaking the one complex line involving backticks into three shorter
simpler lines, no backticks needed.
There are a lot of cases to test this with,
man 1 passwd and reading the text regarding the -l option specifically
says:
Note that this does not disable the account. The user may still be able to
login using another
authentication token (e.g. an SSH key). To disable the account,
administrators should use usermod
--expiredate
Thanks for taking the time to report an issue and so help to improve
Ubuntu.
Selecting the LAMP Server task in tasksel installs Linux (Ubuntu),
Apache2, MySQL and PHP5. By design.
Leaving the root MySQL password blank does not somehow uninstall MySQL.
It just installs it in a less secure way.
@Alvin: file a new bug against ubuntu-serverguide, the package which
installs the Ubuntu Server Guide :)
Note that this bug is marked Invalid, so adding stuff to it will not get
much accomplished.
--
No password set on install of slapd-2.4.18-0ubuntu1
https://bugs.launchpad.net/bugs/447099
You
fusiondog: Could I recommend that you consider doing something positive?
If you are willing to work with upstream (that is, with the developers
of openssh) to get this option included by default in their released
source code, that would make getting it included into future releases of
Ubuntu
Apparently apache2-mpm-worker *is* the default choice of mpm, at least
some of the time (though the machine I first checked on had apache-mpm-
prefork, I am unsure why). My mistake, it would appear.
Using apache2-mpm-prefork would appear to be a viable workaround, unless
it leads to performance
Mike,
I suspect the problem was caused by an odd/corrupt/invalid set of
answers to the configuration questions for postfix, which are normally
stored in /var/cache/debconf/config.dat .
If you happen to have a backup of that file from the time when the issue
occurred, we could look at that file
Dekar: Did you actually test this at all? Please provide some evidence
to support your claims.
You have said that you believe this issue is:
A real problem, exploitable for many people in a default
installation. Includes serious remote denial of services,
local root privilege escalations,
Mike,
(1) The new line in parameters thing means that somehow debconf thinks
there is a newline in a previous stored response to one of its
questions, and that this is a problem. Are you sure you *purged* any
previous postfix install before trying to install it afresh?
I just tried this here on
Confirmed on Ubuntu 9.04 Jaunty amd64.
Steps to reproduce (and capture a backtrace) are:
# Ensure we dump core
ulimit -c 200
# Delete any pre-existing core file
rm core
# Create a command input file for use by gdb
echo bt /tmp/bt
# Create a trivial PHP script
echo -e ?php\n?\n /tmp/a.php
#
Since two people other than the original reporter have now reproduced
this bug, I am setting its status to confirmed.
** Changed in: php5 (Ubuntu)
Status: Incomplete = Confirmed
--
Segmentation fault when running any script
https://bugs.launchpad.net/bugs/392521
You received this bug
** Summary changed:
- Segmentation fault when running any script
+ Segmentation fault when using php -l to validate any PHP script
--
Segmentation fault when using php -l to validate any PHP script
https://bugs.launchpad.net/bugs/392521
You received this bug notification because you are a
It was when this failure occured, I changed the hostname to bl5400, and
tried again same result.
I strongly suspect that somewhere in one or more of your system's
configuration files, that old numeric host name still exists.
Please confirm that the old numeric hostname has been edited into the
If the driver concerned were part of Ubuntu that might be fixable. But
you state it is unsupported, so the Ubuntu community can't support it,
unfortunately.
I suspect the driver does not directly need postfix, just any way to
send email out from this machine; postfix is the default choice for
To those who are experiencing this issue, and would like it fixed:
PLEASE provide more specific detail on exactly how to reproduce this
issue.
So far, we do not even seem to have information on which release of
Ubuntu is involved, much less which versions of apache2 and php5 and
Joomla. Clear
An attempted set of steps to reproduce this issue follows. I failed to
reproduce it!
Those who can reproduce it, please document, in a way similar to this,
exactly how you (and so others!) can also reproduce this issue.
Just in case the web display on LP messes up my PHP script, I am attaching
As a further test, I have also installed php5-suhosin,
rebooted the virtual machine, and then retested it
with 100,000 repetitions using ab.
It all still works fine. /var/log/apache2/error.log contains
no errors relating to canary mismatch, and even doing
sudo grep -ri canary mismatch
Nitro322:
Since this behaviour is what upstream provided in PHP 5.2.4, changing
that in an LTS release is probably not all that safe (who knows how many
PHP applications running on existing 8.04 LTS servers might depend on
it?). Whether upstream *intended* that behaviour or not is not really
the
Given a way to detect broken DNS at package install time, it might be
reasonable to set name resolve order to broadcast first
at that point, if such brokenness is detected. A comment line indicating that
resolve order was set like this because DNS brokenness was detected at
date/time could
Thanks for helping to improve Ubuntu. At this point I think we're
mainly aiming for a more complete bug report. Any work to fix this
would come after that, once we have a clear, complete and reproducible
bug report to work with.
(1) Please provide a complete set of steps to reproduce this
The mysql apparmor profiles work fine for me here (Ubuntu Jaunty 9.04).
Please describe what you mean by the profiles being bogus in
considerably more depth. Please be constructive -- suggest imrpovements
to them if you feel they are needed.
If you have chosen to manually move MySQL database
@Wolfgang: At minimum, please do
sudo chmod 755 /
to fix the permissions on /
and then restart samba (or just reboot).
Jonathan
--
samba does not start since upgrade to 9.04
https://bugs.launchpad.net/bugs/371530
You received this bug notification because you are a member of Ubuntu
Server
@Martin: If ping any name fails, I wonder if the DNS redirection opt-
out has somehow effectively opted out of *all* DNS resolution? That
could explain why ping yahoo.com (for example) now fails. Can you still
browse the web, deal with email, etc as normal once opted out from the
DNS
@Daniel: I get the same results as you ( 0.1 ) on Ubuntu Jaunty 9.04
amd64. I also tested morodoch's PHP example code, and it works fine
here also:
$ php -r echo PHP_VERSION; echo PHP_EOL; echo 0.6/6; echo PHP_EOL;
5.2.6-3ubuntu4.1
0.1
$ echo -e
@Mathias: That's fine. I was just following the example set by some
other parameters in that same file, very close to the line being
discussed, such as
set_postfix_option smtpd_tls_mandatory_protocols = SSLv3, TLSv1
and also
set_postfix_option tls_random_source = dev:/dev/urandom
which
OK. The underlying issue here now seems to be:
On Ubuntu 9.04 Desktop, Network Manager causes a network configuration
that leads Apache to start up listening on IPv6, but to restart
listening on IPv4. Specifying network configuration using
/etc/network/interfaces does not cause this behaviour,
If you do not wish to follow recommends, use the --no-install-recommends
option to apt-get :)
sudo apt-get install mysql-server --no-install-recommends
will do what the submitter seems to desire.
I am not convinced this is a bug.
--
MySQL-server-5.1 indirectly installs postfix
DIAGNOSIS:
Based on the [client ::1] in the log entries, I strongly suspect an IPv6
related issue here.
In Jaunty, /etc/hosts has a line
::1 localhost ip6-localhost ip6-loopback
where in Intrepid, this was
::1 ip6-localhost ip6-loopback
I *strongly* suspect that allow from localhost
** Summary changed:
- Accessing http://localhost gives without reason a 403 Forbidden error page
+ Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
I meant:
Could you please attach copies of the two files /etc/hosts and
/etc/hostnames to this bug report?
--
package postfix 2.5.5-1.1 failed to install/upgrade: subprocess
post-installation script returned error exit status 75
https://bugs.launchpad.net/bugs/365625
You received this bug
Thanks for reporting this, and so helping to make Ubuntu even better.
As far as i can tell, something about the configuration of your machine
apparently caused the scripts concerned to think your hostname was '04'.
This is not a valid hostname, since hostnames should start with a
letter.
Could
I am unable to duplicate this here in a Jaunty (rc) virtual machine.
The default /etc/postfix/main.cf file does not seem to contain an entry
for smtpd_tls_mandatory_ciphers when I install postfix. I also unpacked
the postfix 2.5.5-1.1 source package and do not see any obvious sign of
this in
bug only seen when dovecot-postfix is installed, not when installing
just postfix.
** Package changed: postfix (Ubuntu) = dovecot (Ubuntu)
--
postfix: invalid value for smtpd_tls_mandatory_ciphers in main.cf
https://bugs.launchpad.net/bugs/365390
You received this bug notification because you
unable to set package name to dovecot-postfix
** Changed in: dovecot (Ubuntu)
Status: Incomplete = Confirmed
--
postfix: invalid value for smtpd_tls_mandatory_ciphers in main.cf
https://bugs.launchpad.net/bugs/365390
You received this bug notification because you are a member of Ubuntu
Fix created, will upload debdiff soon.
** Changed in: dovecot (Ubuntu)
Status: Confirmed = In Progress
--
postfix: invalid value for smtpd_tls_mandatory_ciphers in main.cf
https://bugs.launchpad.net/bugs/365390
You received this bug notification because you are a member of Ubuntu
Server
Debdiff attached.
Note that this is hand edited to remove over 5MB of cruft
generated because the dovecot build regenerates
a lot of autotools files that are in the original source
tarball and does not take care of replacing them
in its clean target. But that's (I think!) a totally
separate
** Changed in: dovecot (Ubuntu)
Status: In Progress = Confirmed
--
postfix: invalid value for smtpd_tls_mandatory_ciphers in main.cf
https://bugs.launchpad.net/bugs/365390
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in
I made the same change here on my Ubuntu 8,10 Intrepid x64 desktop.
It made no difference at all, motd info including the landscape-sysinfo
output is always displayed after login.
Jonathan
--
motd disappears when using PasswordAuthentication in OpenSSH server
In that case, may be this one should be marked as dup of #74164
No, they are not the same thing.
#30455 asks for DHCP to affect the config file for ntpdate, which was
used at boot to set system time on some older versions of Ubuntu.
#74164 asks that DHCP should be used by default to request
I am unable to duplicate this issue on my local
Ubuntu Intrepid 8.10 (x64) desktop, even before
making any of the changes suggested in this message.
For those who are affected by this:
ssh -4 somehost
will use IPv4 only to connect, which would appear to
be a viable workaround.
To make IPv4
I am not sure this issue still matters.
In Ubuntu Intrepid 8.10, ntpdate is not
(as far as I can see) run by default at boot
time anyway. Bug #74164 causes the dhcp client to
not request ntp-servers by default, but once that
is done, things just work regarding obtaining
and using NTP server
The version of php5 in Ubuntu 8.10 Intrepid is 5.2.6-2ubuntu4
This appears to me to have dynamically spelled correctly, and least in
the USA English version of the description.
Could you please state the exact version of php5 you have installed, and
what locale you are using?
Thanks! (And yes,
Never mind. Confirmed, This issue only happens in some of the binary
packages generated, not all.
Already correct in: php5, php5-common, libapache2-mod-php5, libapache2
-mod-php5filter, php5-cgi, php5-cli
Incorrect in: php5-dev, php5-dbg, php-pear, php5-curl, php5-gd,
php5-gmp, php5-ldap,
debdiff attached.
** Attachment added: php5-5.2.6-2ubuntu6.debdiff
http://launchpadlibrarian.net/20067354/php5-5.2.6-2ubuntu6.debdiff
--
English description of php5 packages wrong
https://bugs.launchpad.net/bugs/303612
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 238755 ***
https://bugs.launchpad.net/bugs/238755
Based on:
Your account has expired; please contact your system administrator
chfn: PAM authentication failed
adduser: `/usr/bin/chfn -f MySQL Server mysql' returned error code 1. Exiting.
I would say you
at is defined in ISO POSIX and has been a part of the Linux Standards
Base (LSB) since LSB 1.0.
Who deprecated it, when, and why -- no information on this was included
in your report?
Without such information, this report appears to be invalid.
If you have knowledge of a specific security flaw
In php5_5.2.6-2ubuntu1, the Depends: line for php-pear in debian/control
reads:
Depends: php5-common (= ${source:Version}), php5-cli | php4-cli
So apparently the current php-pear does depend on either php4-cli or
php5-cli. Is this insufficient? I could post a debdiff that just
changes this to
60 matches
Mail list logo
