This bug is still present on Ubuntu 18.04.5 LTS with systemd
237-3ubuntu10.50. Please reopen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800836
Title:
systemd-networkd doesn't process IPv6 RA
Probably. My (fully updated) 20.04.1 LTS box is still at version
1.18.0-2build1, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906986
Title:
defective ir-keytable udev rule → custom
Public bug reported:
ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-keytable.rules
containing the following rule:
ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
/etc/rc_maps.cfg -s $name"
After upgrading to Focal, this does not get triggered at boot, nor if I
** Attachment added: "Output from 'lshw'"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+attachment/5397631/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Somewhere between 4.15.0-112-generic and 5.3.0-62-generic the kernel
config option SATA_MOBILE_LPM_POLICY was changed from 0 (the upstream
default) to 3. This is causing frequent SATA link resets, resulting in
I/O stalls and errors. For example:
ata1.00: exception Emask 0x0
** Attachment added: "Output from 'smartctl -a /dev/sda'"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1889968/+attachment/5397632/+files/smartctl_-a__dev_sda.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm that the following commands fixes the problem so Ubound
can start again:
echo 'alias / -> /upper/,' >> /etc/apparmor.d/tunables/alias
apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.unbound
I noticed that when it starts, another AppArmor-related error message is
logged:
[
That does not work, same error message when attempting to restart
unbound.
The apparmor_parser command results in the following being logged to the
system journal:
aug. 28 16:08:02 ubuntu audit[6536]: AVC apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
Sure, I can test if you tell me how, ideally spoon-fed. Like I said, I
have no experience with AppArmor so I don't know how to install alias
rules.
By the way, I finished the my blog post, of the six DNSSEC validators I
tested it was only Unbound that didn't work in the live environment (but
of
I don't know anything about AppArmor, so I am afraid I can't help you
with that.
I was just researching DNSSEC validators for a blog post I'm working on,
testing them on both Fedora and Ubuntu (using a live VM). Since Unbound
didn't seem to work (unless I did 'aa-complain /usr/sbin/unbound') I
Correct, as mentioned under «Steps to reproduce» I did my testing using
live media in a virtual machine.
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841364
Title:
AppArmor breaks the
Public bug reported:
Immediately after installing Unbound, it starts up normally. However, if
you try to restart it afterwards (without changing anything), it fails
with the following error message:
Aug 25 10:41:26 ubuntu unbound[6650]: /etc/unbound/unbound.conf:10: error:
cannot open include
We had another server running 4.4.0-148-generic crash just now. It has a
different role then the firewalls that we originally saw the crash with.
After an automatic reboot, it got back up with 4.4.0-150-generic (which
had been installed at an earlier stage but not rebooted into), and
crashed twice
** Summary changed:
- [possible regression] kernel BUG at
[...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207
+ [4.4.0-144 regression] kernel BUG at
[...]/linux-lts-xenial-4.4.0/net/core/skbuff.c:1207
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Peter, and thanks for confirming the bug.
We first experienced this issue in 4.4.0-144 so if you're saying
4.4.0-143 is stable that would mean the bug was introduced in 4.4.0-144.
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And a third crash, this time after upgrading to 4.4.0-146-generic.
Uptime just 21h41m. Backtrace looks the same.
I've now reverted back to 4.4.0-116-generic. I'll let you know if we
experience similar crashes with this version.
[78056.952451] [ cut here ]
[78056.975336]
Public bug reported:
Following a kernel upgrade from linux-image-4.4.0-116-generic to linux-
image-4.4.0-144-generic, our IPTables-based firewall have become
unstable and have crashed twice with identical-looking backtraces after
a short uptime.
When running linux-image-4.4.0-116-generic the
Public bug reported:
I think this says it all:
root@backup:~# snapper create-config /
Creating config failed (/sbin/chsnap not installed).
root@backup:~# apt-file search chsnap
root@backup:~# dpkg -L snapper | grep chsnap
root@backup:~# dpkg -l snapper
Desired=Unknown/Install/Remove/Purge/Hold
|
Hi Christian. Some comments/corrections:
1) On servers privacy extensions are *not* always enabled. As I pointed
out in comment #24, if NM is not in use, privacy extensions are only
enabled for userspace-created interfaces such as "vlan123". It is *not*
enabled by default for physical interfaces
Still happens on a fully updated Trusty LTS.
** Changed in: mountall (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547193
Title:
Impossible to answer
I ran across the same bug. It was caused by the root filesystem being
specified on the kernel command line with the root=UUID= syntax.
This is not handled by the case "$dev" in stanza in activate() in
/usr/share/initramfs-tools/scripts/local-top/lvm2. See attached
screenshot. If I change the
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547193
Title:
Impossible to answer "disk drive not ready" question on serial console
To manage notifications about this bug go to:
In case anyone's interested in knowing why setting
net/ipv6/conf/all/use_tempaddr=2 no longer changes the value of pre-
existing interfaces (thus ensuring privacy extensions are disabled by
default for physical interfaces configured through
/etc/network/interfaces), it's because
This issue seems to have been resolved in Xenial as a side-effect of
changing to systemd, as systemd-sysctl.service runs before
NetworkManager.service and networking.service. When those services
configure a device-specific use_tempaddr sysctl, it will be left alone.
--
You received this bug
Correction to my previous comment: "disable_ipv6" should of course have
read "use_tempaddr" throughout, except for the part about NM bouncing
the disable_ipv6 sysctl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The situation appears to have improved somewhat in Xenial. The
net/ipv6/conf/all/disable_ipv6 sysctl appears to have become a no-op in
recent kernels, so when 10-ipv6-privacy.conf gets applied during the
bootup sequence (by systemd-sysctl.service) it does *not* change the
effective per-device
Steve, some suggestions for you to try:
1) Reinstate 95-multipath.rules to /{etc,lib}/udev/rules.d as described in
comment #1
2) Install the package «multipath-tools-boot»
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, so I found the bug. The problematic code is in
sysfs_attr_set_value() in libmultipath/sysfs.c:
devpath = udev_device_get_syspath(dev);
condlog(4, "open '%s'/'%s'", devpath, attr_name);
if (stat(devpath, ) != 0) {
condlog(4, "stat '%s' failed: %s",
Ok, so I found the bug. The problematic code is in
sysfs_attr_set_value() in libmultipath/sysfs.c:
devpath = udev_device_get_syspath(dev);
condlog(4, "open '%s'/'%s'", devpath, attr_name);
if (stat(devpath, ) != 0) {
condlog(4, "stat '%s' failed: %s",
Okay, sorry about the irrelevant verification on Vivid then. But I'd
like to point out that Trusty behaves exactly the same, i.e., the bug is
*not* fixed. Using the exact same multipath.conf as I mentioned in
comment #31 with multipath-tools on 0.4.9-3ubuntu7.9, I get the exact
same behaviour.
Okay, sorry about the irrelevant verification on Vivid then. But I'd
like to point out that Trusty behaves exactly the same, i.e., the bug is
*not* fixed. Using the exact same multipath.conf as I mentioned in
comment #31 with multipath-tools on 0.4.9-3ubuntu7.9, I get the exact
same behaviour.
I tested it on Vivid, and it does not work. The dev_loss_tmo and
fast_io_fail_tmo sysfs settings do *not* get set. More information on my
test environment below:
root@ucstest:~# cat /etc/multipath.conf
defaults {
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
devices
device {
vendor "HP.*"
I tested it on Vivid, and it does not work. The dev_loss_tmo and
fast_io_fail_tmo sysfs settings do *not* get set. More information on my
test environment below:
root@ucstest:~# cat /etc/multipath.conf
defaults {
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
devices
device {
vendor "HP.*"
Public bug reported:
The scripts in the multipath-tools-boot referer to a non-existent module
"dm-emc":
/usr/share/initramfs-tools/hooks/multipath:
for x in dm-multipath dm-round-robin dm-emc; do
manual_add_modules ${x}
done
/usr/share/initramfs-tools/scripts/local-top/multipath:
Public bug reported:
The scripts in the multipath-tools-boot referer to a non-existent module
"dm-emc":
/usr/share/initramfs-tools/hooks/multipath:
for x in dm-multipath dm-round-robin dm-emc; do
manual_add_modules ${x}
done
/usr/share/initramfs-tools/scripts/local-top/multipath:
Public bug reported:
/lib/udev/rules.d/95-multipath.rules was removed in multipath-tools
0.4.9-3ubuntu7.5.
While researching an unrelated issue, I noticed that /usr/share
/initramfs-tools/hooks/multipath still refer to this file:
add_udev_rules()
{
for rules in 95-multipath.rules; do
if [
Public bug reported:
/lib/udev/rules.d/95-multipath.rules was removed in multipath-tools
0.4.9-3ubuntu7.5.
While researching an unrelated issue, I noticed that /usr/share
/initramfs-tools/hooks/multipath still refer to this file:
add_udev_rules()
{
for rules in 95-multipath.rules; do
if [
After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have
found that the problem is caused by the removal of the file
/lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the
following:
#
# udev rules for multipathing.
# The persistent symlinks are created with the
After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have
found that the problem is caused by the removal of the file
/lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the
following:
#
# udev rules for multipathing.
# The persistent symlinks are created with the
Small correction to what I wrote above, what actually appears on the
serial console is the following (note "keys:"):
The disk drive for /opt/vnx is not ready yet or not present.
keys:Continue to wait, or Press S to skip mounting or M for manual recovery
--
You received this bug notification
Public bug reported:
System information: Cisco UCS B200M2 blade, fnic.ko HBA. The system
boots from local storage, but mounts the following file system on an EMC
VNX during bootup:
opt_vnx (3600601603a71320022967e0a1f38e411) dm-0 DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc'
Public bug reported:
System information: Cisco UCS B200M2 blade, fnic.ko HBA. The system
boots from local storage, but mounts the following file system on an EMC
VNX during bootup:
opt_vnx (3600601603a71320022967e0a1f38e411) dm-0 DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc'
Public bug reported:
When booting a server that is suffering from a (probably unrelated) bug
in multipath-tools, I get the following questions posed on the serial
console during bootup:
The disk drive for /opt/vnx is not ready yet or not present.
Continue to wait, or Press S to skip mounting or
Public bug reported:
The dibbler-{client,relay,server} packages do not include any
/etc/logrotate.d configuration snippets. They should, otherwise the file
system on which /var/log/dibbler is located is bound to run out of free
space eventually.
** Affects: dibbler (Ubuntu)
Importance:
I just realised that this bug also impacts NetworkManager, at least on
Vivid: I set the property "ipv6.ip6-privacy" on the default wired
Ethernet interface to 0 (in order to prevent a remote CIFS mount from
freezing every few hours), however after a reboot, privacy extensions
remained active. My
Public bug reported:
I have configured the following in /etc/network/interfaces:
auto eth0
iface eth0 inet6 auto
privext 0
According to interfaces(5), this should disable IPv6 Privacy Extensions.
However, after booting the machine,
/proc/sys/net/ipv6/conf/eth0/use_tempaddr contains the value
Ok, so I did some more testing. It appears that the problem isn't
specific to the dev_loss_tmo and fast_io_fail_tmo setting. This is
evidenced by the terminal log below. In multipath.conf (which we know
for certain is being read, as the created multipath map gets the correct
alias), I instruct it
Ok, so I did some more testing. It appears that the problem isn't
specific to the dev_loss_tmo and fast_io_fail_tmo setting. This is
evidenced by the terminal log below. In multipath.conf (which we know
for certain is being read, as the created multipath map gets the correct
alias), I instruct it
I verified that this bug is *NOT* fixed by trying the exact identical
configuration (which is as minimal as possible) both with Ubuntu Trusty
and with Scientific Linux 6 (RHEL6 clone). The test machine is a Cisco
B200M2 blade server, using the Cisco VIC FCoE HBA (fnic.ko driver). The
storage array
I verified that this bug is *NOT* fixed by trying the exact identical
configuration (which is as minimal as possible) both with Ubuntu Trusty
and with Scientific Linux 6 (RHEL6 clone). The test machine is a Cisco
B200M2 blade server, using the Cisco VIC FCoE HBA (fnic.ko driver). The
storage array
To me fix doesn't actually appear to work. After upgrading to multipath-
tools 0.4.9-3ubuntu7.4on an amd64 trusty and rebooting, the
fast_io_fail_tmo and dev_loss_tmo values do not get written to sysfs:
$ grep . /sys/class/fc_remote_ports/*/*_tmo
To me fix doesn't actually appear to work. After upgrading to multipath-
tools 0.4.9-3ubuntu7.4on an amd64 trusty and rebooting, the
fast_io_fail_tmo and dev_loss_tmo values do not get written to sysfs:
$ grep . /sys/class/fc_remote_ports/*/*_tmo
Public bug reported:
If irqbalance is started with the --policyscript option, Upstart is
unable to manage it properly (bug #406397 is being triggered), and
stopping/restarting it fails. Noticed this when the
1.0.6-2ubuntu0.14.04.2 update hit Trusty yesterday. See below:
$ /sbin/stop irqbalance
Public bug reported:
If irqbalance is started with the --policyscript option, Upstart is
unable to manage it properly (bug #406397 is being triggered), and
stopping/restarting it fails. Noticed this when the
1.0.6-2ubuntu0.14.04.2 update hit Trusty yesterday. See below:
$ /sbin/stop irqbalance
** Also affects: irqbalance (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/406397
Title:
init: job stuck with expect
** Also affects: irqbalance (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/406397
Title:
init: job stuck with expect fork/daemon when parent
*** This bug is a security vulnerability ***
Public security bug reported:
In order to close the recently disclosed security vulnerability in SSLv3
(CVE-2014-3566 a.k.a. POODLE), one needs to disable SSLv3 support.
According to
http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_SSL,
FYI, this bug is now fixed by http://kernel.ubuntu.com/git?p=ubuntu
/ubuntu-trusty.git;a=commit;h=6ac0d80c79b062b44135cec6436d6eeeaeed1ec2.
I've tested linux-image-3.13.0-35-generic version 3.13.0-35.62~precise1
and can confirm it's working OK. So this bug report can probably be
closed.
Tore
--
Hi, I'm also affected by this issue. I have a number of virtual machines
running Precise which are now left in limbo - I cannot use the original
Precise kernel (3.2.0) because of some missing features, and I cannot
upgrade to the Trusty kernel (or upgrade the entire distribution to
Trusty for that
This affects me, too. After boot, the necessary ipmi_{si,devintf}
modules aren't loaded, so ipmitool and related monitoring doesn't work.
However this bug cannot possibly be in the ejabberd package, so I'm
reassigning it to openipmi.
** Package changed: ejabberd (Ubuntu) = openipmi (Ubuntu)
--
This affects me, too. After boot, the necessary ipmi_{si,devintf}
modules aren't loaded, so ipmitool and related monitoring doesn't work.
However this bug cannot possibly be in the ejabberd package, so I'm
reassigning it to openipmi.
** Package changed: ejabberd (Ubuntu) = openipmi (Ubuntu)
--
We notice this here as well, as we're increasingly turning up new
services and VMs without IPv4. It fails with a rather cryptic error
message:
Jul 8 07:10:03 rpki-validator ntpdate[689]: Can't find host ntp.ubuntu.com:
Name or service not known (-2)
Jul 8 07:10:03 rpki-validator ntpdate[689]:
We notice this here as well, as we're increasingly turning up new
services and VMs without IPv4. It fails with a rather cryptic error
message:
Jul 8 07:10:03 rpki-validator ntpdate[689]: Can't find host ntp.ubuntu.com:
Name or service not known (-2)
Jul 8 07:10:03 rpki-validator ntpdate[689]:
Indeed. This happens also with IPv6 interfaces, independently of any
specific delay caused by the hardware, as the ifup scripts doesn't
ensure that IPv6 Duplicate Address Detection has completed, nor that
Stateless Address Auto-Configuration has.
In the following case, /etc/network/interfaces
Hi, I forgot to mention that the problems I reported in comment #5 was
reproduced on Ubuntu 12.04.4. I'm glad to hear that it has been since
fixed, but since 12.04.4 is supposed to be «Long Term Support», perhaps
it would be an idea to backport the fix for IPv6 DAD? Thanks for
considering. :-)
I don't think this is really fixed in recent versions either. At least I
dist-upgraded my test server to Trusty now, but the script from comment
#5 still shows that the interface only has a tentative LL address
assigned by the time it is started by upstart:
Mar 24 20:42:59 ucstest kernel: [
Public bug reported:
The new style of bonding configuration (using iface bond0 [...] \
bond_slaves none for the master interface plus iface ethX inet manual
\ bond_master bond0 for each slave interface) results in the MAC
address of the bond0 interface being randomly picked from one of the
For what it's worth, we never had any problem with the old style
bond_master eth0 eth1 syntax. On a server, typically all the slaves
will become available pretty much at the same time during the boot
process - devices hot-plugged at a later time is generally not the use
case you'd need to optimise
Sorry, that should be bond_slaves eth0 eth1 of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1288196
Title:
MAC address of bonding interface is randomly picked
To manage notifications
Don't get me wrong, I meant to indicate that this seems completely fine
by me; my point was simply that I was happy with waiting until the
primary slave is available before with the old style of configuration,
therefore I will be happy with waiting in a similar manner in the future
too (even
Public bug reported:
Currently, the Linux kernel doesn't provide IPV6_RECVPKTINFO ancillary
data on datagrams coming in from IPv4-mapped clients (e.g.,
:::192.0.2.1) on INET6 sockets in the default dual personality mode,
nor does it honour IPV6_PKTINFO when sending datagrams on such a socket
This is really more a RFE/missing functionality than a bug per se, so
confirming.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Output from: multipathd -kshow config
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+attachment/3487090/+files/multipathd_-kshow_config.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Attachment added: Output from: multipath -v4
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+attachment/3487091/+files/multipath_-v4.txt
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a
** Attachment added: Output from: multipathd -kshow config
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+attachment/3487090/+files/multipathd_-kshow_config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Output from: multipath -v4
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+attachment/3487091/+files/multipath_-v4.txt
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a
Public bug reported:
My device section of /etc/multipath.conf contains the following (I'll
attach the complete file in a bit):
fast_io_fail_tmo 3
dev_loss_tmo 2147483647
This is also visible in the output from multipathd -kshow config, so
it's being correctly parsed. However, the settings
Public bug reported:
My device section of /etc/multipath.conf contains the following (I'll
attach the complete file in a bit):
fast_io_fail_tmo 3
dev_loss_tmo 2147483647
This is also visible in the output from multipathd -kshow config, so
it's being correctly parsed. However, the settings
(In reply to comment #2)
I'm suspending the bug. Change the state when any of the proposals
are accepted.
Hi Ulrich,
RFC 6724 has just been published, obsoleting RFC 3484. It assigns global
scope to RFC 1918 addresess.
As requested, I'm therefore changing the state of the bug.
Tore
--
You
That's interesting. The reason why Fedora started carrying this patch in
the first place, is because I submitted
https://bugzilla.redhat.com/show_bug.cgi?id=577626.
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The init script contains the following code:
if [ x$CONFIGURE_IFACE = xyes ] ; then
$DAEMON --mktun
ip link set $TUN_DEVICE up
ip route add $DYNAMIC_POOL dev nat64
ip route add $IPV6_PREFIX dev nat64
fi
** Patch added: tayga-init.patch
https://bugs.launchpad.net/bugs/1031772/+attachment/3244761/+files/tayga-init.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031772
Title:
Init script
Also, you might want to replace the static nat64 for $TUN_DEVICE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031772
Title:
Init script adds spurious IPv4 default route if dynamic-pool or
The second part is now committed, here:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6b9511f6e98429c01b741754bc58795bf59f693e
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI,
The Fedora project has decided to consider IPv6-only network attachment
failing out-of-the-box a release blocker for Fedora 17. And the required
patches to fix that is hitting the NetworkManager upstream code as we
speak. One significant commit is here:
Stéphane, the same patch was posted in this bug as well, see comment
#316. (The one in #317 is no longer necessary, as it's been included in
the NSPR upstream code for a long time now.)
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
on changing these defaults for Oneiric. However,
they won't be changed for Natty because it's already quite late in the
cycle to do so»
From
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/761558/comments/2
Best regards,
--
Tore Anderson
--
You received this bug notification
you have is all about. Could you be more specific?
Best regards,
--
Tore Anderson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761558
Title:
Default to enabling IPv6 addresses, but set
I am no longer using KDE, so I can't re-confirm, sorry. However, do feel
free to close the ticket as out of date if you prefer.
Tore
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in Ubuntu.
Great!
However, is IPv4 success still required in order to bring up interfaces?
If so, that still needs to change before you can say that Ubuntu truly
supports IPv6 networks out of the box.
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
When /etc/resolv.conf contains options rotate, and I try to look up a
hostname that first points to a CNAME, which then points to another
hostname with both an A and an record, the record isn't
returned. Instead I get an IPv4-mapped IPv6 address containing the A
the recovery menu issue,
though.
start on runlevel [23]
stop on runlevel [!23]
respawn
exec /sbin/getty -L 115200 ttyS0
--
Tore Anderson
** Attachment added: console.png
https://bugs.launchpad.net/bugs/590709/+attachment/2452526/+files/console.png
--
You received this bug notification
. Thought I'd test and looked for the installation ISO in the above
location, but could not find anything. Could you give me a direct download
link to new installation ISO (server flavour)?
Best regards,
--
Tore Anderson
--
You received this bug notification because you are a member of Ubuntu
Bugs
and
what isn't.
I'll do my best, but I can't promise you I find the time before next
week, I'm going away from Friday, and I've got a really busy schedule
today and tomorrow.
Best regards,
--
Tore Anderson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm out of the office for a few days, and won't have access to the UCS
equipment in the lab. I hope it'll still be available for my testing
when I return - I'll let you know.
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Steve,
See comment #7. I need an updated installation ISO in order to confirm.
Tore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801610
Title:
Include enic fnic drivers in ubuntu-installer
To
Herton,
The issue is that the *installer* (or perhaps more precisely, the .udeb)
does not contain these modules. The regular kernel .deb had them
included all along.
I'd be happy to test that the issue is fixed, but in order to do so I
need an install media (e.g. an ISO) that has been built
** Attachment added: Syslog, Oneiric alpha-3, singlestac IPv4, wired
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/761558/+attachment/2258180/+files/test2.oneiric-a3.wired.singlestack.syslog
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: Syslog, Oneiric alpha-3, dualstack, wireless
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/761558/+attachment/2258181/+files/test3.oneiric-a3.wireless.dualstack.syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs,
until it gives up
completely, leaving the network disconnected.
* See attachment test4.oneiric-a3.wireless.singlestack.syslog
--
Tore Anderson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761558
1 - 100 of 315 matches
Mail list logo
