So, this managed to break at least my VPN setup quite well.
See #1672491 with the details, but the short version is that 'specify
egress interface for each dnsmasq upstream server' breaks things in two
cases.
The first could be argued to be a bug on the VPN client side, though a
behavior change o
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698
Title:
[SRU] Upgrade network-manager to l
This bug was fixed in the package network-manager -
1.2.6-0ubuntu0.16.04.1
---
network-manager (1.2.6-0ubuntu0.16.04.1) xenial; urgency=medium
* Rebase to upstream 1.2.6 release (LP: #1645698)
* debian/rules: allow parallel building (copied from yakkety)
* Dropped patch that was
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698
Title:
[SRU] Upgrade network-manager to latest point release
Status in OEM
inxi -N: Network: Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network
Adapter
driver: ath9k
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
Controller
driver: r8169
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+s
I did test 1.2.6-0ubuntu0.16.04.1 and my observation is that the network
applet is shown correctly and is functional as expected in about 70% of
the resume situations. In the other cases killing and restarting the
applet is a work around.
I also tested the network manager on Manjaro 16.10.3 and Ko
On closer examination the suspend issue that I was seeing was not
related to the 1.2.6-0ubuntu0.16.04.1 networkmanager upgrade but a bios
upgrade I performed a few days earlier. The forced reboot only occurred
when suspending while powered and resuming on battery after unplugging
the laptop, which
Hi Harm, could you please provide the detail information about the hardware
which issue happened on?
ex.
* what's the platform brand and what's network devices?
* lspci -vvvnn, lsusb -vvv, and the /var/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Harm, can you find any logs that indicate that network-manager has
anything to do with that? Is that problem reliably reproducible with the
updated network-manager but not with the older network-manager?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
I also tested 1.2.6-0ubuntu0.16.04.1 and unfortunately it seems to break
suspend on my system. Instead of suspending, the system goes into a
forced reboot.
** Tags removed: verification-done xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a
I tested 1.2.6-0ubuntu0.16.04.1 from xenial-proposed and it works for me
with no problems and it also seems to fix #1585863
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
[Impact]
This SRU would try to have the latest well-tested upstream point release
(1.2.6) of 1.2.x land in Xenial, which is the successor of the current
1.2.2 version, fixing quite some bugs that's suitable to land in the
stable branch.
https://cgit.freede
Hello Aron, or anyone else affected,
Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.6-0ubuntu0.16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
This bug was fixed in the package network-manager - 1.2.6-0ubuntu1
---
network-manager (1.2.6-0ubuntu1) yakkety; urgency=medium
* Rebase to upstream point release 1.2.6 (LP: #1645698)
* Refreshing patches, dropped ones that are merged upstream:
- wifi-clear-WiFi-requested_scan
I've walked through the tests I can do and the yakkety version works,
tagging verification-done-yakkety.
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
htt
** Tags added: somerville
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698
Title:
[SRU] Upgrade network-manager to latest point release
Status in OEM Priori
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
** Changed in: oem-priority
Assignee: Yuan-Chen Cheng (ycheng-twn) => Alex Tu (alextu)
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launc
@cyphermox, most of the common cases are covered before I push changes
to the git repo. I've made some minor updates to
NetworkManager/DistroTesting page and let's continue use it for smoke
testing.
** Description changed:
[Impact]
This SRU would try to have the latest well-tested upstream
Given the large number of changes in a "backport" SRU and the changes to
patches (looks like they are upstreamed, but maybe some bits are
missing?), I think this bug is lacking in terms of a comprehensive set
of test cases.
Some time ago I had captured the kind of tests I'd normally do when
upload
** Changed in: network-manager (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698
Title:
[SRU] Upgrade ne
@jbicha, would be great to make another new upload to zesty, I've
prepared an update of 1.4.4 in git repo:
https://code.launchpad.net/~network-manager/network-
manager/+git/ubuntu/+ref/master
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
[Impact]
This SRU would try to have the latest well-tested upstream point release
(1.2.6) of 1.2.x land in Xenial, which is the successor of the current
1.2.2 version, fixing quite some bugs that's suitable to land in the
stable branch.
https://cgit.freede
- d/rules: yes that helped a lot for testing
- commenting out patch: in xenial branch we haven't switched to gbp-pq
yet, and historically some patches were commented out when not used, and
I'm following it
- it was believed not useful during a bunch update of n-m 1.2 packages
(both debian and ubu
Thanks Aron, the update seems mostly fine but some small comments
- usually SRUs changes are kept to the minimum, I guess you can argue
that the debian/rules change is safe and useful to you but unsure how
much the SRU team is going to like that (it's probably fine though but
we should at least tr
@ubuntu-sponsor, please help sponsor the following branch xenial, which has
been updated to 1.2.6 as well:
https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/xenial
** Description changed:
[Impact]
This SRU would try to have the latest well-tested upstream point
Mark as Fix Released in Zesty.
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/16
Just to let know the other users who might search for the reason of
networking regression in this place: after installation of this update
yesterday, I observe on my laptop (Lenovo X220) a problem with wifi
after a sleep/resume, as reported earlier by Dalila.
Symptoms:
- laptop won't connect auto
** Changed in: network-manager (Ubuntu Xenial)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698
Title:
[SRU] Upgrade
** Summary changed:
- [SRU] network-manager
+ [SRU] Upgrade network-manager to latest point release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1645698
Title:
30 matches
Mail list logo
