Public bug reported:
unbound.service in Ubuntu 20.04LTS Focal has insufficient dependencies
for the ExecStartPre package-helper root_trust_anchor_update command to
reliably succeed, while it depends on network.target that is no
guarantee that network is available.
While unbound startup succeeds,
For nfs-server and the risk of applying the fix to stable releases, this
is my take:
It won't break anything unless you've done something truly esoteric, and
then you're on your own anyway IMHO.
It will enable nfs-server to consistently start in configurations using
static addressing, which is
For this I honestly see no risks of regressions for nfs-server.
Also, be aware that on systems using DHCP depending on network.target or
network-online.target has the same effect simply due to the inherent
ordering of DHCP packets not passing through until the interface is able
to pass traffic.
OK, getting the network delay got a little bit convoluted as you can't
clear dependencies with overrides but instead have to copy the unit file
and edit it.
I'm no systemd expert so this can probably be improved, but on a focal
VM host of ours (KVM/Ganeti) that uses systemd-networkd I needed to
First off, nfs-server starts but doesn't export the unresolvable hosts.
The failures do show in systemctl status nfs-server.
To reproduce in a VM you'll likely need something that causes
network.target to be fulfilled but actual network traffic to not be
forwarded until a few seconds later when
I should note that we have observed this on both 18.04LTS (bionic) and
20.04LTS (focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918141
Title:
nfs-server.service needs name resolution and
Public bug reported:
nfs-server.service has insufficient dependencies to start correctly in a
setting where the nfs exports list contains DNS host names (not in local
hosts file) or netgroups served via network (for example sssd).
Typical failures listed by systemctl status nfs-server.service
This indeed has to be a packaging bug. The last changelog entry says
"Build using python2" but there is no dependency of anything python in
the ganglia-monitor package:
Depends: libapr1 (>= 1.2.7), libc6 (>= 2.14), libconfuse2 (>= 3.2.1~),
libganglia1 (= 3.6.0-7ubuntu4), libpcre3, zlib1g (>=
Public bug reported:
The kernel.pid_max sysctl defaults to 32768. This is a very historic
limit to provide compatibility with ancient binaries.
Moving on to the year 2020 multicore CPU:s for desktops, laptops and
servers is the standard, and together with PID randomization wraparound
happens
Johan Guldmyr pointed out that my udev rule attempted to apply the
attribute changes to partitions as well, which causes errors in system
log files.
Uploading a fixed version.
** Attachment added: "90-smartarray-limitiosize.rules"
We realized that this likely affects older controllers using the cciss
driver as well, updated udev rule for completeness.
** Attachment added: "90-smartarray-limitiosize.rules"
As a workaround this udev rule can be used.
Caveat: It works as intended for us, but I'm not an udev expert.
** Attachment added: "90-hpsa-limitiosize.rules"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828213/+files/90-hpsa-limitiosize.rules
--
You received
Last time I checked the hpsa driver is part of the kernel shipped with
Ubuntu...
Regardless of whether the core kernel is doing it right or not, the hpsa
driver should not advertise a larger max_sectors_kb than it can handle
with good performance.
FYI, the hpsa driver in the xenial default
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828122/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828123/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828124/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828125/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828121/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828120/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828118/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828119/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
Title:
apport information
** Tags added: apport-collected xenial
** Description changed:
Upgrading our HP(E) servers to xenial we have discovered a severe
performance regression affecting write performance on Smart Array RAID
logical drives.
Firmware is up to date with latest HPE SPP
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828116/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1668557/+attachment/4828117/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828074/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668557
** Attachment added: "hpssacli-show-config-detail.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828075/+files/hpssacli-show-config-detail.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Upgrading our HP(E) servers to xenial we have discovered a severe
performance regression affecting write performance on Smart Array RAID
logical drives.
Firmware is up to date with latest HPE SPP release at the time of
testing.
This performance regression has been verified
Upstream bug/discussion: https://github.com/anholt/libepoxy/issues/72
Main issue seems to be libepoxy having been unmaintained for some time,
but this issue is showing up in other distros as well so will have to be
fixed sooner or later.
Patch is trivial, bug/crash is due to passing on a pointer
*** This bug is a duplicate of bug 1574886 ***
https://bugs.launchpad.net/bugs/1574886
** This bug has been marked a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1574886 ***
https://bugs.launchpad.net/bugs/1574886
** This bug has been marked a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1574886 ***
https://bugs.launchpad.net/bugs/1574886
** This bug has been marked a duplicate of bug 1574886
All gtk applications Segfault if no GLX context is active
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It wasn't as easy as just rebuilding the package, build fails due to a
test failing: https://rt.cpan.org/Public/Bug/Display.html?id=89976
Getting a newer source package from http://packages.ubuntu.com/vivid
/libpdl-stats-perl and just doing dpkg-buildpackage on it gives me a
.deb, and with it
** Package changed: pdl (Ubuntu) = libpdl-stats-perl (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434508
Title:
PDL::Stats::Basic needs to be recompiled against the newly installed
PDL
Public bug reported:
[Impact]
Ubuntu trusty/14.04 (LTS).
Although package can be installed, it's not usable due to pdl, which it
depends on, has been upgraded but this package has not been rebuilt
against it.
This affects all LTS installations (mostly enterprise environments, compute
** Also affects: hundredpapercuts
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/1434508
Title:
PDL::Stats::Basic needs to be recompiled against the newly
As suggested earlier, this issue seems to be tracked in bug 1140716.
That bug recently logs Fix Released.
In hindsight, I'm guessing that the original issue of this bug was
something completely different given its age. But since this was what
popped up when searching...
--
You received this
Same here on precise amd64. Booting with 3.2.0-39 X hangs shortly after
login with the earlier mentioned hangcheck messages in the kernel log
(machine is remotely login:able). Reverting to 3.2.0-38 yields a stable
machine.
This is on a machine with an Intel i5 CPU on an ASUS P8H67-V
motherboard,
** Tags removed: verification-needed-precise verification-needed-quantal
** Tags added: verification-done verification-done-precise
verification-done-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have now tested the NFS 4.1 functionality of both the Precise and
Quantal kernels and they both work as expected. No regressions have been
found when testing on machines not using NFS 4.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For starters, no regressions noticed on machines not using the new features:
amd64 laptop doing laptoppy things, also reading/writing nfs3.
amd64 server, doing mostly local IO.
Pending results from NFS 4.1 tests this is looking promising.
--
You received this bug notification because you are a
Out if curiosity, which version of hpacucli are you guys using? Version?
32bit or 64bit?
Running Precise, I see this problem on controllers using the old cciss
driver (P400 for example), but not on controllers using the hpsa driver
(P810 for example). This is with hpacucli 9.10 64bit.
This all
hpacucli 8.x is only available as 32bit binaries.
9.x is available as both 32bit and 64bit binaries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006212
Title:
cciss: hpacucli ctrl slot=0 create
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065536
Title:
rsyslog imrelp module doesn't do DNS resolve to hostname
To manage notifications about this bug go to:
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789174
Title:
rsyslog fails to create tcp socket.
To manage notifications about this bug go to:
iwl4965 is a kernel module
** Package changed: module-init-tools (Ubuntu) = linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997123
Title:
iwl4965 works imposible slow because it
I have stability/connectivity issues on University campuses, most of
them using high-end Cisco wireless equipment, when I have 11n enabled on
Ubuntu 12.04LTS.
This was not a problem with 10.04LTS, so this is a regression.
--
You received this bug notification because you are a member of Ubuntu
Is this perhaps a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836250 ??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997123
Title:
iwl4965 works imposible slow because it
This should be fixed ASAP, Ganglia is an important component in many
server environments which is the target of LTS releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910678
Title:
gmond
Public bug reported:
Binary package hint: ifupdown
net-device-up is emitted when bonding link members are configured, which
is rather misleading as the machine won't get connectivity until the
master device is configured. This leads to problems if you for example
wants to use a post-up hook in
** Patch added: Proposed fix to not emit events for bonding member devices.
https://bugs.launchpad.net/bugs/660974/+attachment/1693852/+files/upstart.patch
--
net-device-up emitted for bonding members
https://bugs.launchpad.net/bugs/660974
You received this bug notification because you are
A lame workaround is to simply add this to /etc/rc.local (before the exit 0):
/sbin/initctl start statd
--
mountall for /var races with rpc.statd
https://bugs.launchpad.net/bugs/525154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On my lucid install ipmi_si seems to autoload, but ipmi_devintf doesn't.
Loading ipmi_devintf is enough to have /dev/ipmi0 created and ipmitool then
works.
--
ipmi modules need to manually inserted and device created
https://bugs.launchpad.net/bugs/110992
You received this bug notification
On my lucid install ipmi_si seems to autoload, but ipmi_devintf doesn't.
Loading ipmi_devintf is enough to have /dev/ipmi0 created and ipmitool then
works.
--
ipmi modules need to manually inserted and device created
https://bugs.launchpad.net/bugs/110992
You received this bug notification
Public bug reported:
Please include the backport of the driver for mantis/hopper based DVB
cards in the Ubuntu Lucid kernel. There are lots of DVB cards that uses
this driver.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577264 for an
excellent summary including the patches accepted in
The driver is included in 2.6.33, so it works with the latest upstream
kernel.
This backport inclusion request is specific to the Lucid (LTS) kernel.
** Tags removed: needs-kernel-logs needs-upstream-testing
--
Include backport of driver for mantis/hopper DVB cards
On Sun, 28 Mar 2010, ceg wrote:
Is this still an issue with recent releases? mdrun isn't around
anymore
Haven't verified, but I suspect it is.
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se |ni
I'm also seeing this, but on intrepid.
And, argh!
I looked in Edit-Preferences-Applications, and when the behaviour for
PDF states always ask and the damn thing didn't obey that I gave up my
first efforts...
Btw, the main reason I want to disable it is that my firefox always
crashes when left
That's funny, since the bug is that the cciss-driver on _dapper_ doesn't
support large devices.
The main issue here is what kind of support we really can expect for the
LTS releases, you should keep in mind that the LTS-releases are the ones
mainly deployed in larger environments where you don't
Testing on hardy it works, naturally, because it's 5.2.4-2ubuntu4 and
since the bug is fixed upstreams in 5.2.4 ...
--
open_basedir restriction causes bogus warnings
https://bugs.launchpad.net/bugs/164386
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Binary package hint: xorg-driver-fglrx
Package: xorg-driver-fglrx
Source: linux-restricted-modules-2.6.24 (2.6.24.6-4.13)
Version: 1:7.1.0-8-01+2.6.24.6-4.13
Ubuntu hardy amd64 on HP8510p (mobility HD2600).
X using fglrx worked until doing an aptitude update and rebooting
Public bug reported:
Binary package hint: php5-cgi
Enabling an open_basedir restriction causes bogus warnings to be
emitted.
Testcase (using php-cli):
# /usr/bin/php5 -d open_basedir=/tmp/ -r 'var_dump(file_exists(/tmp/nosuch));'
Warning: file_exists(): open_basedir restriction in effect.
Debian packaging of the cciss 2.6.18-5 driver.
This is the driver above, I have only added some packaging to produce a
source package that can be used by module-assistant. The module-
assistant target also produces a meta package which depends on the
latest (ie. newly built) module package.
The
Public bug reported:
Binary package hint: linux-image-2.6.15-28-amd64-server
The Dapper cciss driver doesn't handle devices larger than 2TB in size.
This is becoming a real problem in environments like ours where we
prefer having all our servers on the Ubuntu LTS track. For example, the
HP
cciss 2.6.18-5 driver (available from http://cciss.sourceforge.net/)
hacked so it compiles cleanly on Ubuntu Dapper AMD64. Only tested on
Dapper AMD64 in a HP DL320s with SmartArray P400 controller and a raid6
set consisting of 11x750GB SATA drives.
To build:
apt-get install module-assistant
m-a
Public bug reported:
Binary package hint: wesnoth
Wesnoth 1.2.3 has gameplay bugs; the character supposed to go to a
specific place to finish the chapter (South Guard: Vengeance) does not
show up at all. Neither does the other veterans from the previous
chapter.
See
The issue might be that the machine in question had edgy-backports (to
get working gphoto2 stuff), and edgy-backports and feisty has the same
libgphoto2-2 version.
--
udev-rule for PTP class detection broken
https://bugs.launchpad.net/bugs/67532
You received this bug notification because you are
This is a machine upgraded from edgy, and doing dpkg-reconfigure
libgphoto2-2 indeed gives me a correct 45-libgphoto2.rules that has the
comment about being for a new udev version.
I suspect that when doing an upgrade it's still running the old udev-
version, and thus generates the file for the
Indeed, editing /etc/udev/rules.d/45-libgphoto2.rules and replacing BUS
with SUBSYSTEM makes it work.
Incidentally, this coincides with the output style from
/usr/lib/libgphoto2/print-camera-list udev-rules-0.98 which is supposed
to output a file usable by udev 0.98+...
Could it be so simple as
To add insult to injury, /etc/cron.d/drupal-5.1 isn't even a filename
that's valid since it contains a dot. Verify by running:
run-parts --list /etc/cron.d
and notice how drupal-5.1 isn't listed.
Renaming it to drupal-51 makes it show up.
--
/etc/cron.d/drupal-5.1 contains nonexistant path
Public bug reported:
Binary package hint: drupal
When installing drupal-5.1 on feisty I get this:
-8-
dpkg: error processing drupal-5.1 (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
drupal-5.1
-8-
Public bug reported:
Binary package hint: drupal
I find the following default configuration items of drupal-5.1 in Feisty
needing improvement:
- In /etc/drupal/5.1/htaccess the directive RewriteBase /drupal is
commented, this makes Clean URLs not work in the default configuration
since the
Public bug reported:
Binary package hint: drupal
In drupal-5.1 on Feisty /etc/cron.d/drupal-5.1 contains references to
/usr/share/drupal which doesn't exist. This should probably be
/usr/share/drupal-5.1 instead.
** Affects: drupal (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
drupal-5.1 on feisty recommends postgresql-server-8.2 which doesn't
exist. Since I have postgresql-8.2 installed I'm not interested in the
mysql-server that aptitude tries to install to satisfy the recommends.
** Affects: drupal (Ubuntu)
Importance: Undecided
Public bug reported:
Ubuntu Dapper on AMD64.
mdrun fails if a large disk is present in the system, causing boot to
fail if you have your root partition on MD.
Our setup:
Dual 3ware 9550-SX cards, each with two units which maps to:
sda - single disk (250GB)
sdb - raid5 (1.2TB)
sdc - single disk
Patch that fixes /proc/partinfo parsing in mdrun so system with large
devices present can boot when having root on MD.
--
mdrun fails if large disk present, thus boot fails.
https://launchpad.net/bugs/57972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ehm.
That would be /proc/partitions and nothing else.
--
mdrun fails if large disk present, thus boot fails.
https://launchpad.net/bugs/57972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
76 matches
Mail list logo
