[Touch-packages] [Bug 1971932] [NEW] error in rsync protocol data stream
Public bug reported: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: New Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0
[Touch-packages] [Bug 1971763] Re: www-browser is not satisfied by the default Firefox snap
The Firefox deb is not installed by default (on a minimal or normal install). Installing it manually does fulfill the dependency. www-browser defaults to wslu if the user did not already install the Firefox deb. This is problematic because the translation packages Ubuntu asks its users to install will pull wslu, and break the desktop, on a fresh install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1971763 Title: www-browser is not satisfied by the default Firefox snap Status in apt package in Ubuntu: Incomplete Bug description: When installing a package that has the virtual-package www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1971763/+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 1971715] Re: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
For conversion backwards use idn2 -d domain.com How ever it doesn't stop why it doesn't work for idn package it self -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: New Bug description: On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+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 1856187] Re: Cups wont print to smb-shared printer requiring user authentication via kerberos
Solved upstream with later versions of cups -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1856187 Title: Cups wont print to smb-shared printer requiring user authentication via kerberos Status in cups package in Ubuntu: New Bug description: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not true: the printer requires authentication. Maybe a bug. This print server requires any user to be authenticated and have a kerberos ticket. This is true. The user has a kerberos ticket and this user is allowed to print. The users kerberos ticket cache is available in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it into account. May be a bug too. Changing "AuthInfoRequired" from "none" to "username,password" allows cups to print. But this has to be done editing /etc/cups/printers.conf. The web printer configuration just does not allow to set anything else than "none". This is a bug. Documentation misses what "AuthInfoRequired" has to be set for if kerberos authentication will be used. This is a bug too! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 13:54:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856187/+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 1852474] Re: cups not printing if authentication required by server
Solved upstream with later versions of cups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1852474 Title: cups not printing if authentication required by server Status in cups package in Ubuntu: Confirmed Bug description: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1852474/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Hello leonpano, or anyone else affected, Accepted wpa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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. ** Tags added: verification-needed verification-needed-jammy -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1915707] Re: keyboard settings not applied
thanks, closing since it's fixed ** Changed in: console-setup (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1915707 Title: keyboard settings not applied Status in console-setup package in Ubuntu: Fix Released Bug description: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1915707/+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 1915707] Re: keyboard settings not applied
Solved with a later version of required packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1915707 Title: keyboard settings not applied Status in console-setup package in Ubuntu: Fix Released Bug description: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1915707/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
Hello Ilgaz, or anyone else affected, Accepted openssl into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.2 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: openssl (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Fix Committed Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-25-generic&series=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget&curl doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5
[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels
Hello Julian, or anyone else affected, Accepted apt into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.3.9ubuntu0.1 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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: apt (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: apt (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: New Status in apt source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: New Status in apt source package in Impish: Fix Committed Status in unattended-upgrades source package in Impish: New Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable unattended-upgrades may need changes to its test suite to accommodate this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.15 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: New Status in apt source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: New Status in apt source package in Impish: Fix Committed Status in unattended-upgrades source package in Impish: New Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable unattended-upgrades may need changes to its test suite to accommodate this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1968154] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.8 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: apt (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: New Status in apt source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: New Status in apt source package in Impish: Fix Committed Status in unattended-upgrades source package in Impish: New Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable unattended-upgrades may need changes to its test suite to accommodate this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
Solved by a later version of systemd and sshd. To have it work as intended sshd has to be compiled with different options set. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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 1615381] Re: apt-get autoremove may remove current kernel
Hello Jarno, or anyone else affected, Accepted apt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.0.8 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. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: apt (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Tags removed: verification-done verification-done-bionic ** 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 1
[Touch-packages] [Bug 1615381] Please test proposed package
Hello Jarno, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.15 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: apt (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Ar
[Touch-packages] [Bug 1968028] Re: unattended-upgrades if enabled wont disable interactivemode
Solved by a new version of upgrade tools. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1968028 Title: unattended-upgrades if enabled wont disable interactivemode Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1968028/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
Meanwhile even the distros working until yesterday stopped working today (5. May 2022 around 22:00). The bug seems related to pipewire and switching to this new infrastructure. It breaks nearly everything related with sound and bluetooth. Modules involved: - pipewire-pulse - wireplumber -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
These modules seem to collide with pipewire-media-session, but are required by bluez-stack to connect bluetooth headsets (or other devices) to pulseaudio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
Indeed those modules are not installed in vanilla Ubuntu. We don't use PipeWire for audio or Bluetooth, although Kubuntu/Xubuntu might. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
xubuntu and kubuntu, as lubuntu do use pipewire for audio. kali switched last night to use it. openSUSE did so too. i did not test on a plain vanilla gnome based ubuntu until now. Will do it later this day (if time permits). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1965439] Re: software-properties-qt can no longer launch when called by kdesu
Affects me also -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Invalid Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1951586] Re: Need option to specify wifi regulatory domain
@jvonau I just came back to this while trawling through my still-open bug list and had a look at what happens on the desktop. At least on our Pi desktop images (using NetworkManager), no wifi regulatory domain gets set at all (at least on my local network). Just in case it made any difference, I also tried switching on "location services", but there was no effect on the regulatory domain. It appears that the effort to make NetworkManager (or more broadly, the GNOME desktop) location aware stalled some considerable time ago [1] [2] [3] [1]: http://linuxwireless.sipsolutions.net/en/developers/GSoC/2009/GeoClue_regulatory/ [2]: https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA#using_network_manager_to_change_regulatory_domains [3]: https://wireless.wiki.kernel.org/en/developers/Regulatory#automatic_country_discovery Also, I don't see any option to manually set the regulatory domain in the UI. Now that crda's gone in jammy, and "iw" isn't seeded on the desktop image (for the Pi at least; is the PC any different?) there's effectively no way for the user to set the wifi regulatory domain (something that's fairly important ... legal stuff and all that) "out of the box" either via the GUI or via the command line. I've added the info the jammy release notes, and I'm going to add a few targets here as this clearly needs some work on several fronts, presumably netplan for servers and NetworkManager for desktops. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Kinetic) Importance: Medium Status: Triaged -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: New Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: New Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1971763] Re: www-browser is not satisfied by the default Firefox snap
The gimp-help-* packages have a dependency on only virtual packages rather than firefox-esr | firefox | chromium | x-www-browser or something which is a bug. as it will pick a random one. Also I'm not sure why it would depend on the non-graphical browser virtual package (www-browser) instead of a graphical browser (x-www-browser). There's no way for repositories to declare the default provider of a virtual package, unfortunately. An approach would be default-x-www- browser | x-www-browser but it's also suboptimal. ** Package changed: apt (Ubuntu) => gimp-help (Ubuntu) ** Changed in: gimp-help (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1971763 Title: www-browser is not satisfied by the default Firefox snap Status in gimp-help package in Ubuntu: Triaged Bug description: When installing a package that has the virtual-package www-browser as a dependency, the Firefox snap is not taken into account. This leads to wslu being installed on Ubuntu 22.04 Desktop (notably when installing the GIMP translation packages), which breaks the ding desktop behaviour: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1971757 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp-help/+bug/1971763/+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 1961427] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2022-05-06 06:22 EDT---
Here are the originally reported failures:
> But I found in "bedtools":
> bedtools: bgzf.c:351: bgzf_hopen: Assertion
> `compressBound(BGZF_BLOCK_SIZE) < BGZF_MAX_BLOCK_SIZE' failed. test-
> intersect.sh: line 201: 1981 Aborted (core dumped)
> $htsutil samtobam one_block.sam one_block.bam
>
> or in libbio:
> perl: bgzf.c:142: bgzf_open: Assertion
> `compressBound(BGZF_BLOCK_SIZE) < BGZF_MAX_BLOCK_SIZE' failed.Failed
> 268/268 subtests
I just double-checked, and apparently bedtools bundles htslib (under
src/utils/htslib). I didn't check libbio, but most likely it does this
as well. So the patch must be cherry-picked into all of the bundled
copies.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Incomplete
Status in zlib package in Ubuntu:
Incomplete
Status in zlib source package in Focal:
New
Status in zlib source package in Impish:
New
Status in zlib source package in Jammy:
Incomplete
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, &dest_len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected.
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
Reproduction: z15 only:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, &dest_len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
To manage notifications about this bug go to:
https://bug
[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
** Description changed: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. - [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. + [backported patch] + + the backported patch adds support to mount cgroup2 (new way) in addition + to the old way (cgroup + __DEVEL_ option) and also adds a fallback to do + that when mounting cgroups1 fails (because host is already using non- + hybrid v2 cgroups). This way the default behaviour remains the same, + apart from when trying to boot xenial on latest kernels and userspace + that opts into using cgroups2-only. + [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [backported patch] the backported patch adds support to mount cgroup2 (new way) in
[Touch-packages] [Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
Good news, proposed patch fixed the issue. Fresh Kubuntu (Turkish) on a VM with proposed patches enabled. Original symptom isn't there # sudo ua status [sudo] ilgaz için parola: SERVICE AVAILABLE DESCRIPTION cc-eal no Common Criteria EAL2 Provisioning Packages cis no Security compliance and audit tools esm-infrayesUA Infra: Extended Security Maintenance (ESM) fips no NIST-certified core packages fips-updates no NIST-certified core packages with priority security updates livepatchyesCanonical Livepatch service This machine is not attached to a UA subscription. Additionally this works (another symptom, wget) # wget https://cdimage.ubuntu.com/kubuntu/releases/22.04/release/kubuntu-22.04-desktop-amd64.iso.torrent --2022-05-06 14:33:48-- https://cdimage.ubuntu.com/kubuntu/releases/22.04/release/kubuntu-22.04-desktop-amd64.iso.torrent cdimage.ubuntu.com (cdimage.ubuntu.com) çözümleniyor... 91.189.91.124, 91.189.91.123, 185.125.190.37, ... cdimage.ubuntu.com (cdimage.ubuntu.com)|91.189.91.124|:443 bağlanılıyor... bağlantı kuruldu. HTTP isteği gönderildi, cevap bekleniyor... 200 OK Uzunluk: 280634 (274K) [application/x-bittorrent] Kayıt yeri: ‘kubuntu-22.04-desktop-amd64.iso.torrent’ kubuntu-22.04-desktop-a 100%[===>] 274,06K 505KB/ssüre 0,5s 2022-05-06 14:33:49 (505 KB/s) - ‘kubuntu-22.04-desktop- amd64.iso.torrent’ kaydedildi [280634/280634] # apt info openssl Package: openssl Version: 3.0.2-0ubuntu1.2 Priority: important Section: utils Origin: Ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Fix Committed Bug description: [Impact] Due to the case comparison differences in the Turkish locale, some routines in OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking crypto. [Test Plan] This bug is really easy to trigger: sudo locale-gen tr_TR.UTF-8 LANG=C curl https://ubuntu.com/ > /dev/null # This work LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails The error is curl: (35) error:0372:digital envelope routines::decode error [Where problems could occur] This patch set is relatively massive, and can cause regressions, as illustrated by the patch #5 which fixes one such regression. Those regressions would likely show up as either libssl crashes, in case of uninitialized objects, or as algorithm selection failures if somehow the case comparison is buggy. [Other Info] The fix has already been released upstream as part of their 3.0.3 release. [Original report] I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-25-generic&series=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget&curl doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUS DESCRIPTION cc-eal yes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR
[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe
So this is a bit of a pickle this SRU. Basically we need to decide on one of the two worlds: staying compliant with what the manufacturers demand (not performing the FCC unlock by default) and not breaking users (as previously modemmanager was automatically performing the unlock). We would probably need to consult someone regarding the legal aspect of automatically unlocking the devices - so it's something we really should do. Since by default we should really REALLY make sure that we're not breaking existing users, but then again - we shouldn't be doing things that are 'not okay' by our main packages as well. However, in the meantime, I'll review the SRU as-is, without the auto- unlocking, consider pulling it into focal-proposed and then set a block- proposed tag until we know for sure which way to go. We can always patch the package with the unlocks and re-upload, if needed. A bit of additional data regarding the regression potential of this change, maybe even some pros of just going with 1.118 as-is: * From what I know, some of the locked modems (the Lenovo-shipped ones I think?) are already broken by a firmware upgrade right now. * Users upgrading to the next LTS (22.04), once upgrades are enabled, will encounter this issue anyway, having to manually perform the unlock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1965901] Re: SRU the new 1.18 serie to focal for hwe
Hello Sebastien, or anyone else affected, Accepted libmbim into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.26.2-1~ubuntu20.04.1 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: libmbim (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: libqmi (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1965901] Re: SRU the new 1.18 serie to focal for hwe
Added the block-proposed-focal tag until we have clarity on how to proceed with the missing auto-unlocking functionality. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1965901] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted modemmanager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.18.6-1~ubuntu20.04.1 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. ** Tags added: blocked-proposed-focal ** Tags removed: blocked-proposed-focal ** Tags added: block-proposed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1965901] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted libqmi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.30.4-1~ubuntu20.04.1 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: modemmanager (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Bug description: [Impact] We want to update to the newer serie for better hardware support (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1962541] Autopkgtest regression report (wpa/2:2.10-6ubuntu1)
All autopkgtests for the newly accepted wpa (2:2.10-6ubuntu1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: netplan.io/0.104-0ubuntu2 (arm64) network-manager/1.36.4-2ubuntu1 (amd64) 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/jammy/update_excuses.html#wpa [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 wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1971984] [NEW] pcscd 1.9.5-3 do not start automatically, only manual
Public bug reported: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: New Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971986] [NEW] System hangs / flickers
Public bug reported: Till Ubuntu 21.10, everything was working properly. After installing Ubuntu 22.04, the system hangs all of a sudden, or the screen flickers soon after login. When I am in middle of some work, I am loosing the entire work. This is not specific to an application. It happened with skype, thunderbird, zoom, gnucash etc., Some issue with ubuntu 22.04 in the screen display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1011.12-oem 5.10.6 Uname: Linux 5.10.0-1011-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 6 18:26:20 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.10.0-1011-oem, x86_64: installed virtualbox/6.1.32, 5.10.0-1011-oem, x86_64: installed virtualbox-guest/6.1.26, 5.10.0-1011-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1011-oem root=UUID=42b34cdf-ac70-4604-baa3-b7db4540f825 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN46WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:br1.70:efr1.41:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu -- 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/1971986 Title: System hangs / flickers Status in xorg package in Ubuntu: New Bug description: Till Ubuntu 21.10, everything was working properly. After installing Ubuntu 22.04, the system hangs all of a sudden, or the screen flickers soon after login. When I am in middle of some work, I am loosing the entire work. This is not specific to an application. It happened with skype, thunderbird, zoom, gnucash etc., Some issue with ubuntu 22.04 in the screen display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1011.12-oem 5.10.6 Uname: Linux 5.10.0-1011-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 6 18:26:20 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.10.0-1011-oem, x86_64: installed virtualbox/6.1.32, 5.10.0-1011-oem, x86_64: installed virtualbox-guest/6.1.26, 5.10.0-1011-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1011-oem root=UUID=42b34cdf-ac70-4604-baa3-b7db4540f825 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.release: 1.70 dmi.bios.vendor:
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
I just ran into this bug also on Ubuntu 20 LTS after updating the kernel a week ago (multiboot laptop with Ubuntu and Windows 10). After figuring out that it's not a hardware issue (since windows still booted normally), I made the switch to Jammy, installed Ubuntu and all my software from scratch, and it worked during the first boot cycle. Rebooting a week later after living on standby, I am screwed again. Why is this neither fixed nor is there a set of instructions how to deal with it for the time being, if it is HIGH priority? Could you please provide simple, pedestrian instructions (including full paths, etc.) for a user who is used to working in bash, but not to the technical details of the inner workings of Ubuntu. I need a robust workaround until this bug is eventually fixed, and have a hard time believing that the bug still shows after the last post is 4 weeks old. Any help is appreciated. -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1971992] [NEW] openssl rmd160 digest broken
Public bug reported: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971992 Title: openssl rmd160 digest broken Status in openssl package in Ubuntu: New Bug description: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971992/+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 1951586] Re: Need option to specify wifi regulatory domain
Connection via NetworkManager to AP 2993 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5017] device (wlp2s0): Activation: starting connection '181-rpi4-64bit-raspios-LARGE' (9a51eba2-3723-4750-8a72-aa2e4c723140) 2994 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5083] audit: op="connection-add-activate" uuid="9a51eba2-3723-4750-8a72-aa2e4c723140" name="181-rpi4-64bit-raspios-LARGE" pid=1342 uid=1000 result="success" 2995 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5173] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') 2996 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5309] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') 2997 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5364] device (wlp2s0): Activation: (wifi) connection '181-rpi4-64bit-raspios-LARGE' requires no security. No secrets needed. 2998 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5365] Config: added 'ssid' value '181-rpi4-64bit-raspios-LARGE' 2999 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5366] Config: added 'scan_ssid' value '1' 3000 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5366] Config: added 'bgscan' value 'simple:30:-70:86400' 3001 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5367] Config: added 'key_mgmt' value 'NONE' 3002 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5508] device (wlp2s0): supplicant interface state: disconnected -> scanning 3003 May 6 09:55:54 124-u2204-desk NetworkManager[641]: [1651845354.5509] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning 3004 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: SME: Trying to authenticate with 02:72:82:96:ac:1e (SSID='181-rpi4-64bit-raspios-LARGE' freq=2437 MHz) 3005 May 6 09:55:55 124-u2204-desk kernel: [ 686.915199] wlp2s0: authenticate with 02:72:82:96:ac:1e 3006 May 6 09:55:55 124-u2204-desk kernel: [ 686.919826] wlp2s0: send auth to 02:72:82:96:ac:1e (try 1/3) 3007 May 6 09:55:55 124-u2204-desk kernel: [ 686.922147] wlp2s0: authenticated 3008 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: Trying to associate with 02:72:82:96:ac:1e (SSID='181-rpi4-64bit-raspios-LARGE' freq=2437 MHz) 3009 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1109] device (wlp2s0): supplicant interface state: scanning -> authenticating 3010 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating 3011 May 6 09:55:55 124-u2204-desk kernel: [ 686.929202] wlp2s0: associate with 02:72:82:96:ac:1e (try 1/3) 3012 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: Associated with 02:72:82:96:ac:1e 3013 May 6 09:55:55 124-u2204-desk kernel: [ 686.937597] wlp2s0: RX AssocResp from 02:72:82:96:ac:1e (capab=0x401 status=0 aid=1) 3014 May 6 09:55:55 124-u2204-desk kernel: [ 686.938943] wlp2s0: associated 3015 May 6 09:55:55 124-u2204-desk kernel: [ 686.940900] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready 3016 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1276] device (wlp2s0): supplicant interface state: authenticating -> associating 3017 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1277] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating 3018 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 02:72:82:96:ac:1e completed [id=0 id_str=] 3019 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 3020 May 6 09:55:55 124-u2204-desk wpa_supplicant[683]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US 3021 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1389] device (wlp2s0): supplicant interface state: associating -> completed 3022 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1390] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "181-rpi4-64bit-raspios-LARGE" 3023 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1391] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed 3024 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1457] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') 3025 May 6 09:55:55 124-u2204-desk NetworkManager[641]: [1651845355.1504] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) 3026 May 6 09:55:55 124-u2204-desk avahi-daemon[636]: Joining mDNS multicast group on interface wlp2s0.IPv6
[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
** Changed in: fwupd (Ubuntu) Status: New => Fix Committed -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: New Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: New Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: New Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable
** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- 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/1915966 Title: Please merge initramfs-tools 0.139 from Debian unstable Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Please merge initramfs-tools 0.139 from Debian unstable. Updated changelog and diff against Debian unstable to be attached shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Hi Johannes, > Rebooting a week later after living on standby, I am screwed again. Can you please explain what problems you experienced as a result of this bug? My previous understanding was that there was no real effect, and just a failed udev rule (which should not be running anyways) and noise in the logs. To work around this for the time being, you can simply remove the offending udev rule: # rm /lib/udev/rules.d/66-snapd-autoimport.rules -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
I just made a fresh install of Ubuntu 22.04. For an unknown reason pcscd.socket is DISABLED. $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) To solve the problem you can do: sudo systemctl enable pcscd.socket Then reboot, or run "sudo systemctl start pcscd.socket". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: New Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Hi, thanks. I shall try this. This enabling of the pcscd.socket stays persistent trough restarts i may hope ? Is this a bug in pcscd-lite or elsewhere ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: New Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1972009] [NEW] Totem fails to find video - kinetic ubuntu raspi pi
Public bug reported: Running test kinetic ubuntu daily - raspi 4 8GB daily ISO When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per the testcase - received the error - An error occurred - the specified movie could not be found. No further errors encountered -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" - please correct if need be. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 Uname: Linux 5.15.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 17:07:53 2022 ImageMediaBuild: 20220506 LogAlsaMixer: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image kinetic raspi-image wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972009 Title: Totem fails to find video - kinetic ubuntu raspi pi Status in gstreamer1.0 package in Ubuntu: New Bug description: Running test kinetic ubuntu daily - raspi 4 8GB daily ISO When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per the testcase - received the error - An error occurred - the specified movie could not be found. No further errors encountered -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" - please correct if need be. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 Uname: Linux 5.15.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 17:07:53 2022 ImageMediaBuild: 20220506 LogAlsaMixer: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972009/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
I will post the contents of the 2 systemd configuration files: "pcscd.service" and "pcscd.socket" later. I saw that they where not totally the same like in your blog. But now i'am on Ubuntu 18.04 and I saw that they where the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: New Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971272] Re: Merge cyrus-sasl2 from Debian unstable for kinetic
** Changed in: cyrus-sasl2 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1971272 Title: Merge cyrus-sasl2 from Debian unstable for kinetic Status in cyrus-sasl2 package in Ubuntu: New Bug description: Upstream: tbd Debian: 2.1.28+dfsg-4 Ubuntu: 2.1.27+dfsg2-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium * d/copyright: java/* files were removed upstream * d/copyright: Reformat the default license's margin * d/copyright: Add project's license to include/makemd5.c * Move SCRAM to libsasl2-modules (Closes: #977360) * Install additional GS2 module for Heimdal * Remove Roberto from the Uploaders * Drop 0005-Fixes-in-library-mutexes.patch * Drop 0021-Fix-keytab-option-for-MIT-Kerberos.patch * Remove former logcheck conffile (Closes: #1009851) * lintian: Fix excessive-priority-for-library-package * lintian: Fix package-contains-empty-directory -- Bastian Germann Wed, 20 Apr 2022 01:01:01 +0200 cyrus-sasl2 (2.1.28+dfsg-3) unstable; urgency=high * Set MIT/Heimdal CFLAGS instead of CPPFLAGS * Drop unnecessary 0027-properly-create-libsasl2.pc.patch * Prevent installing outdated ChangeLog (Closes: #1009681) * Remove debug log message and its logcheck rule (Closes: #805310) * Self-reference pluginviewer man as saslpluginviewer (Closes: #1009380) * Get rid of broken README.configure-options * Add sasldbconverter2.8 manpage * d/copyright: Add missing KTH license * Install libsasl.5 manpage [ Debian Janitor ] * Remove constraints unnecessary since buster -- Bastian Germann Fri, 15 Apr 2022 12:02:13 +0200 cyrus-sasl2 (2.1.28+dfsg-2) unstable; urgency=medium * Remove cruft -- Bastian Germann Fri, 25 Feb 2022 18:58:54 +0100 cyrus-sasl2 (2.1.28+dfsg-1) experimental; urgency=medium * Drop upstream patches * Import new release signing key * Reset repacksuffix * New upstream version 2.1.28+dfsg (CVE-2022-24407) * Rebase 0027-properly-create-libsasl2.pc.patch -- Bastian Germann Tue, 22 Feb 2022 23:40:47 +0100 cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium [ Andreas Hasenack ] * Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152) -- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100 cyrus-sasl2 (2.1.27+dfsg2-2) unstable; urgency=medium [ Helmut Grohne ] * Fix FTCBFS: (Closes: #928512) + cross.patch: Support caching SPNEGO support test. + Provide SPNEGO support test result. [ Vagrant Cascadian ] * Set date in man pages (Closes: #995145) -- Bastian Germann Wed, 17 Nov 2021 01:23:49 +0100 cyrus-sasl2 (2.1.27+dfsg2-1) unstable; urgency=medium * Add bage to uploaders (Closes: #799864) * Use upstream patches where possible * Amend off-by-one in _sasl_add_string function * Replace some patches by upstream equivalents * Apply the patches in order of to their prefixes * Add missing caret (^) in logcheck rule (Closes: #830764) * Remove unnecessary GPL copy * Add missing copyright/licenses * Repack, getting rid of more problematic files * Build html documentation * Make the package rebuildable * Remove outdated README.Debian info * Disable autostart via debhelper * Drop unnecessary patch * Remove alternative, old build dep libmysqlclient-dev Annotate documentation Build-Depends with :native [ Frédéric Brière ] * Make logcheck snippet compatible with systemd journal -- Bastian Germann Sun, 14 Nov 2021 14:11:18 +0100 cyrus-sasl2 (2.1.27+dfsg-2.3) unstable; urgency=medium * Non-maintainer upload. * d/watch: Check the github releases page * Get rid of a patch's patch * Recover upstream-compatible patch license (Closes: #996866) + Relicense libobj patch * Fix lintian: unused-override ### Old Ubuntu Delta ### cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1) jammy; urgency=medium * SECURITY UPDATE: SQL injection in SQL plugin - debian/patches/CVE-2022-24407.patch: escape password for SQL insert/update commands in plugins/sql.c. - CVE-2022-24407 -- Marc Deslauriers Tue, 22 Feb 2022 14:17:18 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1971272/+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 1677781] Re: Missing dep8 tests
** Changed in: cyrus-sasl2 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1677781 Title: Missing dep8 tests Status in cyrus-sasl2 package in Ubuntu: Triaged Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source cyrus-sasl2 zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/cyrus-sasl2 status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1 3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe 4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5 WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5 Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G WY9JzBOc6MUi46Hh9ZN5 =szTz -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 1947329] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1947329 Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Confirmed Bug description: Pop up comes in just after turn on. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 15 01:40:29 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2021-10-05 (10 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to focal on 2021-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1947329/+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 1972009] Re: Totem fails to find video - kinetic ubuntu raspi pi
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1972009 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972009 Title: Totem fails to find video - kinetic ubuntu raspi pi Status in gstreamer1.0 package in Ubuntu: New Bug description: Running test kinetic ubuntu daily - raspi 4 8GB daily ISO When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per the testcase - received the error - An error occurred - the specified movie could not be found. No further errors encountered -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" - please correct if need be. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 Uname: Linux 5.15.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 17:07:53 2022 ImageMediaBuild: 20220506 LogAlsaMixer: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972009/+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 1971272] Re: Merge cyrus-sasl2 from Debian unstable for kinetic
** Changed in: cyrus-sasl2 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1971272 Title: Merge cyrus-sasl2 from Debian unstable for kinetic Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: Upstream: tbd Debian: 2.1.28+dfsg-4 Ubuntu: 2.1.27+dfsg2-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium * d/copyright: java/* files were removed upstream * d/copyright: Reformat the default license's margin * d/copyright: Add project's license to include/makemd5.c * Move SCRAM to libsasl2-modules (Closes: #977360) * Install additional GS2 module for Heimdal * Remove Roberto from the Uploaders * Drop 0005-Fixes-in-library-mutexes.patch * Drop 0021-Fix-keytab-option-for-MIT-Kerberos.patch * Remove former logcheck conffile (Closes: #1009851) * lintian: Fix excessive-priority-for-library-package * lintian: Fix package-contains-empty-directory -- Bastian Germann Wed, 20 Apr 2022 01:01:01 +0200 cyrus-sasl2 (2.1.28+dfsg-3) unstable; urgency=high * Set MIT/Heimdal CFLAGS instead of CPPFLAGS * Drop unnecessary 0027-properly-create-libsasl2.pc.patch * Prevent installing outdated ChangeLog (Closes: #1009681) * Remove debug log message and its logcheck rule (Closes: #805310) * Self-reference pluginviewer man as saslpluginviewer (Closes: #1009380) * Get rid of broken README.configure-options * Add sasldbconverter2.8 manpage * d/copyright: Add missing KTH license * Install libsasl.5 manpage [ Debian Janitor ] * Remove constraints unnecessary since buster -- Bastian Germann Fri, 15 Apr 2022 12:02:13 +0200 cyrus-sasl2 (2.1.28+dfsg-2) unstable; urgency=medium * Remove cruft -- Bastian Germann Fri, 25 Feb 2022 18:58:54 +0100 cyrus-sasl2 (2.1.28+dfsg-1) experimental; urgency=medium * Drop upstream patches * Import new release signing key * Reset repacksuffix * New upstream version 2.1.28+dfsg (CVE-2022-24407) * Rebase 0027-properly-create-libsasl2.pc.patch -- Bastian Germann Tue, 22 Feb 2022 23:40:47 +0100 cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium [ Andreas Hasenack ] * Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152) -- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100 cyrus-sasl2 (2.1.27+dfsg2-2) unstable; urgency=medium [ Helmut Grohne ] * Fix FTCBFS: (Closes: #928512) + cross.patch: Support caching SPNEGO support test. + Provide SPNEGO support test result. [ Vagrant Cascadian ] * Set date in man pages (Closes: #995145) -- Bastian Germann Wed, 17 Nov 2021 01:23:49 +0100 cyrus-sasl2 (2.1.27+dfsg2-1) unstable; urgency=medium * Add bage to uploaders (Closes: #799864) * Use upstream patches where possible * Amend off-by-one in _sasl_add_string function * Replace some patches by upstream equivalents * Apply the patches in order of to their prefixes * Add missing caret (^) in logcheck rule (Closes: #830764) * Remove unnecessary GPL copy * Add missing copyright/licenses * Repack, getting rid of more problematic files * Build html documentation * Make the package rebuildable * Remove outdated README.Debian info * Disable autostart via debhelper * Drop unnecessary patch * Remove alternative, old build dep libmysqlclient-dev Annotate documentation Build-Depends with :native [ Frédéric Brière ] * Make logcheck snippet compatible with systemd journal -- Bastian Germann Sun, 14 Nov 2021 14:11:18 +0100 cyrus-sasl2 (2.1.27+dfsg-2.3) unstable; urgency=medium * Non-maintainer upload. * d/watch: Check the github releases page * Get rid of a patch's patch * Recover upstream-compatible patch license (Closes: #996866) + Relicense libobj patch * Fix lintian: unused-override ### Old Ubuntu Delta ### cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1) jammy; urgency=medium * SECURITY UPDATE: SQL injection in SQL plugin - debian/patches/CVE-2022-24407.patch: escape password for SQL insert/update commands in plugins/sql.c. - CVE-2022-24407 -- Marc Deslauriers Tue, 22 Feb 2022 14:17:18 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1971272/+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 1968154] Autopkgtest regression report (apt/2.3.9ubuntu0.1)
All autopkgtests for the newly accepted apt (2.3.9ubuntu0.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.16 (s390x, amd64) 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/impish/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: New Status in apt source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: New Status in apt source package in Impish: Fix Committed Status in unattended-upgrades source package in Impish: New Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable unattended-upgrades may need changes to its test suite to accommodate this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1972005] [NEW] Unable to save or attach email attachments since upgrading to 22.04 from 20.04
You have been subscribed to a public bug: This bug reporting process is very cumbersome. I tried using the update- bug application but none of the available options were relevant. If I selected other, I was forced to select a package. How am I supposed to know what package the bug is in? So I just picked one so I could get by this nonsensical barrier. As for the bug I am trying to report: since upgrading to 22.04 last week from 20.04, I have been unable to save attachments to my local disk from Gmail in Chrome or Firefox. Everything appears to work however the file is never actually saved to the file system. Also, when I drag files from the Files app to the browser, either to upload to Jira or attach to Gmail, it appears to work but the attachment is never actually uploaded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-desktop 1.481 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 11:26:07 2022 InstallationDate: Installed on 2021-07-31 (279 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-25 (11 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Unable to save or attach email attachments since upgrading to 22.04 from 20.04 https://bugs.launchpad.net/bugs/1972005 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972005] Re: Unable to save or attach email attachments since upgrading to 22.04 from 20.04
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1972005 Title: Unable to save or attach email attachments since upgrading to 22.04 from 20.04 Status in ubuntu-meta package in Ubuntu: New Bug description: This bug reporting process is very cumbersome. I tried using the update-bug application but none of the available options were relevant. If I selected other, I was forced to select a package. How am I supposed to know what package the bug is in? So I just picked one so I could get by this nonsensical barrier. As for the bug I am trying to report: since upgrading to 22.04 last week from 20.04, I have been unable to save attachments to my local disk from Gmail in Chrome or Firefox. Everything appears to work however the file is never actually saved to the file system. Also, when I drag files from the Files app to the browser, either to upload to Jira or attach to Gmail, it appears to work but the attachment is never actually uploaded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-desktop 1.481 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 11:26:07 2022 InstallationDate: Installed on 2021-07-31 (279 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-25 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1972005/+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 1968179] Re: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted
** Tags added: kernel-sound -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1968179 Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted Status in pulseaudio package in Ubuntu: New Bug description: I noticed some dynamic distortion starting today. It is not periodic but rather seems to be effected by the music played. Running a VM i do not get the same problem with windows. The distortion is also heard through the Analog port of my Lenovo USB C Dock Gen 2. I checked with different headphones/speakers the problem persists. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 16:21:40 2022 InstallationDate: Installed on 2020-07-31 (615 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2020 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrDTCN20WW(V1.06):bd06/09/2020:br1.20:efr1.20:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968179/+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 1968154] Autopkgtest regression report (apt/2.0.8)
All autopkgtests for the newly accepted apt (2.0.8) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (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/focal/update_excuses.html#apt [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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in apt source package in Bionic: Fix Committed Status in unattended-upgrades source package in Bionic: New Status in apt source package in Focal: Fix Committed Status in unattended-upgrades source package in Focal: New Status in apt source package in Impish: Fix Committed Status in unattended-upgrades source package in Impish: New Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable unattended-upgrades may need changes to its test suite to accommodate this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1615381] Autopkgtest regression report (apt/2.0.8)
All autopkgtests for the newly accepted apt (2.0.8) for focal have finished running. The following regressions have been reported in tests triggered by the package: reprotest/0.7.14 (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/focal/update_excuses.html#apt [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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1968179] Re: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted
** Description changed: I noticed some dynamic distortion starting today. It is not periodic but rather seems to be effected by the music played. Running a VM i do not get the same problem with windows. The distortion is also heard through the Analog port of my Lenovo USB C Dock Gen 2. I checked with different headphones/speakers the problem persists. + + Update 06.05.22: The Problem doesn't occur when i use a Bluetooth + speaker or the headphone jack from the laptop and not the dock. I wasnt + able to find an up to date ALSA driver using this guide + https://wiki.ubuntu.com/Audio/UpgradingAlsa, the older ones didnt help. + The position fix quirk tipps + https://wiki.ubuntu.com/Audio/PositionReporting didnt help. Nor the + various other commands from + https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 16:21:40 2022 InstallationDate: Installed on 2020-07-31 (615 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2020 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrDTCN20WW(V1.06):bd06/09/2020:br1.20:efr1.20:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1968179 Title: [81YM, Realtek ALC257, Black Headphone Out, Right] Sound is distorted Status in pulseaudio package in Ubuntu: New Bug description: I noticed some dynamic distortion starting today. It is not periodic but rather seems to be effected by the music played. Running a VM i do not get the same problem with windows. The distortion is also heard through the Analog port of my Lenovo USB C Dock Gen 2. I checked with different headphones/speakers the problem persists. Update 06.05.22: The Problem doesn't occur when i use a Bluetooth speaker or the headphone jack from the laptop and not the dock. I wasnt able to find an up to date ALSA driver using this guide https://wiki.ubuntu.com/Audio/UpgradingAlsa, the older ones didnt help. The position fix quirk tipps https://wiki.ubuntu.com/Audio/PositionReporting didnt help. Nor the various other commands from https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 16:21:40 2022 InstallationDate: Installed on 2020-07-31 (615 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [81YM, Realtek ALC257, Black Headph
[Touch-packages] [Bug 1677781] Re: Missing dep8 tests
** Changed in: cyrus-sasl2 (Ubuntu) Status: Triaged => In Progress ** Changed in: cyrus-sasl2 (Ubuntu) Importance: Wishlist => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1677781 Title: Missing dep8 tests Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source cyrus-sasl2 zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/cyrus-sasl2 status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1 3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe 4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5 WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5 Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G WY9JzBOc6MUi46Hh9ZN5 =szTz -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
** Changed in: cyrus-sasl2 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: cyrus-sasl2 (Ubuntu Jammy) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 source package in Impish: Triaged Status in cyrus-sasl2 source package in Jammy: In Progress Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1972029] [NEW] dhclient overriding stub-resolv.conf file on Jammy
Public bug reported: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd- resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1972029 Title: dhclient overriding stub-resolv.conf file on Jammy Status in isc-dhcp package in Ubuntu: New Bug description: [Issue] On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten if dhclient is executed. While debugging this, I found the reference on LP#1889068 [0] of the move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit- hooks.d/, and this new hook [2] has no reference of make_resolv_conf() being called. [Reproducer] - I used a cloud-image based Jammy installation (uvt-kvm). Once in: $ cat /run/system/resolve/stub-resolv.conf And one will see: nameserver 127.0.0.53 options edns0 trust-ad search . Then: $ sudo dhclient $ cat /run/system/resolve/stub-resolv.conf You'll see the definition of the nameserver(s) in, and the stub IP address no longer there. To revert this, a `systemctl restart systemd-resolved` is needed. [Impact] This is an improper way to keep nameserver(s) in *resolv* files; the override of the file should never happen in these circumstances. [Extra] - As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from a Focal installation to a Jammy one, and the problem _does not happen_ when such hook is in place. [ . . . ] Let me know if further clarification is needed to proceed. Thank you. BR, pprincipeza [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068 [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/ [2] https://paste.ubuntu.com/p/YQdG6z4WS7/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+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 1972009] Re: Totem fails to find video - kinetic ubuntu raspi pi
*** This bug is a duplicate of bug 1969512 *** https://bugs.launchpad.net/bugs/1969512 Sorry, I think this is a duplicate of 1969512 (marking as such) -- I have found, in the course of investigating that one that we may either need to switch the ISO test to use an OGG (or OGV) file instead (or mandate that gstreamer1.0-libav is installed first) but the bug still stands (even with that pkg installed, totem's reporting the same message). ** This bug has been marked a duplicate of bug 1969512 Totem unable to play video: "The specified movie could not be found" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972009 Title: Totem fails to find video - kinetic ubuntu raspi pi Status in gstreamer1.0 package in Ubuntu: New Bug description: Running test kinetic ubuntu daily - raspi 4 8GB daily ISO When attempting to run "totem big_buck_bunny_720p_surround.mp4" as per the testcase - received the error - An error occurred - the specified movie could not be found. No further errors encountered -- I ran ubuntu-bug totem but see that the package selected is "gstreamer1.0" - please correct if need be. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-1006.6-raspi 5.15.30 Uname: Linux 5.15.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 17:07:53 2022 ImageMediaBuild: 20220506 LogAlsaMixer: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972009/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer
> These two statements seem to be contradictory. If driverless printing
is more reliable, that would seem to imply that files sent directly to
the printer print more reliably than files sent through the CUPS
filters, which would seem to imply that it is the filters, not the
printer, that have bugs.
Driverless printing does not mean sending PostScript files directly to
the printer, it means that the client discovers the printer via DNS-SD,
queries the printer for its capabilities via IPP, and then prints in one
of the formats PDF, Apple Raster, PWG Raster, or PCLm to the printer,
dpending what it supports. CUPS does this automatically if no
"conventional" print queue exists (remove any queue for your printer).
Or you can create a print queue with the lpadmin command and the "-m
everywhere" model specification.
Does this perhaps work for you?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1968722
Title:
File fails to print when rendered with CUPS, prints fine when fed
directly to printer
Status in cups package in Ubuntu:
Incomplete
Bug description:
I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI
socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
same physical printer configured driverless in CUPS with a different
name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.
The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when
sent through the CUPS Postscript renderer, i.e., the former printer.
In particular, the file stops printing after four pages and then the
printer spits out this error page:
ERROR:
typecheck
OFFENDING-COMMAND:
known
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Lpstat:
device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
device for HP_LaserJet_500_color_M551_1637DA:
implicitclass://HP_LaserJet_500_color_M551_1637DA/
device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd',
'/etc/cups/ppd/duplex.ppd',
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2:
grep: /etc/cups/ppd/simplex.ppd: Permission denied
grep: /etc/cups/ppd/duplex.ppd: Permission denied
grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1971992] Re: openssl rmd160 digest broken
** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971992 Title: openssl rmd160 digest broken Status in openssl package in Ubuntu: Confirmed Bug description: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971992/+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 1971992] Re: openssl rmd160 digest broken
Hey Jan, thanks for the report. This has been discussed upstream at https://github.com/openssl/openssl/issues/16994. OpenSSL 3 has deprecated RIPEMD160 and thus moved them to the legacy provider according to the official openssl migration guide at https://www.openssl.org/docs/manmaster/man7/migration_guide.html. It looks like it can be worked around for now by adding -provider legacy as in: openssl rmd160 -provider legacy < some-file or by modifying your openssl.cnf to always load the legacy provider. ** Bug watch added: github.com/openssl/openssl/issues #16994 https://github.com/openssl/openssl/issues/16994 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971992 Title: openssl rmd160 digest broken Status in openssl package in Ubuntu: Confirmed Bug description: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971992/+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 1971992] Re: openssl rmd160 digest broken
** Changed in: openssl (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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1971992 Title: openssl rmd160 digest broken Status in openssl package in Ubuntu: Won't Fix Bug description: Using 3.0.2-0ubuntu1.1 on Ubuntu 22.04 (AMD64) I get ``` openssl rmd160 < some-file Error setting digest 405755EFCF7F:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:../crypto/evp/evp_fetch.c:349:Global default library context, Algorithm (RIPEMD160 : 99), Properties () 405755EFCF7F:error:0386:digital envelope routines:evp_md_init_internal:initialization error:../crypto/evp/digest.c:252: ``` Other digest types work fine. Using what is (according to `openssl version`) the same version of openssl from Macports on a Mac M1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1971992/+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 1923672] Re: [FFe] Provide access to GPIO to default user
** Changed in: ubuntu-settings (Ubuntu Impish) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923672 Title: [FFe] Provide access to GPIO to default user Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Status in ubuntu-settings source package in Impish: Won't Fix Status in ubuntu-settings source package in Jammy: Fix Released Bug description: At present, access to the GPIO pins is provided to the dialout group by the udev rules from the rpi.gpio-common package. However, rpi.gpio is a single GPIO library, and the device(s) it provides access to are not specific to it. Moreover, the interface used is deprecated and the /dev/gpiochip* interface is now the favoured mechanism for controlling the GPIO pins. The choice of the dialout group appears reasonable (historically it's used to provide access to the serial ports, and indeed the serial ports are part of the GPIO header on Raspberry Pi devices), but the rules should be extended to cover the modern /dev/gpiochip* devices, the related /dev/spidev* and /dev/i2c-* devices, and should be placed in a central location (i.e. ubuntu-raspi-settings) rather than in a specific GPIO library (like rpi.gpio). Related to this is LP: #1923363 which seeks to ensure equal access across images (the default user is currently granted "dialout" group membership on the pi server images, but not the desktop ones). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1923672/+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 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable
** Changed in: lvm2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1928973 Title: Please merge lvm2 2.03.11-2.1 from Debian unstable Status in lvm2 package in Ubuntu: Fix Released Bug description: Please merge lvm2 2.03.11-2.1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1928973/+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 1972036] [NEW] Plasma Wayland won't wake up from sleep
Public bug reported: SUMMARY My laptop wouldn't wake up or show anything after I opened the lid. It was on Wayland. STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake it up the next day 3. OBSERVED RESULT Opening the lid or pressing the power button doesn't do anything. EXPECTED RESULT Lock screen should appear as soon as the lid is open. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-27-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION I didn't get to check if it woke up or the display wasn't working because I was at work, and was in a rush. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.418 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail Date: Fri May 6 20:33:23 2022 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: wayland PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: third-party-packages jammy Uname: Linux 5.15.0-27-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) UserGroups: N/A _MarkForUpload: True ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected jammy third-party-packages ** Also affects: kwin (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected ** Description changed: SUMMARY My laptop wouldn't wake up or show anything after I opened the lid. It was on Wayland. STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake it up the next day 3. OBSERVED RESULT Opening the lid or pressing the power button doesn't do anything. EXPECTED RESULT Lock screen should appear as soon as the lid is open. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-27-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION I didn't get to check if it woke up or the display wasn't working because I was at work, and was in a rush. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.418 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail Date: Fri May 6 20:33:23 2022 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: fail + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-02-24 (71 days ago) + InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + Package: wayland + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_CA:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_CA.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + Tags: third-party-packages ja
[Touch-packages] [Bug 1972036] CasperMD5CheckMismatches.txt
apport information ** Attachment added: "CasperMD5CheckMismatches.txt" https://bugs.launchpad.net/bugs/1972036/+attachment/5587475/+files/CasperMD5CheckMismatches.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1972036 Title: Plasma Wayland won't wake up from sleep Status in kubuntu-meta package in Ubuntu: New Status in kwin package in Ubuntu: New Status in plasma-workspace package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: SUMMARY My laptop wouldn't wake up or show anything after I opened the lid. It was on Wayland. STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake it up the next day 3. OBSERVED RESULT Opening the lid or pressing the power button doesn't do anything. EXPECTED RESULT Lock screen should appear as soon as the lid is open. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-27-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION I didn't get to check if it woke up or the display wasn't working because I was at work, and was in a rush. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.418 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail Date: Fri May 6 20:33:23 2022 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: wayland PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: third-party-packages jammy Uname: Linux 5.15.0-27-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1972036/+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 1972036] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1972036/+attachment/5587476/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1972036 Title: Plasma Wayland won't wake up from sleep Status in kubuntu-meta package in Ubuntu: New Status in kwin package in Ubuntu: New Status in plasma-workspace package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: SUMMARY My laptop wouldn't wake up or show anything after I opened the lid. It was on Wayland. STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake it up the next day 3. OBSERVED RESULT Opening the lid or pressing the power button doesn't do anything. EXPECTED RESULT Lock screen should appear as soon as the lid is open. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-27-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION I didn't get to check if it woke up or the display wasn't working because I was at work, and was in a rush. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.418 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail Date: Fri May 6 20:33:23 2022 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: wayland PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: third-party-packages jammy Uname: Linux 5.15.0-27-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1972036/+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 1972036] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1972036/+attachment/5587477/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1972036 Title: Plasma Wayland won't wake up from sleep Status in kubuntu-meta package in Ubuntu: New Status in kwin package in Ubuntu: New Status in plasma-workspace package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: SUMMARY My laptop wouldn't wake up or show anything after I opened the lid. It was on Wayland. STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake it up the next day 3. OBSERVED RESULT Opening the lid or pressing the power button doesn't do anything. EXPECTED RESULT Lock screen should appear as soon as the lid is open. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-27-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION I didn't get to check if it woke up or the display wasn't working because I was at work, and was in a rush. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.418 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail Date: Fri May 6 20:33:23 2022 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: fail DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-24 (71 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: wayland PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: third-party-packages jammy Uname: Linux 5.15.0-27-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-04-20 (16 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1972036/+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 1965439] Re: software-properties-qt can no longer launch when called by kdesu
Facing the same problem with fresh install of Kubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by kdesu Status in kdesu package in Ubuntu: Confirmed Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Invalid Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Jammy: Confirmed Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Invalid Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1971101] Re: package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Hello, note your filesystem is full: Filesystem 1K-blocks Used Available Use% Mounted on udev 9812920981292 0% /dev tmpfs 202808 1508201300 1% /run /dev/sda5 11167656 11000192 0 100% / That causes errors like this: cp: error writing '/var/tmp/mkinitramfs_jx7Z98//usr/bin/kmod': No space left on device cp: error writing '/var/tmp/mkinitramfs_jx7Z98//usr/lib/x86_64-linux-gnu/liblzma.so.5.2.4': No space left on device mkdir: cannot create directory ‘/var/tmp/mkinitramfs_jx7Z98/etc/modprobe.d’: No space left on device mkdir: cannot create directory ‘/var/tmp/mkinitramfs_jx7Z98/lib/modprobe.d’: No space left on device mkdir: cannot create directory ‘/var/tmp/mkinitramfs_jx7Z98//etc/modprobe.d’: No space left on device These errors are preventing your system update from finishing. Free up some space on the root filesystem, and then try: sudo apt install -f or sudo dpkg --configure -a The full screen issue may require talking with VirtualBox support. Thanks ** Information type changed from Private Security to Public -- 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/1971101 Title: package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Slow system. I get notified all the time. Oh, by the way, I need help getting this virtual screen to go back full screen. Thanks! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 1 01:38:42 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-01 (212 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1971101/+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 1964040] Re: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de er
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- 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/1964040 Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: Expired Bug description: When I run apt-get autoremove command a problems happen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-tools-common:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1593 F pulseaudio rolando2195 F pulseaudio CasperMD5CheckResult: skip Date: Mon Mar 7 19:55:15 2022 Dependencies: ErrorMessage: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 HibernationDevice: RESUME=UUID=8bf13fc7-285e-42ac-a5aa-730d1ecadca1 InstallationDate: Installed on 2018-04-27 (1410 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G Keyboard Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UN PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic root=UUID=d72ca49b-f913-4292-9cb4-fa7e3d62ff1d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 1.187.26 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542UN.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542UN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX542UN.300:bd09/19/2017:svnASUSTeKCOMPUTERINC.:pnX542UN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X542UN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964040/+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 1971221] Re: firefox is flashing
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1971221 Title: firefox is flashing Status in xorg package in Ubuntu: New Bug description: when firefox window behind other APP windows, it is flashing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 11:53:34 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP104 [GeForce GTX 1080] [103c:82fb] InstallationDate: Installed on 2022-05-01 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=ff0f1b3b-e57d-46bf-817b-a2bf7bd47098 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2022 dmi.bios.release: 14.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd04/01/2022:br14.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1971221/+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 1872778] Re: update-crypto-policies not affecting Gnome Online Accounts
I just encountered this issue when upgrading from 21.10 to 22.04, not with a google account but with an orange.fr account. Workarounded thanks to #4. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1872778 Title: update-crypto-policies not affecting Gnome Online Accounts Status in gnome-online-accounts package in Ubuntu: Incomplete Status in gnutls28 package in Ubuntu: Confirmed Bug description: -crypto-policies 20190816git-1 -gnome-online-accounts 3.36.0-1ubuntu1 Changing between DEFAULT, LEGACY, and EMPTY has no affect on attempts to connect to accounts through Online Accounts. Changing to LEGACY or EMPTY should at least change the following error: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). Under either LEGACY or EMPTY the (not long enough) error is nonsensical. The persistence of the incorrect error message could imply that gnome-online-accounts is not respecting settings made by crypto-policies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872778/+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
