Public bug reported:
Hi.
(sorry if this is in the wrong place, but a nice person at
#ubuntu@LiberaChat told me to try here)
The current hwe-netboot kernel for bionic is still suffering from the
bug described in #1893956, which basically lacks the support for Intel
X710 NICs. Causing netboot to
@Corey yeah! I'll test asap!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866361
Title:
[SRU] Connections to Neutron are not closed properly in v0.26.0
To manage notifications about this bug go
Tested in bionic according to the testcase with:
* python3-openstacksdk 0.27.0-0ubuntu1~cloud0
* openstack-dashboard3:15.1.1-0ubuntu1.1~cloud1
* python3-octavia-dashboard 3.0.0-0ubuntu1~cloud0
It fixes the bug.
** Tags removed: verification-stein-needed
** Tags added:
I still dont see the new version in stein-proposed.. Did something fail
in the deployment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866361
Title:
[SRU] Connections to Neutron are not closed
Hi!
Re-tested with systemd=237-3ubuntu10.39 from proposed (and
libsystemd0=237-3ubuntu10.39), and it works.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi!
Tested with systemd=237-3ubuntu10.34 from proposed (and
libsystemd0=237-3ubuntu10.34) and it seems to fix the problem.
What's interesting though, is that a fresh install of bionic came with a
newer version (systemd=237-3ubuntu10.38) - which has the bug. This test
effectively ended up in a
I'm also affected
gnome-online-accounts 3.28.0-0ubuntu2.1 in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849426
Title:
Daily Limit Exceeded error for Google calendar
To manage
Yes that's the same issue. And it seems to be fixed in some version as
well? I just tested it on Eoan, using systemd 242-6, and the valid__lft
and preferred_lft did indeed change to 'forever'. Don't know which
version it was fixed in though. Do you think it kan be backported to
Bionic?
The
Repro instructions:
- (Enable systemd-networkd debug logging)
- Start a server with its interface configured with DHCP
- In the netplan config, configure the interface wtih static addressing, using
the exact same address as it already has gotten from DHCP
- Either wait for the initial DHCP lease
@ddstreet It seems to work as expected in Eoan!
netplan.io 0.98-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836695
Title:
systemd fails to setup static routes at boot when using DHCP
Hi. I did som further investigation here, and I think I've figured out
what happens in networkd here.
Aug 21 10:54:45 nettest1 systemd-networkd[5463]: ens3: Removing address:
2001:700:1d00:ec00:5054:ff:fe49:4bc9/64 (valid for 4w 2d)
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Removing
I should add that if I set "dhcp4: no" explicit when confiugring static
addressing, it behaves as expected, but according to the current
documentation, this parameter should default to "no", so this should not
be neccescary.
--
You received this bug notification because you are a member of
** Summary changed:
- systemd-network fails to apply static IPv4 when the static IP is the same as
previously configured by DHCP
+ systemd-networkd fails to apply static IPv4 when the static IP is the same as
previously configured by DHCP
--
You received this bug notification because you are
Public bug reported:
In bionic, running systemd 237-3ubuntu10.22 and netplan.io
0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface
with a static IPv4 address if the statically confiugred address is the
same as the interface already has gotten from DHCP.
This will cause the
Will anything be done here? This basically breaks keepalived for bionic.
I.e, will keepalived >= 2.0.x be available for bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819074
Title:
** Summary changed:
- User-defined IPv4 routing tables are not created when using DHCP and setting
use_routes to false
+ User-defined IPv4 routing tables are not created when using DHCP and setting
use-routes to false
** Description changed:
Using netplan.io 0.97-0ubuntu1~18.04.1 with this
Public bug reported:
Using netplan.io 0.97-0ubuntu1~18.04.1 with this configuration:
network:
ethernets:
eth0:
dhcp4: true
dhcp4-overrides:
use-routes: false
routes:
- to: 0.0.0.0/0
via:
Verified that the fix works with netplan.io=0.97-0ubuntu1~18.04.1 in
bionic.
network:
version: 2
renderer: networkd
ethernets:
ens10: {}
this brings ens10 up without an address.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can we have a status on this? I can also confirm that the suggested
workaorund works, but this should be fixed anyhow, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not
It works initally, but if we reboot the l3-agent that has the router,
the ip6tables rule disappears when the router is re-created on a new
l3-agent.
After adding this manually:
ip6tables -t mangle -A neutron-l3-agent-scope -i qg-28f7e259-d2 -j MARK
--set-xmark 0x400/0x
it works
Hi, we are still able to reproduce this bug in Queens. neutron-l3-agent
2:12.0.2-0ubuntu1~cloud0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570122
Title:
ipv6 prefix delegated subnets are not
This bug is still valid in the 14.0.7 release of nova
root@controller01.skylow:~# apt-cache depends nova-placement-api
nova-placement-api
Depends: nova-common
Depends: init-system-helpers
Depends: lsb-base
Depends:
python:i386
python
Conflicts: nova-api
Public bug reported:
After cleaning boot partition
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-50-generic 3.16.0-50.67~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
Uname: Linux 3.16.0-50-generic x86_64
ApportVersion:
Seems like it is fixed now, in the unity package:
$ sudo apt-cache policy unity
unity:
Installert: 7.2.2+14.04.20140714-0ubuntu1.1
See changelog:
https://launchpad.net/ubuntu/+source/unity/7.2.2+14.04.20140714-0ubuntu1.1
And the associated bug:
dovercrash: I'm having that issue with chrome as well.
$ sudo apt-cache policy google-chrome-stable
google-chrome-stable:
Installed: 36.0.1985.125-1
Same versions of unity and compiz that you have.
Tried to reproduce it with other applications (gedit, gnome-terminal,
firefox), but it does
pureblood: Any chance that you can figure out exactly which of the
config folders you deleted that acutally did the trick? I really don't
want to delete everything..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done.. But where did that bug report go?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324482
Title:
[Dell XPS 13 (L322X)] Ubuntu 14.04 LTS - DisplayPort does not wake up
after unlocking screen.
I don't think i get any popup, but there is indeed a .crash file in /var/crash.
I've attached a link to the file, as it is 30MB.
http://files.larserikp.com/ubuntucrash/_usr_bin_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
When I lock the screen, and leave for approx 30 minutes, the screen
attached to the DisplayPort does not wake up. When i remove the
DisplayPort adapter, the Unity session dies, and I'm forced to do a
relog. See attached debug info.
ProblemType: Bug
DistroRelease: Ubuntu
Christopher, done :-)
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1324482
It's fairly similar to sanette's bug though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314213
Title:
[Lenovo
This bug also affects me. Dell XPS 13. I have exactly the symptoms that
sanette describes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314213
Title:
[Lenovo ThinkPad X220] External DP1 monitor
This bug affects me too.
ATi Mobility HD 4500, 3.2.0-31 kernel and 12.04 x64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993187
Title:
ubuntu 12.04 completely freezes frequently.
To manage
Struggling with the same thing on a school with around 60 laptops
connecting to a NFS server via LDAP and autofs. I have had some other
problems that have arose because of this. For instance a Network Manager
bug that disabled the wifi card if the laptop went into
hibernation/suspend. Of course
Struggling with the same thing on a school with around 60 laptops
connecting to a NFS server via LDAP and autofs. I have had some other
problems that have arose because of this. For instance a Network Manager
bug that disabled the wifi card if the laptop went into
hibernation/suspend. Of course
Isn't this bug fixed yet in 10.04? It's a very serious bug when you have
many computers that need to be connected to a wifi automatically, with
no user intervention. I might try the hard workaround of removing all
write permissions on that file, but I don't like that sort of dirty
hacks to make it
I looks to me that the bug reporter installed the 10.04 beta with i386
architecture, but I also experienced this bug after installing the final
release on x86_64.
Removing packages as Sergey K describes worked here too, so thanks!
--
Totem can't locate codecs h.264 and mpeg4
The solution to my problems with usb-creator was to use a combination of
the above:
1) Formatting the USB drive with Gparted made the drive usable by usb-
creator (as sdb1)
2) Moving the image to my home directory made the file readable by usb-
creator (I also had a folder with utf-8 characters)
To elaborate futher:
1) fixed the DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound: The
given volume was not found error
2) fixed the Installation failure error
--
Fails repeatably with DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound:
The given volume was not found
I've got the same problem on computers that have got a fresh install,
but that have had their LDAP configuration updated from a puppetmaster
server. The problem appeared after I set up LDAP/PAM authentication on
the computers. The error message from /var/log/messages:
Dec 8 11:29:48 vust1-3
Actually, I haven't seen the only uid 0... message anywhere. Would it
be in syslog?
--
Policykit authentication fails with 'Error.Failed: Only uid 0 may invoke this
method.'
https://bugs.launchpad.net/bugs/439552
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks, that did it. Now I got that error message too ;-) I'll have to
try to apply that patch somehow, then. If there's no pending update
around the corner.
--
Policykit authentication fails with 'Error.Failed: Only uid 0 may invoke this
method.'
https://bugs.launchpad.net/bugs/439552
You
Thank you, Andreas, the setuid patch did the trick for me.
--
Policykit authentication fails with 'Error.Failed: Only uid 0 may invoke this
method.'
https://bugs.launchpad.net/bugs/439552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: ubiquity
Hello, I was trying to install Linux Mint 4.0 (Ubuntu 7.10), when the
installer suddenly crashed. Installation crashes just after chosen
location:
This is the error-message I am presented with:
Traceback (most recent call last):
File
** Attachment added: syslog
http://launchpadlibrarian.net/12423958/syslog
--
crash on installation, Linux Mint 4.0
https://bugs.launchpad.net/bugs/198513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
44 matches
Mail list logo
