Public bug reported:
On Ubuntu 13.04, using the stock dovecot and logwatch, I get unmatched
entries for dovecot when sieve delivers into a mailbox that has
whitespace in its name. The line which detects sieve deliveries (line
157) assumes that the mailbox name will not have whitespace:
}
I'm also seeing this problem on 2 of the machines under my control.
Two others running bind9 do notpo have this problem. The two that have
this problem do have DNSSEC enabled (though only one of them is actually
serving a DNSSEC-using zone).
This seems to be related to Debian bug #570852
The problem with the init script in the debian bug was that bind9 itself
wasn't dying, and the init script was set up to wait until bind9 died.
It was made moot by by upstream release of bind 9.8.1, which fixed the
problem of bind9 not dying.
--
You received this bug notification because you are
Public bug reported:
The /etc/nagios-plugins/config/pgsql.cfg configuration file includes a
check_pgsql_4 command, which should force the connection to use IPv4.
However, the program called, /usr/lib/nagios/plugins/check_pgsql, does
not actually accept the -4 parameter. I'd rather see this
Public bug reported:
This started up when I upgraded to Oneiric.
I'm fairly consistently finding that when using wput with --binary and
--limit-rate for an ftp upload, the upload ends with a buffer overflow.
A sample recent run (host, username, and password obscured):
oloryn@fornost:~$
This problem also exists in Natty. I just installed a new server with
Natty, and it has this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/564476
Title:
OverflowError, long int exceeds
This good idea is still unimplemented over 2 years later. For something
that's 'not hard to achieve', that's quite a while.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/199418
Title:
imagemagick
What's holding this up?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/58625
Title:
subversion doesn't includes a /etc/init.d/svnserve script
To manage notifications about this bug go to:
Public bug reported:
On Ubuntu 13.04, using the stock dovecot and logwatch, I get unmatched
entries for dovecot when sieve delivers into a mailbox that has
whitespace in its name. The line which detects sieve deliveries (line
157) assumes that the mailbox name will not have whitespace:
}
Public bug reported:
The /etc/nagios-plugins/config/pgsql.cfg configuration file includes a
check_pgsql_4 command, which should force the connection to use IPv4.
However, the program called, /usr/lib/nagios/plugins/check_pgsql, does
not actually accept the -4 parameter. I'd rather see this
I'm also seeing this problem on 2 of the machines under my control.
Two others running bind9 do notpo have this problem. The two that have
this problem do have DNSSEC enabled (though only one of them is actually
serving a DNSSEC-using zone).
This seems to be related to Debian bug #570852
The problem with the init script in the debian bug was that bind9 itself
wasn't dying, and the init script was set up to wait until bind9 died.
It was made moot by by upstream release of bind 9.8.1, which fixed the
problem of bind9 not dying.
--
You received this bug notification because you are
In utopic, /usr/share/man/man1/gem.1.gz points to gem2.1.1.gz, and comes
from the ruby package.
Note that in trusty, /usr/share/man/man1/gem.1.gz pointed to
gem1.9.1.1.gz (also from the ruby package), and gem1.9.1.1.gz comes
from the ruby1.9.1 package. Looks like gem2.1.1.gz was left out of the
In utopic, /usr/share/man/man1/gem.1.gz points to gem2.1.1.gz, and comes
from the ruby package.
Note that in trusty, /usr/share/man/man1/gem.1.gz pointed to
gem1.9.1.1.gz (also from the ruby package), and gem1.9.1.1.gz comes
from the ruby1.9.1 package. Looks like gem2.1.1.gz was left out of the
Also happened to me on 14.10-15.04 upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282294
Title:
Cannot open pixbuf loader module file
To manage notifications about this bug go to:
This problem still exists in 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247116
Title:
package w3c-markup-validator (not installed) failed to
install/upgrade: subprocess installed
Just checked this on 14.04 and 15.10, and this fix is present. I
presume it was added upstream?
** Changed in: logwatch (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in
Just checked this on 14.04 and 15.10, and this fix is present. I
presume it was added upstream?
** Changed in: logwatch (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1440608 ***
https://bugs.launchpad.net/bugs/1440608
** This bug has been marked a duplicate of bug 1440608
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except
the latest one
--
You received this bug notification because you are a
I agree with cavsfan that /etc/kernel/postinst.d/apt-auto-removal should
not be triggered when you delete a kernel. What is happening is that
/etc/apt/apt.conf.d/01autoremove-kernels is being set to prevent
kernel[0] and kernel[-2] from being autoremoved, instead of kernel[0]
and kernel[-1].
Also note that while 15.10 does change the permissions on
/sys/kernel/debug/tracing (from drwxr-xr-x in 15.04 to drwx-- in
15.10), the permissions on /sys/kernel/debug are drwx-- on both
15.10 and 15.04 - which means that /sys/kernel/debug shouldn't be
readable from a non-root account on
Also note that while 15.10 does change the permissions on
/sys/kernel/debug/tracing (from drwxr-xr-x in 15.04 to drwx-- in
15.10), the permissions on /sys/kernel/debug are drwx-- on both
15.10 and 15.04 - which means that /sys/kernel/debug shouldn't be
readable from a non-root account on
Public bug reported:
After upgrading to Xenial, an often-run cron job that uses Dnsruby
started kicking out a warning:
/usr/lib/ruby/vendor_ruby/dnsruby.rb:413: warning: constant
Dnsruby::TimeoutError is deprecated
That line is:
class ResolvTimeout < TimeoutError
Evidently, under Ruby 2.3
Ah. Apparently 304.134 release I got was from the graphics-drivers PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634802
Title:
Could not insert module
To manage notifications about this bug
Apparently, there was a nvidia-304-304.134 release in the past week. I
still had to uncomment the "#PATCH[1]="buildfix_kernel_4.3.patch" line
in dkms.conf and run 'dpkg-reconfigure nvidia-304' to get rid of the
mtrr-add and mtrr-del references so it would load, but the speed problem
that others
This problem still exists in 17.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671922
Title:
apticron calls apt-listchanges with incorrect arguments
To manage notifications about this bug go
Public bug reported:
I just upgraded my Nagios3 server from Yakkety to Zesty, and the icon
and status map images no longer display. Icons come up as broken
images, and status map images show as question marks. I can see the
images under both /usr/share/nagios/htdocs/images/logos/ and
Public bug reported:
After updating to 16.10, apticron report emails no longer show Package
Details, instead showing the usage message from apt-listchanges. E.g.:
apticron report [Thu, 09 Mar 2017 19:09:15 -0500]
apticron
I tried the proposed nagios-immages/0.9.1ubuntu0.1, and it indeed fixes
this problem.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tied that last link to the Debian bug, linked above. That includes a
patch, or since apticron seems to have fixed this in 1.1.59, 1.1.61
(which is in artful) could be backported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I dug into this a bit. I added the line
print("apt-listchanges arguments: ", str(sys.argv))
as the first line of main in apt-listchanges. Next time apticron was
called, it produced this:
---
apticron report [Tue, 27 Jun 2017 23:14:42 -0400]
** Bug watch added: Debian Bug tracker #837413
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837413
** Also affects: apticron (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837413
Importance: Unknown
Status: Unknown
--
You received this bug notification because
This might be related to http://git.net/ml/general/2016-09/msg13810.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671922
Title:
apticron calls apt-listchanges with incorrect arguments
To
Yes, this is the host icons not showing (or, specifically, pointing to
the wrong location) on the map, hosts, services, host groups, and host
groups/grid pages (at least).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I note that currently, bionic shows the same version of fail2ban as
artful (0.9.7-2). Might it be possible to upgrade to version 0.10.0 or
later, which adds the ability to handle IPv6 addresses?
** Affects: fail2ban (Ubuntu)
Importance: Undecided
Status: New
This is potentially especially annoying to me, because I have backups
that use s3cmd that run under cron, with the expectation that they emit
nothing when the backups go ok. Spewing these warnings could
potentially spam my inbox daily.
--
You received this bug notification because you are a
36 matches
Mail list logo
