[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes
Hello Nicolas, or anyone else affected,
Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Tags added: verification-needed-hirsute
--
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/1934147
Title:
systemd leaks abandoned session scopes
Status in snapd:
New
Status in systemd:
New
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Groovy:
Won't Fix
Status in systemd source package in Hirsute:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Bug description:
[impact]
systemd may leak sessions, leaving empty cgroups around as well as
abandoned session scopes.
[test case]
on a system where the user has a ssh key that allows noninteractive
login to localhost, and also has noninteractive sudo, run:
$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
reload; done
check the sessions to see there have been leaked sessions:
$ loginctl list-sessions
SESSION UID USER SEAT TTY
1 1000 ubuntu ttyS0
350 1000 ubuntu
351 1000 ubuntu
360 1000 ubuntu
...
to verify the sessions were leaked, clear them out with:
$ echo '' | sudo tee
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events
that should result in all the leaked sessions being cleaned up.
[regression potential]
issues during systemd pid1 reexec/reload, or issues while cleaning up
sessions, including leaking sessions/cgroups
[scope]
this is needed for all releases
upstream bug linked above, and upstream PR:
https://github.com/systemd/systemd/pull/20199
[original description]
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
$ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
daemon-reload & ssh localhost sleep 1 & done
Wait > 1 second
$ jobs -p | xargs --verbose --no-run-if-empty kill -KILL
To clean out STOPPED jobs and
$ systemctl status --all 2> /dev/null | grep --before-context 3
abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
Hello Denys, or anyone else affected, Accepted systemd into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Hirsute) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Confirmed Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string
[Touch-packages] [Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
Hello Robert, or anyone else affected, Accepted systemd into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed-hirsute -- 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/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: [impact] suspend-then-hibernate not possible using systemctl [test case] configure a system to allow suspend-then-hibernate but not hybrid- sleep, e.g. by editing /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it: $ sudo systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported [regression potential] failure to correctly enter hybrid-sleep and/or suspend-then-hibernate, or other issues around suspending/hibernating [scope] This is needed in b and later. The bug appears to have been introduced by a typo in the original suspend-then-hibernate commit c58493c00af, and then fixed with larger changes in commit c8cd8ca3986. this is also present in b, by a backport of the functionality [other info] note that if hybrid-sleep is allowed/possible, then calling 'systemctl suspend-then-hibernate' does actually perform suspend-then-hibernate; this typo only controls what suspend action logind checks for support of, not what suspend action it actually performs. [original description] ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. 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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
Hello bugproxy, or anyone else affected, Accepted systemd into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: In Progress Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in netplan.io source package in Focal: New Status in systemd source package in Focal: In Progress Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: Fix Committed Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: In Progress Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
Hello Yao, or anyone else affected, Accepted systemd into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Committed Bug description: We are planning to do SRU to systemd in focal, to avoid unwanted screen rotations on some Dell laptop models. [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A3E or 0E0E, install this package and kernel 5.13, or kernel with this patch backported: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23 * Rotate the laptop and the display should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * This fix would only take effect with kernel 5.13 or the above patch backported. [scope] this is needed for all releases this is being fixed upstream by https://github.com/systemd/systemd/pull/20314 [Other info] * The patch mentioned above is going to have a separated SRU for linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1939255 Title: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once Status in systemd package in Ubuntu: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: In Progress Bug description: [impact] on a system where systemd-resolved is running, if dhclient is used on more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter- hooks.d/resolved' script multiple times, which then restarts systemd- resolved multiple times, triggering the unit's start-limit throttle which results in the unit entering failed state [test case] on a system with more than 5 available interfaces to run dhclient on (where all the interfaces will get a dhcp response), run dhclient with the interfaces: $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15 check if systemd-resolved failed: $ journalctl -b -1 -u systemd-resolved ... Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start request repeated too quickly. Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with result 'start-limit-hit'. Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name Resolution. [regression potential] failure to start/stop/restart systemd-resolved, or problems adding dhclient-provided DNS nameservers to systemd-resolved [scope] this is needed only for b/f the dhclient 'hook' script is provided by the systemd package in focal and earlier, and needs fixing in those releases in h and later, the 'hook' script is included in the isc-dhcp-client package and notifies systemd-resolved in a more direct way without requiring restarting, and so doesn't trigger the restart limiting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+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 1934147] Re: systemd leaks abandoned session scopes
Hello Nicolas, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1934147
Title:
systemd leaks abandoned session scopes
Status in snapd:
New
Status in systemd:
New
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Groovy:
Won't Fix
Status in systemd source package in Hirsute:
In Progress
Status in systemd source package in Impish:
Fix Committed
Bug description:
[impact]
systemd may leak sessions, leaving empty cgroups around as well as
abandoned session scopes.
[test case]
on a system where the user has a ssh key that allows noninteractive
login to localhost, and also has noninteractive sudo, run:
$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
reload; done
check the sessions to see there have been leaked sessions:
$ loginctl list-sessions
SESSION UID USER SEAT TTY
1 1000 ubuntu ttyS0
350 1000 ubuntu
351 1000 ubuntu
360 1000 ubuntu
...
to verify the sessions were leaked, clear them out with:
$ echo '' | sudo tee
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events
that should result in all the leaked sessions being cleaned up.
[regression potential]
issues during systemd pid1 reexec/reload, or issues while cleaning up
sessions, including leaking sessions/cgroups
[scope]
this is needed for all releases
upstream bug linked above, and upstream PR:
https://github.com/systemd/systemd/pull/20199
[original description]
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
$ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
daemon-reload & ssh localhost sleep 1 & done
Wait > 1 second
$ jobs -p | xargs --verbose --no-run-if-empty kill -KILL
To clean out STOPPED jobs and
$ systemctl status --all 2> /dev/null | grep --before-context 3
abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Hello Mason, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Fix Committed
** Tags removed: verification-done
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
with systemd-resolved disabled, dhclient doesn't correctly notify
resolvconf about dns server(s)
[test case]
install resolvconf and ifupdown and disable systemd-resolved and
systemd-networkd, use ifupdown to get a dhcp address where the lease
includes a dns nameserver, verify resolvconf is using that dhcp-
provided nameserver
[regression potential]
failure to correctly notify systemd-resolved about new dhclient-
provided nameserver(s)
[scope]
this is needed for f and earlier
in g and later the hook script is moved to the isc-dhcp package, and
edited to correctly check is-enabled systemd-resolved instead of only
checking for the existence of the binary
[original description]
The functionality exists to allow users to revert to the traditional ifupdown
package for network configuration. Alongside this, systemd's often-buggy
resolver can be disabled. However, there's a logic error in the systemd-
supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system
from populating /etc/resolv.conf properly when systemd-resolved is disabled.
The issue is here:
if [ -x /lib/systemd/systemd-resolved ] ; then
Instead of checking to see if the systemd-resolved service is enabled or
active, which would be the correct behaviour, this checks for the existence of
a binary, assuming that if it exists it's supposed to be used.
I've not tested this in the absence of resolvconf, but if systemd-resolved
isn't enabled, it's difficult to imagine this code wanting to run. I've tested
this with resolvconf and ifupdown driving dhclient, and it corrects the
behaviour that was broken with the introduction of systemd-resolved.
I'm attaching a patch, and am also including it here for easy access:
*** resolved.broken 2019-11-19 15:01:28.785588838 +
--- resolved2019-11-19 15:08:06.519430073 +
***
*** 14,20
# (D) = master script downs interface
# (-) = master script does nothing with this
! if [ -x /lib/systemd/systemd-resolved ] ; then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in
--- 14,21
# (D) = master script downs interface
# (-) = master script does nothing with this
! systemctl is-active systemd-resolved > /dev/null 2>&1
! if [ $? -eq 0 ]; then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
Hello Robert, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.52 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: In Progress Status in systemd source package in Impish: Fix Committed Bug description: [impact] suspend-then-hibernate not possible using systemctl [test case] configure a system to allow suspend-then-hibernate but not hybrid- sleep, e.g. by editing /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it: $ sudo systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported [regression potential] failure to correctly enter hybrid-sleep and/or suspend-then-hibernate, or other issues around suspending/hibernating [scope] This is needed in b and later. The bug appears to have been introduced by a typo in the original suspend-then-hibernate commit c58493c00af, and then fixed with larger changes in commit c8cd8ca3986. this is also present in b, by a backport of the functionality [other info] note that if hybrid-sleep is allowed/possible, then calling 'systemctl suspend-then-hibernate' does actually perform suspend-then-hibernate; this typo only controls what suspend action logind checks for support of, not what suspend action it actually performs. [original description] ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. 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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1782984] Autopkgtest regression report (libx11/2:1.6.4-3ubuntu0.5)
All autopkgtests for the newly accepted libx11 (2:1.6.4-3ubuntu0.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: awesome/4.2-4 (amd64, i386, arm64, s390x, ppc64el) openssh/1:7.6p1-4ubuntu0.5 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#libx11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit
[Touch-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1939986/+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 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2021 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.0.4 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1939986/+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 1369651] Re: "libmtp error: Could not send object info" when copying content to root MTP folder
This happens for me on 20.04 LTS when the file being copied has a colon (:) in its name. The error doesn't pop up until the very end of the file copy process, and in the end, the file is not copied to the destination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1369651 Title: "libmtp error: Could not send object info" when copying content to root MTP folder Status in mtp package in Ubuntu: Confirmed Bug description: ENVIRONMENT: Ubuntu device: ubuntu-rtm/14.09-proposed build 40 Desktop: Ubuntu 14.10 SUMMARY: "libmtp error: Could not send object info" when copying content to root MTP folder STEPS: 1) Connect Ubuntu MTP device over USB 2) Attempt to copy some content to the root of the MTP folder EXPECTED RESULT: The copy operation should succeed. (This is the Android behaviour). ACTUAL RESULT: An error message is presented on desktop: "libmtp error: Could not send object info" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1369651/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Changed in: wpa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Committed
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1931045] Re: FFMPEG silently falls back to software encoding on AMD GPU
** Changed in: ffmpeg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1931045 Title: FFMPEG silently falls back to software encoding on AMD GPU Status in Mesa: New Status in ffmpeg package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Bug description: FFMPEG hardware encoding fails on AMD hardware: Passing -hwaccel vaapi flag as per command below: Command used was: ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -ss 15 -i input.mp4 -t 25 -c:v h264_vaapi -global_quality 15 -c:a copy -map 0 output.mkv Will silently fail and transcoding will be done on CPU silently when using on AMD GPU. The only sign that something is wrong is this WARNING: [hevc_vaapi @ 0x55f2ca003e80] Driver does not support some wanted packed headers (wanted 0xd, found 0x1). and for h264: Press [q] to stop, [?] for help [h264_vaapi @ 0x55762dd4de80] Driver does not support some wanted packed headers (wanted 0xd, found 0x1). During transcode operation CPU usage is high, and GPU usage is zero. FFPROBE on OUTPUT.MKV reports that encoder used was software. My syste: Thinkpad T14s (AMD Ryzen7) Ubuntu Mate 21.04 (5.11) bash $ sudo inxi -x -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: Lenovo driver: amdgpu v: kernel bus ID: 07:00.0 Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 2-2:2 Display: server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.11.0-18-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 direct render: Yes To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1931045/+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
Re: [Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
Sigh yes it does look like you found amd fixed the same bug. Oh well at least I learnt some things yesterday. -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket...
[Touch-packages] [Bug 1942139] Re: Debug symbols not available for 237-3ubuntu10.51
The correct Launchpad project for this is ddeb-retriever - reassigning there. ** Package changed: systemd (Ubuntu) => ddeb-retriever ** Changed in: ddeb-retriever Importance: Undecided => High ** Changed in: ddeb-retriever Status: Invalid => In Progress ** Changed in: ddeb-retriever Assignee: (unassigned) => Colin Watson (cjwatson) -- 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/1942139 Title: Debug symbols not available for 237-3ubuntu10.51 Status in ddeb-retriever: In Progress Bug description: I am trying to install the debug symbols for systemd 237-3ubuntu10.51 from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do not seem to be available. The latest version I see is systemd-dbgsym 237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic- updates/main. I do see the ddeb package file for version 10.51 here http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to be included in bionic or bionic-updates package index files. Is there a timeline for when this will be released? Note that I am having the same problem with libsystemd0 with the same versions. Please let me know if I should open a separate bug for that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ddeb-retriever/+bug/1942139/+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 1940528] Re: curl 7.68 does not init OpenSSL correctly
I don't see the patch in debian/patches/series. Am I missing something? ** Changed in: curl (Ubuntu Focal) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1940528 Title: curl 7.68 does not init OpenSSL correctly Status in curl package in Ubuntu: Fix Released Status in curl source package in Bionic: New Status in curl source package in Focal: Incomplete Bug description: [Impact] * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL global state prior to executing any OpenSSL APIs. This may lead to duplicate engine initiation, which upon engine unload may cause use- after-free or double-free of any methods that engine installs. This has been fixed in curl 7.74 by correctly calling OpenSSL init api prior to any other calls to OpenSSL apis. [Test Plan] * This should be reproducible with any engines that allocate & register methods, and free them upon engine unload. Then use curl with openssl backend to test for corrupted stack. * I.e. on arm64, compile and configure pka engine from https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f (i.e. without the double-free protections proposed in https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there is no need for the engine to actually work or have access to anything, as the issue is reproducible when engine is enabled but cannot be effectively used. * curl any https website ... PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 3520 0 --:--:-- --:--:-- --:--:-- 3520 (exit status 0) is good output from fixed curl. Whereas: PKA_ENGINE: PKA instance is invalid PKA_ENGINE: failed to retrieve valid instance 100 338 100 3380 0 1169 0 --:--:-- --:--:-- --:--:-- 1169 Segmentation fault (core dumped) (exit status non-zero) is bad output from currently broken curl. [Where problems could occur] * Correctly calling OpenSSL init function prior to any other OpenSSL apis changes the behaviour of the library slightly - specifically openssl configuration file and engines are initialised and loaded earlier, meaning that site-local customizations are applied correctly whenever using curl cli utility or libcurl4 (the openssl version of curl). This will make engine support working correctly across the board. However, if one has missconfigured openssl conf and missconfigured engines which are now actually attempted to be used one may experience unexpected behaviour changes (since potentially existing configuration was not actually taking effect). [Other Info] * References: https://github.com/curl/curl/commit/1835cb916e0d40eb8bc1165d5627a0b64f911bac https://github.com/openssl/openssl/issues/13548 https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Hello Stephen, or anyone else affected, Accepted libx11 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libx11 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur
[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Hello Stephen, or anyone else affected, Accepted libx11 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libx11/2:1.6.9-2ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libx11 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: In Progress Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems
[Touch-packages] [Bug 1942139] Re: Debug symbols not available for 237-3ubuntu10.51
the infrastructure people kicked the cronjob/scripting so hopefully ddebs should get updated soon, but if not, I'd suggest asking in irc in #ubuntu-devel on libera.chat, or you could open a question on launchpad here: https://answers.launchpad.net/launchpad/+addquestion technically ddebs.u.c isn't handled by the launchpad admins, but I think there's enough cross-over that the right person could pick it up. I'm not sure where else (besides irc) is the right place to report problems with ddebs.u.c. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1942139 Title: Debug symbols not available for 237-3ubuntu10.51 Status in systemd package in Ubuntu: Invalid Bug description: I am trying to install the debug symbols for systemd 237-3ubuntu10.51 from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do not seem to be available. The latest version I see is systemd-dbgsym 237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic- updates/main. I do see the ddeb package file for version 10.51 here http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to be included in bionic or bionic-updates package index files. Is there a timeline for when this will be released? Note that I am having the same problem with libsystemd0 with the same versions. Please let me know if I should open a separate bug for that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942139/+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 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
Just a suggestion, before opening an upstream bug, y'all might want to test with the latest upstream code, as I think this is fixed already? You can use this ppa to test with the latest upstream (daily) code if it makes things easier for you: https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd If I've misunderstood the bug and this isn't fixed upstream yet, I apologize and please ignore the noise :) -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero.
[Touch-packages] [Bug 1942139] Re: Debug symbols not available for 237-3ubuntu10.51
I see, thanks for the update and for following up. Let me know if there is anything needed on my end. -- 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/1942139 Title: Debug symbols not available for 237-3ubuntu10.51 Status in systemd package in Ubuntu: New Bug description: I am trying to install the debug symbols for systemd 237-3ubuntu10.51 from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do not seem to be available. The latest version I see is systemd-dbgsym 237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic- updates/main. I do see the ddeb package file for version 10.51 here http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to be included in bionic or bionic-updates package index files. Is there a timeline for when this will be released? Note that I am having the same problem with libsystemd0 with the same versions. Please let me know if I should open a separate bug for that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942139/+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 1942139] Re: Debug symbols not available for 237-3ubuntu10.51
This isn't a bug in systemd, this looks like a problem with the tooling that updates the ddebs archive. I'll leave this bug open and ping the infrastructure people, as I'm not sure what the right place to open a bug for this kind of thing is. -- 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/1942139 Title: Debug symbols not available for 237-3ubuntu10.51 Status in systemd package in Ubuntu: New Bug description: I am trying to install the debug symbols for systemd 237-3ubuntu10.51 from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do not seem to be available. The latest version I see is systemd-dbgsym 237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic- updates/main. I do see the ddeb package file for version 10.51 here http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to be included in bionic or bionic-updates package index files. Is there a timeline for when this will be released? Note that I am having the same problem with libsystemd0 with the same versions. Please let me know if I should open a separate bug for that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942139/+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 1685878] Re: Gedit bottom scroll bar goes on top of final line
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #809 https://gitlab.gnome.org/GNOME/gtk/issues/809 ** Changed in: gtk Importance: Medium => Unknown ** Changed in: gtk Status: Expired => Unknown ** Changed in: gtk Remote watch: GNOME Bug Tracker #781669 => gitlab.gnome.org/GNOME/gtk/issues #809 -- 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/1685878 Title: Gedit bottom scroll bar goes on top of final line Status in GTK+: Unknown Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1685878/+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 387626] Re: Wireless notification icon show full/no signal instead of the actual signal strength
Upstream bug was closed as "RESOLVED FIXED" on 2016-02-23 so fixed in all currently supported releases of Ubuntu. ** Changed in: hundredpapercuts Status: Triaged => Fix Released ** Changed in: network-manager-applet (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/387626 Title: Wireless notification icon show full/no signal instead of the actual signal strength Status in One Hundred Papercuts: Fix Released Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Invalid Status in network-manager-applet package in Ubuntu: Fix Released Bug description: The wireless notification[notify-osd] on wireless connection, always shows signal strength as full, while there are icons for all signal strengths > /usr/share/icons/Human/scalable/status/notification-network-wireless-* This confuses users , who are used to the white as being no signal in the panel icon. This confusion could be avoided if the signal strengths are shown appropriately, this needs to be corrected. -OLD DESCRIPTION-- The new wireless notification connection message always uses the icon for a wireless signal strength of no signal. It would be nice if it showed the actual signal strength instead. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387626/+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 1597840] Re: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1u
** Tags removed: disco eoan xenial ** Tags added: focal ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1597840 Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 Status in One Hundred Papercuts: Confirmed Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg9 package in Ubuntu: Confirmed Bug description: Just got back from restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 29 12:14:30 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libjpeg-turbo8 1.4.2-0ubuntu3 multiarch-support 2.23-0ubuntu3 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 DuplicateSignature: package:libjpeg-turbo8-dev:1.4.2-0ubuntu3 Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 InstallationDate: Installed on 2016-06-13 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1597840/+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 1597840] Re: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1u
Sorry for the 'noise'. Updating currently affected releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1597840 Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 Status in One Hundred Papercuts: Confirmed Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg9 package in Ubuntu: Confirmed Bug description: Just got back from restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 29 12:14:30 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libjpeg-turbo8 1.4.2-0ubuntu3 multiarch-support 2.23-0ubuntu3 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 DuplicateSignature: package:libjpeg-turbo8-dev:1.4.2-0ubuntu3 Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 InstallationDate: Installed on 2016-06-13 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1597840/+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 1942208] Re: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers"
If I installed nvidia driver during the installation by selecting "Third-Party packages". It will use pre-signed driver instead. Please consider to use `ubuntu-drivers install` which will handle the corresponding actions. (e.g. prime-select, enabling RTD3) ** Tags added: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1942208 Title: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers" Status in OEM Priority Project: Confirmed Status in software-properties package in Ubuntu: New Bug description: [steps to reproduce] 1. Install Stock ubuntu 20.04.3 on XPS 15 9510 2. Installing without using "Third-party packages" 3. After installation completed, launch "Software & Updates" -> "Additional Drivers" -> "Using NVIDIA driver 470" 4. dpkg -l | grep nvidia [Expected result] It should use pre-signed nvidia driver instead of dkms e.g. linux-modules-nvidia-470-5.11.0-27-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.11.0-27-generic linux-signatures-nvidia-5.11.0-27-generic [Actual result] ii nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package --- $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy software-properties-* software-properties-gtk: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages software-properties-kde: Installed: (none) Candidate: (none) Version table: software-properties-qt: Installed: (none) Candidate: 0.98.9.5 Version table: 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe i386 Packages 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/universe i386 Packages software-properties-common: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942208/+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 1942208] [NEW] The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers"
Public bug reported: [steps to reproduce] 1. Install Stock ubuntu 20.04.3 on XPS 15 9510 2. Installing without using "Third-party packages" 3. After installation completed, launch "Software & Updates" -> "Additional Drivers" -> "Using NVIDIA driver 470" 4. dpkg -l | grep nvidia [Expected result] It should use pre-signed nvidia driver instead of dkms e.g. linux-modules-nvidia-470-5.11.0-27-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.11.0-27-generic linux-signatures-nvidia-5.11.0-27-generic [Actual result] ii nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package --- $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy software-properties-* software-properties-gtk: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages software-properties-kde: Installed: (none) Candidate: (none) Version table: software-properties-qt: Installed: (none) Candidate: 0.98.9.5 Version table: 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe i386 Packages 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/universe i386 Packages software-properties-common: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages ** Affects: oem-priority Importance: Undecided Assignee: jeremyszu (os369510) Status: New ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1942208 Title: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers" Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: [steps to reproduce] 1. Install Stock ubuntu 20.04.3 on XPS 15 9510 2. Installing without using "Third-party packages" 3. After installation completed, launch "Software & Updates" -> "Additional Drivers" -> "Using NVIDIA driver 470" 4. dpkg -l | grep nvidia [Expected result] It should use pre-signed nvidia driver instead of dkms e.g. linux-modules-nvidia-470-5.11.0-27-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.11.0-27-generic linux-signatures-nvidia-5.11.0-27-generic [Actual result] ii nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package --- $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy software-properties-* software-properties-gtk: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages software-properties-kde: Installed: (none) Candidate: (none) Version table: software-properties-qt: Installed: (none) Candidate: 0.98.9.5 Version
[Touch-packages] [Bug 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Removing EOL release tags ** Tags removed: groovy vivid wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Status in One Hundred Papercuts: Confirmed Status in Light Display Manager: Confirmed Status in systemd: New Status in lightdm package in Ubuntu: Confirmed Bug description: auth.log complaints: Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm. Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "oem" Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for user oem by (uid=0) As per lp:1309535 #18 comment such 'warnings' should be silenced (as they scared unawared users about the both needs of pam's gnome/kde) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0 Uname: Linux 3.18.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Dec 19 10:47:07 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+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 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
So it turns out that if you have security.nesting=true set on the container, then the systemd in proposed manages to set up a unified hierarchy and the test fails. This is the difference between the production test runs and mine. I filed a bug upstream https://github.com/systemd/systemd/issues/20593 I'm not sure I want to argue for a hint for this, because the systemd tests are failing for other reasons when triggered by other packages. It's probably better to upload a systemd that skips the failing test case. ** Bug watch added: github.com/systemd/systemd/issues #20593 https://github.com/systemd/systemd/issues/20593 -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last
[Touch-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d
https://portal.admin.canonical.com/C132790 (internal ticket) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1756547 Title: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d Status in Launchpad itself: In Progress Status in Ubuntu Translations: Triaged Status in gettext package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: Some strings of GNOME Shell are untranslated in the Czech translation on Ubuntu 18.04 although they are translated upstream and when I try to manually translate them on launchpad, I get this error: "number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match". The bad strings are: %d minute ago %d minutes ago %d hour ago %d hours ago %d week ago %d weeks ago %d month ago %d months ago %d year ago %d years ago They seem to be correct, but they are not accepted for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1505670] Re: "uncaptured python exception"
Hi Rolf,
I'm trying to reproduce the issue on impish, but I only get this:
root@ondevelopment:~# /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('fd42:ce31:bcba:21af:216:3eff:fe27:28d6', 8000, 0, 0): 9223372036854775807
(:[Errno 111] Connection refused
[/usr/lib/python3.9/asyncore.py|read|83]
[/usr/lib/python3.9/asyncore.py|handle_read_event|417]
[/usr/lib/python3.9/asyncore.py|handle_connect_event|425])
when removing squid-deb-proxy. Otherwise, I get this:
root@ondevelopment:~# /usr/share/squid-deb-proxy-client/apt-avahi-discover
http://127.0.0.1:8000/
root@ondevelopment:~# /usr/share/squid-deb-proxy-client/apt-avahi-discover
http://[fd42:ce31:bcba:21af:216:3eff:fe27:28d6]:8000/
Could you be so kind to share steps to reproduce or some configuration needed?
I would appreciate it... thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1505670
Title:
"uncaptured python exception"
Status in python2.7 package in Ubuntu:
New
Status in squid-deb-proxy package in Ubuntu:
Confirmed
Status in python2.7 source package in Bionic:
New
Status in squid-deb-proxy source package in Bionic:
New
Status in python2.7 source package in Focal:
New
Status in squid-deb-proxy source package in Focal:
New
Bug description:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection
refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
error: uncaptured python exception, closing channel
('172.24.74.129', 3142): 2147483647 (:[Errno 111]
Connection refused [/usr/lib/python2.7/asyncore.py|read|83]
[/usr/lib/python2.7/asyncore.py|handle_read_event|446]
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
http://172.24.74.145:3142/
The last line still returns the proper proxy URI so as far as I can
tell things are still working. The IP 10.1.2.3 is for an n2n VPN.
This is on trusty with version 0.8.6ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+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 1374825] Re: VDPAU does not work in libav on Utopic
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mplayer (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mplayer2 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1374825 Title: VDPAU does not work in libav on Utopic Status in libav package in Ubuntu: Invalid Status in mplayer package in Ubuntu: Won't Fix Status in mplayer2 package in Ubuntu: Won't Fix Status in mpv package in Ubuntu: Invalid Status in vlc package in Ubuntu: Invalid Bug description: After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support has stopped working in all applications that use libav. In mplayer2, it prints "Cannot find codec 'h264_vdpau' in libavcodec..." and in VLC I get "[7f909958] vdpau_avcodec generic error: decoder profile not supported: 6". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1374825] Re: VDPAU does not work in libav on Utopic
Ubuntu 14.04 (trusty) reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1374825 Title: VDPAU does not work in libav on Utopic Status in libav package in Ubuntu: Invalid Status in mplayer package in Ubuntu: Won't Fix Status in mplayer2 package in Ubuntu: Won't Fix Status in mpv package in Ubuntu: Invalid Status in vlc package in Ubuntu: Invalid Bug description: After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support has stopped working in all applications that use libav. In mplayer2, it prints "Cannot find codec 'h264_vdpau' in libavcodec..." and in VLC I get "[7f909958] vdpau_avcodec generic error: decoder profile not supported: 6". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d
Sorry for taking so long to get round to this; it had entirely fallen off my list. We haven't upgraded gettext from xenial's version yet, but I've started preparing a backport in https://launchpad.net/~cjwatson/+archive/ubuntu/launchpad/+packages. ** Changed in: launchpad Importance: Undecided => High ** Changed in: launchpad Status: Confirmed => In Progress ** Changed in: launchpad Assignee: (unassigned) => Colin Watson (cjwatson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1756547 Title: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d Status in Launchpad itself: In Progress Status in Ubuntu Translations: Triaged Status in gettext package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: Some strings of GNOME Shell are untranslated in the Czech translation on Ubuntu 18.04 although they are translated upstream and when I try to manually translate them on launchpad, I get this error: "number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match". The bad strings are: %d minute ago %d minutes ago %d hour ago %d hours ago %d week ago %d weeks ago %d month ago %d months ago %d year ago %d years ago They seem to be correct, but they are not accepted for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1756547/+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 1374825] Re: VDPAU does not work in libav on Utopic
** Changed in: vlc (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1374825 Title: VDPAU does not work in libav on Utopic Status in libav package in Ubuntu: Invalid Status in mplayer package in Ubuntu: Confirmed Status in mplayer2 package in Ubuntu: Confirmed Status in mpv package in Ubuntu: Invalid Status in vlc package in Ubuntu: Invalid Bug description: After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support has stopped working in all applications that use libav. In mplayer2, it prints "Cannot find codec 'h264_vdpau' in libavcodec..." and in VLC I get "[7f909958] vdpau_avcodec generic error: decoder profile not supported: 6". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1942176] [NEW] While printing the printer is printing an error message on the sheet cups_handleerror
Public bug reported:
When using the printer it prints this on the sheet:
___
userdict dup(\004)cvn{}put (\004\004)cvn{}put
/cups_handleerror{
2B$error /newerror false put
(:PostScript error in") print cups_query_keywords print (": ) print
$error /errorname get 128 string cvs print
(;offending command:) print $error /command get 128 string cvs print(
) print flush
} bind def
errordict /timeout {} put
/cups_query_query_keyword(?Unknown) def
_
THIS IS THE TERMINAL OUTPUT
overlord@OverLord:~$ lsmod|grep usb
usbhid 57344 0
hid 135168 2 usbhid,hid_generic
btusb 61440 0
btrtl 24576 1 btusb
btbcm 16384 1 btusb
btintel28672 1 btusb
bluetooth 638976 15 btrtl,btintel,btbcm,bnep,btusb,rfcomm
overlord@OverLord:~$ tail -f /var/log/syslog
Aug 31 12:43:40 OverLord kernel: [71467.827350] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:43:40 OverLord systemd[1]: Started Configure Plugged-In Printer.
Aug 31 12:43:40 OverLord udev-configure-printer: add usb-001-006
Aug 31 12:43:41 OverLord udev-configure-printer: device devpath is
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1
Aug 31 12:43:41 OverLord udev-configure-printer: MFG:EPSON MDL:L220 Series
SERN:- serial:5647584B3134343800
Aug 31 12:43:41 OverLord kernel: [71468.715833] usb 1-1.1: USB disconnect,
device number 6
Aug 31 12:43:41 OverLord kernel: [71468.716232] usblp1: removed
Aug 31 12:43:41 OverLord udev-configure-printer: remove
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1
Aug 31 12:43:48 OverLord udev-configure-printer: no corresponding CUPS device
found
Aug 31 12:43:48 OverLord systemd[1]: configure-printer@usb-001-006.service:
Succeeded.
Aug 31 12:44:33 OverLord kernel: [71520.685232] usb 1-1.1: new full-speed USB
device number 7 using ehci-pci
Aug 31 12:44:34 OverLord kernel: [71520.957538] usb 1-1.1: New USB device
found, idVendor=04b8, idProduct=08d1, bcdDevice= 1.00
Aug 31 12:44:34 OverLord kernel: [71520.957549] usb 1-1.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Aug 31 12:44:34 OverLord kernel: [71520.957553] usb 1-1.1: Product: EPSON L220
Series
Aug 31 12:44:34 OverLord kernel: [71520.957556] usb 1-1.1: Manufacturer: EPSON
Aug 31 12:44:34 OverLord kernel: [71520.957559] usb 1-1.1: SerialNumber:
5647584B3134343800
Aug 31 12:44:34 OverLord kernel: [71521.306906] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:44:34 OverLord systemd[1]: Started Configure Plugged-In Printer.
Aug 31 12:44:34 OverLord udev-configure-printer: add usb-001-007
Aug 31 12:44:34 OverLord udev-configure-printer: device devpath is
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1
Aug 31 12:44:34 OverLord udev-configure-printer: MFG:EPSON MDL:L220 Series
SERN:- serial:5647584B3134343800
Aug 31 12:44:39 OverLord kernel: [71526.576813] usblp1: removed
Aug 31 12:44:40 OverLord kernel: [71527.090914] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:44:41 OverLord udev-configure-printer: URI contains USB serial number
Aug 31 12:44:41 OverLord udev-configure-printer: URI match:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1
Aug 31 12:44:41 OverLord udev-configure-printer: URI of detected printer:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1, normalized:
epson l220 series serial 5647584b3134343800 interface 1
Aug 31 12:44:41 OverLord udev-configure-printer: URI of print queue:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1, normalized:
epson l220 series serial 5647584b3134343800 interface 1
Aug 31 12:44:41 OverLord udev-configure-printer: Queue
ipp://localhost/printers/L220-Series has matching device URI
Aug 31 12:44:41 OverLord udev-configure-printer: Re-enabled printer
ipp://localhost/printers/L220-Series
Aug 31 12:44:41 OverLord systemd[1]: configure-printer@usb-001-007.service:
Succeeded.
Aug 31 12:44:46 OverLord telegram-desktop_telegram-desktop.desktop[53993]:
OpenType support missing for "DAOpenSansSemibold", script 12
^C
overlord@OverLord:~$ lsusb
Bus 002 Device 040: ID 04f2:b249 Chicony Electronics Co., Ltd
Bus 002 Device 044: ID 1a2c:4c5e China Resource Semico Co., Ltd
Bus 002 Device 043: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical
Mouse
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR
Bus 001 Device 007: ID 04b8:08d1 Seiko Epson Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002
[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1940504] Re: Support Alder Lake P graphics
SRU: https://lists.ubuntu.com/archives/kernel-
team/2021-August/123678.html (linux-firmware:focal)
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Description changed:
+ [SRU Justification:linux-firmware]
+
+ [Impact]
+
+ It shows the firmware is missing, and runtime power management has been
+ disabled:
+
+ i915 :00:02.0: [drm] Failed to load DMC firmware
+ i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
+
+ [Fix]
+
+ Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
+
+ [Test Case]
+
+ Verified on Intel ADL-M/ADL-P RVPs.
+
+ [Where problems could occur]
+
+ It's a new firmware for new GPU, not possible to introduce regressions.
+
+ [Other Info]
+
+ Impish has this already. And while ADL-P/M support begins since v5.14,
+ only focal (for oem-5.14) is being nominated.
+
+ =
+
+ [SRU Justification:mesa,libdrm]
+
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
New
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1942161] Re: Hubstaff keyboard shortcuts don't work
Thanks for the bug report. Unfortunately Hubstaff doesn't seem to be part of the Ubuntu distro so we can't handle its bugs here. But you can report bugs at https://support.hubstaff.com/contact/ That is unless you find the same bug with other programs in which case we should discuss it here. ** Summary changed: - Keyboard shortcuts don't work + Hubstaff keyboard shortcuts don't work ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942161 Title: Hubstaff keyboard shortcuts don't work Status in Ubuntu: Incomplete Bug description: I used Hubstaff for time tracking and it has a keyboard shortcut as `Ctrl+Shift+Alt+T` to turn on/off the timer. I don't know why it doesn't work or what programs does it affect the shortcut as it works occasionally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 31 10:33:28 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3285] InstallationDate: Installed on 2021-08-21 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=1d7fea11-a01e-4f83-9e25-3a0e8fab7620 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M GRENADE (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd09/20/2017:br5.12:svnMSI:pnMS-7A39:pvr2.0:rvnMSI:rnA320MGRENADE(MS-7A39):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1942161/+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
