[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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 verified the SRUs (in bug 1754671) with openvpn-systemd-resolved NOT installed. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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 which we have introduced this SRU. So I want to ask you whether you could install BOTH the SRUs for systemd and network-manager as I have described in comment #12. Note that network-manager is only in bionic-proposed and not in the official updates, systemd is perhaps already in the update, if not at least in bionic-proposed. Make sure you have installed both. Then reboot and check whether your problem gets solved. If not, we need additional information to solve your problem, therefore I ask you to follow the instructions of comment #9 (and also of https://wiki.ubuntu.com/DebuggingNetworkManager). Thank you very much in advance. Note also 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829913 Title: openconnect VPN is not propagating internal DNS anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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 have introduced this SRU. So I want to ask you whether you could install BOTH the SRUs for systemd and network-manager as I have described in comment #11 and if after installing these packages and rebooting the problem still persists follow my instructions of comment #10 to provide us additional information to solve the problem. Thank you very much in advance. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 #18? Thanks. -- 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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
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 the check for the IP addresses fail. We do not have a type too slow reaction here which could get worked around/fixed by adding a longer delay or making timeouts longer, the structure stays empty even after several minutes. The request for this structure seems not to cause any interaction with network manager as the debug log which is shown on each failed test does not show entries at the time of calling the get_ip6_config() method. Skipping the check_connected_device_config() call makes the remaining tests of the configuration/connection being done and they all pass safely, especially also the check_low_level_config() call which actually confirms that the interface has gotten the correct IP addresses (check_connected_device_config() in the IPv6 case only checks for the minimum number of IPs though). So as a workaround (fix?) I have skipped the check_connected_device_config() function call now. This way all tests pass for me with the correct IP addresses confirmed. This I have done in the last commit in the merge request attached to this bug report. The others are general fixes/improvements on the nm.py script. ** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- 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-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
** 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-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792579] Re: Network Disconnecting Intermittantly
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792579 Title: Network Disconnecting Intermittantly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
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 on cosmic->disco upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1824425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
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. https://bugs.launchpad.net/bugs/1824425 Title: network-manager dies in package postinst on cosmic->disco upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1824425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793763] Re: NetworkManager interaction with dhclient triggers IP conflict detection at dhcp server, causes ip address changing every day
** 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 detection at dhcp server, causes ip address changing every day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1793763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800968] Re: nm-applet only show current wifi connection
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800968 Title: nm-applet only show current wifi connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803236] Re: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS
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. https://bugs.launchpad.net/bugs/1803236 Title: network-manager: switch from dnsmasq (16.04) to systemd-resolve (18.04) breaks DNS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1803236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818666] Re: no network(with cable)
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 cable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814473] Re: latest systemd, network-manager, kernel updates killed networking
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. https://bugs.launchpad.net/bugs/1814473 Title: latest systemd, network-manager, kernel updates killed networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824425] Re: network-manager dies in package postinst on cosmic->disco upgrade
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 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 on cosmic->disco upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1824425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827879 Title: Killer Wireless 1525 firmware crashes on suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828313] Re: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04.
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828313 Title: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1828313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828134] Re: Wifi not working after suspend/resume cycle
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 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828134 Title: Wifi not working after suspend/resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1828134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
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 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
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 when a printer driver gets updated (can happen during a general system update or an upgrade to a new Ubuntu version). We need your error_log (in debug mode, see "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems) to judge whether you are suffering this bug or something else. ** 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 jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. + - Stop CUPS, edit the PPD file (in /etc/cups/ppd/) removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus:
[Bug 1828102] Re: Regression in ModemManager
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 the SRU does not get published in time, so Disco is much more important. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828102] Re: Regression in ModemManager
** 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 terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 dwmw2's settings, but no one answered. -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
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 and the log of the failure in the main loop does not get lost. If the main loops hang indefinitely, autopkgtest kills the script and no results are available. Next step is improving the script for events taking too long to happen. Especially things like waiting for a hard-coded time interval and then checking a state ones (and fail if the desired state did not get reached, in check_connected_device_config()) I will replace by repeated checking over a given time interval, like assertEventually() does). Probably I will also make certain timeouts longer. ** Changed in: network-manager (Ubuntu) Status: New => In Progress -- 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-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Testing help needed: Network Manager Bionic SRU Regression
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 of systemd) is especially supposed to let the correct DNS being used when a VPN is used only for servers in the VPN. The fix got verified (meaning that the reproducer shown in the bug description does not suffer the bug any more) and the SRU started to get rolled out to -updates. Soon after that some users reported regressions and the roll-out got stopped. The regression bug reports are here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913 openconnect VPN is not propagating internal DNS anymore https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566 network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838 1.10.14-0ubuntu2 breaks DNS propagation from VPN To try to find out what happened I have asked all the reporters for further information but did not get answers, except with bug 1829566 but the user did not answer everything. For me it looks like that only very few users suffered regressions in very special cases, as there were not more bug reports coming up and these bug reports did not accumulate large amounts of me-too votes and duplicates. I asked Brian Murray (Tuesday's shift of SRU team) on #ubuntu-release and he tell that it is better to ask for help and further testing on the Ubuntu mailing lists instead of retrying the roll-out to -updates. So I would like to ask you whether you could help with testing the 1.10.14-0ubuntu2 package of network-manager on Bionic (from -proposed) or give some helpful hint. Thanks in advance Till -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[Bug 1835957] Re: cupsd gobbles up resources
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 up resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835957] Re: cupsd gobbles up resources
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 => Incomplete -- 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 up resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835957] Re: cupsd gobbles up resources
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 even if the replaced packages are newer than the packages you are installing. Does this solve your problem? -- 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 up resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833231] Re: cups ftbfs in eoan (amd64 only)
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 (amd64 only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833231] Re: cups ftbfs in eoan (amd64 only)
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833231 Title: cups ftbfs in eoan (amd64 only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835485] Re: hplip messed up python versions (2/3) in disco
** 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 notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1835485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833231] Re: cups ftbfs in eoan (amd64 only)
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 here: https://github.com/OpenPrinting/cups-filters/issues/131 The contributor of the current version of pdftoraster should fix it soon. ** Bug watch added: github.com/OpenPrinting/cups-filters/issues #131 https://github.com/OpenPrinting/cups-filters/issues/131 ** Also affects: cups-filters (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/1833231 Title: cups ftbfs in eoan (amd64 only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 '~.local.org.com', ignoring: Invalid argument The correct form should be without the dot: Domains=~local.org.com Can you ask to fix that configuration error and try again? Otherwise, queries for the local.org.com domain are not routed to the local dnsmasq instance. Beniamino -- Could you correct your configuration and try again? Please report back here, thanks. ** Changed in: network-manager (Ubuntu Bionic) Status: Triaged => Incomplete -- 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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install
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 libraries which got formerly installed into /usr/lib/ are now installed into /usr/lib/x86_64 -linux-gnu for the 64-bit amd64 versions of the library binaries, into /usr/lib/i386-linux-gnu for the 32-bit i386 versions, ... The proprietary plugin seems not to take account of this and searches for its libraries on hard-coded paths. Therefore adding the links as described in comment #6 solves the problem. Could you make the plugin in a way that it either searches alternative paths or checks by environment variables whether the libraries are in multi-architecture sub-directories or at other alternative positions? This would make it much easier for users of Linux distributions to use the plugin with the distribution's packages of HPLIP. -- 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 notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1825717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825717] Re: hplip issue during hp-setup - stuck at plugin install
** 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 notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1825717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833231] Re: cups ftbfs in eoan (amd64 only)
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833231 Title: cups ftbfs in eoan (amd64 only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Merge] ~till-kamppeter/network-manager:master into network-manager:master
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 details, see:
https://code.launchpad.net/~till-kamppeter/network-manager/+git/network-manager/+merge/369586
This change avoids that in case of failure of the asynchronous operations the
script does not get stuck in the main loop making the autopkgtest application
killing it after hours and without clue about what went wrong. If the
asynchronous operations do not finish withing 5 minutes the main loops which
wait for them are stopped by timer.
This does not influence the probability of a test passing or failing due to
tasks completing too slowly. It only improves debuggability.
--
Your team Network-manager is requested to review the proposed merge of
~till-kamppeter/network-manager:master into network-manager:master.
diff --git a/debian/tests/nm.py b/debian/tests/nm.py
index 5037daa..ab3571d 100755
--- a/debian/tests/nm.py
+++ b/debian/tests/nm.py
@@ -274,8 +274,16 @@ class NetworkManagerTest(network_test_base.NetworkTestBase):
def add_activate_cb(client, res, data):
self.cb_conn = self.nmclient.add_and_activate_connection_finish(res)
ml.quit()
+
+def timeout_cb():
+print("Main loop timed out!")
+ml.quit()
+return False
+
self.nmclient.add_and_activate_connection_async(partial_conn, self.nmdev_w, ap.get_path(), None, add_activate_cb, None)
+timeout_tag = GLib.timeout_add_seconds(300, timeout_cb)
ml.run()
+GLib.source_remove(timeout_tag)
self.assertNotEqual(self.cb_conn, None)
active_conn = self.cb_conn
self.cb_conn = None
@@ -674,8 +682,16 @@ Logs are in '%s'. When done, exit the shell.
def add_activate_cb(client, res, data):
self.cb_conn = self.nmclient.add_and_activate_connection_finish(res)
ml.quit()
+
+def timeout_cb():
+print("Main loop timed out!")
+ml.quit()
+return False
+
self.nmclient.add_and_activate_connection_async(partial_conn, self.nmdev_e, None, None, add_activate_cb, None)
+timeout_tag = GLib.timeout_add_seconds(300, timeout_cb)
ml.run()
+GLib.source_remove(timeout_tag)
self.assertNotEqual(self.cb_conn, None)
active_conn = self.cb_conn
self.cb_conn = None
--
ubuntu-desktop mailing list
ubuntu-desktop@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1036236] Re: hpcups and hpijs driver use different rasterization
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 hpcups and do even automatic migration. If you observe any output quality advantage in HPIJS, please report a new bug to HPLIP upstream (https://bugs.launchpad.net/hplip/), so that they can compare and improve the hpcups driver. Nothing of Ubuntu and its packaging is involved here. So I am closing this bug. ** Changed in: hplip (Ubuntu) Status: Incomplete => 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/1036236 Title: hpcups and hpijs driver use different rasterization To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1036236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 queries to public destinations being done through the public DNS. This works correctly and so the systemd update together with the network-manager update fixes the bug described here. So I am marking this bug as verified in Bionic. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1780310] Re: Option 'finishings' has value '3' and cannot be edited
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 you find here now: https://github.com/OpenPrinting/system-config-printer/issues/122 ** Bug watch added: github.com/OpenPrinting/system-config-printer/issues #122 https://github.com/OpenPrinting/system-config-printer/issues/122 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780310 Title: Option 'finishings' has value '3' and cannot be edited To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1780310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Note that these packages are only in bionic-proposed, not in the official updates, due to the fact that we need to sort out the regressions. So follow the instructions of installing the proposed packages in bug 1754671, comment #28 and comment #49. Does this combination solve your problem? Please reboot to make sure that everything gets replaced by the newer versions. If this still does not help, please follow my instructions in this bug report, 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured 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-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Does this combination solve your problem? Please reboot to make sure that everything gets replaced by the newer versions. If this still does not help, please follow my instructions in comment #8 and comment #10. -- 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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Does this combination solve your problem? Please reboot to make sure that everything gets replaced by the newer versions. If this still does not help, please follow my instructions in comment #8 and comment #10. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 queries to public destinations being done through the public DNS. This works correctly and so the systemd update together with the network-manager update fixes the bug described here. So I am marking this bug as verified in Bionic. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done 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/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
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 again to Disco. ** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: In Progress => 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831261] Re: OpenVPN Other DNS Servers ignored if no Search Domains specified
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/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 Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. ** 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/1831261 Title: OpenVPN Other DNS Servers ignored if no Search Domains specified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1831261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
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 reproduce their problems after having set logging to debug mode but instead, one could simply start to work with the error_log auto-captured by Apport. Up to now no one complained that it somehow overloaded system resources. Please add a line "LogDebugHistory 200" to your /etc/cups/cupsd.conf and restart CUPS. I will remove this change from the next release of the CUPS package. OdyX, could you remove the LogDebugHistory=9 default change from the CUPS package for Debian (remove log-debug-history-nearly- unlimited.patch)? Thanks. ** Changed in: cups (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
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: New => In Progress -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
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: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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 test: Run sudo nmcli con modify "$COMPANY VPN" ipv4.dns-priority -1 ipv4.dns- search ~. and check whether this solves the problem. Tell us your result. If this does not solve the problem, reboot and follow my instructions in comment #9. Attach the log file you get. After that, downgrade network-manager to the old version again to get back to a working configuration. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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 Then restart journald: sudo systemctl restart systemd-journald and NetworkManager: sudo systemctl restart network-manager Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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 Then restart journald: sudo systemctl restart systemd-journald and NetworkManager: sudo systemctl restart network-manager Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 Then restart journald: sudo systemctl restart systemd-journald and NetworkManager: sudo systemctl restart network-manager Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 systemd-journald and NetworkManager: sudo systemctl restart network-manager Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1731417] Re: Installed network printer removed automatically when turned off
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 changes. Note that this version of cups-filters requires an update of QPDF which you will automatically get together with cups-filters. Please tell whether this version solves your problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. ** Changed in: network-manager (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- 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 systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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 Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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 Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 systemd-journald and NetworkManager: sudo systemctl restart network-manager Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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. https://bugs.launchpad.net/bugs/1829913 Title: openconnect VPN is not propagating internal DNS anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731417] Re: Installed network printer removed automatically when turned off
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 this version do not make much sense. So I recommend you to upgrade to 19.04 (Disco) and try whether the problem still persists for you and report back here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 original network-manager version of Bionic (1.10.6) or do you only need ot after the update (1.10.14)? -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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/ubuntu/ppa Please follow this link, follow the instructions in the section "Adding this PPA to your system", then update your system with the command sudo apt dist-upgrade This will update only systemd as I did not upload any other package for Bionic to my PPA. Make also sure you have the update of network-manager (1.10.14-0ubuntu2) installed. Reboot and check whether everything works correctly now. -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 original network-manager version of Bionic (1.10.6) or do you only need ot after the update (1.10.14)? -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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/ubuntu/ppa Please follow this link, follow the instructions in the section "Adding this PPA to your system", then update your system with the command sudo apt dist-upgrade This will update only systemd as I did not upload any other package for Bionic to my PPA. Make also sure you have the update of network-manager (1.10.14-0ubuntu2) installed. Reboot and check whether everything works correctly now. -- 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: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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", then update your system with the command sudo apt dist-upgrade This will update only systemd as I did not upload any other package for Bionic to my PPA. Make also sure you have the update of network-manager (1.10.14-0ubuntu2) installed. Reboot and check whether everything works correctly now. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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", then update your system with the command sudo apt dist-upgrade This will update only systemd as I did not upload any other package for Bionic to my PPA. Make also sure you have the update of network-manager (1.10.14-0ubuntu2) installed. Reboot and check whether everything works correctly now. ** Changed in: network-manager (Ubuntu Bionic) Status: New => Incomplete ** 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/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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", then update your system with the command sudo apt dist-upgrade This will update only systemd as I did not upload any other package for Bionic to my PPA. Make also sure you have the update of network-manager (1.10.14-0ubuntu2) installed. Reboot and check whether everything works correctly now. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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. https://bugs.launchpad.net/bugs/1829913 Title: openconnect VPN is not propagating internal DNS anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
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? Perhaps we could add a dependency which would install this package automatically. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
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 addition, you could report a bug upstream, suggesting to let the rutes be saved in /etc/NetworkManager/system-connections in dotted-quad notation if they cannot be represented in CIDR notation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
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 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output
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. https://bugs.launchpad.net/bugs/1825946 Title: 'nm' autopkgtest fails due to GI stderr output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
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. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828102] Re: Regression in ModemManager
** 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828102] Re: regression in modemmanager
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) Status: New => In Progress ** Description changed: + [Impact] + + [Test case] + + [Regression potential] + + The patch is tiny, fixing an obvious overlook, and it only affects CDMA + broadband modems, so the risk of a regression is very low. + + [Original description] + ModemManager disconnects after ~30 sec caused by a typo in 1.8 - see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 + see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828102] Re: regression in modemmanager
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 reproduce the bug. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
