Now my Bionic test box is running for the whole weekend and it does not
show any irregularities. No crash reports. The new network-manager seems
to work fine on Bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-m
Also on the Bionic VM on my main laptop I have updated network-manager
to 1.10.14 and there are no issues.
--
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/1809132
Tit
Ian, could you perhaps apply the patch of comment #13 and see whether
you get your problem fully solved (no need of setting AuthType Default
for /)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.
Now after 3 months time for testing and no complaints coming up, Ken
VanDine, Will Cooke, Olivier Tilloy, and me agreed on considering this
SRU as verified. So I have marked this bug report appropriately.
Thanks to everyone who has tested this.
** Tags removed: verification-needed verification-ne
** Description changed:
+ [Impact]
+
+ * The new modemmanager package adds DW5820e support.
+ * This modemmanager version is needed to support new devices.
+
+ [Test Case]
+
+ * install modemmanager, libmbim, and libqmi from -proposed
+ * reboot and try WWAN function to see if any regressio
** Description changed:
[Impact]
- * The new modemmanager package adds DW5820e support.
- * This modemmanager version is needed to support new devices.
+ * The new modemmanager package adds DW5820e support.
+ * This modemmanager version is needed to support new devices.
[Test Case]
Replacement for the debdiff for libqmi 1.22.0 in Bionic.
This debdiff also contains the most recent fixes In Debian and in Disco
(see https://bugs.launchpad.net/ubuntu/+source/libqmi/1.22.0-1.2):
--
libqmi (1.22.0-1.2) unstable; urgency=medium
* Non-maintainer upload.
* Add debian/pa
Which browser did you use?
Does the preview of the browser's print dialog also show the broken printout?
Can you print the same web pages with another browser?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
T
Yuan-Chen, Alex: I have finished to prepare the three needed packages,
including a fix on libqmi coming in yesterday. Now I am simply waiting
for the upload of the packages getting sponsored (probably by Ken
VanDine) and the SRU team putting the packages into bionic-proposed.
Feel free to add anyt
This is most probably covered by the update to modemmanager 1.10, bug
1819615.
--
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/1821052
Title:
No connexion with mobi
Fixed libqmi package.
** Patch added: "libqmi_1.18.0-3ubuntu1_1.22.0-1.2~ubuntu18.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5247982/+files/libqmi_1.18.0-3ubuntu1_1.22.0-1.2~ubuntu18.04.1.debdiff
--
You received this bug notification because
Fixed libmbim package.
** Patch added: "libmbim_1.14.2-2.1ubuntu1_1.18.0-1~ubuntu18.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5247983/+files/libmbim_1.14.2-2.1ubuntu1_1.18.0-1~ubuntu18.04.1.debdiff
--
You received this bug notification beca
Edelharn, the update is not ready yet. Please keep watching bug 1819615
(subscribe to it) and when it is told there that the new package
(modemmanager 1.10) is ready for testing, you can install it. And give
your feedback also in that bug so that we can pass the new package into
the official update
Fixed modemmanager package.
** Patch added: "modemmanager_1.6.8-2ubuntu1_1.10.0-1~ubuntu18.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5247989/+files/modemmanager_1.6.8-2ubuntu1_1.10.0-1~ubuntu18.04.1.debdiff
--
You received this bug notifica
The SRU bug 1809132 has the same proposed package as this one and it got
marked verified after three months without complaints and also after
some testing by me and in agreement with Ken VanDine, Will Cooke,
Olivier Tilloy.
So at least the new network-manager version should not cause any
regressio
By the way, if there is one SRU package to fix several separately
reported bugs, each of these bugs should link to the others, so that a
single bug cannot cause the removal of the SRU even if it gets verified
in the other bugs. Or the SRU package needs one "master bug" where the
verification gets h
To anyone who has observed this problem:
Please check the contents of your /var/crash/ directory.
Is there a file with the ".crash" extension and NetworkManager or
networkmanager in its name and the day when you observed the problem as
file date?
In this case also NetworkManager has crashed.
Th
Thanks, nice collection of crashes, but no NetworkManager.
--
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/1810316
Title:
gnome-control-center SIGABRT when n-m is n
Does this need any fix in network-manager? Seems to be fully fixed by
the kernel patch.
--
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/1818204
Title:
Qualcomm Athe
Thanks. Closed network-manager tasks.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Invalid
** Changed in: network-manager (Ubuntu Cosmic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
As soon as the patch is incorporated upstream I will post the resulting
patch here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic,
Updated the proposed patch for upstream according to their requirements.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, printing fa
I have looked into the error_log files and the processing by the filters
on 16.04 takes ~20 seconds and on 14.04 less time. The 326 seconds you
observe on 16.04 is caused by the printer's processing of the PostScript
it receives. The PostScript is generated by Ghostscript (you find the
Ghostscript
OdyX, can you do the 2.2.9 for Debian, so that it syncs into Ubuntu?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1803149
Title:
Update to 2.2.9
Status in cups pac
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: avahi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
No, not yet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, printing fails without explanation / logs /
debuggability
Status in
Done. Pull request posted:
https://gitlab.gnome.org/GNOME/gtk/merge_requests/434
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, pri
Now the update from Bionic to Cosmic is correctly working. Thank you for
the fix.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this bug notification
Moved to HPLIP and added upstream task as original reporter is using
upstream package.
** Package changed: cups (Ubuntu) => hplip (Ubuntu)
** Also affects: hplip
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1806226
Title:
Dell C2665dnf gets broken installation
Status in
** Package changed: cups (Ubuntu) => gutenprint (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1805108
Title:
CUPS are not compatible with Gutenprint
Status in gute
Please attach the PPD file of your test queue "2660",
/etc/cups/ppd/2660.ppd.
Please also attach the output file of:
ipptool -tv ipp://Dell-C2665dnf-D38EA3.local:631/ipp/print get-printer-
attributes-2.0.test > attr.txt
Also run the command
driverless ipp://Dell-C2665dnf-D38EA3.local:631/ipp/pr
** Also affects: cups (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: cups (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: cups (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you
Sponsored all the CUPS package uploads: disco, cosmic, bionic, xenial,
and subscribed SRU team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576
Title:
MaxJobTime=0 res
debdiff for disco.
** Patch added: "gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220192/+files/gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubu
debdiff for bionic.
** Patch added: "gtk+3.0_3.22.30-1ubuntu1_3.22.30-1ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220194/+files/gtk+3.0_3.22.30-1ubuntu1_3.22.30-1ubuntu1.1.debdiff
--
You received this bug notification because you are a memb
I have now added debdiffs for disco and for the SRUs. Please can someone
with appropriate rights upload them? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1763520
debdiff for cosmic.
** Patch added: "gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu2.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/5220193/+files/gtk+3.0_3.24.1-1ubuntu2_3.24.1-1ubuntu2.1.debdiff
--
You received this bug notification because you are a member o
** Description changed:
+ [Impact]
+
+ The problem occurs when the printer's driver package is updated and with
+ this the PPD is replaced and one of the default settings of the queue is
+ not available any more in the new PPD file. Then the setting is prefixed
+ with "Custom." and with this the
** Changed in: gtk+3.0 (Ubuntu)
Status: Triaged => In Progress
** Changed in: gtk+3.0 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gtk+3.0 (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for the new debdiffs. I have uploaded all these packages now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1804576
Title:
MaxJobTime=0 results in jobs being cance
*** This bug is a duplicate of bug 1780310 ***
https://bugs.launchpad.net/bugs/1780310
This is actually a system-config-printer bug. It is treated here:
https://github.com/zdohnal/system-config-printer/issues/122
Note that the IPP attributes orientation-requested and print-quality
never get
network-manager 1.10.14-0ubuntu2 witrh the fix for this bug got
transferred to bionic-updates. Thanks to the SRU team for the great
cooperation.
** Changed in: network-manager (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a mem
debdiff for SRU for disco.
** Patch added: "modemmanager_1.10.0-1_1.10.0-1ubuntu0.19.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+attachment/5263493/+files/modemmanager_1.10.0-1_1.10.0-1ubuntu0.19.04.1.debdiff
** Changed in: modemmanager (Ubuntu Disco)
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 r
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)
** Summary changed:
- regression in modemmanager
+ Regression in ModemManager
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1828102
Title:
Regression in ModemManage
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
Touch seeded packages, which is subscribed to modemmanager i
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
Touch seeded packages, which is subscribed to network-mana
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.
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 add
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 receive
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
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? Pe
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
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/1829838
Title:
1.10.14-0ubuntu2 breaks DNS
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
Touch seeded packages, which is subscribed to network-manager in
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 m
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
Touch seeded packages, which is subsc
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
Touch seeded packages, which is subscribed to network-m
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
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 or
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
Touch seeded packages, which is subscr
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
Touch seeded packages, which is subscr
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
Touch seeded packages, which is subscr
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 syste
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
dwmw2, yes, exactly for this case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in NetworkManager:
Fix Re
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
T
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
T
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
T
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
following
Sponsored SRUs for Bionic and Disco.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Title:
PreserveJobHistory and PreserveJobLog do not respect numeric input as
out
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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1747765
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: N
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 repr
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. /etc/NetworkM
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 update
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 b
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
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:
network-m
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:
network-m
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:
network-m
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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1829913
Title:
openconnect VPN is not propa
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
Touch seeded pack
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1846334
Title:
cupsd assert failure: free(): invalid pointer
Status in cups
For me it looks more like a kernel issue, as the Wi-Fi principally works
(network-manager must have set it up correctly). The weak signal issue
looks more like something in the driver.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificati
Great work, thank you very much!
It will need some testing of which I can only test the reproducer in the
initial description of this bug report, not any regressions which the
first attempt of upstream-update-based SRU, as I could not reproduce
these by myself.
So I would say to take this as a ne
Sorry for the late reply, I was on a conference last week.
I installed the PPA now and tested with the reproducer of the initial
posting. This works for me. Also the machine in general seems to work OK
with this version of network-manager.
Thank you very much Dariusz for packaging this version.
Now network-manager is hanging on (all autopkg tests passed):
Not touching package due to block request by freeze (contact #ubuntu-
release if update is needed)
Which freeze do we currently have on Bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Joe_Bishop, a new Bionic SRU for bug 1754671 got issued, now much less
invasive simply backporting the fixes and not being a full upstream
update. Please follow the instructions in bug 1754671. If you are still
running 1.10.14 (the old SRU) please downgrade to the old network-
manager and then do t
Jean, a new Bionic SRU for bug 1754671 got issued, now much less
invasive simply backporting the fixes and not being a full upstream
update. Please follow the instructions in bug 1754671. If you are still
running 1.10.14 (the old SRU) please downgrade to the old network-
manager and then do the upd
No worries about my previous comment, it is solved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671
Title:
Full-tunnel VPN DNS leakage regression
Status in Network
Looks like that during boot time components get fired up in wrong order,
some dependency in the systemd service files is needed.
--
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
Jean, does this mean that 1.10.6-2ubuntu1.1 works perfectly for you and
1.10.6-2ubuntu1.2 shows the problem you mention?
--
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/bug
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
To
101 - 200 of 1107 matches
Mail list logo
