@Tom Matthews: Are you sure that
https://bugs.launchpad.net/netplan/+bug/1759014/comments/62 is netplan's
fault? On my test box the systemd renderer DHCP settings end up in the
same stanza for IPv4 and IPv6, like
[DHCP]
RouteMetric=
UseMTU=true
UseRoutes=false
UseDNS=false
netplan even
Verified netplan.io 0.96-0ubuntu0.18.10.3 using
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
Verified netplan.io 0.96-0ubuntu0.18.10.3 using
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: fa:16:3e:09:85:54
set-name: ens3
ens4:
dhcp4: true
dhcp4-overrides:
Verified netplan.io 0.96-0ubuntu0.18.04.4 using the configuration from
https://bugs.launchpad.net/netplan/+bug/1776228/comments/16. Routes are
configured as expected.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification
Verified netplan.io 0.96-0ubuntu0.18.04.4 with the configuration from
https://bugs.launchpad.net/netplan/+bug/1759014/comments/52. Routes are
configured as expected, as is DNS.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
The systemd issue on Bionic has been resolved with systemd
237-3ubuntu10.21:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804478
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776228
The systemd issue on Bionic has been resolved with systemd
237-3ubuntu10.21:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804478
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
netplan.io 0.96-0ubuntu0.18.04.3 with systemd 237-3ubuntu10.19:
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
addresses:
netplan.io 0.96-0ubuntu0.18.04.3 with systemd 237-3ubuntu10.19:
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: fa:16:3e:28:d1:28
set-name: ens3
ens4:
dhcp4: true
Submitted
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759014
Title:
Netplan has no way to control DHCP client
To manage
Public bug reported:
[Impact]
Network interfaces not using route information from DHCP4 do not reach
configured state, but remain 'configuring' on Bionic.
[Test Case]
1) Launch a VM with two network interfaces connected to ports on
distinct network, each configured using DHCP4.
2) Configure
Applied
https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb
to systemd 237-3ubuntu10.15 on Bionic. It does indeed fix the issue in
https://bugs.launchpad.net/netplan/+bug/1759014/comments/48 and
https://bugs.launchpad.net/netplan/+bug/1776228/comments/14.
Should I
Verified using netplan.io 0.96-0ubuntu0.18.04.2 and systemd
237-3ubuntu10.15 with
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
Verified using netplan.io 0.96-0ubuntu0.18.10.2 and systemd
239-7ubuntu10.10 with
network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
netplan.io 0.96-0ubuntu0.18.04.2 works fine as 0.96-0ubuntu0.18.04.1
did.
Subsequent hickup up of systemd 237-3ubuntu10.15 also remains as
expected.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a
netplan.io (0.96-0ubuntu0.18.10.2 works fine as netplan.io
0.96-0ubuntu0.18.10.1 did. What changes did make a new test necessary?
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Mathieu, I don't think Cosmic or Disco systemd are affected. They are
both >= v239, and Cosmic behaved fine when verifying
https://bugs.launchpad.net/netplan/+bug/1776228.
It would just be a shame having the LTS release remain broken with DHCP
configurations, that used to work before.
--
You
Verification of https://bugs.launchpad.net/netplan/+bug/1776228
confirmed that systemd v237 has issues triggered by customizing DHCP
config, which systemd v239 corrected.
Are there any plans to apply these systemd fixes in the Ubuntu LTS
release?
--
You received this bug notification because
Also verified cosmic. Worked out of the box with netplan.io
0.96-0ubuntu0.18.10.1, systemd 239-7ubuntu10.10, and a netplan
configuration:
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: fa:16:3e:02:43:e7
Works fine with now with netplan.io 0.96-0ubuntu0.18.04.1!
The issue https://github.com/systemd/systemd/issues/9289 remains (as
expected) with the current systemd 237-3ubuntu10.15, but is not directly
caused by netplan. See also
https://bugs.launchpad.net/netplan/+bug/1759014/comments/35
** Bug
** Description changed:
Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
support for the ED25519 signature algorithm.
As ED25519 is quickly gaining traction as most demanded and preferred
elliptic curve algorithm, it would be a substantial issue not to have
- any
Public bug reported:
Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
support for the ED25519 signature algorithm.
As ED25519 is quickly gaining traction as most demanded and preferred
elliptic curve algorithm, it would be a substantial issue not to have
any support for it in
Fix was released with which version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686066
Title:
Rhythmbox no support for iPod nano 7th gen
To manage notifications about this bug go to:
Yes, confirmed. After fixing the Glance configuration as noted in
comment #1, also image creations via Glance CLI using API v1 do assign
ownership correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, confirmed. After fixing the Glance configuration as noted in
comment #1, also image creations via Glance CLI using API v1 do assign
ownership correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I found the configuration problem of Glance, that caused glance-registry
to work in an unauthenticated context, as a consequence not to record
image owners via API v1. That means I could fix my immediate problem of
orphaned snapshots created by Nova.
Nevertheless, I think as the installation
I found the configuration problem of Glance, that caused glance-registry
to work in an unauthenticated context, as a consequence not to record
image owners via API v1. That means I could fix my immediate problem of
orphaned snapshots created by Nova.
Nevertheless, I think as the installation
Public bug reported:
We have installed and configured Kilo according to the installation
guide, which recommends using Glance API v2:
http://docs.openstack.org/kilo/install-guide/install/apt/content/glance-
verify.html
In this configuration snaphosts created by nova end up without any
owner,
Public bug reported:
We have installed and configured Kilo according to the installation
guide, which recommends using Glance API v2:
http://docs.openstack.org/kilo/install-guide/install/apt/content/glance-
verify.html
In this configuration snaphosts created by nova end up without any
owner,
I am observing exactly the same failure on a HP 8530w. Kernel panic
messages are the same as those on on the screen shots referred to in the
original report.
These failures are intermittent. With 3.13.0-62 they inhibit the boot
about 80% of the time. With 3.13.0-61 they also occurred, but less
** Attachment added: dmesg-after-suspend
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390764/+attachment/4324818/+files/dmesg-after-suspend
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Exceuted the tracing steps suggested in
https://wiki.ubuntu.com/DebuggingKernelSuspend using the latest mainline
kernel
# uname -r
3.19.0-031900-generic
and everything worked as expected. The suspend state was entered seconds
after running
# sync echo 1 /sys/power/pm_trace pm-suspend
and
** Attachment added: dmesg-before-suspend
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390764/+attachment/4324817/+files/dmesg-before-suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: wakeup
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390764/+attachment/4324816/+files/wakeup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390764
Title:
Display
IIRC it did also occur in Precise. I don't remember how earlier releases
behaved.
** 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.
Kernel 3.19.0-031900-generic boots fine, but doesn fix the issue,
either.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.19.0-031900
--
You received this bug notification because you are a member of
Managed to upgrade to latest BIOS release by temporarily mounting a
Windows HD. Result:
# dmidecode -s bios-version dmidecode -s bios-release-date
68PDV Ver. F.20
12/08/2011
The dimming issue when resuming from suspend remains.
--
You received this bug notification because you are a member of
Tested qemu-utils 2.0.0+dfsg-2ubuntu1.8. Successful.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts
Tested qemu-utils 2.0.0+dfsg-2ubuntu1.8. Successful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To manage notifications
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
To
No success to get any more recent version than F.12 flashed without a
natively running Windows -- which my Laptop doesn't have. And F.12
doesn't fix the dimming issue when resuming from suspend.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
Managed to upgrade from F.0C to
# dmidecode -s bios-version dmidecode -s bios-release-date
68PDV Ver. F.12
06/08/2010
using the Rom.ISO from
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=3781683spf_p.tpst=swdMainspf_p.prp_swdMain
=wsrp-
Same problem with Kubuntu 14.04, on a HP 8530w, NVIDIA Quadro FX 770M,
xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/451282
Title:
display is fully
Public bug reported:
The symptoms reported with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282 persist.
After resuming from sudpend the display returns fully dimmed, and
display brightness can't be adjusted, neither using FN keys, nor using
KDE power management control.
The issue
Additional information: Unlike described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282 the problem
does not disappear with subsequents suspen/resume cycles.
So far a reboot is the only way for me to get display brightness back.
--
You received this bug notification because you
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256036/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390764
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256044/+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/1390764
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256040/+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/1390764
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256041/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256045/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390764
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256042/+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/1390764
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256038/+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/1390764
Title:
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256034/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390764
apport information
** Tags added: apport-collected
** Description changed:
The symptoms reported with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282 persist.
After resuming from sudpend the display returns fully dimmed, and
display brightness can't be adjusted, neither
apport information
** Attachment added: PccardctlIdent.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256039/+files/PccardctlIdent.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256037/+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/1390764
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256035/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390764
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256043/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390764
Title:
Done.
** Description changed:
The symptoms reported with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/451282 persist.
- After resuming from sudpend the display returns fully dimmed, and
+ After resuming from suspend the display returns fully dimmed, and
display brightness can't be
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1390764/+attachment/4256046/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Christopher, the BIOS update package you are referring me to contains
only Windows runnable files, and doesn't contain the README file your
BIOSUpdate link is referring to:
Extracting cabinet: Downloads/sp55640.exe
extracting bios/HPQFlash.exe
extracting bios/Rom.CAB
extracting
Public bug reported:
The bug https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1064605
seems to be back with Icehouse. Despite enabling the panel in Horizon
using ENABLE_JUJU_PANEL ist still described in
http://docs.openstack.org/trunk/config-reference/content/configure-
dashboard.html
Public bug reported:
The bug https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1064605
seems to be back with Icehouse. Despite enabling the panel in Horizon
using ENABLE_JUJU_PANEL ist still described in
http://docs.openstack.org/trunk/config-reference/content/configure-
dashboard.html
64 matches
Mail list logo
