[Bug 1874651] Re: SyntaxWaning on bad equality check
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874651 Title: SyntaxWaning on bad equality check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3cmd/+bug/1874651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744411] [NEW] Upgrade to fail2ban 0.10.0 or later?
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744411 Title: Upgrade to fail2ban 0.10.0 or later? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1744411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683109] Re: icon/statusmap images don't work after upgrading to Zesty
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. https://bugs.launchpad.net/bugs/1683109 Title: icon/statusmap images don't work after upgrading to Zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-images/+bug/1683109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671922] Re: apticron calls apt-listchanges with incorrect arguments
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. https://bugs.launchpad.net/bugs/1671922 Title: apticron calls apt-listchanges with incorrect arguments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1671922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671922] Re: apticron calls apt-listchanges with incorrect arguments
** 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 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 to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1671922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671922] Re: apticron calls apt-listchanges with incorrect arguments
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1671922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671922] Re: apticron calls apt-listchanges with incorrect arguments
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]
apticron has detected that some packages need upgrading on:
morannon.ln.benshome.net
[ 172.17.113.244 ]
The following packages are currently pending an upgrade:
bsdutils 1:2.29-1ubuntu2.1
grub-legacy-ec2 0.7.9-153-g16a7302f-0ubuntu1~17.04.1
libblkid1 2.29-1ubuntu2.1
libfdisk1 2.29-1ubuntu2.1
libmount1 2.29-1ubuntu2.1
libnss-resolve 232-21ubuntu5
libpam-systemd 232-21ubuntu5
libsmartcols1 2.29-1ubuntu2.1
libsystemd0 232-21ubuntu5
libudev1 232-21ubuntu5
libuuid1 2.29-1ubuntu2.1
mount 2.29-1ubuntu2.1
nplan 0.23~17.04.1
systemd 232-21ubuntu5
systemd-sysv 232-21ubuntu5
udev 232-21ubuntu5
util-linux 2.29-1ubuntu2.1
uuid-runtime 2.29-1ubuntu2.1
Package Details:
Usage: apt-listchanges [options] {--apt | filename.deb ...}
apt-listchanges arguments: ['/usr/bin/apt-listchanges', '--which=both',
'--headers', '-f', 'text']
---
The problem appears to be that there are no .deb files provided (as all
of the other arguments look valid). The execution of apt-listchanges is
in line 225 of /usr/sbin/aptcron (on 17.10):
/usr/bin/apt-listchanges --which=both --headers -f text $DEBS
It would appear that $DEBS at this point is empty, rather than
containing pathnames for the .debs to be listed. This would seem to
point to a problem in lines 194 - 213, where DEBS is set.
--
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 to:
https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1671922/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683109] Re: icon/statusmap images don't work after upgrading to Zesty
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. https://bugs.launchpad.net/bugs/1683109 Title: icon/statusmap images don't work after upgrading to Zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1683109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671922] Re: apticron calls apt-listchanges with incorrect arguments
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 to: https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1671922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683109] [NEW] icon/statusmap images don't work after upgrading to Zesty
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 /usr/share/nagios3/htdocs/images/logos/. Evidently, the images are for some reason not being found in either place. ** Affects: nagios3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683109 Title: icon/statusmap images don't work after upgrading to Zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1683109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671922] [NEW] apticron calls apt-listchanges with incorrect arguments
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 has detected that some packages need upgrading on:
dos3.benshome.net
[ 104.131.218.115 10.128.254.248 2001:470:1f07:3f3::1 ]
[ 2001:470:1f06:3f3::2 104.131.218.115 2001:470:1f07:3f3::1 ]
The following packages are currently pending an upgrade:
libarchive13 3.2.1-2ubuntu0.1
Package Details:
Usage: apt-listchanges [options] {--apt | filename.deb ...}
Looks like perhaps apt-listchanges has had a change in argument format, and
apticron hasn't been changed to accomodate it?
** Affects: apticron (Ubuntu)
Importance: Undecided
Status: New
--
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 to:
https://bugs.launchpad.net/ubuntu/+source/apticron/+bug/1671922/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634802] Re: Could not insert module
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 go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634802] Re: Could not insert module
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 have noted appears to have been dealt with. At least watching Netflix on this particular machine is back to where it was on 16.04. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592667] [NEW] Use of dnsruby triggers a deprecation warning under Xenial
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 (the default Ruby for Xenial), TimeoutError should be Timeout::Error. I also note that this package appears to be sourced from the old RubyForge site. The project has been moved to https://github.com/alexdalitz/dnsruby. The latest release (1.59.2) has the above problem fixed. ** Affects: dnsruby (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592667 Title: Use of dnsruby triggers a deprecation warning under Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsruby/+bug/1592667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10
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 either release, so this looks like a code change in check_disk. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1516451 Title: check_disk plugin broken after upgrade to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10
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 either release, so this looks like a code change in check_disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516451 Title: check_disk plugin broken after upgrade to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446269] Re: autoremove kernel management leaves one single kernel
*** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446269 Title: autoremove kernel management leaves one single kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1446269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
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]. Take a recent situation. After the installation of kernel 3.19.0-28, the kernels 3.19.0-25, 3.19.0-26, and 3.19.0-28 are installed, and /etc/apt/apt.conf.d/01autoremove-kernels is set to prevent 3.19.0-26 and 3.19.0-28 from being removed. When you run the autoremove in this situation, 3.19.0-25 is removed. If /etc/kernel/postinst.d/apt-auto-removal is triggered during this removal, it will mark as not-for-autoremoval (according to the comments at the top of apt-auto-removal): * the currently booted version - this will be 3.19.0-28 * the kernel version we've been called for - this will be 3.19.0-25 (which is the kernel we've just removed - why are we marking for non-auto-removal a kernel which has already been removed?) * the latest kernel version - this will be 3.19.0-28 * the second-latest kernel version, if the booted kernel version is already the latest and this script is called for that same version - this doesn't apply, as this script isn't being called for the latest version, it's being called for the version we're deleting. The result is that /etc/apt/apt.conf.d/01autoremove-kernels is set to prevent 3.19.0-25 and 3.19.0-28 from being autoremoved, while the system actually contains 3.19.0-26 and 3.19.0-28. Autoremove will, in this case, want to remove 3.19.0-26, leaving only 3.19.0-28. I think the fact that having a kernel removal trigger /etc/kernel/postinst.d/apt-auto-removal will result in marking for non- auto-removal a kernel that is already removed alone indicates that something is not being done correctly. Either don't trigger /etc/kernel/postinst.d/apt-auto-removal on a kernel remove, or tweak /etc/kernel/postinst.d/apt-auto-removal to handle the fact that the kernel it's being called for is being deleted, not added (perhaps don't do criteria 2 (the kernel version we've been called for) and do criteria 4 (tweak criteria 4's conditions to have it apply on a deletion). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440608 Title: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194960] Re: unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace
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 Ubuntu. https://bugs.launchpad.net/bugs/1194960 Title: unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1194960/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1194960] Re: unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace
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. https://bugs.launchpad.net/bugs/1194960 Title: unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1194960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247116] Re: package w3c-markup-validator (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/w3c-markup-validator/+bug/1247116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282294] Re: Cannot open pixbuf loader module file
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: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418636] Re: /usr/share/man/man1/gem.1.gz is a dangling symlink
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 utopic ruby2.1 package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418636 Title: /usr/share/man/man1/gem.1.gz is a dangling symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/1418636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418636] Re: /usr/share/man/man1/gem.1.gz is a dangling symlink
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 utopic ruby2.1 package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ruby-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1418636 Title: /usr/share/man/man1/gem.1.gz is a dangling symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-defaults/+bug/1418636/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1194960] [NEW] unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace
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:
} elsif ( ($User, $Mailbox) = ( $ThisLine =~ /^$dovecottag
(?:lda\(|deliver\(|lmtp\(\d+, )(.*)\): (?:[^:]+: )?sieve: msgid=.*:
stored mail into mailbox '(\S+)'/ ) ) {
It's quite possible to have whitespace in mailbox names. In my case,
using a Thunderbird client with Dovecot IMAP will allow mailboxes with
whitespace in the name to be created quite easily.
This can be fixed by instead accepting non-single-quote characters in
the mailbox name :
} elsif ( ($User, $Mailbox) = ( $ThisLine =~ /^$dovecottag
(?:lda\(|deliver\(|lmtp\(\d+, )(.*)\): (?:[^:]+: )?sieve: msgid=.*:
stored mail into mailbox '([^']+)'/ ) ) {
I've got this fix running on my mail server, and it clears up the
unmatched sieve delivery entries I had been getting.
** Affects: logwatch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/1194960
Title:
unmatched entries for dovecot sieve deliveries when mailbox name
contains whitespace
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1194960/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1194960] [NEW] unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace
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:
} elsif ( ($User, $Mailbox) = ( $ThisLine =~ /^$dovecottag
(?:lda\(|deliver\(|lmtp\(\d+, )(.*)\): (?:[^:]+: )?sieve: msgid=.*:
stored mail into mailbox '(\S+)'/ ) ) {
It's quite possible to have whitespace in mailbox names. In my case,
using a Thunderbird client with Dovecot IMAP will allow mailboxes with
whitespace in the name to be created quite easily.
This can be fixed by instead accepting non-single-quote characters in
the mailbox name :
} elsif ( ($User, $Mailbox) = ( $ThisLine =~ /^$dovecottag
(?:lda\(|deliver\(|lmtp\(\d+, )(.*)\): (?:[^:]+: )?sieve: msgid=.*:
stored mail into mailbox '([^']+)'/ ) ) {
I've got this fix running on my mail server, and it clears up the
unmatched sieve delivery entries I had been getting.
** Affects: logwatch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194960
Title:
unmatched entries for dovecot sieve deliveries when mailbox name
contains whitespace
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1194960/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061154] [NEW] pgsql.cfg includes a check_pgsql_4 command, but check_pgsql does not actually take the -4 argument
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 fixed by adding the -4 parameter to check_pgsql than by deleting the command from pgsql.cfg, as this is actully a useful function. ** Affects: nagios-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1061154 Title: pgsql.cfg includes a check_pgsql_4 command, but check_pgsql does not actually take the -4 argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1061154/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1061154] [NEW] pgsql.cfg includes a check_pgsql_4 command, but check_pgsql does not actually take the -4 argument
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 fixed by adding the -4 parameter to check_pgsql than by deleting the command from pgsql.cfg, as this is actully a useful function. ** Affects: nagios-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061154 Title: pgsql.cfg includes a check_pgsql_4 command, but check_pgsql does not actually take the -4 argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1061154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58625] Re: subversion doesn't includes a /etc/init.d/svnserve script
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: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/58625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop
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 a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: DNSSEC-enabled named sometimes does not die on service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: DNSSEC-enabled named sometimes does not die on service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop
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 (http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=570852), which is fixed by the upstream 9.8.1 release, which is included in Precise. I'll try to upgrade one of the affected servers this weekend and see if that fixes it. ** Bug watch added: Debian Bug tracker #570852 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570852 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: DNSSEC-enabled named sometimes does not die on service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop
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 (http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=570852), which is fixed by the upstream 9.8.1 release, which is included in Precise. I'll try to upgrade one of the affected servers this weekend and see if that fixes it. ** Bug watch added: Debian Bug tracker #570852 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: DNSSEC-enabled named sometimes does not die on service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199418] Re: imagemagick depends on x stuff
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 depends on x stuff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/199418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 949689] [NEW] Wput ends with buffer overflow when rate-limited
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:~$ wput --binary --limit-rate=5K svnback2012-03-07.zip ftp://user name:passw...@hostname.benshome.net/svnback2012-03-07.zip --00:49:50-- `svnback2012-03-07.zip' = ftp://bhbackup:x@97.74.215.114:21/svnback2012-03-07.zip Connecting to 97.74.215.114:21... connected! encrypted! Logging in as bhbackup ... Logged in! Length: 8,092,575 100%[] 8,092,575 5.04K/s *** buffer overflow detected ***: wput terminated === Backtrace: = /lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x45)[0x34b8d5] /lib/i386-linux-gnu/libc.so.6(+0xe66d7)[0x34a6d7] /lib/i386-linux-gnu/libc.so.6(+0xe5d35)[0x349d35] /lib/i386-linux-gnu/libc.so.6(_IO_default_xsputn+0x91)[0x2cff91] /lib/i386-linux-gnu/libc.so.6(_IO_vfprintf+0x36e6)[0x2a7816] /lib/i386-linux-gnu/libc.so.6(__vsprintf_chk+0xc9)[0x349e09] /lib/i386-linux-gnu/libc.so.6(__sprintf_chk+0x2f)[0x349d1f] wput[0x8052a96] wput[0x804dee5] wput[0x804e588] wput[0x805608d] wput[0x804bbf0] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x27d113] === Memory map: 0011-001ba000 r-xp 08:01 7920 /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14 001ba000-001bb000 ---p 000aa000 08:01 7920 /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14 001bb000-001bf000 r--p 000aa000 08:01 7920 /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14 001bf000-001c rw-p 000ae000 08:01 7920 /usr/lib/i386-linux-gnu/libgnutls.so.26.16.14 001c-00242000 r-xp 08:01 7182 /lib/i386-linux-gnu/libgcrypt.so.11.7.0 00242000-00243000 r--p 00081000 08:01 7182 /lib/i386-linux-gnu/libgcrypt.so.11.7.0 00243000-00245000 rw-p 00082000 08:01 7182 /lib/i386-linux-gnu/libgcrypt.so.11.7.0 00245000-0024a000 r-xp 08:01 51705 /lib/i386-linux-gnu/libnss_dns-2.13.so 0024a000-0024b000 r--p 4000 08:01 51705 /lib/i386-linux-gnu/libnss_dns-2.13.so 0024b000-0024c000 rw-p 5000 08:01 51705 /lib/i386-linux-gnu/libnss_dns-2.13.so 00264000-003da000 r-xp 08:01 51697 /lib/i386-linux-gnu/libc-2.13.so 003da000-003dc000 r--p 00176000 08:01 51697 /lib/i386-linux-gnu/libc-2.13.so 003dc000-003dd000 rw-p 00178000 08:01 51697 /lib/i386-linux-gnu/libc-2.13.so 003dd000-003e rw-p 00:00 0 0046d000-0048b000 r-xp 08:01 51694 /lib/i386-linux-gnu/ld-2.13.so 0048b000-0048c000 r--p 0001d000 08:01 51694 /lib/i386-linux-gnu/ld-2.13.so 0048c000-0048d000 rw-p 0001e000 08:01 51694 /lib/i386-linux-gnu/ld-2.13.so 0057b000-0058b000 r-xp 08:01 7194 /usr/lib/i386-linux-gnu/libtasn1.so.3.1.11 0058b000-0058c000 r--p f000 08:01 7194 /usr/lib/i386-linux-gnu/libtasn1.so.3.1.11 0058c000-0058d000 rw-p 0001 08:01 7194 /usr/lib/i386-linux-gnu/libtasn1.so.3.1.11 00831000-00844000 r-xp 08:01 51712 /lib/i386-linux-gnu/libresolv-2.13.so 00844000-00845000 r--p 00012000 08:01 51712 /lib/i386-linux-gnu/libresolv-2.13.so 00845000-00846000 rw-p 00013000 08:01 51712 /lib/i386-linux-gnu/libresolv-2.13.so 00846000-00848000 rw-p 00:00 0 008bf000-008db000 r-xp 08:01 11212 /lib/i386-linux-gnu/libgcc_s.so.1 008db000-008dc000 r--p 0001b000 08:01 11212 /lib/i386-linux-gnu/libgcc_s.so.1 008dc000-008dd000 rw-p 0001c000 08:01 11212 /lib/i386-linux-gnu/libgcc_s.so.1 00c95000-00c9e000 r-xp 08:01 7923 /usr/lib/i386-linux-gnu/libgnutls-openssl.so.26.16.14 00c9e000-00c9f000 r--p 8000 08:01 7923 /usr/lib/i386-linux-gnu/libgnutls-openssl.so.26.16.14 00c9f000-00ca rw-p 9000 08:01 7923 /usr/lib/i386-linux-gnu/libgnutls-openssl.so.26.16.14 00ddf000-00dea000 r-xp 08:01 51706 /lib/i386-linux-gnu/libnss_files-2.13.so 00dea000-00deb000 r--p a000 08:01 51706 /lib/i386-linux-gnu/libnss_files-2.13.so 00deb000-00dec000 rw-p b000 08:01 51706 /lib/i386-linux-gnu/libnss_files-2.13.so 00e0a000-00e0b000 r-xp 00:00 0 [vdso] 00e1-00e13000 r-xp 08:01 7174 /lib/i386-linux-gnu/libgpg-error.so.0.8.0 00e13000-00e14000 r--p 2000 08:01 7174 /lib/i386-linux-gnu/libgpg-error.so.0.8.0 00e14000-00e15000 rw-p 3000 08:01 7174 /lib/i386-linux-gnu/libgpg-error.so.0.8.0 00ea8000-00ebb000 r-xp 08:01 23393 /lib/i386-linux-gnu/libz.so.1.2.3.4 00ebb000-00ebc000 r--p 00012000 08:01 23393 /lib/i386-linux-gnu/libz.so.1.2.3.4 00ebc000-00ebd000 rw-p 00013000 08:01 23393 /lib/i386-linux-gnu/libz.so.1.2.3.4 08048000-0805c000 r-xp 08:01 2247 /usr/bin/wput 0805c000-0805d000 r--p 00013000 08:01 2247 /usr/bin/wput 0805d000-0805e000 rw-p 00014000 08:01 2247
[Bug 564476] Re: OverflowError, long int exceeds XML-RPC limits
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 XML-RPC limits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/denyhosts/+bug/564476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
