[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] [NEW] Update to systemd 237-3ubuntu10.54 broke dns
Public bug reported: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com ** 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: New Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
Hi Daniel, could you please share the log (e.g. apport, sosreport or journalctl when issue happens)? -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Invalid Status in systemd package in Ubuntu: Invalid Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
I have a 'normal use case' that triggers this: Copying a large file. My system has 32GB of RAM and 4GB of swap. Trying to copy a 29,613MB file from a reasonably fast SD card to my local (cacheless) NVMe SSD is triggering systemd-oomd. -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Invalid Status in systemd package in Ubuntu: Invalid Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1987642] Re: Chile is delaying the DST by one week for 2022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1987642 Title: Chile is delaying the DST by one week for 2022 Status in tzdata package in Ubuntu: Confirmed Status in tzdata source package in Xenial: Confirmed Status in tzdata source package in Bionic: Confirmed Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Kinetic: Confirmed Bug description: Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2]. DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023. Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this. Upstream commit : https://github.com/eggert/tz/commit/711b46f8fc4e8a3d5caf7d4820562d6cdfe9d769 We need to fix this in all or releases back to Xenial. [1] https://www.interior.gob.cl/noticias/2022/08/09/comunicado-el-proximo-sabado-10-de-septiembre-los-relojes-se-deben-adelantar-una-hora/ [2] https://www.timeanddate.com/news/time/chile-dst-delay-2022.html#:~:text=Chile%20is%20delaying%20the%20start,financial%20district%20in%20Chile%27s%20capital. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1987642/+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 1987642] Re: Chile is delaying the DST by one week for 2022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1987642 Title: Chile is delaying the DST by one week for 2022 Status in tzdata package in Ubuntu: Confirmed Status in tzdata source package in Xenial: Confirmed Status in tzdata source package in Bionic: Confirmed Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Kinetic: Confirmed Bug description: Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2]. DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023. Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this. Upstream commit : https://github.com/eggert/tz/commit/711b46f8fc4e8a3d5caf7d4820562d6cdfe9d769 We need to fix this in all or releases back to Xenial. [1] https://www.interior.gob.cl/noticias/2022/08/09/comunicado-el-proximo-sabado-10-de-septiembre-los-relojes-se-deben-adelantar-una-hora/ [2] https://www.timeanddate.com/news/time/chile-dst-delay-2022.html#:~:text=Chile%20is%20delaying%20the%20start,financial%20district%20in%20Chile%27s%20capital. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1987642/+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 1987642] Re: Chile is delaying the DST by one week for 2022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1987642 Title: Chile is delaying the DST by one week for 2022 Status in tzdata package in Ubuntu: Confirmed Status in tzdata source package in Xenial: Confirmed Status in tzdata source package in Bionic: Confirmed Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Kinetic: Confirmed Bug description: Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2]. DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023. Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this. Upstream commit : https://github.com/eggert/tz/commit/711b46f8fc4e8a3d5caf7d4820562d6cdfe9d769 We need to fix this in all or releases back to Xenial. [1] https://www.interior.gob.cl/noticias/2022/08/09/comunicado-el-proximo-sabado-10-de-septiembre-los-relojes-se-deben-adelantar-una-hora/ [2] https://www.timeanddate.com/news/time/chile-dst-delay-2022.html#:~:text=Chile%20is%20delaying%20the%20start,financial%20district%20in%20Chile%27s%20capital. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1987642/+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 1987642] Re: Chile is delaying the DST by one week for 2022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1987642 Title: Chile is delaying the DST by one week for 2022 Status in tzdata package in Ubuntu: Confirmed Status in tzdata source package in Xenial: Confirmed Status in tzdata source package in Bionic: Confirmed Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Kinetic: Confirmed Bug description: Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2]. DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023. Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this. Upstream commit : https://github.com/eggert/tz/commit/711b46f8fc4e8a3d5caf7d4820562d6cdfe9d769 We need to fix this in all or releases back to Xenial. [1] https://www.interior.gob.cl/noticias/2022/08/09/comunicado-el-proximo-sabado-10-de-septiembre-los-relojes-se-deben-adelantar-una-hora/ [2] https://www.timeanddate.com/news/time/chile-dst-delay-2022.html#:~:text=Chile%20is%20delaying%20the%20start,financial%20district%20in%20Chile%27s%20capital. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1987642/+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 1987642] Re: Chile is delaying the DST by one week for 2022
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1987642 Title: Chile is delaying the DST by one week for 2022 Status in tzdata package in Ubuntu: Confirmed Status in tzdata source package in Xenial: Confirmed Status in tzdata source package in Bionic: Confirmed Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Kinetic: Confirmed Bug description: Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2]. DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023. Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this. Upstream commit : https://github.com/eggert/tz/commit/711b46f8fc4e8a3d5caf7d4820562d6cdfe9d769 We need to fix this in all or releases back to Xenial. [1] https://www.interior.gob.cl/noticias/2022/08/09/comunicado-el-proximo-sabado-10-de-septiembre-los-relojes-se-deben-adelantar-una-hora/ [2] https://www.timeanddate.com/news/time/chile-dst-delay-2022.html#:~:text=Chile%20is%20delaying%20the%20start,financial%20district%20in%20Chile%27s%20capital. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1987642/+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 1988062] Re: Tests are failing on builders with proxy set
** Changed in: glib-networking (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1988062 Title: Tests are failing on builders with proxy set Status in glib-networking package in Ubuntu: Fix Committed Bug description: Reported upstream https://gitlab.gnome.org/GNOME/glib- networking/-/issues/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1988062/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server
It looks like jokroepke created an upstream issue: https://github.com/systemd/systemd/issues/24098. ** Bug watch added: github.com/systemd/systemd/issues #24098 https://github.com/systemd/systemd/issues/24098 -- 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/1981431 Title: systemd-resolved: DNSSEC validation failed: incompatible-server Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Incomplete Bug description: Hi, I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4. 2 days ago, I enabled DNSSEC=true through: # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf DNSSEC=yes After running some hours, systemd-resolved stop working. Log lines like incompatible-server starts to spam. Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution... Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors: Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: int.creativesandbox.de Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'. Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution. Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 214.162.in-addr.arpa IN SOA: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN DS: no-signature Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 126.76.214.162.in-addr.arpa IN SOA: no-signature Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question . IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question your-server.de IN SOA: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question 201.138.clients.your-server.de IN DS: incompatible-server Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for question static.237.11.201.138.clients.your-server.de IN : incompatible-server Mention here, I'm running multiple machines with the same config against the same upstream DNS server. From time to time, only one instance is stop working here. Running a manual query also fails here, for example: # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server Running 'resolvectl reset-server-features' helps here and can be considered as workaround. # resolvectl query noc3.wordfence.com noc3.wordfence.com: resolve call failed: DNSSEC validation failed: incompatible-server # resolvectl reset-server-features # resolvectl query noc3.wordfence.com noc3.wordfence.com: 35.155.126.231 -- link: eth0 -- Information acquired via protocol DNS in 26.5ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network By reading issues upstream looks like https://github.com/systemd/systemd/issues/6490. A fix is implemented (https://github.com/systemd/systemd/pull/18624) and released in 248 which is included in Ubuntu 22.04. But there is another fix around this issue (https://github.com/systemd/systemd/pull/20214) which is released in systemd 250. I would like to know if it's possible to backport this fix into Ubuntu 22.04. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981431/+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 1987985] Re: Totem black screen playing a video
** Changed in: gstreamer1.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987985 Title: Totem black screen playing a video Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Click on a video file. totem opens with a black screen. problem with webm, avi, mov totem: Installed: 43~beta-1ubuntu1 I open the bug against totem but the bug seems open against gstreamer1.0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 17:57:01 2022 InstallationDate: Installed on 2022-08-11 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+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 1988078] [NEW] Please backport systemd-hwdb patches to support src:systemd-hwe tests
Public bug reported: [Impact] We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a test script[2] to ensure that no redundant hwdb rules are added to the package, i.e. rules that are already present in src:systemd. This test requires patches to implement --root flag support for the `systemd-hwdb query` command[3]. These patches are already present in kinetic. Without these patches in Jammy, src:systemd-hwe would have to disable these tests, which are important to maintaining HWE hwdb rules in Ubuntu. [1] https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/1983996 [2] https://git.launchpad.net/~canonical-foundations/+git/systemd-hwe/tree/tests/hwdb-redundancy?h=main [3] https://github.com/systemd/systemd/pull/23518 [Test plan] * Create a new directory for testing hwdb rule queries: $ mkdir -p fakeroot/etc/udev/hdwb.d * Add a new .hwdb file to override an existing rule. For example, I chose to override the last entry from /lib/udev/hdwb.d/60-keyboard.hwdb: $ tail -2 /lib/udev/hwdb.d/60-keyboard.hwdb > fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ sed -i 's/chromebook/reserved/g' fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ cat fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* XKB_FIXED_MODEL=reserved * Create the hwdb.bin within fakeroot: $ systemd-hwdb update --root fakeroot $ ls fakeroot/etc/udev/hwdb.bin fakeroot/etc/udev/hwdb.bin * Finally, attempt to query this new hwdb.bin using systemd-hwdb query. On an unpatched system, we will see results from the system's hwdb.bin: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=chromebook ...and on a patched system we should see the overridden rule: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=reserved [Where problems could occur] The patches add support for the --root flag when calling systemd-hwdb query, thus changing the behavior of this command (previously, query would always load the system's hwdb.bin). It is unlikely that existing scripts try to use the --root flag with `systemd-hwdb query`, but if they did, this is where we would see problems. ** 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/1988078 Title: Please backport systemd-hwdb patches to support src:systemd-hwe tests Status in systemd package in Ubuntu: New Bug description: [Impact] We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a test script[2] to ensure that no redundant hwdb rules are added to the package, i.e. rules that are already present in src:systemd. This test requires patches to implement --root flag support for the `systemd- hwdb query` command[3]. These patches are already present in kinetic. Without these patches in Jammy, src:systemd-hwe would have to disable these tests, which are important to maintaining HWE hwdb rules in Ubuntu. [1] https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/1983996 [2] https://git.launchpad.net/~canonical-foundations/+git/systemd-hwe/tree/tests/hwdb-redundancy?h=main [3] https://github.com/systemd/systemd/pull/23518 [Test plan] * Create a new directory for testing hwdb rule queries: $ mkdir -p fakeroot/etc/udev/hdwb.d * Add a new .hwdb file to override an existing rule. For example, I chose to override the last entry from /lib/udev/hdwb.d/60-keyboard.hwdb: $ tail -2 /lib/udev/hwdb.d/60-keyboard.hwdb > fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ sed -i 's/chromebook/reserved/g' fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ cat fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* XKB_FIXED_MODEL=reserved * Create the hwdb.bin within fakeroot: $ systemd-hwdb update --root fakeroot $ ls fakeroot/etc/udev/hwdb.bin fakeroot/etc/udev/hwdb.bin * Finally, attempt to query this new hwdb.bin using systemd-hwdb query. On an unpatched system, we will see results from the system's hwdb.bin: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=chromebook ...and on a patched system we should see the overridden rule: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=reserved [Where problems could occur] The patches add support for the --root flag when calling systemd-hwdb query, thus changing the behavior of this command (previously, query would always load the system's
[Touch-packages] [Bug 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Yes, this fix should be at least SRUed to Ubuntu 22.04 (jammy) and 20.04
(focal). I will prepare the SRU once the current pending one went
through.
** Also affects: apport (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1889443
Title:
"ValueError: ['separator'] has no binary content" when running
`apport-unpack /var/crash/...`
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
New
Status in apport source package in Focal:
New
Status in apport source package in Jammy:
New
Bug description:
The crash file I'm using is as-produced by the system (on groovy), and
appears to have an empty value for separator:
$ grep separator /var/crash/_usr_bin_neomutt.1000.crash
separator:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 77, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in
extract_keys
raise ValueError('%s has no binary content' %
ValueError: ['separator'] has no binary content
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29
12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash
640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23
10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash
640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29
12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash
CurrentDesktop: i3
Date: Wed Jul 29 12:22:54 2020
InstallationDate: Installed on 2019-05-07 (448 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1889443/+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 1987985] Re: Totem black screen playing a video
Wait, it seems nautilus has problems passing arguments to the called application: if i start totem by double click on the video and ask totem for 'Properties' i see a window wit all info 'Unknown' or 'N/A' so let wait for new nautilus who is blocked for dependencies corrado@corrado-n6-kk-0811:~$ apt policy nautilus nautilus: Installed: 1:43~beta.1-2ubuntu2 Candidate: 1:43~beta.1-2ubuntu3 ... The following packages have been kept back: burner-common libburner-media3-1 libnautilus-extension4 nautilus ... I found another app having the same problem... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987985 Title: Totem black screen playing a video Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Click on a video file. totem opens with a black screen. problem with webm, avi, mov totem: Installed: 43~beta-1ubuntu1 I open the bug against totem but the bug seems open against gstreamer1.0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 17:57:01 2022 InstallationDate: Installed on 2022-08-11 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+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 1987573] Re: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it
The `journalctl -xb` output is attached. The error is noted at time "Aug 29 11:12:19". I had to press Ctrl-D at the right moment during boot so that I could get this output. For clarity, I removed the "nofail" to get this error again, and it is reproducible by adding/removing "nofail". ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+attachment/5612388/+files/journalctl.txt -- 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/1987573 Title: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it Status in systemd package in Ubuntu: Incomplete Bug description: After performing `do-release-upgrade` from 20.04 to 22.04.01, the system failed to boot with a message of: Failed to mount /home Dependency failed for Local File Systems. It took some work to figure out, but adding "nofail" to the fstab line allowed boot to proceed, and with that, the system appears to be working without issue. Both /boot and /home are mounted from subvolumes on the same btrfs filesystem. The working fstab is below: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # LABEL=Root / btrfs defaults,subvol=@ 0 1 LABEL=Root /home btrfs defaults,subvol=@home,nofail 0 2 LABEL=EscherBackup /mnt/EscherBackup btrfs defaults0 2 LABEL=PicassoBackup /mnt/PicassoBackup btrfs defaults0 2 LABEL=scratch /mnt/scratchbtrfs defaults0 2 /dev/mapper/cryptswap1 none swap sw 0 0 /dev/mapper/cryptswap2 none swap sw 0 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Aug 24 20:16:42 2022 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+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 1988062] [NEW] Tests are failing on builders with proxy set
Public bug reported: Reported upstream https://gitlab.gnome.org/GNOME/glib- networking/-/issues/195 ** Affects: glib-networking (Ubuntu) Importance: High Status: Triaged ** Tags: update-excuse ** Changed in: glib-networking (Ubuntu) Importance: Undecided => High ** Changed in: glib-networking (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1988062 Title: Tests are failing on builders with proxy set Status in glib-networking package in Ubuntu: Triaged Bug description: Reported upstream https://gitlab.gnome.org/GNOME/glib- networking/-/issues/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1988062/+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 1971932] Re: error in rsync protocol data stream
Please excuse me, it slipped my mind and I only became aware of it through the email notification about a new activity in the bug tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1971932] Re: error in rsync protocol data stream
-z, really? If you could have sent an earlier post with this information, I would have used this solution. Maybe next time ;-) Cheers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1971932] Re: error in rsync protocol data stream
Unfortunately, since I cannot update the target, which is an embedded system, I have been able to help myself by disabling compression. Instead of calling rsync with the parameters -avz I use temporarily only -av for the affected target systems and the synchronization runs without problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1987985] Re: Totem black screen playing a video
I have some video files in my Videos directory. Playing them from command line gives no problem and the video is correctly played also with sound corrado@corrado-n6-kk-0811:~$ cd Videos corrado@corrado-n6-kk-0811:~/Videos$ ls Screencasts x.AVI x.MOV x.mp4 x.webm corrado@corrado-n6-kk-0811:~/Videos$ totem x.webm corrado@corrado-n6-kk-0811:~/Videos$ totem x.AVI corrado@corrado-n6-kk-0811:~/Videos$ totem x.mp4 corrado@corrado-n6-kk-0811:~/Videos$ totem x.MOV corrado@corrado-n6-kk-0811:~/Videos$ but if do double click on any of the files i have a black screen. same with right click on file and selecting 'open with videos' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987985 Title: Totem black screen playing a video Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Click on a video file. totem opens with a black screen. problem with webm, avi, mov totem: Installed: 43~beta-1ubuntu1 I open the bug against totem but the bug seems open against gstreamer1.0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 17:57:01 2022 InstallationDate: Installed on 2022-08-11 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+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 1971932] Re: error in rsync protocol data stream
It's rsync! The new version does not like to work with the old one. I had the same problems. After I upgraded my Ubuntu server (running VMs) from LTS 20.04 to LTS 22.4.1. Since then the backups using rsync of the VMs (max file size 6.2 GB) to the backup server (Debian 10) failed. Intern (within the Ubuntu file tree) rsync still works fine. The rsync error always occurred at the large file (max 6.2 Gb). Ubuntu 22.04: apt-cache policy rsync Installed: 3.2.3-8ubuntu3 Candidate: 3.2.3-8ubuntu3 Version table: *** 3.2.3-8ubuntu3 500 Debian 10: apt-cache policy rsync Installed: 3.1.3-6 Candidate: 3.1.3-6 Version table: *** 3.1.3-6 500 After I upgraded my Debian from 10 (buster) to 11 (bullseye) I had a new version for rsync: apt-cache policy rsync rsync: Installed: 3.2.3-4+deb11u1 Candidate: 3.2.3-4+deb11u1 Version table: *** 3.2.3-4+deb11u1 500 ... tadaa, and it worked -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1987573] Re: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it
Bill - Can you please provide more detailed logs from a failed boot (i.e. complete journalctl output from the failed .mount units)? ** Package changed: btrfs-progs (Ubuntu) => systemd (Ubuntu) -- 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/1987573 Title: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it Status in systemd package in Ubuntu: Incomplete Bug description: After performing `do-release-upgrade` from 20.04 to 22.04.01, the system failed to boot with a message of: Failed to mount /home Dependency failed for Local File Systems. It took some work to figure out, but adding "nofail" to the fstab line allowed boot to proceed, and with that, the system appears to be working without issue. Both /boot and /home are mounted from subvolumes on the same btrfs filesystem. The working fstab is below: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # LABEL=Root / btrfs defaults,subvol=@ 0 1 LABEL=Root /home btrfs defaults,subvol=@home,nofail 0 2 LABEL=EscherBackup /mnt/EscherBackup btrfs defaults0 2 LABEL=PicassoBackup /mnt/PicassoBackup btrfs defaults0 2 LABEL=scratch /mnt/scratchbtrfs defaults0 2 /dev/mapper/cryptswap1 none swap sw 0 0 /dev/mapper/cryptswap2 none swap sw 0 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Aug 24 20:16:42 2022 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+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 1987573] [NEW] /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it
You have been subscribed to a public bug: After performing `do-release-upgrade` from 20.04 to 22.04.01, the system failed to boot with a message of: Failed to mount /home Dependency failed for Local File Systems. It took some work to figure out, but adding "nofail" to the fstab line allowed boot to proceed, and with that, the system appears to be working without issue. Both /boot and /home are mounted from subvolumes on the same btrfs filesystem. The working fstab is below: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # LABEL=Root / btrfs defaults,subvol=@ 0 1 LABEL=Root /home btrfs defaults,subvol=@home,nofail 0 2 LABEL=EscherBackup /mnt/EscherBackup btrfs defaults0 2 LABEL=PicassoBackup /mnt/PicassoBackup btrfs defaults0 2 LABEL=scratch /mnt/scratchbtrfs defaults0 2 /dev/mapper/cryptswap1 none swap sw 0 0 /dev/mapper/cryptswap2 none swap sw 0 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Aug 24 20:16:42 2022 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: systemd (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade jammy -- /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it https://bugs.launchpad.net/bugs/1987573 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- 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 1987920] Re: indicator-datetime fails to build with default gcc (gcc-12)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1987920 Title: indicator-datetime fails to build with default gcc (gcc-12) Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-datetime source package in Kinetic: Confirmed Bug description: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- datetime) which are maintained and are able to build successfully with the default compiler. See https://launchpad.net/bugs/1983374 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1987920/+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 1971932] Re: error in rsync protocol data stream
** Changed in: rsync (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1988033] Re: Login screen is missing the Ubuntu logo
** No longer affects: ubuntu-settings (Ubuntu) -- 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/1988033 Title: Login screen is missing the Ubuntu logo Status in plymouth package in Ubuntu: Fix Committed Bug description: Login screen is missing the Ubuntu logo since the latest updates to kinetic. Looks like plymouth 22.02.122-1ubuntu2 might have triggered it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1988033/+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 1988033] Re: Login screen is missing the Ubuntu logo
Our settings are pointing to a non-existent file now: org.gnome.login-screen logo '/usr/share/plymouth/ubuntu-logo.png' which is the responsibility of source package 'ubuntu-settings'. ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- 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/1988033 Title: Login screen is missing the Ubuntu logo Status in plymouth package in Ubuntu: Fix Committed Bug description: Login screen is missing the Ubuntu logo since the latest updates to kinetic. Looks like plymouth 22.02.122-1ubuntu2 might have triggered it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1988033/+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 1988033] Re: Login screen is missing the Ubuntu logo
https://launchpad.net/ubuntu/+source/plymouth/22.02.122-1ubuntu3 ** Package changed: gnome-shell (Ubuntu) => plymouth (Ubuntu) ** Changed in: plymouth (Ubuntu) Importance: Undecided => Low ** Changed in: plymouth (Ubuntu) Status: New => Fix Committed -- 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/1988033 Title: Login screen is missing the Ubuntu logo Status in plymouth package in Ubuntu: Fix Committed Bug description: Login screen is missing the Ubuntu logo since the latest updates to kinetic. Looks like plymouth 22.02.122-1ubuntu2 might have triggered it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1988033/+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 1979113] Re: Kinetic sound disappeared after today updates (still trying to use pipewire-media-session)
This was fixed in ubuntu-meta 1.488 when wireplumber was introduced (which should also uninstall pipewire-media-session). ** Package changed: pipewire (Ubuntu) => ubuntu-meta (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => 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/1979113 Title: Kinetic sound disappeared after today updates (still trying to use pipewire-media-session) Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: on my laptop sound disappeared after today updates. Sound was already disappeared on my two desktop but I didn't know which updates to attribute the problem to. Today updates are: Start-Date: 2022-06-18 10:05:42 Commandline: apt upgrade Requested-By: corrado (1000) Upgrade: gnome-text-editor:amd64 (42.1-1, 42.2-1), tracker:amd64 (3.3.1-1, 3.3.1-2), libedata-book-1.2-26:amd64 (3.44.2-1, 3.44.2-2), libkeyutils1:amd64 (1.6.1-2ubuntu3, 1.6.1-3ubuntu1), libebook-1.2-20:amd64 (3.44.2-1, 3.44.2-2), libecal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libedataserver-1.2-26:amd64 (3.44.2-1, 3.44.2-2), evolution-data-server:amd64 (3.44.2-1, 3.44.2-2), libsnmp-base:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), libqt5serialport5:amd64 (5.15.4-1, 5.15.4-2), libxrender1:amd64 (1:0.9.10-1build4, 1:0.9.10-1.1), libsnmp40:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), evolution-data-server-common:amd64 (3.44.2-1, 3.44.2-2), pipewire-media-session:amd64 (0.4.1-2ubuntu2, 0.4.1-3ubuntu1), libglib2.0-bin:amd64 (2.72.1-1, 2.72.2-2), libqt5positioning5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), libpipewire-0.3-common:amd64 (0.3.51-1ubuntu3, 0.3.52-1), pipewire-pulse:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gnome-bluetooth-3-common:amd64 (42.0-5, 42.1-1), libqt5core5a:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), qt5-gtk-platformtheme:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libgspell-1-common:amd64 (1.10.0-1, 1.11.1-1), libgtksourceview-5-common:amd64 (5.4.1-3build1, 5.4.2-1), libmalcontent-0-0:amd64 (0.10.4-1, 0.10.5-1), libqt5charts5:amd64 (5.15.4-1, 5.15.4-2), libqt5script5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), libencode-locale-perl:amd64 (1.05-1.1, 1.05-2), libqt5network5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), tracker-miner-fs:amd64 (3.3.0-1build1, 3.3.1-1), libgspell-1-2:amd64 (1.10.0-1, 1.11.1-1), pipewire:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5dbus5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libsepol2:amd64 (3.4-1, 3.4-2), firefox-trunk:amd64 (103.0~a1~hg20220612r620615-0ubuntu0.22.10.1~umd1, 103.0~a1~hg20220615r620926-0ubuntu0.22.10.1~umd1), gir1.2-gtk-3.0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libcamel-1.2-63:amd64 (3.44.2-1, 3.44.2-2), libglib2.0-data:amd64 (2.72.1-1, 2.72.2-2), gnome-calendar:amd64 (42.1-1, 42.2-1), libqt5widgets5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libexempi8:amd64 (2.5.2-1build1, 2.6.1-2), libqt5gui5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libgstreamer-plugins-good1.0-0:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), libgnome-bluetooth-3.0-13:amd64 (42.0-5, 42.1-1), libebook-contacts-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libwoff1:amd64 (1.0.2-1build4, 1.0.2-2), libqt5multimedia5:amd64 (5.15.4-1, 5.15.4-2), libedataserverui-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libxtst6:amd64 (2:1.2.3-1build4, 2:1.2.3-1.1), gir1.2-gnomebluetooth-3.0:amd64 (42.0-5, 42.1-1), libspa-0.2-bluetooth:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gstreamer1.0-gtk3:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), ipp-usb:amd64 (0.9.21-1, 0.9.22-1), gstreamer1.0-plugins-good:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), libhtml-format-perl:amd64 (2.12-1.1, 2.12-2), libgupnp-av-1.0-3:amd64 (0.14.0-3, 0.14.1-1), gstreamer1.0-pipewire:amd64 (0.3.51-1ubuntu3, 0.3.52-1), enchant-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), pipewire-bin:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5svg5:amd64 (5.15.4-1, 5.15.4-2), libglibmm-2.4-1v5:amd64 (2.66.2-2, 2.66.4-1), tracker-extract:amd64 (3.3.0-1build1, 3.3.1-1), libgtksourceview-5-0:amd64 (5.4.1-3build1, 5.4.2-1), libqt5multimediawidgets5:amd64 (5.15.4-1, 5.15.4-2), libestr0:amd64 (0.1.10-2.1build3, 0.1.11-1), libglib2.0-0:amd64 (2.72.1-1, 2.72.2-2), libspa-0.2-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gnome-shell-extension-ubuntu-dock:amd64 (72~ubuntu5, 72~ubuntu6), libgtk-3-0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtkmm-3.0-1v5:amd64 (3.24.5-1build1, 3.24.6-1), libopenmpt0:amd64 (0.6.3-1, 0.6.4-1), gtk-update-icon-cache:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libedata-cal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libgtk-3-common:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtk-3-bin:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libtracker-sparql-3.0-0:amd64 (3.3.1-1, 3.3.1-2), libenchant-2-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), libpipewire-0.3-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), inxi:amd64 (3.3.16-1-1, 3.3.18-1-1), libsigc++-2.0-0v5:amd64 (2.10.4-2ubuntu3,
[Touch-packages] [Bug 1979113] [NEW] Kinetic sound disappeared after today updates (still trying to use pipewire-media-session)
You have been subscribed to a public bug: on my laptop sound disappeared after today updates. Sound was already disappeared on my two desktop but I didn't know which updates to attribute the problem to. Today updates are: Start-Date: 2022-06-18 10:05:42 Commandline: apt upgrade Requested-By: corrado (1000) Upgrade: gnome-text-editor:amd64 (42.1-1, 42.2-1), tracker:amd64 (3.3.1-1, 3.3.1-2), libedata-book-1.2-26:amd64 (3.44.2-1, 3.44.2-2), libkeyutils1:amd64 (1.6.1-2ubuntu3, 1.6.1-3ubuntu1), libebook-1.2-20:amd64 (3.44.2-1, 3.44.2-2), libecal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libedataserver-1.2-26:amd64 (3.44.2-1, 3.44.2-2), evolution-data-server:amd64 (3.44.2-1, 3.44.2-2), libsnmp-base:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), libqt5serialport5:amd64 (5.15.4-1, 5.15.4-2), libxrender1:amd64 (1:0.9.10-1build4, 1:0.9.10-1.1), libsnmp40:amd64 (5.9.1+dfsg-1ubuntu2.1, 5.9.1+dfsg-4ubuntu1), evolution-data-server-common:amd64 (3.44.2-1, 3.44.2-2), pipewire-media-session:amd64 (0.4.1-2ubuntu2, 0.4.1-3ubuntu1), libglib2.0-bin:amd64 (2.72.1-1, 2.72.2-2), libqt5positioning5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), libpipewire-0.3-common:amd64 (0.3.51-1ubuntu3, 0.3.52-1), pipewire-pulse:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gnome-bluetooth-3-common:amd64 (42.0-5, 42.1-1), libqt5core5a:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), qt5-gtk-platformtheme:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libgspell-1-common:amd64 (1.10.0-1, 1.11.1-1), libgtksourceview-5-common:amd64 (5.4.1-3build1, 5.4.2-1), libmalcontent-0-0:amd64 (0.10.4-1, 0.10.5-1), libqt5charts5:amd64 (5.15.4-1, 5.15.4-2), libqt5script5:amd64 (5.15.4+dfsg-1, 5.15.4+dfsg-2), libencode-locale-perl:amd64 (1.05-1.1, 1.05-2), libqt5network5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), tracker-miner-fs:amd64 (3.3.0-1build1, 3.3.1-1), libgspell-1-2:amd64 (1.10.0-1, 1.11.1-1), pipewire:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5dbus5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libsepol2:amd64 (3.4-1, 3.4-2), firefox-trunk:amd64 (103.0~a1~hg20220612r620615-0ubuntu0.22.10.1~umd1, 103.0~a1~hg20220615r620926-0ubuntu0.22.10.1~umd1), gir1.2-gtk-3.0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libcamel-1.2-63:amd64 (3.44.2-1, 3.44.2-2), libglib2.0-data:amd64 (2.72.1-1, 2.72.2-2), gnome-calendar:amd64 (42.1-1, 42.2-1), libqt5widgets5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libexempi8:amd64 (2.5.2-1build1, 2.6.1-2), libqt5gui5:amd64 (5.15.4+dfsg-2, 5.15.4+dfsg-3), libgstreamer-plugins-good1.0-0:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), libgnome-bluetooth-3.0-13:amd64 (42.0-5, 42.1-1), libebook-contacts-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libwoff1:amd64 (1.0.2-1build4, 1.0.2-2), libqt5multimedia5:amd64 (5.15.4-1, 5.15.4-2), libedataserverui-1.2-3:amd64 (3.44.2-1, 3.44.2-2), libxtst6:amd64 (2:1.2.3-1build4, 2:1.2.3-1.1), gir1.2-gnomebluetooth-3.0:amd64 (42.0-5, 42.1-1), libspa-0.2-bluetooth:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gstreamer1.0-gtk3:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), ipp-usb:amd64 (0.9.21-1, 0.9.22-1), gstreamer1.0-plugins-good:amd64 (1.20.2-1ubuntu2, 1.20.3-1ubuntu1), libhtml-format-perl:amd64 (2.12-1.1, 2.12-2), libgupnp-av-1.0-3:amd64 (0.14.0-3, 0.14.1-1), gstreamer1.0-pipewire:amd64 (0.3.51-1ubuntu3, 0.3.52-1), enchant-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), pipewire-bin:amd64 (0.3.51-1ubuntu3, 0.3.52-1), libqt5svg5:amd64 (5.15.4-1, 5.15.4-2), libglibmm-2.4-1v5:amd64 (2.66.2-2, 2.66.4-1), tracker-extract:amd64 (3.3.0-1build1, 3.3.1-1), libgtksourceview-5-0:amd64 (5.4.1-3build1, 5.4.2-1), libqt5multimediawidgets5:amd64 (5.15.4-1, 5.15.4-2), libestr0:amd64 (0.1.10-2.1build3, 0.1.11-1), libglib2.0-0:amd64 (2.72.1-1, 2.72.2-2), libspa-0.2-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), gnome-shell-extension-ubuntu-dock:amd64 (72~ubuntu5, 72~ubuntu6), libgtk-3-0:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtkmm-3.0-1v5:amd64 (3.24.5-1build1, 3.24.6-1), libopenmpt0:amd64 (0.6.3-1, 0.6.4-1), gtk-update-icon-cache:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libedata-cal-2.0-1:amd64 (3.44.2-1, 3.44.2-2), libgtk-3-common:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libgtk-3-bin:amd64 (3.24.33-2ubuntu1, 3.24.34-1ubuntu1), libtracker-sparql-3.0-0:amd64 (3.3.1-1, 3.3.1-2), libenchant-2-2:amd64 (2.3.2-1ubuntu2, 2.3.3-1), libpipewire-0.3-modules:amd64 (0.3.51-1ubuntu3, 0.3.52-1), inxi:amd64 (3.3.16-1-1, 3.3.18-1-1), libsigc++-2.0-0v5:amd64 (2.10.4-2ubuntu3, 2.10.8-1), python3-paramiko:amd64 (2.9.3-0ubuntu1, 2.10.4-1ubuntu1), libnet-smtp-ssl-perl:amd64 (1.04-1, 1.04-1.1), intel-media-va-driver:amd64 (22.4.2+dfsg1-2, 22.4.3+dfsg1-1), libxv1:amd64 (2:1.0.11-1build2, 2:1.0.11-1.1), libebackend-1.2-10:amd64 (3.44.2-1, 3.44.2-2), libpipewire-0.3-0:amd64 (0.3.51-1ubuntu3, 0.3.52-1) End-Date: 2022-06-18 10:06:01 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire 0.3.52-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.21.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult:
[Touch-packages] [Bug 1987126] Re: No audio devices are recognized
According to the attached info, the kernel does know about your audio devices: !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xa113 irq 127 1 [Camera ]: USB-Audio - USB 2.0 Camera Sonix Technology Co., Ltd. USB 2.0 Camera at usb-:00:14.0-5, high speed But I think the problem here is that PulseAudio is no used/supported in Ubuntu 22.10. The goal is to use PipeWire instead. So what exactly isn't working, and where? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1987126 Title: No audio devices are recognized Status in pulseaudio package in Ubuntu: Incomplete Bug description: No audio devices are recognized, both in and out. This worked on 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pulseaudio 1:16.1+dfsg1-1ubuntu1 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf] ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 19 11:35:58 2022 InstallationDate: Installed on 2022-07-09 (41 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to kinetic on 2022-08-19 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: Default string dmi.board.name: PRIME H370M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Nobilis dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd09/14/2018:br5.13:svnEquusComputerSystems:pnNobilis:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH370M-PLUS:rvrRev1.xx:cvnNobilis:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: Nobilis dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: Equus Computer Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987126/+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 1987665] Re: The "Settings" app is missing the 'Appearance' option
Thank you for your bug report. According to your report you use a GNOME upstream session CurrentDesktop: GNOME The Appearance option is an Ubuntu customization and such only available on Ubuntu sessions ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-settings (Ubuntu) Status: New => Invalid ** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center (Ubuntu) -- 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/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in gnome-control-center package in Ubuntu: Invalid Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987665/+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 1987985] Re: Totem black screen playing a video
Thank you for your bug report. Is there any error displayed on the command line or in the journal? Does $ gst-launch-1.0 playbin uri=file:///dir/to/video.avi has the same issue? ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987985 Title: Totem black screen playing a video Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Click on a video file. totem opens with a black screen. problem with webm, avi, mov totem: Installed: 43~beta-1ubuntu1 I open the bug against totem but the bug seems open against gstreamer1.0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 17:57:01 2022 InstallationDate: Installed on 2022-08-11 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987985/+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 1988023] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612334/+files/ProcModules.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612335/+files/SystemdDelta.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612336/+files/UdevDb.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612337/+files/acpidump.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612333/+files/ProcInterrupts.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612332/+files/ProcCpuinfoMinimal.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612331/+files/ProcCpuinfo.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612330/+files/Lsusb-v.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612328/+files/Lsusb.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612327/+files/Lspci-vt.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612325/+files/Dependencies.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612329/+files/Lsusb-t.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612326/+files/Lspci.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". - Please help check why need type twice "CapsLock" for switching - uppercase/lowercase and how to fix it. + Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-29 (0 days ago) + InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) + MachineType: Lenovo ThinkSystem SR630 V2 + Package: systemd 249.11-0ubuntu3.4 + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro + ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 + SystemdFailedUnits: + Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). + Unit \xe2\x97\x8f.service could not be found. + Tags: jammy uec-images + Uname: Linux 5.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 04/21/2022 + dmi.bios.release: 1.30 + dmi.bios.vendor: Lenovo + dmi.bios.version: AFE118I-1.30 + dmi.board.asset.tag: none + dmi.board.name: 7Z70CTO1WW + dmi.board.vendor: Lenovo + dmi.board.version: 05 + dmi.chassis.asset.tag: none + dmi.chassis.type: 23 + dmi.chassis.vendor: Lenovo + dmi.chassis.version: none + dmi.ec.firmware.release: 1.80 + dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: + dmi.product.family: ThinkSystem + dmi.product.name: ThinkSystem SR630 V2 + dmi.product.sku: 7Z70CTO1WW + dmi.product.version: 05 + dmi.sys.vendor: Lenovo ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1988023/+attachment/5612324/+files/CurrentDmesg.txt -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=
[Touch-packages] [Bug 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+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 1988023] [NEW] Could not switch uppercase/lowercase by using keyboard of laptop
You have been subscribed to a public bug: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- Could not switch uppercase/lowercase by using keyboard of laptop https://bugs.launchpad.net/bugs/1988023 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- 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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] Status in NVIDIA / egl-wayland: New Status in GTK+: Fix Released Status in egl-wayland package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1965563/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
One thing we changed in 22.10 is that we enabled the wpe backend, which is the better maintained rendered and what upstream is testing. The non- wpe codepath was even hitting errors on arm64 on recent versions as described in https://bugs.webkit.org/show_bug.cgi?id=237636 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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
