[Bug 1787802] [NEW] appstreamcli crashed with signal 5 in g_variant_new_parsed_va()
Public bug reported: Crashed when triggerred from initramfs, had to uninstall it to make progress. Reinstalled and running it manually shows no crashes but an assertion: (appstreamcli:5869): GLib-CRITICAL **: 11:01:51.409: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed AppStream cache update completed successfully ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: appstream 0.12.0-3 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Aug 18 21:19:53 2018 ExecutablePath: /usr/bin/appstreamcli InstallationDate: Installed on 2017-12-02 (259 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: appstreamcli refresh-cache Signal: 5 SourcePackage: appstream StacktraceTop: g_variant_new_parsed_va () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_parsed () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libappstream.so.4 () at /usr/lib/x86_64-linux-gnu/libappstream.so.4 as_cache_file_save () at /usr/lib/x86_64-linux-gnu/libappstream.so.4 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() UpgradeStatus: Upgraded to cosmic on 2018-08-07 (11 days ago) UserGroups: ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash cosmic need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787802 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752202] [NEW] U2F not working after upgrade: systemd dropped udev rules and libu2f-udev not installed
Public bug reported: Summary: * libu2f-udev is not installed automatically, and after upgrading systemd it has lost its udev rules for U2F devices. * installing u2f-host (which pulls in libu2f-udev) doesn't seem to be enough to get it working either, had to manually reload the rules Long version: I upgraded from XUbuntu 17.10 to 18.04 daily build for testing. Previously I was able to use a Yubikey U2F device with Chromium and Firefox, however after the upgrade no U2F device was detected, the browser just timed out the U2F detection. I installed u2f-host to debug the problem further but it told me that it couldn't find any U2F devices. I looked in /dev/hidraw* and my user couldn't access any. Running this and repluggingt the device fixed the permissions: sudo udevadm control --reload-rules. It looks like that systemd used to have udev rules for U2F devices but they got dropped recently, pointing to libu2f-udev: https://salsa.debian.org/systemd-team/systemd/commit/655e466caf37af36f527d42f164901b658203a2d Which is fine, except libu2f-udev is not installed automatically: libu2f-udev Reverse Depends: libu2f-host0 ubuntu-mate-desktop ubuntu-mate-core ubuntu-budgie-desktop libu2f-host0 Reverse Depends: libu2f-host-dev u2f-host pamu2fcfg libpam-u2f This seems wrong, individual desktop environments shouldn't bring this in, either the applications that use them (firefox, chromium) should recommend it, or a package common to all desktop flavours should pull it in. Please make libu2f-udev automatically installed as it was before when it was part of systemd, and reload the udev rules when it is installed. I'm filing this bug against systemd because the package that broke the behaviour was systemd, when udev rules got dropped from it the other packages' dependencies should've been updated so that the rules are not lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Feb 28 00:22:33 2018 InstallationDate: Installed on 2017-12-02 (87 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: root=UUID=0cc81157-5ab2-46eb-b70b-cb3c62f635e8 ro quiet vt.handoff=7 initrd=\EFI\ubuntu\initrd.img resume=/dev/nvme0n1p2 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-02-24 (3 days ago) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1752202 Title: U2F not working after upgrade: systemd dropped udev rules and libu2f- udev not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752202/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1681597] [NEW] DNS broken after >50m of uptime
Public bug reported: After about 50m of uptime news.ycombinator.com stops working in Chromium: news.ycombinator.com’s server's DNS address could not be found. DNS_PROBE_FINISHED_NXDOMAIN $ host news.ycombinator.com Host news.ycombinator.com not found: 2(SERVFAIL) This is a *regression* from Ubuntu 16.10, where DNS worked flawlessly. Workarounds: * 'systemctl restart systemd-resolved' solves the problem for another 50m * disable systemd-resolved and use the DNS server directly. This involves removing 'resolve [!UNAVAIL=return]' from nsswitch.conf, and disabling the systemd-resolved unit Logs show DNSSEC related errors, and DNSSEC getting disabled and reenabled: -- Logs begin at Mon 2017-04-10 23:10:59 BST, end at Tue 2017-04-11 00:11:14 BST. -- Apr 10 23:11:01 bolt systemd[1]: Starting Network Name Resolution... Apr 10 23:11:01 bolt systemd-resolved[1351]: Positive Trust Anchors: Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 10 23:11:01 bolt systemd-resolved[1351]: Negative trust anchors: 10.in-addr.arpa 16.172.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 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Apr 10 23:11:01 bolt systemd-resolved[1351]: Using system hostname 'bolt'. Apr 10 23:11:01 bolt systemd[1]: Started Network Name Resolution. Apr 10 23:11:05 bolt systemd-resolved[1351]: Switching to DNS server 194.168.4.100 for interface wlp3s0. Apr 10 23:11:06 bolt systemd-resolved[1351]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.4.100. Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question com IN SOA: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question ubuntu.com IN DS: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question ubuntu.com IN SOA: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN DS: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN A: failed-auxiliary Apr 10 23:11:06 bolt systemd-resolved[1351]: Server 194.168.4.100 does not support DNSSEC, downgrading to non-DNSSEC mode. Apr 10 23:11:06 bolt systemd-resolved[1351]: Switching to DNS server 194.168.8.100 for interface wlp3s0. Apr 10 23:11:07 bolt systemd-resolved[1351]: Using degraded feature set (UDP+EDNS0) for DNS server 194.168.8.100. Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question clamav.net IN DS: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question clamav.net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question cvd.clamav.net IN DS: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question cvd.clamav.net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN DS: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question current.cvd.clamav.net IN TXT: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: Server 194.168.8.100 does not support DNSSEC, downgrading to non-DNSSEC mode. Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: failed-auxiliary Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for question daisy.ubuntu.com IN A: failed-auxiliary Apr 10 23:11:52 bolt systemd[1]: Stopping Network Name Resolution... Apr 10 23:11:52 bolt systemd[1]: Stopped Network Name Resolution. Apr 10 23:11:52 bolt systemd[1]: Starting Network Name Resolution... Apr 10 23:11:52 bolt systemd-resolved[2868]: Positive Trust Anchors: Apr 10 23:11:52 bolt systemd-resolved[2868]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Apr 10 23:11:52 bolt systemd-resolved[2868]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Apr 10
