Sorry.
Isn't the directory check on /run/systemd/system going to be true on any
modern ubuntu system? And the "not directory" check will be false and
/usr/lib/php/sessionclean is never going to be executed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04
$ apt-cache policy php-common
php-common:
Installed: (none)
Candidate: 2:75
Version table:
2:75 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
I expect
Getting past a SRU review is a heavy lift without a guaranteed
successful outcome/fix/patch.
I've convinced the powers that be to allow me to use a php7.4 PPA to fix
the bug.
I'll state this again.
I'm surprised more people have not opened bugs or complained. As a php
developer attempting to
If this php7.2 bug is not fixed the changes to cookies defaults in
Chrome 80+ breaks many sites.
Like a webhook call back from PayPal (my problem) but any web site the
requires SameSite=None will be broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Adding the link
https://github.com/php/php-
src/commit/2b58ab23c6ad3301b31a2015f5faa31801147dfd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905109
Title:
Setting session.cookie_samesite=None in
Maybe this commit?
commit 2b58ab23c6ad3301b31a2015f5faa31801147dfd
Author: Pedro Magalhães
Date: Thu Jul 19 02:40:39 2018 +0100
Support for samesite cookies with array syntax
Allows using an alternative array argument with
support for the samesite option on the following
I believe this is the upstream change log entry that address the
SameSite cookie issue I'm experiencing with the bionic php7.2 packaged.
https://www.php.net/ChangeLog-7.php#7.2.34
Added support for the SameSite cookie directive, including an
alternative signature for setcookie(), setrawcookie()
Public bug reported:
I think this issue is related to the bug tracked at
https://bugs.php.net/bug.php?id=78651
Test script:
'None',
'Secure' => true
]);
session_start();
var_dump($_SESSION);
?>
Developer Tools results of the script run with php7.2 and Chrome
87.0.4280.67 show
Public bug reported:
# lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
# apt-cache policy postfix
postfix:
Installed: 3.4.10-1ubuntu1
Candidate: 3.4.10-1ubuntu1
Version table:
*** 3.4.10-1ubuntu1 500
500
Any status on the ppa?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622728
Title:
PHP version conflict for PHPBB3 on Xenial
To manage notifications about this bug go to:
Public bug reported:
# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
# apt-cache policy linux-image-4.4.0-57-generic
linux-image-4.4.0-57-generic:
Installed: 4.4.0-57.78
Candidate: 4.4.0-57.78
Version table:
*** 4.4.0-57.78 500
500
Any status update?
'ubuntu/xenial64' (v20160627.0.0) for 'virtualbox' still has the
problem.
Repeating my 06/19 post:
Is there a HOWTO or link for how to build the xenial image?
Might be easier for us to help troubleshoot the problem if we could
build the xenial image, fix what's wrong, and
command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
hostname -f
Stdout from the command:
Stderr from the command:
sudo: unable to resolve host ubuntu-xenial
mesg: ttyname failed: Inappropriate ioctl for device
hostname: Name or service not know
Is there a HOWTO or link for how to build the xenial image?
Might be easier for us to help troubleshoot the problem if we could
build the xenial image, fix what's wrong, and submit the patches back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
host: OS X 10.11.5
$ vboxmanage --version
5.0.20r106931
$ vagrant --version
Vagrant 1.8.1
$ vagrant init ubuntu/xenial64
$ vagrant box list|grep xenial
ubuntu/xenial64 (virtualbox, 20160531.0.0)
$ vagrant up
$ vagrant ssh -- sudo grep hosts /etc/nsswitch.conf
sudo: unable to
I'll be surprised if the problem is in the Virtualbox 5.0.20, what is
the xenial image you are testing against Dan? Your vagrant box list |
grep xenial?
I had the same problem with 5.0.18, but no longer have it installed.
--
You received this bug notification because you are a member of Ubuntu
Still see the problems with 'ubuntu/xenial64' (v20160527.0.0)
Switching from the user vagrant and ssh key authentication to user
ubuntu and password authentication lets things progress a little further
but run into hostname problem.
The following SSH command responded with a non-zero exit
Public bug reported:
Really a WISHLIST item.
I have many virtual machines running ubuntu/apache2 all with apt-
listchanges installed, all named www.domain.com. When I get my emailed
reports the subject is apt-listchanges: changelogs for www for every
single VM. Not very useful.
It would be
** Patch added: Change openspf.org to openspf.net
https://bugs.launchpad.net/bugs/920610/+attachment/2689432/+files/org-to-net.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920610
Title:
Public bug reported:
When I site fails SPF checks the Message rejected due to message uses
a dead openspf.org domain. Example below:
Recipient address rejected: Message rejected due to: domain owner discourages
use of this host. Please see
*** This bug is a duplicate of bug 709461 ***
https://bugs.launchpad.net/bugs/709461
Same issue here on (although i am running Mint 11).
Every once in a while a mouse click won't register, as if something is
blocking input to the region of the screen I am clicking on. I can
confirm that
Same problem here... Brand new installation of Kubuntu, resized konsole
and wham, total system freeze... If I disable transparency, the system
does not freeze, but results in strange artifacts all over the screen...
Also, on a side note, I would to add that it's a shame to see so many
people
Public bug reported:
Binary package hint: python-virtualenv
$ lsb_release -rd
Description:Ubuntu 10.04.2 LTS
Release:10.04
$ apt-cache policy python-virtualenv
python-virtualenv:
Installed: 1.4.5-1ubuntu1
Candidate: 1.4.5-1ubuntu1
Version table:
*** 1.4.5-1ubuntu1 0
Public bug reported:
Binary package hint: squid3
# lsb_release -rd
Description:Ubuntu 10.10
Release:10.10
# apt-cache policy squid3
squid3:
Installed: 3.1.6-1.1ubuntu1
Candidate: 3.1.6-1.1ubuntu1
Version table:
*** 3.1.6-1.1ubuntu1 0
500
Removed the comment from the cache_dir value in /etc/squid3/squid.conf
cache_dir ufs /var/spool/squid3 100 16 256
# squid3 -z
2011/03/01 06:52:02| WARNING cache_mem is larger than total disk cache space!
2011/03/01 06:52:02| Creating Swap Directories
2011/03/01 06:52:02| /var/spool/squid3
As a remotely exploitable security issue I hope the Importance of this
issue is greater then Wishlist!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in ubuntu.
https://bugs.launchpad.net/bugs/722621
Title:
Sync mailman
As a remotely exploitable security issue I hope the Importance of this
issue is greater then Wishlist!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722621
Title:
Sync mailman 1:2.1.14-1 (main)
Public bug reported:
Binary package hint: squid3
Description:Ubuntu 10.04.2 LTS
Release:10.04
squid3:
Installed: 3.0.STABLE19-1
Candidate: 3.0.STABLE19-1
Version table:
*** 3.0.STABLE19-1 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
100
Fixed ins maverick?
squid3 (3.1.0.13-1) experimental; urgency=low
* New upstream release
- Fixes Follow-X-Forwarded-For support (Closes: #523943)
Though I'm confused. I plug in 523943 in https://bugs.launchpad.net and
I get a bug report for 'Decibel Audio Player'?
--
You received this
Public bug reported:
Binary package hint: alsa-utils
I'm using Ubuntu 10.10. When I tried update my system, alsa-utils
failed to update. Currently I have alsa-utils version
1.0.23-2ubuntu3.3.
This was the output from the update manager:
installArchives() failed: (Reading database ...
--
package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/664824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: rsyslog
Pristine install of lucid patched and up to date.
Installing rsyslog-mysql wants to install all of mysql-server even
though the mysql-server meta package is only a recommended package.
http://packages.ubuntu.com/lucid/rsyslog-mysql
This
Download the .deb, ar xv + tar -xvzf the data.tar.gz and ldd on the
ommysql.so shows all the libraries resolved without mysql-server
installed.
$ ldd ommysql.so
linux-vdso.so.1 = (0x7fff27bff000)
libmysqlclient.so.16 = /usr/lib/libmysqlclient.so.16
(0x7f60d0512000)
# apt-get --no-install-recommends install rsyslog-mysql
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
mysql-server
The following NEW packages will be installed:
rsyslog-mysql
0 upgraded, 1 newly installed, 0 to remove and
Public bug reported:
Binary package hint: samba
http://lists.samba.org/archive/samba/2010-March/154072.html says
...3.4.X does not allow printing under 64 bit clients...
later on you see upstream fix this bug.
http://lists.samba.org/archive/samba/2010-March/154116.html says ...
Fix printing
Public bug reported:
Binary package hint: samba
http://lists.samba.org/archive/samba/2010-March/154072.html says
...3.4.X does not allow printing under 64 bit clients...
later on you see upstream fix this bug.
http://lists.samba.org/archive/samba/2010-March/154116.html says ...
Fix printing
Security team really dropped the ball here.
The whole Download Manager is missing from the previous configuration.
There should have been a big warning on upgrading this package to
identify the problems with the configuration files.
I agree with the original poster, security fixes should not
How about a .config and .template something like this:
.template
Template: dg/bigwarning
Description: WARNING: Incompatible configuration changes:
The upgrade from DG 2.8.0 to DG 2.9 has several configuration file changes
that are not compatible with DG 2.8
.config
db_get dg/bigwarning
Or
** Changed in: bzr/1.13
Status: Fix Committed = Fix Released
--
ErrorFromSmartServer - AbsentContentFactory object has no attribute
'get_bytes_as' exception while pulling from Launchpad
https://bugs.launchpad.net/bugs/354036
You received this bug notification because you are a member of
** Changed in: bzr/1.13
Status: Confirmed = Fix Committed
** Changed in: bzr/1.13
Assignee: (unassigned) = Bob Tanner (tanner)
--
ErrorFromSmartServer - AbsentContentFactory object has no attribute
'get_bytes_as' exception while pulling from Launchpad
https://bugs.launchpad.net
Merged into 1.13.2, I cannot change the bug task Status, so posting
here. See http://permalink.gmane.org/gmane.comp.version-control.bazaar-
ng.general/57030 for my question regarding changing Status.
--
ErrorFromSmartServer - AbsentContentFactory object has no attribute
'get_bytes_as' exception
Merged into 1.14rc2. Thanks.
--
ErrorFromSmartServer - AbsentContentFactory object has no attribute
'get_bytes_as' exception while pulling from Launchpad
https://bugs.launchpad.net/bugs/354036
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 269429 ***
https://bugs.launchpad.net/bugs/269429
** This bug has been marked a duplicate of bug 269429
pycrypto-2.0.1 uses md5 sha1 modules which will be deprecated in 2.6/3.0
--
deprecation warning in bzrlib/filters/__init__.py
*** This bug is a duplicate of bug 269429 ***
https://bugs.launchpad.net/bugs/269429
** This bug has been marked a duplicate of bug 269429
pycrypto-2.0.1 uses md5 sha1 modules which will be deprecated in 2.6/3.0
--
Deprecation warning for md5 and sha modules with Python 2.6
** Also affects: python-crypto (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bzr
Importance: Undecided
Status: New
--
pycrypto-2.0.1 uses md5 sha1 modules which will be deprecated in 2.6/3.0
https://bugs.launchpad.net/bugs/269429
You received this bug
** Changed in: bzr
Assignee: (unassigned) = Bob Tanner (tanner)
Status: New = Fix Committed
Target: None = 1.14rc1
--
pycrypto-2.0.1 uses md5 sha1 modules which will be deprecated in 2.6/3.0
https://bugs.launchpad.net/bugs/269429
You received this bug notification because you
Please see https://bugs.launchpad.net/bzr/+bug/342170 there's a bzr
branch with the above upstream patches applied that should work for
Ubuntu people. Please let me know what else I can do to help.
--
pycrypto-2.0.1 uses md5 sha1 modules which will be deprecated in 2.6/3.0
** Changed in: python-crypto (Ubuntu)
Assignee: (unassigned) = Ubuntu Core Development Team (ubuntu-core-dev)
--
pycrypto-2.0.1 uses md5 sha1 modules which will be deprecated in 2.6/3.0
https://bugs.launchpad.net/bugs/269429
You received this bug notification because you are a member of
48 matches
Mail list logo
