[Bug 1930879] [NEW] Current hwe-netboot kernel does not support Intel X710 NICs
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 be impossible with these cards. Would it be possible to update this to a newer version? The kernel that the hwe-netboot installs (5.4.0-74-generic) has the fix included, and the NIC works perfectly fine on a installed OS with that kernel. ** Affects: linux-meta (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/1930879 Title: Current hwe-netboot kernel does not support Intel X710 NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1930879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866361] Re: [SRU] Connections to Neutron are not closed properly in v0.26.0
@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 to: https://bugs.launchpad.net/cloud-archive/+bug/1866361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866361] Re: [SRU] Connections to Neutron are not closed properly in v0.26.0
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: verification-stein-done -- 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 to: https://bugs.launchpad.net/cloud-archive/+bug/1866361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866361] Re: [SRU] Connections to Neutron are not closed properly in v0.26.0
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 properly in v0.26.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1866361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
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 Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
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 downgrade. ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849426] Re: Daily Limit Exceeded error for Google calendar
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1849426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
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 discussion in the GitHub issue was rather interesting as well. I kind of "agree" that this is a strange thing to do, but I don't think that should be any of systemd's business.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
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 time to expire, and observe that the interface loses its address; OR observe in the debug log that networkd applied the address with a lease time, even though you told netplan to use static addressing Networkd config with static addressing: cat /run/systemd/network/10-netplan-ens3.network [Match] MACAddress= [Network] LinkLocalAddressing=ipv6 Address=10.212.132.107/24 Gateway=10.212.132.1 DNS=8.8.8.8 DNS=8.8.4.4 Domains= Networkd config with DHCP: cat /run/systemd/network/10-netplan-ens3.network [Match] MACAddress= [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true Debug log output from systemd-networkd when netplan tells it to apply static addressing when the interface already has an address from DHCP: Sep 30 10:36:15 nettest1 systemd[1]: Stopped Network Service. Sep 30 10:36:16 nettest1 systemd[1]: Starting Network Service... Sep 30 10:36:16 nettest1 systemd-networkd[6086]: ens3: Adding address: 10.212.132.107/24 (valid for 11h 52min 55s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836695] Re: systemd fails to setup static routes at boot when using DHCP
@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 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1836695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836695] Re: Netplan ignores static routes 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 address:
10.212.128.84/24 (valid for 11h 57min 54s)
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=18
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Routing policy rule
configured
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Could not set route:
Network is unreachable
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Routes set
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Adding address:
10.212.128.84/24 (valid for 12h)
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=19
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=20
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Configured
Basically it seems like networkd does the following on "netplan apply":
1) Remove every address
2) Add routes - which of course will fail with "network is unreachable" because
the interfaces don't have an address yet
3) Adding the addresses
--
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:
Netplan ignores static routes when using DHCP
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1836695/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
** 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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833193] [NEW] systemd-network fails to apply static IPv4 when the static IP is the same as previously configured by DHCP
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 interface to loose its IP address when the DHCP lease exires, even though you've told netplan to configure it as static. I expect systemd-networkd to actually configure an IP address as static, regardless of what address the interface has before from DHCP. # lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.22 # apt-cache policy netplan.io netplan.io: Installed: 0.97-0ubuntu1~18.04.1 A paste of systemd-networkd's debug log when I run "netplan apply" and the interface already has the static IP configured from DHCP. It seems like upon a restart, systemd-networkd will allways add whatever IP config it had before the service stopped, and then apply changes (if any). Since my new config has the same IP as it already had, it does nothing even though the new config has static configuration. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "systemd-networkd debug log" https://bugs.launchpad.net/bugs/1833193/+attachment/5271319/+files/systemd-networkd-debug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833193 Title: systemd-network fails to apply static IPv4 when the static IP is the same as previously configured by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
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: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830641] Re: User-defined IPv4 routing tables are not created when using DHCP and setting use-routes to false
** 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 configuration: network: - ethernets: - eth0: - dhcp4: true - dhcp4-overrides: - use-routes: false - routes: - - to: 0.0.0.0/0 - via: 192.168.0.1 - table: 1 - - to: 192.168.0.1/24 - via: 192.168.0.1 - table: 1 - routing-policy: - - to: 0.0.0.0/0 - from: 192.168.0.1/24 - table: 1 + ethernets: + eth0: + dhcp4: true + dhcp4-overrides: + use-routes: false + routes: + - to: 0.0.0.0/0 + via: 192.168.0.1 + table: 1 + - to: 192.168.0.1/24 + via: 192.168.0.1 + table: 1 + routing-policy: + - to: 0.0.0.0/0 + from: 192.168.0.1/24 + table: 1 - eth1: - dhcp4: true - dhcp4-overrides: - use-routes: false - routes: - - to: 0.0.0.0/0 - via: 192.168.30.1 - table: 2 - - to: 192.168.30.1/24 - via: 192.168.30.1 - table: 2 - routing-policy: - - to: 0.0.0.0/0 - from: 192.168.30.1/24 - table: 2 - version: 2 + eth1: + dhcp4: true + dhcp4-overrides: + use-routes: false + routes: + - to: 0.0.0.0/0 + via: 192.168.30.1 + table: 2 + - to: 192.168.30.1/24 + via: 192.168.30.1 + table: 2 + routing-policy: + - to: 0.0.0.0/0 + from: 192.168.30.1/24 + table: 2 + version: 2 I understand from the documentation that netplan should discard the routes recived from DHCP, and add my defined routes. In my configuration - I want so setup source routing, and I expect netplan to create table 1 + I want to setup source routing, and I expect netplan to create table 1 and table 2 from this configuration. But, with this config. None of the tables is actually created: root@bunt:~# ip -4 rule list - 0:from all lookup local - 0:from 192.168.30.1/24 lookup 2 - 0:from 192.168.0.1/24 lookup 1 - 32766:from all lookup main + 0:from all lookup local + 0:from 192.168.30.1/24 lookup 2 + 0:from 192.168.0.1/24 lookup 1 + 32766:from all lookup main 32767:from all lookup default root@bunt:~# ip -4 route show table 1 root@bunt:~# ip -4 route show table 2 The rules are in place, but the routing tables are empty/non-existing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830641 Title: User-defined IPv4 routing tables are not created when using DHCP and setting use-routes to false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1830641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830641] [NEW] User-defined IPv4 routing tables are not created when using DHCP and setting use_routes to false
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: 192.168.0.1 table: 1 - to: 192.168.0.1/24 via: 192.168.0.1 table: 1 routing-policy: - to: 0.0.0.0/0 from: 192.168.0.1/24 table: 1 eth1: dhcp4: true dhcp4-overrides: use-routes: false routes: - to: 0.0.0.0/0 via: 192.168.30.1 table: 2 - to: 192.168.30.1/24 via: 192.168.30.1 table: 2 routing-policy: - to: 0.0.0.0/0 from: 192.168.30.1/24 table: 2 version: 2 I understand from the documentation that netplan should discard the routes recived from DHCP, and add my defined routes. In my configuration I want so setup source routing, and I expect netplan to create table 1 and table 2 from this configuration. But, with this config. None of the tables is actually created: root@bunt:~# ip -4 rule list 0: from all lookup local 0: from 192.168.30.1/24 lookup 2 0: from 192.168.0.1/24 lookup 1 32766: from all lookup main 32767: from all lookup default root@bunt:~# ip -4 route show table 1 root@bunt:~# ip -4 route show table 2 The rules are in place, but the routing tables are empty/non-existing. ** Affects: netplan.io (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/1830641 Title: User-defined IPv4 routing tables are not created when using DHCP and setting use_routes to false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1830641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763608] Re: Netplan ignores Interfaces without IP Addresses
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 Ubuntu.
https://bugs.launchpad.net/bugs/1763608
Title:
Netplan ignores Interfaces without IP Addresses
To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1763608/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724895] Re: MTU not applied on private ethernet interfaces
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 applied on private ethernet interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1724895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570122] Re: ipv6 prefix delegated subnets are not accessable external of the router they are attached.
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 again. -- 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 accessable external of the router they are attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1570122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570122] Re: ipv6 prefix delegated subnets are not accessable external of the router they are attached.
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 accessable external of the router they are attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1570122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700677] Re: nova-api conflicts with nova-placement-api in newton on xenial
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 root@controller01.skylow:~# apt-cache policy nova-placement-api nova-placement-api: Installed: (none) Candidate: 2:14.0.7-0ubuntu1~cloud0 Version table: 2:14.0.7-0ubuntu1~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton/main amd64 Packages 500 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton/main i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700677 Title: nova-api conflicts with nova-placement-api in newton on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1700677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
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: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349128 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
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 only happen in Google Chrome. My workaround is to click some of the icons on the taskbar (the battery icon, or the keyboard layout selector i.e). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
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. https://bugs.launchpad.net/bugs/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324482] Re: [Dell XPS 13 (L322X)] Ubuntu 14.04 LTS - DisplayPort does not wake up after unlocking screen.
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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1324482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324482] Re: [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 Ubuntu. https://bugs.launchpad.net/bugs/1324482 Title: [Dell XPS 13 (L322X)] Ubuntu 14.04 LTS - DisplayPort does not wake up after unlocking screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1324482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324482] [NEW] Ubuntu 14.04 LTS - DisplayPort does not wake up after unlocking screen. Dell XPS 13
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 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 29 12:49:52 2014 DistUpgraded: 2014-04-20 17:09:15,730 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2013-04-25 (398 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=65f7bd26-35ef-41f4-83e9-5fe219eafa9b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-20 (38 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 29 01:14:13 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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: Ubuntu 14.04 LTS - DisplayPort does not wake up after unlocking screen. Dell XPS 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1324482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
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 ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
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 extremely unstable since upgrade to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
