*** This bug is a security vulnerability ***
Public security bug reported:
There is a new upstream version 68.6.0 available which fixes several medium and
high risk security vulnerabilities.
Please release a new Ubuntu package ASAP - see the Debian project, which has
already done so.
** Affect
Had this problem on one of my servers (the only one running bind on
Bionic), installed this proposed-update package on Thursday morning,
31st, and have not seen this error since then. Searching through my logs
I saw this error appearing at least every second day - often more than
once a day - and h
** Also affects: amavisd-milter (Debian)
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/1584180
Title:
new version 1.6.1 out since 2015-05-24
To manage no
Public bug reported:
A new upstream version 1.6.1 was released on May 24th, 2015!
It is really time to package this new version as it has a bug fixed and
some new and important features added.
** Affects: amavisd-milter (Ubuntu)
Importance: Undecided
Status: New
--
You received t
No, I just tested a proposed update from Jamie Strandboge's PPA.
See comment #37 and #41.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186662
Title:
isc-dhcp-server fails to renew lease file
To m
Yes, it seems to fix it, but there is a upgrade-problem:
...
Mar 1 21:52:16 server kernel: [177627.390088] init: isc-dhcp-server main
process (1218) killed by TERM signal
Mar 1 21:52:20 server dhcpd: Internet Systems Consortium DHCP Server 4.2.4
Mar 1 21:52:20 server dhcpd: Copyright 2004-2012
*** This bug is a duplicate of bug 1399615 ***
https://bugs.launchpad.net/bugs/1399615
** This bug has been marked a duplicate of bug 1399615
webalizer damages webalizer.hist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Attached is a patch that makes bindgraph work again. It might not be the right
solution, but it makes it work again.
As bindgraph includes a modified copy of Parse::Syslog, which conflicts with
the default one, the attached patch just renames the copy included in bindgraph.
** Patch added: "bind
** Bug watch added: Debian Bug tracker #760660
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760660
** Also affects: bindgraph (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760660
Importance: Unknown
Status: Unknown
--
You received this bug notification because
No, just look at the script stanzas used in the statd.conf or
winbind.conf as an example.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/406397
Title:
init: job stuck with expect fork/daemon when par
*** This bug is a security vulnerability ***
Public security bug reported:
The Debian project fixed a security issue in the denyhosts package - see
http://lists.debian.org/debian-security-announce/2013/msg00240.html and
CVE-2013-6890.
** Affects: denyhosts (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 516592 ***
https://bugs.launchpad.net/bugs/516592
So, this is more like bug #516592 ...
** This bug has been marked a duplicate of bug 516592
Network manager kills NFS link on going to sleep hanging Gnome etc.
--
You received this bug notification becau
** This bug is no longer a duplicate of bug 79
missing apparmor access rule
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/377268
Title:
package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 f
Sander et al.,
I found a problem in the upstart config file from your resolvconf
patch:
> start on ( virtual-filesystems and starting udev )
This makes a "restart udev" hang, because upstart waits for resolvconf
to finish, which will never happen, as it waits for the signal "virtual-
filesystems
Unfortunately, the included fix (force changing ownership on start-up)
breaks logging of innd and running news-daily, as the logfiles should be
owned by news.news but are now forced to syslog.adm. The init.d script
from syslogd mentioned in https://bugs.launchpad.net/bugs/120085 uses
"syslogd-listf
*** This bug is a duplicate of bug 570103 ***
https://bugs.launchpad.net/bugs/570103
** This bug has been marked a duplicate of bug 570103
rsyslog still includes /etc/default/rsyslog, which isn't used
* You can subscribe to bug 570103 by following this link:
https://bugs.launchpad.net/ubu
Hmm, seems #485556 would be the right bug for my report - if so, I
apologize. What a subtle difference...
--
WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129
idr_callback+0x4f/0x80()
https://bugs.launchpad.net/bugs/442966
You received this bug notification because
Any news on a release date for Karmic?
--
inotify oops with wd == 4096
https://bugs.launchpad.net/bugs/485556
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I just got one yesterday running kernel 2.6.31-20.58, but I'm unsure
whether or not this is the same oops. If you think this is not the same
oops, please tell me so that I can open another bug report.
[2643126.913740] WARNING: at
/build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:12
And once again I was hit by this bug, this time with kernel
2.6.31-19-server #56-Ubuntu, which was just superseded by kernel
2.6.31-20-server #58-Ubuntu, which is running now on my server.
--
WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129
idr_callback+0x4f/0x80()
Public bug reported:
Binary package hint: webalizer
Webalizer 2.01.10-32.5ubuntu1 on Karmic truncates numerical IPv6 addresses
after the first colon, e.g.:
2001:6f8:1ccd::1 is truncated to just 2001.
Please also see Debian bug report #452259, where also a patch is
attached: http://bugs.debian.o
Can you double-check that
a) really this line makes mysql start again (just remove that line, restart
apparmor and try to restart mysql)
b) you really started mysql *after* apparmor
I just double-checked this issue on my system and mysql 5.1 will start
without problems with the proposed line miss
To everyone having problems with not starting mysql daemons:
This bug (or better: omission) does *not* prevent mysql from starting - it just
produces a message in the syslog about a denied file access.
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug
Just to confirm that this bug is still not fixed: I just got this report
on my up-to-date server. The system was more or less idle with the usual
server stuff running (apache, postfix, bind,...).
Dec 24 12:27:59 batleth kernel: [1217678.140504] [ cut here
]
Dec 24 12:27:59
Using
deny /sys/devices/system/cpu/ r,
seems to just suppress the message but makes no difference to
functionality (access to /sys/devices/system/cpu/ is denied and
/proc/stat accessed instead).
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notif
No, not that I have noticed. Mysqld seems to access /proc/stat if
/sys/devices/system/cpu/ is not accessible.
--
missing apparmor access rule
https://bugs.launchpad.net/bugs/79
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Public bug reported:
On Ubuntu Karmic beta1:
If the package ganglia-monitor-3.1.2-2 is installed after gmetad-3.1.2-2,
gmetad won't start anymore due to wrong ownership of /var/lib/ganglia/rrds:
/usr/sbin/gmetad[11457]: Please make sure that /var/lib/ganglia/rrds is owned
by nobody
Gmetad shou
Public bug reported:
Testing with mysql-server-5.1 5.1.37-1ubuntu4 on Karmic Beta1, I get the
following error message in /var/log/syslog after starting mysqld:
kernel: [86913.526900] type=1503 audit(1254826475.203:56): operation="open"
pid=19633 parent=19632 profile="/usr/sbin/mysqld" requested_
** Attachment added: "proposed patch to make logging to console configurable"
http://launchpadlibrarian.net/20022706/lsb-base.patch
--
clutters console with messages during normal work
https://bugs.launchpad.net/bugs/61760
You received this bug notification because you are a member of Ubuntu
It would be nice to have at least a way to disable that "feature", something
like a flag in /etc/default/...
I know that there is an environment variable called QUIET which can be set to
'yes', but unfortunately, programs like 'ifup' call sub-shells with a cleaned
environment, so that this varia
30 matches
Mail list logo
