Jean, could you for your tests in addition to installing the two SRUs
uninstall the openvpn-systemd-resolved package with
sudo apt purge openvpn-systemd-resolved
and then reboot?
The openvpn-systemd-resolved is actually not needed for network-manager
with systemd-resolved in Ubuntu and I have
Joe_Bishop, we need your cooperation to find out whether our SRU of
Network Manager for Bionic (NM 1.10.14) actually has a regression or
whether your problem was caused by the missing update of systemd. With
this information we can help many other users of Bionic who suffer other
bugs and for
Jean, we need your cooperation to find out whether our SRU of Network
Manager for Bionic (NM 1.10.14) actually has a regression or whether
your problem was caused by the missing update of systemd. With this
information we can help many other users of Bionic who suffer other bugs
and for which we
Jean, note that if you test the two SRUs and confirm us that they solve
the problem for you, you unblock this SRU and give us way to provide
further SRUs on Network Manager in the future, as Bionic has still some
years to go.
--
You received this bug notification because you are a member of
OK, then this is actually no regression. Closing ...
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => Invalid
** Tags removed: bionic regression-proposed
--
You received this bug
Thank you very much for your great cooperation. I wish other bug
reporters do so, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager 1.10.14-0ubuntu2 ignores
Does this mean that for you there is now no regression in the Bionic SRU
of Network Manager (1.10.14-0ubuntu2)? Can I mark this bug report as
"Invalid" then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Best would even be if you could run the tests as shown in the "[Test
case]" section of the description of bug 1754671, but in addition
capture the full journal with all messages of systemd-resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please also run the command
systemd-resolve --status
and post the output here for each of your tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager 1.10.14-0ubuntu2
Mal, regarding your log files of comments #12 and #13, did you do the
booting and the dig commands in less than 1 minute for each NM version?
Each of the logs spans a time frame of little less than 1 minute?
Could you also repeat your tests after correcting your configuration
according to comment
Mal, could you also provide logs of sytemd-resolved (if needed complete
journal) for your tests?
** Changed in: network-manager (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On further investigations I have found out that, despite of Network
Manager setting up all the requested configurations correctly, sometimes
the nmdev.get_ip6_config() in the check_connected_device_config()
function in nm.py stays empty (but does not stay None) letting the
initial test pass and
** Merge proposal linked:
https://code.launchpad.net/~till-kamppeter/network-manager/+git/network-manager/+merge/369586
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836209
Title:
network
Please provide us with logs of Network Manager in debug mode. See
https://wiki.ubuntu.com/DebuggingNetworkManager
for instructions.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Closing then. Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824425
Title:
network-manager dies in package postinst
vorlon, as it only happens during the Cosmic -> Disco upgrade and Cosmic
is EOL, should we close this then?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793763
Title:
NetworkManager interaction with dhclient triggers IP conflict
Please provide a log of network-manager in debug mode, following the
instructions on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Please follow the instructions of Thomas Haller in your upstream bug
report.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please report this bug to Trisquel. Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818666
Title:
no network(with
As manual setup of networking also does not work it looks more like a
kernel problem, moving ...
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does this happen repeatedly since your update, for example at every
boot? If so, could you provide a log of network-manager in debugging
mode, as described on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could you do the logging like in your comment #4 of your question again
but in debug mode, as described on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Reported upstream as
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
#213
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213
** Also affects: network-manager via
I have checked the gtk+3.0 SRU in bionic-proposed now and could
reproduce the bug before updating and encountered correct behavior after
the update. So I am marking this SRU as verified.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
Jason, the message you mention has nothing to do with the bug reported
here, it is from the color management daemon and in no case prevents a
job from printing. The bug reported here is about a problem of the
GTK/GNOME print dialog not handling printer driver updates correctly. It
only happens
Added description changes from comment #5.
Please could someone with appropriate rights sponsor the uploads of the
attached debdiffs (SRUs)? Thanks.
It would be great if at least the SRU for Disco could get uploaded and
rolled out. Cosmic is very close before EOL, so it can easily happen
that
** Description changed:
[Impact]
+ ModemManager disconnects from CDMA modem after 30 sec failing to check
+ signal status due to incorrect error handling
+
[Test case]
+
+ connect to a cdma device without an extra AT channel (Eg. Samsung
+ brightside phone) and modemmanager will
seb128, it seems that dwmw2 NEEDS this SRU, without he does not get his
environment working correctly, with SRU he gets it at least working
setting the parameters he mentioned. I asked the posters of the
regressions whether they get their situation fixed when using this SRU,
the systemd SRU and
I am currently doing improvements on the test script, making them
available here:
https://code.launchpad.net/~till-kamppeter/network-manager/+git/network-
manager/+merge/369586
I already added timrout s to the GLIb main loops so that in case of a
failure here nm.py continues with the other tests
Lukasz, I do not see any problems with this package, neither on the
https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic
page nor on
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html
which are the regressions actually caused?
--
You
Hi,
to solve several problems with Network Manager in Bionic, an update from
upstream version 1.10.6 to 1.10.14 was done as an SRU, conducted in this
Launchpad bug report:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671
This SRU (together with an already published SRU
When doing the downgrade, skip the ...-dev... packages.
Do you have a proprietary driver package from Samsung installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835957
Title:
cupsd gobbles
Before downgrading, could you follow the instructions of the section
"error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems and
provide us the error_log of the time between boot and the first job,
when CUPS is hogging the CPU? Thanks.
** Changed in: cups (Ubuntu)
Status: New =>
To downgrade, create a new directory and download all the *.deb files
from the "Built files" section of
https://bugs.launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.8/+build/16742546
into it. In a terminal window go into this directory and run the command
sudo dpkg -i *.deb
This will work
Fixed cups-filters released upstream:
https://github.com/OpenPrinting/cups-filters/releases/tag/release-1-25-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833231
Title:
cups ftbfs in eoan
The bug in pdftoraster mentioned in the previous comment (#3) got fixed
and I can build the CUPS packages now locally again. I will prepare a
new release of cups-filters soon.
** Changed in: cups-filters (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you
** Also affects: hplip
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/1835485
Title:
hplip messed up python versions (2/3) in disco
To manage
The log linked in the initial description has been deleted, but I have also
discovered a build problem when building locally, not being able to identify my
problem with the one reported here.
I have observed a segfault in pdftoraster during the "make check". I have
already reported it upstream
I asked on the upstream mailing list and got the following answer:
--
Hi,
the domain specification in the configuration reported on launchpad:
[Resolve]
Cache=no
DNS=127.0.0.54
Domains=~.local.org.com
is invalid:
systemd-resolved[13415]: Failed to add search domain
To the HP developers at HP:
Debian and Ubuntu (and perhaps also other modern Linux distributions)
have multi-architecture support which allows installing libraries for
different architectures on the same system (most prominently having also
32-bit i386 libraries on 64-bit amd64 systems). The
** Also affects: hplip
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/1825717
Title:
hplip issue during hp-setup - stuck at plugin install
To manage
Is this still relevant?
According to
https://launchpad.net/ubuntu/+source/cups/2.2.10-6ubuntu1
the CUPS 2.2.10-6ubuntu1 package has built on all platforms.
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Till Kamppeter has proposed merging ~till-kamppeter/network-manager:master into
network-manager:master.
Commit message:
nm.py autopkgtest: Added timers to make the main loops time out if the
asynchronous processes do not finish.
Requested reviews:
Network-manager (network-manager)
For more
J T, you are posting your auto-generated bug data here but do not post a
comment telling what is exactly your observation.
Note that in HPLIP upstream HPIJS is still contained but not further
developed. We also do not explicitly support it any more in Ubuntu, we
encourage users to switch to
I have checked again on Bionic, making sure that the installed systemd
actually comes from the bionic-proposed repository, that the behavior
according to the test case shown in the initial description of this bug
is correct, DNS queries of destinations in the VPN done through the
VPN's DNS and DNS
Upstream has moved system-config-printer to the GitHub of OpenPrinting.
You find it now here:
https://github.com/OpenPrinting/system-config-printer
There you find also all the opened and closed issues and pull requests
with the same numbers.
The upstream issue corresponding to this bug report
Mal, thanks for the logs, could you tell me, to make it easier for me to
find what went wrong, tell me which host names you queried with "dig",
which IP they should return, and through which DNS? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could you then follow the instructions of the comment #7 and comment #9?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829913
Title:
openconnect VPN is not propagating internal DNS anymore
To
The SRU for systemd has arrived in bionic-proposed (see bug 1754671).
Could you make sure that you have installed BOTH the network-manager and
systemd SRUs from bionic-proposed (to make sure that I did not perhaps
do something wrong with the systemd update in my PPA). Versions should
be:
The SRU for systemd has arrived in bionic-proposed (see bug 1754671).
Could you make sure that you have installed BOTH the network-manager and
systemd SRUs from bionic-proposed (to make sure that I did not perhaps
do something wrong with the systemd update in my PPA). Versions should
be:
The SRU for systemd has arrived in bionic-proposed (see bug 1754671).
Could you make sure that you have installed BOTH the network-manager and
systemd SRUs from bionic-proposed (to make sure that I did not perhaps
do something wrong with the systemd update in my PPA). Versions should
be:
I have checked again on Bionic, making sure that the installed systemd
actually comes from the bionic-proposed repository, that the behavior
according to the test case shown in the initial description of this bug
is correct, DNS queries of destinations in the VPN done through the
VPN's DNS and DNS
Debdiff for Bionic SRU, using the patch from upstream.
** Patch added: "gtk+3.0_3.22.30-1ubuntu3_3.22.30-1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/gtk+3.0/+bug/1763520/+attachment/5268922/+files/gtk+3.0_3.22.30-1ubuntu3_3.22.30-1ubuntu4.debdiff
--
You received this
Closing Cosmic task as Cosmic goes EOL in a month from now and Disco is
available. In addition, the problem only occurs when updating from an
older Ubuntu release. So it is recommended to generally update to Disco
instead of to Cosmic and in case one updated to Cosmic getting this
problem to
First, please try the systemd SRU proposed in bug 1754671. If it does
not solve your problem, do the following:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2.
I have raised the default LogDebugHistory some years ago as most
printing problems happen during the execution of a job and this way one
gets a logging with debug verbosity only for jobs and standard verbosity
for all the rest. This way one often did not need to ask the bug-
reporting users to
SRU for Cosmic sponsored, thanks.
** Changed in: cups (Ubuntu Xenial)
Status: New => In Progress
** Changed in: cups (Ubuntu Bionic)
Status: New => In Progress
** Changed in: cups (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: cups (Ubuntu Disco)
Status:
I have sponsored the Xenial SRU now, but the one for Cosmic is missing
the addition of the patch to debian/patches/series.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
Sponsored SRUs for Bionic and Disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
PreserveJobHistory and PreserveJobLog do not respect numeric input as
outlined in the docs
To
What do you mean with "Can't do anything"? Does your problem now also
occur with the old version, too?
What I want to ask you to do is the following:
With network-manager and systemd updated the problem occurs for you. To
find a possible solution, install the updates, reboot, and do the
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
dwmw2, yes, exactly for this case.
--
You received this bug notification because you are a member of Network-
manager, which is subscribed to NetworkManager.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
To manage notifications about this bug go to:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart
I have now backported cups-filters 1.23.0 to Cosmic. To install it, go
to my PPA
https://launchpad.net/~till-kamppeter/+archive/ubuntu/ppa
Follow the instructions under "Adding this PPA to your system" and then
update your system. You will get the new cups-filters which contains my
cha
dwmw2, yes, exactly for this case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
To manage notifications about this bug go to:
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart systemd-journald
and NetworkManager:
sudo systemctl restart network-manager
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart systemd-journald
and NetworkManager:
sudo systemctl restart network-manager
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart systemd-journald
and NetworkManager:
sudo systemctl restart network-manager
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart
I am rather new to network-manager internals, but could you try the
command
sudo nmcli con modify "$COMPANY VPN" ipv4.dns-priority -1 ipv4.dns-
search ~.
Does this solve your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am rather new to network-manager internals, but could you try the
command
sudo nmcli con modify "$COMPANY VPN" ipv4.dns-priority -1 ipv4.dns-
search ~.
Does this solve your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am rather new to network-manager internals, but could you try the
command
sudo nmcli con modify "$COMPANY VPN" ipv4.dns-priority -1 ipv4.dns-
search ~.
Does this solve your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The 1.23.0-1 version got uploaded to the development of 19.10 (Eoan).
For getting it into an already released Ubuntu version, a Stable Release
Update (SRU) would be needed. But note that if you are still using 18.10
(Cosmic), that in a few months (end-July) the support for Cosmic ends,
so SRUs for
dwmw2, the systemd fix was mainly meant for people with standard
configuration where this fix is actually needed and solve the problem.
You are writing that adding "dns-priority=-1;dns-search=~." solves the
problem for you. Where/to which file did you add this? Do you need this
already with the
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA so that you can
already test/get your problem solved. Please tell here whether it
actually fixes the bug.
Here is my PPA:
https://launchpad.net/~till-kamppeter/+archive
dwmw2, the systemd fix was mainly meant for people with standard
configuration where this fix is actually needed and solve the problem.
You are writing that adding "dns-priority=-1;dns-search=~." solves the
problem for you. Where/to which file did you add this? Do you need this
already with the
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA so that you can
already test/get your problem solved. Please tell here whether it
actually fixes the bug.
Here is my PPA:
https://launchpad.net/~till-kamppeter/+archive
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA:
https://launchpad.net/~till-kamppeter/+archive/ubuntu/ppa
Please follow this link, follow the instructions in the section "Adding
this PPA to your system", t
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA:
https://launchpad.net/~till-kamppeter/+archive/ubuntu/ppa
Please follow this link, follow the instructions in the section "Adding
this PPA to your system", t
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA:
https://launchpad.net/~till-kamppeter/+archive/ubuntu/ppa
Please follow this link, follow the instructions in the section "Adding
this PPA to your system", t
Could you also try whether the combination of both the network-manager
update (1.10.14) AND the proposed systemd update (237-3ubuntu10.22) of
bug 1754671 works for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are these DNS servers listed in the output of
systemd-resolve --status
If yes, could you try the updated network-manager in combination with
the proposed systemd update of bug 1754671?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Which version of Ubuntu are you using? If it is Bionic, could you also
try the systemd update of bug 1754671? If this does not help, try
downgrading network-manager.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
In the initial posting you say that "systemd-resolve --status" shows the
new DNS but does not get used, could you also try out the systemd fix of
bug 1754671?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
1.10.14-0ubuntu2 breaks DNS propagation from VPN
To manage
In bug 120 you say:
I had this same issue and I circumvented it installing the update-
systemd-resolved script through the openvpn-systemd-resolved package.
Does this mean that if you install the openvpn-systemd-resolved package
your problem gets solved without downgrading network-manager?
Looks like that the new version of network-manager is not working
correctly with the systemd-resolved of Bionic.
** Tags added: regression-update
** Also affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Could anyone who still has this problem supply a list of the routes he
has entered and how he has entered them and also attach the
/etc/NetworkManager/system-connections file to this bug report? Thanks.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You
Michael Gale, your issue is different to the OP's one. The routes the OP
has entered are all CIDR notable, he even uses CIDR when entering them
via command line.
So please report a new bug, showing which routes you have entered and
how they end up in /etc/NetworkManager/system-connections.
In
dwmw2, did you apply the systemd fix from comment #27? For this bug to
be fixed you need BOTRH the fixed packages of network-manager and
systemd.
--
You received this bug notification because you are a member of Network-
manager, which is subscribed to NetworkManager.
dwmw2, did you apply the systemd fix from comment #27? For this bug to
be fixed you need BOTRH the fixed packages of network-manager and
systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Dan, if you are on it, preparing a network-manager SRU for Xenial, could
you also add the patch which fixes bug 1754671? Here we also need a
network-manager SRU for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The network-manager SRU 1.10.14-0ubuntu2 is in -updates now and the
autopkg test got successfully repeated with it, so this SRU can be
tranferred to -updates, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- regression in modemmanager
+ Regression in ModemManager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828102
Title:
Regression in ModemManager
To manage notifications about
debdiff for SRU for cosmic.
** Patch added: "modemmanager_1.8.2-1_1.8.2-1ubuntu0.18.10.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+attachment/5263498/+files/modemmanager_1.8.2-1_1.8.2-1ubuntu0.18.10.1.debdiff
** Changed in: modemmanager (Ubuntu Cosmic)
yparitcher, thank you very much for this bug report and the patch. To
start the SRU approval process could you please edit the initial
description, filling in the [Impact] and [Test case] sections? The first
is to describe what impact this bug has to the users, the second is for
describing how to
401 - 500 of 14425 matches
Mail list logo
