In mysql-5.5, we are on 5.5.46 in Precise and Trusty and this was fixed
in upstream release 5.5.41.
In mysql-5.6, we are on 5.6.27 in Trusty, Vivid, Wily and Xenial and
this was fixed in upstream release 5.6.22.
** Changed in: mysql-5.5 (Ubuntu Precise)
Status: Triaged => Fix Released
**
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1478849
Title:
infinite loop in /usr/
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1435709
Title:
mysql.service fail to
Importance in Ubuntu -> Low since this has been filed upstream. In
Ubuntu we will follow what upstream does for this.
** Bug watch added: MySQL Bug System #70672
http://bugs.mysql.com/bug.php?id=70672
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=70672
Importance: Un
Let's try ubiquity. I don't know if that's right, but I think it's
closer.
** Package changed: bcache-tools (Ubuntu) => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
AIUI, it isn't appropriate for a package to modify another package's
behaviour from under its feet in this way. Debian Policy Appendix G (not
formally policy I don't think) says: "Do not attempt to divert a
conffile, as dpkg does not handle it well.". Though
https://wiki.debian.org/ConfigPackages d
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
** Changed in: vsftpd (Ubuntu)
Importance: Undecided => Wishlist
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/1514431
Title:
vsftpd does no
>From log:
Configurando odbc-mdbtools:amd64 (0.7.1-1ubuntu1) ...
odbcinst: error while loading shared libraries: libodbcinst.so.2: cannot open
shared object file: No such file or directory
dpkg: error al procesar el paquete odbc-mdbtools:amd64 (--configure):
el subproceso instalado el script pos
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I think what you're really saying here is that there is no installer
support for bcache. I'd say that this would be primarily a wishlist bug
in the installer that you are using, even if bcache-tools needs
modifying
** Changed in: mysql-5.6 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: mysql-5.6 (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
> I think the importance got to be set to critical.
It makes little difference what the Importance is set to. Please, help
fix it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458
** Description changed:
+ [User Impact]
+
+ pollen operators must maintain a delta on /etc/init/pollen.conf in order
+ to maintain a pollen service that restarts on boot.
+
+ [Test Case]
+
+ 1. apt-get install pollen
+ 2. reboot
+ 3. status pollen
+
+ Expected results: pollen service running
+
** Changed in: openldap (Ubuntu)
Status: Confirmed => Triaged
** Changed in: openldap (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/14
Looks like this was fixed in 5.6.7 upstream so it is fixed in Xenial's
5.6.14+dfsg-1ubuntu1. Marking Fix Released.
Trusty is still affected I think, but as above backporting the fix is
non-trivial. Volunteers welcome.
** Changed in: php5 (Ubuntu)
Status: Triaged => Fix Released
** Also af
According to the Debian bug, this was fixed upstream in 4.2.8p1 and
Debian sid is now on 1:4.2.8p4+dfsg-3 so I think that means this is
fixed in Debian. Ubuntu will pick it up on the next merge which I am
expecting to be done this cycle.
--
You received this bug notification because you are a mem
Thanks, this sounds reasonable. I'd prefer to send this to Debian to
minimise our delta in Ubuntu, so this needs checking and forwarding to
Debian if appropriate.
** Tags added: needs-upstream-report
** Changed in: net-snmp (Ubuntu)
Importance: Undecided => Medium
--
You received this bug no
Looks like upstream no longer needs this since they have embedded the
lens they need, so no point backporting this fix to stable releases. It
is fixed in the development release for the future.
** Changed in: augeas (Ubuntu Vivid)
Importance: High => Low
** Changed in: augeas (Ubuntu Wily)
Oh, it's a security bug. Un-triaging as I don't want to step on the
security team triaging this.
** Changed in: php5 (Ubuntu Trusty)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://
This is fixed in 5.6.14+dfsg-1ubuntu1 based on the NEWS file in there
reporting upstream 64938 fixed so I'm marking this Fix Released in
Xenial.
It looks like this does still affect Trusty and was committed to 5.5.22
upstream and can be cherry-picked from http://git.php.net/?p=php-
src.git;a=commi
** Tags added: bitesize systemd-boot
** Changed in: openvpn (Ubuntu)
Status: New => Triaged
** Changed in: openvpn (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
htt
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
** Changed in: php5 (Ubuntu)
Importance: Undecided => Low
** Tags added: neds-upstream-report
** Tags removed: neds-upstream-report
** Tags added: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
>From log:
2015-11-01 23:54:51 2917 [ERROR] InnoDB: ./ibdata1 can't be opened in
read-write mode
2015-11-01 23:54:51 2917 [ERROR] InnoDB: The system tablespace must be writable!
2015-11-01 23:54:51 2917 [ERROR] Plugin 'InnoDB' init function returned error.
2015-11-01 23:54:51 2917 [ERROR] Plugin
>From the comments it sounds like this issue is caused either by user
error or by VMWare WorkStation and so is not a bug in Ubuntu? In this
case I'm marking this bug Invalid, but if someone disagrees and thinks
there is a bug in Ubuntu here then please explain and set the status
back to New.
** Ch
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
>From log:
Nov 02 15:39:18 hostname systemd[1]: Job
dev-disk-by\x2duuid-728009cc\x2dfcdc\x2d4b6a\x2da504\x2d689cfbc0fb0d.device/start
timed out.
Nov 02 15:39:18 hostname systemd[1]: Timed out waiting for device
dev-disk-by\x2duuid-728009cc\x2dfcdc\x2d4b6a\x2da504\x2d689cfbc0fb0d.device.
Nov 02
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Does this issue affect the backport only, or does it also affect haproxy
on Trusty or the release the backport was from?
Since you've reported this as affecting the backport I'll reassign to
the backports project,
*** This bug is a duplicate of bug 1510885 ***
https://bugs.launchpad.net/bugs/1510885
** This bug has been marked a duplicate of bug 1510885
package mysql-server-5.6 5.6.25-3+deb.sury.org~trusty+1 failed to
install/upgrade: trying to overwrite '/usr/share/man/man1/innochecksum.1.gz',
whi
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1512603
Title:
nut-monitor systemd service is absent in nut-client package since
Ubuntu vivid
To manage not
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to powernap in Ubuntu.
https://bugs.launchpad.net/bugs/1460712
Title:
Powernap systemd setup is broken
To manage notifications about this bug go to:
https://bu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Sorry, moving from MariaDB 10.0 to MySQL 5.6 automatically is not a
supported path at the moment. You need to migrate your database
manually.
** Changed in: mysql-5.6 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
** Changed in: unixodbc (Ubuntu)
Status: New => Triaged
** Changed in: unixodbc (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1513268
Anyone can do it. I was just trying to be helpful in identifying what
needed doing. But I have now filed this in Debian for you.
> FYI, Redhat fixed a similar report on Fedora 23 within a few hours,
after their official final freeze.
Have Red Hat released a version of RHEL with tipc support? Othe
** Changed in: squid3 (Ubuntu)
Assignee: Robie Basak (racb) => Tiago Stürmer Daitx (tdaitx)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1473691
Title:
Update to lat
Thanks. I'll mark Fix Released as that reflects Xenial, and Won't Fix
for Trusty as that is our current conclusion. But I am open to debate on
this. My concern is to not break existing users by changing behaviour on
them in an update automatically recommended to them. Since the
workaround is so sim
Uploaded 1.24.7 to Trusty now that 1.22.8-0ubuntu1~14.04.1 is in trusty-
updates. I'm not sure why it is still in trusty-proposed but that
doesn't matter as it should be superceded by this new upload once
accepted.
I added a changelog note to explain the packaging difference from the
previous pack
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like this was fixed upstream in 2.4.8 so it is fixed in Vivid,
Wily and Xenial, but affects Trusty. It looks like this should be
trivial to cherry-pick to Trusty. I will put this on the server team's
backlog.
The patch applied to the upstream 2.4 branch is
https://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/modules/metadata/mod_remoteip.c?r1=1569003&r2=1569006&pathrev=1569006
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug repor
** Summary changed:
- Please include patch for Apache PR 54651 in trusty-updates
+ Incorrect trusted proxy match test in mod_remoteip
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/15
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The bug sounds valid to me, but note that 14.04 users may be relying on
the current behaviour. So if we fix the bug, we might break those users.
On the other hand, the bug is trivial to work around (just truncate
P
** Description changed:
libxml's libxml_disable_entity_loader was not threadsafe on php-fpm
prior to 5.5.22 and 5.6.6. This allowed attackers to perform an XXE
attack even though the entity loader was disabled in your code.
Zend came up with a separate library for this:
https://github
>From log:
Setting up exim4-config (4.82-3ubuntu2) ...
/var/lib/dpkg/info/exim4-config.config: 32: /etc/exim4/update-exim4.conf.conf:
Syntax error: Unterminated quoted string
dpkg: error processing package exim4-config (--configure):
subprocess installed post-installation script returned error e
Thank you for your report.
The problem here lies with an unfortunate interaction in the third party
package you used, and is not a bug in Ubuntu, so I'm marking this as
Invalid in Ubuntu.
If you need help resolving this, you can find pointers to get help for
this sort of problem here: http://www.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
** Changed in: mysql-5.6 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1510671
Title:
package mysql-server-5.6 5.6.27-0ubuntu1 fai
>From log:
2015-10-28 17:30:23 15986 [Note] InnoDB: Completed initialization of buffer pool
2015-10-28 17:30:23 15986 [ERROR] InnoDB: auto-extending data file ./ibdata1 is
of a different size 640 pages (rounded down to MB) than specified in the .cnf
file: initial 768 pages, max 0 (relevant if no
Uploaded 1.24.7 to Wily, with only minor changes. See
https://git.launchpad.net/~ubuntu-server/ubuntu/+source/juju-
core/+git/packaging/log/?h=basak/vivid and please pull them in for any
future uploads.
Good to upload to Trusty with only minor changes again but I'm holding
until 1.22.8-0ubuntu1~14
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Trusty)
Status: New => Triaged
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member
Uploaded to Xenial. It's making its way through xenial-proposed now but
will then wait on the upstream release and then we can remove the block-
proposed tag.
I made a couple of minor changes to the Xenial upload. There was a
syntax error in debian/copyright that lintian picked up. I also dropped
** Also affects: juju-core (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu Wily)
Status: New => Triaged
** Changed in: juju-core (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubunt
block-proposed needed as 1.25.0 is not yet released upstream and will
break in Ubuntu until it is.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/15105
** Changed in: squid3 (Ubuntu)
Status: Triaged => In Progress
** Changed in: squid3 (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Changed in: mysql-5.6 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1509840
Title:
package mysql-server-5.6 (not installed) failed to
** Tags added: mysql-packaging-policy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1490071
Title:
MariaDB writes to /var/lib/mysql after crossgrade, preventing users
from reve
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for your report.
Version 5.6.24-2+deb.sury.org~precise+2 is a package from a third party
PPA which isn't under the control of Ubuntu developers, so we can't fix
it as part of Ubuntu, sorry. For this reason I'm marking this bug as
Invalid in Ubuntu. You might be able to get help for this
> or just manually grab the .deb files from Xenial and install it on
Wily if you like - that should work
I should add that if you do this you should manually downgrade back to
packages from Wily later, to make sure that you receive any future
security updates.
--
You received this bug notificati
Thanks Dominic. I've uploaded this to Xenial, which as it is for the
development release I don't have to worry as much about regressing
existing users.
Can someone confirm that the problem with letsencrypt is fixed with
Xenial, please (or just manually grab the .deb files from Xenial and
install i
That's not the correct way build from a Debian or Ubuntu source package.
Use "debian/rules build" or "dpkg-buildpackage". See the documentation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.
** Also affects: augeas (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: augeas (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: augeas (Ubuntu)
Status: New => Triaged
** Changed in: augeas (Ubuntu Vivid)
Status: New => Triaged
**
** Attachment added: "asterisk_11.7.0~dfsg-1ubuntu1_amd64.build"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1510099/+attachment/4506523/+files/asterisk_11.7.0%7Edfsg-1ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I am unable to reproduce and successfully test built asterisk 1:11.7.0
~dfsg-1ubuntu1 on Trusty using sbuild. Could it be some issue with your
build environment? See my build log attached.
I'm marking this Invalid
Importance: High because I think it's important to the Ubuntu Server
Team to help ensure that Let's Encrypt works well on Ubuntu. Find me
(rbasak) in #ubuntu-server on Freenode during UK working hours if you
need any help.
** Changed in: augeas (Ubuntu)
Importance: Undecided => High
** Tags ad
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We can't bump augeas in Vivid and Wily as they are already released, but
it looks like it should be fairly easy to cherry-pick just this fix
without regressing existing users. Is this accurate?
In this case, if so
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Looks like this still affects Debian VCS master since the patch there
also uses DOVECOT_VERSION: http://anonscm.debian.org/cgit/collab-
maint/dovecot.git/tree/debian/patches/dovecot-drac.patch#n58
If this is true,
I have verified that apache2 2.4.12-2ubuntu2 (in Vivid and Wily) ships
with:
SSLProtocol all -SSLv3
I'm with Seth in that retrospectively updating existing 14.04
deployments risks breaking users. Even if we could update only fresh
installs of 14.04, that would be particularly confusing an
> Doing so would require the CPC team to update /etc/default/lxc-net,
setting USE_LXC_BRIDGE to false.
Note that this would cause a conffile prompt for all users using cloud
images who dist-upgrade to pick up the latest updates after another lxc
SRU, which breaks people doing automatic deployments
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for trying. It might be a reasonable feature request for apt
to make it possible to call a shell or to provide arguments so that we
can call a shell though, in order to resolve this bug. It would be a
reasonably generic solution.
--
You received this bug notification because you are a m
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Hi Robin,
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This request looks reasonable to me. I'll add it to the queue. To help
process it faster, we will need:
Identification of the upstream patch in upstream VCS (commit ID and
preferably a link to the commi
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You may find it helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. Please can you
provide steps to reproduce the problem, and then change the bug status
back to
I also get "ValueError: /usr/bin/python3.4 (deleted) does not exist" by
starting with a Vivid cloud image, installing lxc and juju-local from
the archive, and then do-release-upgrade -d to Wily. So this will happen
to every Juju charm developer on upgrade, I think. No PPA required.
Separate from t
Oh, I'm sorry. In my reproducer the error visible on the screen was
"ValueError: /usr/bin/python3.4 (deleted) does not exist" but apport
reported DpkgTerminalLog with "invoke-rc.d: unknown initscript,
/etc/init.d/lxc not found." so I think they are just one bug.
--
You received this bug notificat
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see that libmnl-dev is in universe in Ubuntu so it should be
relatively easy to add the build dependency, but we are in final freeze
right now so this may have to wait until the next release.
This bug also shoul
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
chkrootkit is in universe in Wily so will not receive much attention
now. But I don't really understand your bug report either - you have not
provided steps to reproduce the bug or detailed the difference between
w
I'm told that Canonical IS would like this bug fixed so they don't have
to use a workaround, so we'll do that.
** Changed in: pollen (Ubuntu Trusty)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to th
@Jacek,
Right, but who actually needs this fixed? Do you need this fixed? If yes
then Triaged is fine. If not then let's leave it Won't Fix until
somebody actually comes forward. No point in doing an SRU that nobody
will use.
** Changed in: pollen (Ubuntu Trusty)
Status: Triaged => Won't F
No need to fix Trusty as we don't think anyone is impacted. If this is
incorrect then we can reopen.
** Changed in: pollen (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug repo
Confirmed based on
https://wiki.strongswan.org/projects/strongswan/wiki/ConfigSetupSection:
"if enabled, certificate revocation lists (CRLs) fetched via HTTP or
LDAP will be cached in /etc/ipsec.d/crls/ under a unique file name
derived from the certification authority's public key"
So /etc/ipsec.d
** Changed in: exim4 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1473839
Title:
using deleted file /var/log/exim4/mainlog.1
To manage n
** Also affects: psmisc (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: psmisc (Ubuntu Precise)
Status: New => Triaged
** Changed in: psmisc (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: psmisc (Ubuntu)
Status: New => Fix Released
*
Please could you rebase on 1.24.6-0ubuntu2? I'm not sure whether the MIR
changes have any implications for our process either - eg. for Vivid..
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.
** Also affects: juju-core (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Triaged
** Changed in: juju-core (Ubuntu Vivid)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
I see that five people are affected by this now so clearly there is some
kind of issue here. But as a developer I don't think this bug is ready
to be tackled by a developer.
Please could someone post exact steps to reproduce on a fresh Ubuntu
system? We need a test case before anyone can really lo
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please specify what Ubuntu release you are using and provide exact steps
to reproduce the problem. Once done, please change the bug status back
to New.
>From your description it sounds likely to me that this bug a
Thanks Jan.
** Changed in: nagios-plugins (Ubuntu)
Status: New => Triaged
** Changed in: nagios-plugins (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://
Thanks Andreas. Marking Fix Released as Wily has has 4.86-3ubuntu1 so
should have this fix already.
I'm not sure this warrants fixing in Trusty, as from what I've read this
behaviour shouldn't cause any significant impact to users expect for
late closure of the file. But if someone feels strongly
** Changed in: moin (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to moin in Ubuntu.
https://bugs.launchpad.net/bugs/1507390
Title:
UnicodeEncodeError on German LanguageSetup
To manage noti
301 - 400 of 3243 matches
Mail list logo
