[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
I think this probably should be reworded: [Regression Potential] No, ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Disco: Fix Committed Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830503] Re: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1830503 Title: [MSI B450 TOMAHAWK (MS-7C02), Realtek ALC892, Red Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: No sound Motherboard MSI B450 Tomahawnk CPU APU AMD Ryzen 5 2400G-4 Core RX Vega. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 26 00:08:58 2019 InstallationDate: Installed on 2019-05-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inanna 1251 F pulseaudio /dev/snd/controlC0: inanna 1251 F pulseaudio /dev/snd/pcmC0D3p: inanna 1251 F...m pulseaudio Symptom_Jack: Red Line Out, Rear Symptom_Type: No sound at all Title: [MS-7C02, Realtek ALC892, Red Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd12/19/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1830503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837888] Re: lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1
Moving this bug to the kernel as investigation discovered a kernel regression in overmounting protection behavior in 5.3 rc1. So not a LXC bug but a kernel one. ** Package changed: lxc (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1837888 Title: lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1 Status in linux package in Ubuntu: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/lxc/20190724_134725_e90e9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/lxc/20190724_130343_e90e9@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/lxc/20190724_131610_e90e9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
** Changed in: nginx (Ubuntu Bionic) Status: Incomplete => Invalid ** Changed in: nginx (Ubuntu) Status: Incomplete => Invalid ** Changed in: openssl (Ubuntu Bionic) Status: New => Fix Released ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in nginx source package in Bionic: Invalid Status in openssl source package in Bionic: Fix Released Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
This change has made the system effectively inappropriate for use in a business situation where mistakes are to be avoided. In the old system, searching within a folder for a file to send to a client would only list files from that folder. Now, file-open and so on show me files from ANYWHERE ON THE SYSTEM FOR ANY CLIENT WHATSOEVER, leaving the user a single mis-click away from a GDPR violation. Choosing a folder should set a boundary on the files displayed. If I want search, I'll search. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
Looks like the update to 1.1.1-1ubuntu2.1~18.04.4 resolved the issue! The listed failing tests above are now passing. I don't see a way I can close out an issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: Incomplete Status in openssl source package in Bionic: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828102] Re: Regression in ModemManager
@till-kamppeter are you able to verify this for disco? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: Fix Committed Status in modemmanager source package in Eoan: Fix Released Bug description: [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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
I've just updated the two machines where I was seeing this to 237-3ubuntu10.25 and in both cases the update was successful and managed to complete without disconnecting the network. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] restarting systemd-networkd drops carrier on all bond slaves, temporarily interrupting networking over the bond. [test case] on a bionic system with 2 interfaces that can be put into a bond, create config files such as: root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev [NetDev] Name=bond0 Kind=bond root@lp1833671:~# cat /etc/systemd/network/20-ens8.network [Match] Name=ens8 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/20-ens9.network [Match] Name=ens9 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/30-bond0.network [Match] Name=bond0 [Network] Address=1.2.3.4/32 restart networkd, or reboot, and verify the bond is up: root@lp1833671:~# ip a 3: ens8: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 4: ens9: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 5: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff inet 1.2.3.4/32 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::4030:62ff:fecc:362b/64 scope link valid_lft forever preferred_lft forever restart networkd and check /var/log/syslog: root@lp1833671:~# systemctl restart systemd-networkd root@lp1833671:~# cat /var/log/syslog ... Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Gained carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Gained carrier [regression potential] this changes how bond slaves are managed, so regressions could affect any configurations using bonding. [other info] the patch is already included in d, and ifupdown manages networking in x, so this is needed only for b. [original description] Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
Hello Ken, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
Hello Balint, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-meta source package in Disco: Fix Committed Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
Hello Balint, or anyone else affected, Accepted ubuntu-meta into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.417.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-meta source package in Disco: Fix Committed Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
Hello jowfdoijdfdwfwdf, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now,
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
Hello Tom, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] restarting systemd-networkd drops carrier on all bond slaves, temporarily interrupting networking over the bond. [test case] on a bionic system with 2 interfaces that can be put into a bond, create config files such as: root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev [NetDev] Name=bond0 Kind=bond root@lp1833671:~# cat /etc/systemd/network/20-ens8.network [Match] Name=ens8 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/20-ens9.network [Match] Name=ens9 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/30-bond0.network [Match] Name=bond0 [Network] Address=1.2.3.4/32 restart networkd, or reboot, and verify the bond is up: root@lp1833671:~# ip a 3: ens8: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 4: ens9: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 5: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff inet 1.2.3.4/32 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::4030:62ff:fecc:362b/64 scope link valid_lft forever preferred_lft forever restart networkd and check /var/log/syslog: root@lp1833671:~# systemctl restart systemd-networkd root@lp1833671:~# cat /var/log/syslog ... Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Gained carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Gained carrier [regression potential] this changes how bond slaves are managed, so regressions could affect any configurations using bonding. [other info] the patch is already included in d, and ifupdown manages networking in x, so this is needed only for b. [original description] Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for
[Touch-packages] [Bug 1837937] Re: CRASH
?? Im lost -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837937 Title: CRASH Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 gnome: Installed: (none) Candidate: 1:3.30+1ubuntu1 Version table: 1:3.30+1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837944] Re: systemd-journal failed to write entry read only mode
*** This bug is a duplicate of bug 1837937 *** https://bugs.launchpad.net/bugs/1837937 ** This bug has been marked a duplicate of bug 1837937 CRASH -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837944 Title: systemd-journal failed to write entry read only mode Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837937] Re: CRASH
The version installed on your system is: "linux-image-5.2.0-9-generic 5.2.0-9.10" and this version is not yet released. ** Attachment added: "linux.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+attachment/5279290/+files/linux.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837937 Title: CRASH Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 gnome: Installed: (none) Candidate: 1:3.30+1ubuntu1 Version table: 1:3.30+1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837944] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837944 Title: systemd-journal failed to write entry read only mode Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837937] Re: CRASH
no and its greyed out... ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837937 Title: CRASH Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 gnome: Installed: (none) Candidate: 1:3.30+1ubuntu1 Version table: 1:3.30+1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu devel/universe amd64 Packages The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837944] [NEW] systemd-journal failed to write entry read only mode
Public bug reported: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan package-from-proposed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837944 Title: systemd-journal failed to write entry read only mode Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 systemd: Installed: 240-6ubuntu10 Candidate: 240-6ubuntu10 Version table: *** 240-6ubuntu10 500 500 http://archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 240-6ubuntu9 500 500 http://archive.ubuntu.com/ubuntu devel/main amd64 Packages systemd-journal failed to write entry read only mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:39 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837944/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
This bug was fixed in the package ubuntu-meta - 1.417.2 --- ubuntu-meta (1.417.2) bionic; urgency=medium * Added xdg-desktop-portal-gtk to desktop-recommends (LP: #1795959) -- Ken VanDine Tue, 09 Jul 2019 13:11:04 -0400 ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795959] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Released Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837938] [NEW] Incorrect: "python3 /usr/lib/software-properties/software-properties-dbus"
Public bug reported: Incorrect: root 13608 1 0 09:29 ?00:00:00 python3 /usr/lib/software-properties/software-properties-dbus YES: root 13608 1 0 09:29 ?00:00:00 /usr/bin/python3 /usr/lib/software-properties/software-properties-dbus ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-common 0.98.5 Uname: Linux 5.2.2-050202-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:25 2019 InstallationDate: Installed on 2018-12-02 (235 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to eoan on 2018-12-02 (234 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1837938 Title: Incorrect: "python3 /usr/lib/software-properties/software-properties- dbus" Status in software-properties package in Ubuntu: New Bug description: Incorrect: root 13608 1 0 09:29 ?00:00:00 python3 /usr/lib/software-properties/software-properties-dbus YES: root 13608 1 0 09:29 ?00:00:00 /usr/bin/python3 /usr/lib/software-properties/software-properties-dbus ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-common 0.98.5 Uname: Linux 5.2.2-050202-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:26:25 2019 InstallationDate: Installed on 2018-12-02 (235 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to eoan on 2018-12-02 (234 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1837938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837926] [NEW] snapd snap ftbfs in eoan due to python-apt regression
Public bug reported: snapd snap FTBFS in launchpad snap build due to python-apt regression in eoan https://launchpad.net/~xnox/+snap/snapd/+build/626157 ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: core20 rls-ee-incoming ** Tags added: core20 ** Tags added: rls-ee-incoming ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1837926 Title: snapd snap ftbfs in eoan due to python-apt regression Status in python-apt package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: snapd snap FTBFS in launchpad snap build due to python-apt regression in eoan https://launchpad.net/~xnox/+snap/snapd/+build/626157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1837926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
I have accepted this to disco-proposed conditionally without the fix landing in eoan yet as per the ongoing 242 systemd merge, mostly because the proposed changes are already merged and accepted upstream. But to make sure eoan is not left without this fix, please be sure to push the changes to eoan-proposed as soon as the systemd merge is done, uploaded and migrated. If possible, I'd prefer not releasing these out of -proposed without the eoan counterparts at least present in eoan-proposed. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
Hello jowfdoijdfdwfwdf, or anyone else affected, Accepted systemd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
Hello Dan, or anyone else affected, Accepted systemd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward
[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
I have accepted this to disco-proposed conditionally without the fix landing in eoan yet as per the ongoing 242 systemd merge, mostly because the proposed changes are already merged and accepted upstream. But to make sure eoan is not left without this fix, please be sure to push the changes to eoan-proposed as soon as the systemd merge is done, uploaded and migrated. If possible, I'd prefer not releasing these out of -proposed without the eoan counterparts at least present in eoan-proposed. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent from the dhcp address it provided, 10.10.0.75, then this configuration will result in the client being unable to reach anything through the router, because all its packets will have a source address of 10.10.0.5, which the router would drop/reject. [regression potential] this only affects dhcp routes provided by a dhcp server using the 'static' or 'classless' route dhcp options. Since this behavior is currently the default when a system doesn't add static address(es) to interfaces that also get dhcp addresses, this is likely not a change in behavior for the vast majority of systems. And any systems that do add static address(es) would usually be able to route through a gateway from either the dhcp-provided, or static, address. So the regression potential for this change should be low.
[Touch-packages] [Bug 1837894] Re: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
We've also seen regressions with lxc which atm appear to be related to a regression in mounting sysfs in containers which use user namespaces (bug 1837888 for reference, though there's no activity on the bug as of yet, just some irc discussion about the regression). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837894 Title: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
** Changed in: nginx (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: Incomplete Status in openssl source package in Bionic: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837894] Re: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
boot-and-services failed because: Jul 24 13:09:02 autopkgtest systemd[1]: Starting Container c1... Jul 24 13:09:02 autopkgtest systemd-nspawn[891]: Failed to mount sysfs (type sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not permitted Jul 24 13:09:02 autopkgtest systemd-nspawn[891]: Failed to add new veth interfaces (ve-c1:host0): No such process Jul 24 13:09:02 autopkgtest systemd[1]: systemd-nspawn@c1.service: Main process exited, code=exited, status=1/FAILURE Jul 24 13:09:02 autopkgtest systemd[1]: systemd-nspawn@c1.service: Failed with result 'exit-code'. Jul 24 13:09:02 autopkgtest systemd[1]: Failed to start Container c1. as did upstream TEST-01: Failed to mount sysfs (type sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not permitted and upstream TEST-24: Failed to mount sysfs (type sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not permitted those seem to be the problem on all arch failure logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837894 Title: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
** Also affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nginx (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Status in nginx source package in Bionic: New Status in openssl source package in Bionic: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837914] [NEW] restart systemd-jounald fails
Public bug reported: While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal/journal- file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: journal xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837914 Title: restart systemd-jounald fails Status in systemd package in Ubuntu: New Bug description: While restarting systemd-jounald, the following error message occurs: systemd-journald[28007]: Assertion 'f' failed at ../src/journal /journal-file.c:143, function journal_file_close(). Aborting. release: Ubuntu 16.04.5 LTS systemd version: 229-4ubuntu21.22 This issue is reported at https://github.com/systemd/systemd/issues/12400 and solved at https://github.com/systemd/systemd/pull/12679 Please cherry-pick this fix to the ubuntu16.04 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833758] Re: lvm2: vgcfgbackup in postinst takes several minutes
** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1833758 Title: lvm2: vgcfgbackup in postinst takes several minutes Status in lvm2 package in Ubuntu: New Bug description: The postinst for lvm2 includes a call to vgcfgbackup; in the version included in eoan 2.03.02-2ubuntu4 (and 2.03.02-2ubuntu3 before it), this command takes several minutes to run when invoked in an schroot as happens when a building a package with sbuild that ends up pulling lvm2 as part of its build dependency chain. An example package with lvm2 in its build depends is rsnapshot, but this behavior was seen with a build of glibc. Some notes: - this behavior is NOT seen with the version of lvm2 in disco. - this happens in bionic with a 4.15 kernel and disco with a 5.0 kernel (different hosts, so different sets of block devices) - this happens regardless of whether the host is currently using logical volumes or not Here's the time difference between running the disco version and the eoan version: (disco-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Failed to connect to lvmetad. Falling back to device scanning. real0m0.204s user0m0.014s sys 0m0.010s (eoan-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Device /dev/sda not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. real4m11.405s user0m0.470s sys 0m0.576s /proc/mounts in the schroot: (eoan-amd64)root@HOSTNAME:~# cat /proc/mounts eoan-amd64 / overlay rw,relatime,lowerdir=/var/lib/schroot/union/underlay/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34,upperdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/upper,workdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/work 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=10197712k,nr_inodes=2549428,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/sda2 /home ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sda2 /tmp ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /run/shm tmpfs
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** Attachment added: "log-network-manager-with-segmentation.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279222/+files/log-network-manager-with-segmentation.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
** Attachment added: "log-network-manager-without-segmentation.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279221/+files/log-network-manager-without-segmentation.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
Jean, thank you for the input, could you retest these two cases (with and without split connection) but create debug logs of Network Manager and systemd-resolved, following the instructions on https://wiki.ubuntu.com/DebuggingNetworkManager (and/or of my comment #10)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
This bug report expired because 17.04 is not supported anymore. Did anyone recreate a corresponding bug report for a more recent version of Ubuntu? If so, can you please publish the link so we can subscribe to it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Won't Fix Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837888] [NEW] lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/lxc/20190724_134725_e90e9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/lxc/20190724_130343_e90e9@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/lxc/20190724_131610_e90e9@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1837888 Title: lxc 3.0.3-0ubuntu1 ADT test failure with linux 5.3.0-0.1 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/lxc/20190724_134725_e90e9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/lxc/20190724_130343_e90e9@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/lxc/20190724_131610_e90e9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1837888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837894] [NEW] systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837894 Title: systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/s/systemd/20190724_154200_5c46d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/s/systemd/20190724_143708_5c46d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/s/systemd/20190724_135803_5c46d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837443] Re: [Power9][Witherspoon dd2.3] unable to set hwclock
I believe /sbin/hwclock is the default tool for manually setting the hwclock in Linux. I’m nervous that higher level workloads may depend on the correct functioning of the /sbin/hwclock tool for their successful operation. The /sbin/hwclock tool is shipped with the util-linux package. Adding util-linux as impacted and assigning to Foundations team to comment on whether the /sbin/hwclock tool not operating on witherspoon is a serious issue or not. ** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: bugproxy (bugproxy) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1837443 Title: [Power9][Witherspoon dd2.3] unable to set hwclock Status in The Ubuntu-power-systems project: Triaged Status in util-linux package in Ubuntu: New Bug description: On the upgraded witherspoon Power9 system we are unable to set hwclock. ubuntu@bobone:~$ uname -a Linux bobone 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:31:42 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@bobone:~$ cat /etc/issue Ubuntu 19.04 \n \l ubuntu@bobone:~$ date Mon Jul 22 18:25:04 UTC 2019 ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sleep 5s; sudo /sbin/hwclock 2019-07-22 18:25:26.799805+00:00 ubuntu@bobone:~$ ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sleep 5s; sudo /sbin/hwclock --verbose hwclock from util-linux 2.33.1 System Time: 1563820048.938797 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1101096600 seconds after 1969 Last calibration done at 1101096600 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2019/07/22 18:27:29 Hw clock time : 2019/07/22 18:27:29 = 1563820049 seconds since 1969 Time since last adjustment is 462723449 seconds Calculated Hardware Clock drift is 0.00 seconds 2019-07-22 18:27:28.877732+00:00 ubuntu@bobone:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1837443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
My systemd is newer (237-3ubuntu10.24), instead network manager is locked at 1.10.6 (1.10.6-2ubuntu1.1). I've upgraded network-manager as suggested to 1.10.14-0ubuntu2 and rebooted. I've shut down both my Wifi and LAN since I'm at the office, and hooked up my phone with USB tethering to use an external connection and use the VPN to my office. First test: it works. I get my DNS from the VPN: Link 61 (tun2) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.27.0.42 172.27.0.33 DNS Domain: ~. Following the test case in #1754671: when I enable the split connection, this is the full result of systemd-resolve --status, where I do not see any DNS coming from the VPN: Global DNS Domain: mycompany.com DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 48 (tun1) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 43 (tun0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 42 (enp0s20f0u2) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.42.129 DNS Domain: ~. Link 11 (br-b2c3b7f9b208) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 10 (br-775248335fa8) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 9 (br-6671ba352ece) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 8 (br-642ed19f0ac7) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 7 (br-5699f03e12bc) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 6 (br-1f97d7363f0e) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 5 (docker0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 4 (br-dbf7ef8f9ab9) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enx106530b07160) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :