[Touch-packages] [Bug 1615381] Autopkgtest regression report (apt/1.6.15)
All autopkgtests for the newly accepted apt (1.6.15) for bionic have finished running. The following regressions have been reported in tests triggered by the package: autopkgtest/5.3.1ubuntu1.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#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 1968154] Autopkgtest regression report (apt/1.6.15)
All autopkgtests for the newly accepted apt (1.6.15) for bionic have finished running. The following regressions have been reported in tests triggered by the package: autopkgtest/5.3.1ubuntu1.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#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 1972070] Re: gdk-pixbuf does not support saving as gif
** Description changed: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" - Is write support for GIF dropped for any reason? - - Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: - Installed: 2.42.8+dfsg-1 - Candidate: 2.42.8+dfsg-1 - Version table: - *** 2.42.8+dfsg-1 500 + Installed: 2.42.8+dfsg-1 + Candidate: 2.42.8+dfsg-1 + Version table: + *** 2.42.8+dfsg-1 500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1972070 Title: gdk-pixbuf does not support saving as gif Status in gdk-pixbuf package in Ubuntu: New Bug description: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1972070/+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
Yes, the print job in question works when I print it to the driverless printer.
I would not say that it is therefore reasonable to declare that this issue is
resolved, but *shrug* whatever.
--
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 1966886] Re: ssh-copy-id and Dropbear Server
I don't know much about dropbear but from your explanation it does indeed sound like this is an upstream OpenSSH bug that should be reported at https://bugzilla.mindrot.org/. -- 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/1966886 Title: ssh-copy-id and Dropbear Server Status in openssh package in Ubuntu: New Bug description: on Dropbear SSH Servers ssh-copy-id installs the key in /etc/dropbear/authorized_keys only the openwrt dropbear server uses that path https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch the upstream dropbear server uses the normal path ~/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+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
The breaking change in sudo appears to be one of those in: https://tracker.debian.org/news/1237774/accepted-sudo-196-1exp2-source- into-experimental/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/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 sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Impish: Invalid Status in kubuntu-settings source package in Impish: Invalid Status in policykit-1 source package in Impish: Invalid Status in software-properties source package in Impish: Invalid Status in sudo source package in Impish: Invalid Status in ubuntustudio-default-settings source package in Impish: Invalid 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 sudo 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 1972070] [NEW] gdk-pixbuf does not support saving as gif
Public bug reported: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Is write support for GIF dropped for any reason? Description:Ubuntu 22.04 LTS Release:22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1972070 Title: gdk-pixbuf does not support saving as gif Status in gdk-pixbuf package in Ubuntu: New Bug description: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Is write support for GIF dropped for any reason? Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1972070/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
** Changed in: wpa (Debian) Status: Unknown => Fix Released ** Changed in: wpa (Debian) Importance: Wishlist => Unknown -- 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/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Fix Released Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level Status in openssl package in Ubuntu: Confirmed Bug description: openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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] Autopkgtest regression report (openssl/3.0.2-0ubuntu1.2)
All autopkgtests for the newly accepted openssl (3.0.2-0ubuntu1.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: mysql-8.0/8.0.29-0ubuntu0.22.04.2 (i386) resource-agents/1:4.7.0-1ubuntu7 (armhf) seqkit/2.1.0+ds-1 (arm64) ngircd/26.1-1 (s390x) linux-lowlatency/5.15.0-30.31 (arm64) python-bonsai/1.3.0+ds-3build1 (armhf) 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#openssl [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 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=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget 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.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
Apparently downgrading to the version of sudo in impish solves the problem, which means a change in sudo caused this. ** Also affects: sudo (Ubuntu) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntustudio-default-settings (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: policykit-1 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: kubuntu-settings (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: kdesu (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu Impish) Status: New => Invalid ** Changed in: sudo (Ubuntu Jammy) Status: New => Confirmed ** Changed in: ubuntustudio-default-settings (Ubuntu Impish) Status: New => Invalid ** Changed in: software-properties (Ubuntu Impish) Status: New => Triaged ** Changed in: kubuntu-settings (Ubuntu Impish) Status: New => Invalid ** Changed in: kdesu (Ubuntu Impish) Status: New => Invalid ** Changed in: policykit-1 (Ubuntu Impish) Status: New => Invalid ** Changed in: software-properties (Ubuntu Impish) Status: Triaged => Invalid ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo 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 sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kdesu source package in Impish: Invalid Status in kubuntu-settings source package in Impish: Invalid Status in policykit-1 source package in Impish: Invalid Status in software-properties source package in Impish: Invalid Status in sudo source package in Impish: Invalid Status in ubuntustudio-default-settings source package in Impish: Invalid 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 sudo 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:
[Touch-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu
It also affects me in Kubuntu 22.04 in both Muon and Discover. A work- around (besides the one mentioned above) is to open Settings --> System Settings --> Driver Manager and put in the password when prompted. That will open to the Drivers tab, but you can open any of the other tabs from there. -- 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 1972059] [NEW] One screen does not come back from lock
Public bug reported: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. 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 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: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago) dmi.bios.date: 11/11/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All 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 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 ubuntu wayland-session -- 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/1972059 Title: One screen does not come back from lock Status in xorg package in Ubuntu: New Bug description: I have 2 screen (Dell). Since having upgraded to 22.04, one of them struggles to come back after a lock. Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer. I have found that if I do Ctrl-Alt-F1... the screen comes back. I have a DP and HDMI cable and tried to switch them around, it is always the same screen: a Dell U2415 UltraSharp 24. Never happened with any other version since about 18.04. 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 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: Sat May 7 13:39:19 2022 DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 seconds (Configuring libpam-systemd (amd64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2020-02-01 (825 days ago) InstallationMedia:
[Touch-packages] [Bug 1972056] [NEW] [openssl3] please sync openssl.cnf to ease changing security level
Public bug reported: openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Summary changed: - please sync openssl.cnf to ease changing security level + [openssl3] please sync openssl.cnf to ease changing security level -- 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/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level Status in openssl package in Ubuntu: New Bug description: openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 940230] Re: openssl on 64bit is much slower than before
Can you still reproduce this issue on a newer and supported Ubuntu release? ** Changed in: openssl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/940230 Title: openssl on 64bit is much slower than before Status in openssl package in Ubuntu: Incomplete Bug description: Posting output of openssl speed on precise alpha and 10.04. Some quick googling seems to indicate issues with 64bit asm vs. the C version (might be a good idea to disable 64bit asm). This is on a processor *without* AES-NI (which is still very common). Precise: type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 61725.52k67902.33k69264.13k 146084.86k 148518.23k aes-192 cbc 5.95k56592.77k57542.04k 122330.11k 125277.32k aes-256 cbc 44912.70k48644.01k49539.94k 105978.88k 107372.74k Lucid: type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes aes-128 cbc 74876.87k 118355.41k 138862.76k 144140.50k 141562.78k aes-192 cbc 82093.08k 110813.18k 120764.33k 118315.44k 118527.32k aes-256 cbc 74760.65k96842.01k 104520.45k 106615.81k 103481.34k ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: openssl 1.0.0g-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Fri Feb 24 02:33:44 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1) ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/940230/+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 1608200] Re: please merge openssl from Debian
Latest merge from Debian was in openssl (3.0.0-1ubuntu1), can we close this now? -- 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/1608200 Title: please merge openssl from Debian Status in openssl package in Ubuntu: Incomplete Bug description: I'm not aware of any ABI breakages, but I bumped the shlibs min version anyway. Please triple check + dh_makeshlibs -a -V "libssl1.0.0 (>= 1.0.2h)" --add-udeb="libcrypto1.0.0-udeb" -Xengines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1608200/+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 955675] Re: openssl s_client's '-ssl2' option no longer works in 12.04
This was already replied by Seth Arnold. Additionally, what was missing was "to remove '-ssl2' from the usage string and man pages". This is also already done (checked on both 20.04/focal and 22.04/jammy). ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released -- 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/955675 Title: openssl s_client's '-ssl2' option no longer works in 12.04 Status in openssl package in Ubuntu: Fix Released Bug description: the s_client(1) man page describes -tls1, -ssl3 and -ssl2. The latter isn't recognised by openssl in 12.04: aj@aj-Vostro-260:~$ openssl version OpenSSL 1.0.0g 18 Jan 2012 aj@aj-Vostro-260:~$ openssl s_client -ssl2 unknown option -ssl2 usage: s_client args aj@aj-Vostro-260:~$ openssl s_client -ssl3 connect: Connection refused connect:errno=111 aj@aj-Vostro-260:~$ openssl s_client -tls1 connect: Connection refused connect:errno=111 aj@aj-Vostro-260:~$ This option should still continue to work, please do not leave disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/955675/+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 1590163] Re: disable export grade ciphers
This was done in Ubuntu jammy/22.04. See release notes: https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668 Security Level 2 is now enforced, see here for some more info: https://www.openssl.org/docs/man3.0/man3/SSL_CTX_set_security_level.html ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released -- 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/1590163 Title: disable export grade ciphers Status in openssl package in Ubuntu: Fix Released Bug description: # System device: Aquaris BQ E4.5 OS: Ubuntu 15.04, OTA-11 OpenSSL version: $dpkg --list |grep libssl ii libssl1.0.0:armhf1.0.1f-1ubuntu11.6 armhfSecure Sockets Layer toolkit - shared libraries # Observed behaviour OpenSSL provides export grade ciphers: $openssl ciphers -v EXP EXP-EDH-RSA-DES-CBC-SHA SSLv3 Kx=DH(512) Au=RSA Enc=DES(40) Mac=SHA1 export EXP-EDH-DSS-DES-CBC-SHA SSLv3 Kx=DH(512) Au=DSS Enc=DES(40) Mac=SHA1 export EXP-ADH-DES-CBC-SHA SSLv3 Kx=DH(512) Au=None Enc=DES(40) Mac=SHA1 export EXP-DES-CBC-SHA SSLv3 Kx=RSA(512) Au=RSA Enc=DES(40) Mac=SHA1 export EXP-RC2-CBC-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export EXP-ADH-RC4-MD5 SSLv3 Kx=DH(512) Au=None Enc=RC4(40) Mac=MD5 export EXP-RC4-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export # Expected behaviour No export grade ciphers are provided in binaries. # Rationale Export grade ciphers are insecure. By design. In response to FREAK and Logjam attacks, OpenSSL developers disabled export grade ciphers in OpenSSL v1.0.1m (March 2015), cf. https://www.openssl.org/blog/blog/2015/05/20/logjam-freak-upcoming-changes/>. To bypass similar future attacks, deactivation of export grade ciphers should be backported to 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1590163/+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
both files from /lib/systemd/system/> < >pcscd.service< [Unit] Description=PC/SC Smart Card Daemon Requires=pcscd.socket Documentation=man:pcscd(8) [Service] ExecStart=/usr/sbin/pcscd --foreground --auto-exit $PCSCD_ARGS ExecReload=/usr/sbin/pcscd --hotplug EnvironmentFile=-/etc/default/pcscd [Install] Also=pcscd.socket >pcscd.socket< [Unit] Description=PC/SC Smart Card Daemon Activation Socket [Socket] ListenStream=/run/pcscd/pcscd.comm SocketMode=0666 [Install] WantedBy=sockets.target -- 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 1972055] [NEW] [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: After upgrading Carbon X1 gen 9 to Ubuntu 22.04 (from 20.04), there appeared strange problem with speaker sound in video conferences (Zoom) and also with Chrome (for example YouTube & Preply). The problem is as following: the speaker sound level is reduced when somebody speaks after a gap of silence, then the sound level is quickly increased to normal level. This creates the very strange fluctuating up/down sound level which when sound level is low at the start of each sentence. This problem was not there with Ubuntu 20.04 on the same laptop. This problem is also not presented when using Zoom with Windows 11 on the same machine. Thank you for your consideration. Best regards, Rustem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rustem 1576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 7 11:24:53 2022 InstallationDate: Installed on 2022-04-23 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: May 07 11:15:06 rox1 pulseaudio[1002]: After module unload, module 'module-null-sink' was still loaded! Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XXS62S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS62S00:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS62S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XXS62S00 dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1972055 Title: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: After upgrading Carbon X1 gen 9 to Ubuntu 22.04 (from 20.04), there appeared strange problem with speaker sound in video conferences (Zoom) and also with Chrome (for example YouTube & Preply). The problem is as following: the speaker sound level is reduced when somebody speaks after a gap of silence, then the sound level is quickly increased to normal level. This creates the very strange fluctuating up/down sound level which when sound level is low at the start of each sentence. This problem was not there with Ubuntu 20.04 on the same laptop. This problem is also not presented when using Zoom with Windows 11 on the same machine. Thank you for your consideration. Best regards, Rustem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rustem 1576 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 7 11:24:53 2022 InstallationDate: Installed on 2022-04-23 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: May 07 11:15:06 rox1 pulseaudio[1002]: After module unload, module 'module-null-sink' was still loaded!
[Touch-packages] [Bug 834556] Re: package libssl1.0.0 1.0.0d-2ubuntu2 failed to install/upgrade: libssl1.0.0:i386 1.0.0d-2ubuntu2 (Multi-Arch
This issue is now obsolete, please use a newer Ubuntu release. ** Changed in: openssl (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/834556 Title: package libssl1.0.0 1.0.0d-2ubuntu2 failed to install/upgrade: libssl1.0.0:i386 1.0.0d-2ubuntu2 (Multi-Arch Status in openssl package in Ubuntu: Invalid Bug description: just did a dist upgrade of an earlier oneiric installation ProblemType: Package DistroRelease: Ubuntu 11.10 Package: libssl1.0.0 1.0.0d-2ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 Date: Fri Aug 26 09:17:02 2011 DpkgTerminalLog: Vorbereitung zum Ersetzen von console-setup 1.57ubuntu21 (durch .../console-setup_1.57ubuntu25_all.deb) ... Ersatz für console-setup wird entpackt ... Vormals abgewähltes Paket libssl1.0.0:i386 wird gewählt. dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/libssl1.0.0_1.0.0d-2ubuntu2_i386.deb (--unpack): libssl1.0.0:i386 1.0.0d-2ubuntu2 (Multi-Arch: same) is not co-installable with libssl1.0.0:amd64 1.0.0d-2ubuntu1 (Multi-Arch: no) which is currently installed ErrorMessage: libssl1.0.0:i386 1.0.0d-2ubuntu2 (Multi-Arch InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) SourcePackage: openssl Title: package libssl1.0.0 1.0.0d-2ubuntu2 failed to install/upgrade: libssl1.0.0:i386 1.0.0d-2ubuntu2 (Multi-Arch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/834556/+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 963420] Re: https download performance significantly worse in precise than lucid
Can you still reproduce this issue on a newer and supported Ubuntu release? ** Changed in: openssl (Ubuntu) Status: Confirmed => Incomplete ** Changed in: wget (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/963420 Title: https download performance significantly worse in precise than lucid Status in openssl package in Ubuntu: Incomplete Status in wget package in Ubuntu: Invalid Bug description: In Canonical's openstack installation, I noticed during publishing images that downloads on lucid seemed to occur faster than I could do the same download on precise. $ wget https://cloud-images.ubuntu.com/precise/current/precise-server- cloudimg-amd64-disk1.img -O /dev/null In the above, cloud-images.ubuntu.com is located very close to the instance running, such that on lucid I routinely get > 40M/s. However, on precise I routinely top out at 10M/s, with the highest I've ever seen at 19M/s. I once saw 49M/s on lucid. very strangely (and thus making this harder to isolate), if I change 'https' above to 'http', both lucid and precise download in the 65-80M/S range. Ie, https download is significantly slower in precise compared to lucid. One likely unrelated point, in EC2, using the url https://ubuntu-data.s3.amazonaws.com/ebs/ubuntu-images/ubuntu-lucid-10.04-amd64-server-20100427.1.img.tar.gz from a m1.large instance, lucid and precise are both getting in the 25-30M/s range. With the http url they both get in the 40M/s range. Ie, there seems no real difference on EC2. I do realize that this is difficult to isolate, and it is even possible that my results are affected by other guests on the same host or load on the http server at that time. However, the results have been very consistent over multiple days, over new instances. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-20-virtual 3.2.0-20.32 ProcVersionSignature: User Name 3.2.0-20.32-virtual 3.2.12 Uname: Linux 3.2.0-20-virtual x86_64 AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 1.95-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 21.910968] init: plymouth-upstart-bridge main process (712) killed by TERM signal Date: Fri Mar 23 19:29:54 2012 Ec2AMI: ami- Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Bochs Bochs PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-virtual root=UUID=bc55866c-8487-44b6-b0c7-56deac8b6a38 ro console=ttyS0 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/963420/+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 621125] Re: package libssl0.9.8 0.9.8k-7ubuntu8 failed to install/upgrade: ErrorMessage: пакунок libssl0.9.8 вже встановлено та налаштовано
This issue is now obsolete, please use a newer Ubuntu release. ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/621125 Title: package libssl0.9.8 0.9.8k-7ubuntu8 failed to install/upgrade: ErrorMessage: пакунок libssl0.9.8 вже встановлено та налаштовано Status in openssl package in Ubuntu: Invalid Bug description: Binary package hint: openssl Ubuntu 10.04 LTS libssl0.9.8 0.9.8k-7ubuntu8 Installation hangs up while updating linux-image-2.6.32-24-generic, which libssl depends from. Last lines of log: Running postrm hook script /usr/sbin/update-grub. Generating grub.cfg ... Found linux image: /boot/vmlinuz-2.6.32-24-generic Found initrd image: /boot/initrd.img-2.6.32-24-generic Found linux image: /boot/vmlinuz-2.6.32-23-generic Found initrd image: /boot/initrd.img-2.6.32-23-generic Found linux image: /boot/vmlinuz-2.6.32-22-generic Found initrd image: /boot/initrd.img-2.6.32-22-generic Found linux image: /boot/vmlinuz-2.6.32-21-generic Found initrd image: /boot/initrd.img-2.6.32-21-generic Found memtest86+ image: /boot/memtest86+.bin ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libssl0.9.8 0.9.8k-7ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Aug 20 15:31:50 2010 ErrorMessage: ErrorMessage: пакунок libssl0.9.8 вже встановлено та налаштовано InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: openssl Title: package libssl0.9.8 0.9.8k-7ubuntu8 failed to install/upgrade: ErrorMessage: пакунок libssl0.9.8 вже встановлено та налаштовано To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/621125/+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 675355] Re: package libbind9-30 1:9.4.2.dfsg.P2-2ubuntu0.5 failed to install/upgrade: dependency problems - leaving unconfigured
This issue is now obsolete, please use a newer Ubuntu release. ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/675355 Title: package libbind9-30 1:9.4.2.dfsg.P2-2ubuntu0.5 failed to install/upgrade: dependency problems - leaving unconfigured Status in openssl package in Ubuntu: Invalid Bug description: Binary package hint: bind9 I have reported many of these failures, but they never end. Why can't you bundle them when they are all produced during an upgrade. I have no info about them. I do not have time to keep reporting them. ProblemType: Package Architecture: amd64 Date: Sat Nov 13 20:54:20 2010 DistroRelease: Ubuntu 8.04 ErrorMessage: dependency problems - leaving unconfigured Package: libbind9-30 1:9.4.2.dfsg.P2-2ubuntu0.5 PackageArchitecture: amd64 SourcePackage: bind9 Title: package libbind9-30 1:9.4.2.dfsg.P2-2ubuntu0.5 failed to install/upgrade: dependency problems - leaving unconfigured Uname: Linux 2.6.24-28-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/675355/+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
Thanks. Not really a bug thus, I need to provide rmd160 digests in some workflow. This is a work-around and a good reason to discuss the issue upstream. -- 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
