[Touch-packages] [Bug 2003996] Re: /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_op
This bug was fixed in the package software-properties - 0.99.32 --- software-properties (0.99.32) lunar; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Thu, 02 Feb 2023 15:37:06 +0100 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Jammy: Fix Committed Bug description: * Impact An error is triggered when opening the 'Enable Ubuntu Pro' dialog on a system not connected to internet * Test case Start software-properties-gtk on a offline system, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 * Regression potential The fix is making the magic token request conditional to the connectivity status, if that was wrong we could end up in a situation where we should display a pincode but don't. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogUaAttach.py", line 144, in poll_for_magic_token response = wait(options) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 57, in wait return _wait(options, UAConfig()) File "/usr/lib/python3/dist-packages/uaclient/api/u/pro/attach/magic/wait/v1.py", line 73, in _wait wait_resp = contract.get_magic_attach_token_info( File "/usr/lib/python3/dist-packages/uaclient/contract.py", line 202, in get_magic_attach_token_info response, _ = self.request_url( File "/usr/lib/python3/dist-packages/uaclient/serviceclient.py", line 72, in request_url response, headers = util.readurl( File "/usr/lib/python3/dist-packages/uaclient/util.py", line 324, in readurl resp = request.urlopen(req, timeout=timeout) File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1352, in do_open r = h.getresponse() File "/usr/lib/python3.10/http/client.py", line 1374, in getresponse response.begin() File "/usr/lib/python3.10/http/client.py", line 318, in begin version, status, reason = self._read_status() File "/usr/lib/python3.10/http/client.py", line 279, in _read_status line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") File "/usr/lib/python3.10/socket.py", line 705, in readinto return self._sock.recv_into(b) File "/usr/lib/python3.10/ssl.py", line 1274, in recv_into return self.read(nbytes, buffer) File "/usr/lib/python3.10/ssl.py", line 1130, in read return self._sslobj.read(len, buffer) TimeoutError: The read operation timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state
This bug was fixed in the package software-properties - 0.99.32 --- software-properties (0.99.32) lunar; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Thu, 02 Feb 2023 15:37:06 +0100 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004245 Title: /usr/bin/software-properties- gtk:AttributeError:on_radio_toggled:update_state Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Jammy: Fix Committed Bug description: * Impact An error is triggered when fetching a pin from the Ubuntu Pro server is failing * Test case Start software-properties-gtk on a system offline or having internet connectivity issue, go to the Ubuntu Pro tab, click 'Enable Ubuntu Pro', check that no error report dialog is displayed Verify the error track to ensure there is no report with the new version https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 * Regression potential The fix for that specific issue is to set an initial value to the pin label. If the change of value would confuse some code it would be visible in the Pin section of the Ubuntu Pro tab not reflected the pin code from the server as expected --- The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/0d4bb9d499df175309552a99a411e2909a88fab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004634] Re: Disable Ubuntu Pro registration when not online
This bug was fixed in the package software-properties - 0.99.32 --- software-properties (0.99.32) lunar; urgency=medium [ Nathan Pratta Teodosio ] * Disable the Ubuntu Pro UI with an explanation when not connected (lp: #2004634) * Catch exceptions to wait (lp: #2003996) * Initialize pin as empty string (lp: #2004245) -- Sebastien Bacher Thu, 02 Feb 2023 15:37:06 +0100 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2004634 Title: Disable Ubuntu Pro registration when not online Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Jammy: Fix Committed Bug description: * Impact The current UI allows the user to try to register to Ubuntu Pro even when the system isn't online, which eventually leads to an error since the client fails to contact the server. The updated design disable the registration UI in those cases and inform the user they need to get online to be able to register which is a better experience. * Test Case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - disconnect the system, using for example the top panel indicator - start software-properties-gtk and select the Ubuntu Pro tab - click 'Enable Ubuntu Pro' - The dialog controls should be disabled and a string 'Unable to connect to Ubuntu Pro servers. Check your internet connection.' displayed at the bottom - reconnect the system - the dialog control should become active and the label be removed - register to Ubuntu Pro, that should be working * Regression potential If the connectivity check was wrong or not reliable it could be that the dialog controls would be disabled even if the system is online, or that it would fail to detect that the system isn't connected and let the user try to register anyway. The change also adds a new translatable string. Since currently we don't include translations for that new UI it isn't really a regression. We still plan to fix that by the next languagepack update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004634/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Tested on machine with FM350 installed, with oem 6.0.0-1006 kernel, modem manager 1.20.0-1~ubuntu22.04.1, libmbim-glib4 1.28.0-1~ubuntu20.04 and libqmi-glib5 1.32.0-1~ubuntu0.22.04.1. System can connect to 5g network. --- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: b429ecd3cf5b14431f765b3a415cda29db1d504b --- Hardware | manufacturer: generic | model: MBIM [14C3:4D75] | firmware revision: 81600..00.29.21.24_GC | D47 | h/w revision: V1.0.6 | supported: gsm-umts, lte, 5gnr |current: gsm-umts, lte, 5gnr | equipment id: 358198520003138 --- System| device: /sys/devices/pci:00/:00:1c.0/:71:00.0 |drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) --- Status| lock: sim-pin2 | unlock retries: sim-pin2 (3) | state: connected |power state: on |access tech: lte, 5gnr | signal quality: 64% (cached) --- Modes | supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: none | allowed: 5g; preferred: none | allowed: 3g, 5g; preferred: none | allowed: 4g, 5g; preferred: none | allowed: 3g, 4g, 5g; preferred: none |current: allowed: 3g, 4g, 5g; preferred: none --- IP| supported: ipv4, ipv6, ipv4v6 --- 3GPP | imei: 358198520003138 | enabled locks: fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached --- 3GPP EPS | ue mode of operation: csps-2 |initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: internet | initial bearer ip type: ipv4v6 --- 3GPP 5GNR | mico mode: disabled --- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 --- Bearer| paths: /org/freedesktop/ModemManager1/Bearer/1 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device
[Touch-packages] [Bug 2007837] Re: 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression
Thanks for the links Peter. Looking at the upstream patch, it looks straightforward enough, but can you also provide more detailed steps to reproduce this issue? I gather this would involve setting up a 20.04 host and 22.04 clients, running Backuppc on the latter to pull data from the former. If you can provide a reproducer that'd help accelerate progress towards getting a fix prepared for backporting. Thanks ahead of time. ** Changed in: rsync (Ubuntu Jammy) Status: New => Incomplete -- 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/2007837 Title: 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression Status in rsync package in Ubuntu: New Status in rsync source package in Jammy: Incomplete Status in rsync package in Debian: Unknown Bug description: rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling, leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04) to surface [1]. It practically makes using BackupPC 3 impossible with clients using rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04 can't be used to back up machines with 22.04 is rather surprising and has bitten other users [2]. It's unclear whether the bug will be fixed in 18.04's and 20.04's libfile-rsyncp-perl package (for status, see [3]). Because of this, the rsync maintainer has included a patch in 3.2.4 that fixes this regression [4] (even though not strictly an rsync bug). As a result, rsync 3.2.3 is the only affected version, which happens to be the one packaged in 22.04. This report is to request backporting that fix [4] to Ubuntu 22.04, so that things don't silently break in scenarios where the backup server is left at 20.04, and some backup clients happen to upgrade to 22.04. I'm not sure what the criteria for security releases are, but as the issue causes backup denial of service and has easy mitigation, I think it would make sense to put it through the security channel. [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358 [2]: https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html [3]: https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833 [4]: https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 2007837] Re: 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression
** Also affects: rsync (Ubuntu Jammy) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #969463 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969463 ** Also affects: rsync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969463 Importance: Unknown Status: Unknown -- 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/2007837 Title: 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression Status in rsync package in Ubuntu: New Status in rsync source package in Jammy: New Status in rsync package in Debian: Unknown Bug description: rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling, leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04) to surface [1]. It practically makes using BackupPC 3 impossible with clients using rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04 can't be used to back up machines with 22.04 is rather surprising and has bitten other users [2]. It's unclear whether the bug will be fixed in 18.04's and 20.04's libfile-rsyncp-perl package (for status, see [3]). Because of this, the rsync maintainer has included a patch in 3.2.4 that fixes this regression [4] (even though not strictly an rsync bug). As a result, rsync 3.2.3 is the only affected version, which happens to be the one packaged in 22.04. This report is to request backporting that fix [4] to Ubuntu 22.04, so that things don't silently break in scenarios where the backup server is left at 20.04, and some backup clients happen to upgrade to 22.04. I'm not sure what the criteria for security releases are, but as the issue causes backup denial of service and has easy mitigation, I think it would make sense to put it through the security channel. [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358 [2]: https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html [3]: https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833 [4]: https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 1802718] Re: Allow people to do sudo apt-get build-dep without any further configuration
@Julian Andres Klode: If I understand pull-lp-source's man page correctly, pull-lp-source is not at all a substitute for apt-get build-dep. The latter will install *and update* the relevant source code, so that your dependencies are as secure as the rest of the repository. The former provides a one-off download of the source code. You will not automatically be provided with fixes for that code. -- 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/1802718 Title: Allow people to do sudo apt-get build-dep without any further configuration Status in software-properties package in Ubuntu: Confirmed Bug description: Or provide a reliable CLI method, a direct sed on /etc/atp/sources.list does not feel clean. Motivation: https://askubuntu.com/questions/496549/error-you-must-put- some-source-uris-in-your-sources-list This is specially important for Docker, but also a big annoyance on desktop, as there is no clean CLI way of enabling it. Why not just enable by default and save people the trouble? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1802718/+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 1915910] Update Released
The verification of the Stable Release Update for evince has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Committed Status in evince source package in Kinetic: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
This bug was fixed in the package evince - 43.0-1ubuntu1 --- evince (43.0-1ubuntu1) kinetic; urgency=medium * debian/apparmor-profile: - allow access to the libproxy helper pxgsettings which is needed on some configuration to access remote printers (LP: #1915910) -- Sebastien Bacher Thu, 08 Dec 2022 20:37:29 +0100 ** Changed in: evince (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Committed Status in evince source package in Kinetic: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1960736] Re: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 )
Hi Bartłomiej, NSS is in the regular mozilla bugzilla at https://bugzilla.mozilla.org/home. You can file or search for bugs related to NSS by specifying "NSS" as the Product, e.g.: https://bugzilla.mozilla.org/buglist.cgi?resolution=---_format=advanced=NSS=Importance=Client%20Software=Developer%20Infrastructure=Components=Server%20Software=Other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1960736 Title: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 ) Status in nss package in Ubuntu: New Bug description: I've got the issue with Google Chrome not recognizing any of SSL/TSL certificates as trusted. When I look into certificate checksums it's renders all bytes of it as NULL bytes. I'm aware Google Chrome is proprietary but it depends on ubuntu provided libnss3-package. And libnss provides very nigmatic error code -8018: `/opt/google/chrome$ google-chrome [23391:23426:0213/133531.202486:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018 [23434:23434:0213/133531.266711:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [23391:23427:0213/133531.313065:ERROR:cert_verify_proc_builtin.cc(681)] CertVerifyProcBuiltin for accounts.google.com failed: - Certificate i=3 (CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE) - ERROR: No matching issuer found ' When trying to enter this particular error code into search engine nothing is found. So my suggestion with this bug is to make it more transparent by providing information to what happened - it seems other bug codes has better error messages. To get SEC_ERROR_UNKNOWN_PKCS11_ERROR string I was force to download source code and manually calculate offsets. Another issue is if failing to initialize PKCS11 token should make whole SSL/TLS crypto invalid ? I'm not sure if this is libnss or Google Chrome issue but it behaves differently in Chromium browser with same libnss so I assume either of two is doing better - it's worth to review this from security perspective. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libnss3 2:3.35-2ubuntu2.13 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 13 13:33:51 2022 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.5 [origin: LP-PPA-ubuntu-security-proposed] libgcc1 1:8.4.0-1ubuntu1~18.04 libnspr4 2:4.18-1ubuntu1 libsqlite3-0 3.22.0-1ubuntu0.4 InstallationDate: Installed on 2015-05-08 (2473 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: nss UpgradeStatus: Upgraded to bionic on 2018-08-26 (1266 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1960736/+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 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I'm having similar issues. Following what Fabio mentioned, I think I had a firewall issue but disabling the firewall was not enough, I needed to restart the wifi after disabling the firewall. I guess that is the sequence which addresses the problem for Fabio too. -- 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/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
All tests succeeded, marking verification done.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Committed
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that provides SCRAM in jammy
$ sudo apt install libsasl2-modules-gssapi-mit
# Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
mit:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64:
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
# list installed sasl2 packages:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
# dist-upgrade or install the new sasl2 packages from proposed
# Confirm the same packages are installed as before the upgrade, just at
their newer versions:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
# Confirm the scram mechanism is still there, as before:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
# But now it belongs to the libsasl2-modules package:
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
b) Following (a), perform a release-upgrade to kinetic, and confirm
that the same sasl2 packages remain installed, but now at the kinetic
version:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2
And that the scram mechanism is there, and still belongs to the
libsasl2-modules package:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
c) A jammy system WITHOUT the SCRAM mechanism available (i.e.,
libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM
available after the upgrade, but without installing any new package.
# Start with these sasl2 packages installed on jammy:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
# Confirm SCRAM is not installed:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such
file or directory
# Upgrade to the packages in proposed
# Confirm no new sasl2 packages were installed:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
# Verify that SCRAM is now available, and part of the libsasl2-modules
package:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S
[Touch-packages] [Bug 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
Jammy verification (continued), test (d)
d) It's now possible to have SCRAM and gssapi heimdal mechanisms
installed at the same time
Start with SCRAM available on jammy, by installing the gssapi-mit
package:
$ sudo apt install libsasl2-modules-gssapi-mit
...
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Oct 19 21:06
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Confirming that installing libsasl2-modules-gssapi-heimdal from jammy removes
libsasl2-modules-gssapi-mit:
$ sudo apt install libsasl2-modules-gssapi-heimdal
(...)
The following packages will be REMOVED:
libsasl2-modules-gssapi-mit
And that removes the SCRAM module with it.
Switching to jammy-proposed, however, while still removing
libsasl2-modules-gssapi-mit, will NOT remove the SCRAM module:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-heimdal:amd64 2.1.27+dfsg2-3ubuntu1.2
$ apt-cache policy libsasl2-modules
libsasl2-modules:
Installed: 2.1.27+dfsg2-3ubuntu1.2
Candidate: 2.1.27+dfsg2-3ubuntu1.2
Version table:
*** 2.1.27+dfsg2-3ubuntu1.2 500
500 http://br.archive.ubuntu.com/ubuntu jammy-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.1.27+dfsg2-3ubuntu1.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
2.1.27+dfsg2-3ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
And even though we no longer have libsasl2-modules-gssapi-mit (due to
the expected conflict with -heimdal), the SCRAM module is available:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Dec 12 11:52
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Now performing a release upgrade to kinetic with the system in the above state:
- like before, the summary presents that two (unrelated to cyrus-sasl2)
packages will be removed
- in the end, 13 unrelated packages were removed:
13 packages are going to be removed.
Continue [yN] Details [d]d
Remove (was auto installed) binutils binutils-common
binutils-x86-64-linux-gnu inetutils-telnet libbinutils
libctf-nobfd0 libctf0 libdns-export1110 libgprofng0 libicu70
libisc-export1105 python3-openssl telnet
After the release upgrade, these were the sasl2 packages installed (from
kinetic):
$ dpkg -l | grep sasl2 | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-gssapi-heimdal:amd64 2.1.28+dfsg-6ubuntu2
$ apt-cache policy libsasl2-modules
libsasl2-modules:
Installed: 2.1.28+dfsg-6ubuntu2
Candidate: 2.1.28+dfsg-6ubuntu2
Version table:
*** 2.1.28+dfsg-6ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
And SCRAM remained available:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 2022
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Test (d) succeeded.
--
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/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Committed
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that
[Touch-packages] [Bug 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
Jammy verification (continued), test (c)
c) A jammy system WITHOUT the SCRAM mechanism available (i.e.,
libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM available
after the upgrade, but without installing any new package.
Starting on jammy with these installed:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
SCRAM is not available:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such file
or directory
Enabling proposed and installing the same packages from proposed:
$ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db
(...)
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
Same packages are installed, just a new updated version, and now we have SCRAM
available:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Dec 12 11:52
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Performing a release upgrade to kinetic:
- in the summary, two unrelated packages are going to be removed
- in the end, 13 unrelated packages were removed:
13 packages are going to be removed.
Continue [yN] Details [d]d
Remove (was auto installed) binutils binutils-common
binutils-x86-64-linux-gnu inetutils-telnet libbinutils
libctf-nobfd0 libctf0 libdns-export1110 libgprofng0 libicu70
libisc-export1105 python3-openssl telnet
No new sasl2 package were installed, they just were updated to the kinetic
version:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
$ apt-cache policy libsasl2-modules
libsasl2-modules:
Installed: 2.1.28+dfsg-6ubuntu2
Candidate: 2.1.28+dfsg-6ubuntu2
Version table:
*** 2.1.28+dfsg-6ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
And SCRAM remains available and part of libsasl2-modules:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 2022
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Test (c) succeeded.
--
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/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Committed
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that provides SCRAM in jammy
$ sudo apt install libsasl2-modules-gssapi-mit
# Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
mit:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64:
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
# list installed sasl2 packages:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
# dist-upgrade or install the new sasl2 packages from proposed
# Confirm the same packages are installed as before the upgrade, just at
their newer
[Touch-packages] [Bug 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
Jammy verification (continued), test (b)
b) On the heels of the (a) test, release upgrade to kinetic
The summary two packages are going to be removed, not related to cyrus-sasl2.
At the end, 13 packages were going to be removed, also not related to
cyrus-sasl2:
13 packages are going to be removed.
Continue [yN] Details [d]d
Remove (was auto installed) binutils binutils-common
binutils-x86-64-linux-gnu inetutils-telnet libbinutils
libctf-nobfd0 libctf0 libdns-export1110 libgprofng0 libicu70
libisc-export1105 python3-openssl telnet
After the release upgrade, we got the kinetic version of the cyrus-sasl2
packages installed as expected:
root@j-sasl-scram:~# dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2
root@j-sasl-scram:~# apt-cache policy libsasl2-modules
libsasl2-modules:
Installed: 2.1.28+dfsg-6ubuntu2
Candidate: 2.1.28+dfsg-6ubuntu2
Version table:
*** 2.1.28+dfsg-6ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
And SCRAM is part of libsasl2-modules as expected:
root@j-sasl-scram:~# ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 2022
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
root@j-sasl-scram:~# dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Test (b) succeeded.
--
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/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Committed
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that provides SCRAM in jammy
$ sudo apt install libsasl2-modules-gssapi-mit
# Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
mit:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64:
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
# list installed sasl2 packages:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
# dist-upgrade or install the new sasl2 packages from proposed
# Confirm the same packages are installed as before the upgrade, just at
their newer versions:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
# Confirm the scram mechanism is still there, as before:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
# But now it belongs to the libsasl2-modules package:
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
b) Following (a), perform a release-upgrade to kinetic, and confirm
that the same sasl2 packages remain installed, but now at the kinetic
version:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2
And that the scram mechanism is there, and still belongs to the
[Touch-packages] [Bug 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims
Jammy verification, test by test. First, (a):
a) SCRAM remains installed
Installed libsasl2-modules-gssapi-mit package from jammy, and confirmed scram
is part of it:
ubuntu@j-sasl-scram:~$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Oct 19 21:06
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
ubuntu@j-sasl-scram:~$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
ubuntu@j-sasl-scram:~$ apt-cache policy libsasl2-modules-gssapi-mit
libsasl2-modules-gssapi-mit:
Installed: 2.1.27+dfsg2-3ubuntu1.1
Candidate: 2.1.27+dfsg2-3ubuntu1.1
Version table:
*** 2.1.27+dfsg2-3ubuntu1.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.1.27+dfsg2-3ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Updated to the packages from proposed:
$ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db
libsasl2-modules-gssapi-mit
...
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
SCRAM remains installed, but now belongs to libsasl2-modules:
ubuntu@j-sasl-scram:~$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Dec 12 11:52
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
ubuntu@j-sasl-scram:~$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
Test (a) succeeded.
--
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/1988730
Title:
package libsasl2-modules provides only unsafe SASL bind mechanims
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Jammy:
Fix Committed
Status in cyrus-sasl2 package in Debian:
Fix Released
Bug description:
[ Impact ]
The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
should be in libsasl2-modules.
Normally this would just be an annoyance, but it just so happens that
this also prevents to have the SCRAM mechanism coexist with the GSSAPI
Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
with each other.
This change is moving a file from one package to another, so
appropriate breaks/replaces changes have to be made. This move follows
case #10 from the package transition table[1].
[ Test Plan ]
This test plan revolves around dependency checking and upgrades, to make sure
we don't:
- have conflicting files which would break an upgrade
- have no loss of functionality after an upgrade (since a plugin moved
between packages)
a) SCRAM remains installed
# Install the package that provides SCRAM in jammy
$ sudo apt install libsasl2-modules-gssapi-mit
# Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
mit:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules-gssapi-mit:amd64:
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
# list installed sasl2 packages:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
# dist-upgrade or install the new sasl2 packages from proposed
# Confirm the same packages are installed as before the upgrade, just at
their newer versions:
libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
# Confirm the scram mechanism is still there, as before:
$ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
lrwxrwxrwx 1 root root 18 Aug 16 20:08
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
# But now it belongs to the libsasl2-modules package:
$ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
b) Following (a), perform a release-upgrade to kinetic, and confirm
that the same sasl2 packages remain installed, but now at the kinetic
version:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
libsasl2-modules-db:amd64
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
Thanks! New changelog looks good, I am uploading it now, with a slight change to split one of the lines that was long and generating a lintian error. -- 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/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+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 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
The detected regression looks like a false-positive caused by another dependency. The reported error is `/bin/sh: 1: python: not found` which does not seem to be caused by the changes in libunwind. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Kinetic: Fix Committed Bug description: [ Impact ] * On kernels with page size > 4K Xorg (and presumably other applications relying on libunwind) crashes on startup. This affects anyone running the official arm64 generic-64k kernel or custom non 4k kernels (as used by e.g. apple silicon). The exact error I am seeing in the logs is: Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab456ca998] Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) unw_get_proc_info failed: no unwind info found [-10] Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Segmentation fault at address 0x0 Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Fatal server error: Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Caught signal 11 (Segmentation fault). Server aborting Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Please consult the The X.Org Foundation support Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: at http://wiki.x.org Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: for help. Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) I have not found a workaround other than using wayland (which has other limitations). To reproduce use a kernel configured with a page size of 16K (CONFIG_ARM64_16K_PAGES=y or CONFIG_ARM64_64K_PAGES=y or) and try to start "Ubuntu on Xorg" in gdm. [ Test Plan ] * Make sure Xorg doesn't crash on 4K, 16K and 64K kernels. [ Where problems could occur ] * We will have to make sure the fixed version still works with 4k kernels. The patch is already widely in use so the risk seems low if we test properly. [ Other Info ] * The lunar version ships the bug fix synced from debian * Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1026217 * Upstream fix: https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+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 2006954] Re: openssl: merge unstable's 3.0.8-1
Uploaded, thanks! ** Changed in: openssl (Ubuntu) Status: New => Fix Committed -- 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/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: Fix Committed Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+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 2007698] Re: Please merge 1.9.13p1-1 into lunar
Hi Marc, thanks a lot for taking a look at this. I misunderstood how the changelog must be constructed. I believe the Build-Conflicts can just be dropped as the problem with fakeroot was fixed (LP: #1915250) and sudo doesn't require root to be built anymore (and the file permissions seem to be correct in my PPA). I updated the merge request. Thanks! -- 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/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+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 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)
Also affects on 22.04.2, been encountering this bug for the 2 years I've been having my Dell XPS 17. -- 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/1576844 Title: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly) Status in xorg package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 Several times yesterday and today (April 28-29, 2016) the touchpad (trackpad) on the Dell XPS 13 9343 has frozen. Other functions (keyboard, screen, etc.) have been fine but the pointer has been frozen in place. Then after 1-3 minutes functionality returns. Thank you very much for your assistance and I'd be happy to provide more information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,composite,opengl,cube,rotate] CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Fri Apr 29 16:09:32 2016 DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665] InstallationDate: Installed on 2015-08-06 (267 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 27 15:54:22 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5152 vendor SHP xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576844/+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 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Okay. I got some pcaps now. And apparently our apt-cacher-ng proxy
sometimes serves:
- an InRelease
- with a 200 OK
- and a non-zero Content-Length
- BUT, no content, but instead a TCP-FIN.
Under the right circumstances, this causes apt to stall forever.
The right circumstances seem to include:
- a valid download (or 304) from the same host
- a valid download from another host
---
I created a test server, and got this to reproduce with apt 2.4.9 (from
jammy-proposed):
=
sources.list
=
deb http://junk.devs.nu:3851/ubuntu jammy main
deb http://junk.devs.nu:3851/ubuntu jammy-updates main
deb [arch=amd64 signed-by=/etc/apt/keyrings/zabbix.gpg]
http://repo.zabbix.com/zabbix/6.2/ubuntu jammy main
=
server.py logs
=
13:31:58 [2771009] client connected: ('217.21.199.56', 42838)
13:31:58 [2771009] client said: b'GET /ubuntu/dists/jammy/InRelease
HTTP/1.1\r\nHost: junk.devs.nu:3851\r\nCache-Control: max-age=0\r\nAccept:
text/*\r\nUser-Agent: Debian APT-HTTP/1.3 (2.4.9) non-interactive\r\n\r\n'
13:31:58 [2771009] we say: 200 and serve local InRelease
13:31:58 [2771009] client said: b'GET /ubuntu/dists/jammy-updates/InRelease
HTTP/1.1\r\nHost: junk.devs.nu:3851\r\nCache-Control: max-age=0\r\nAccept:
text/*\r\nUser-Agent: Debian APT-HTTP/1.3 (2.4.9) non-interactive\r\n\r\n'
13:31:58 [2771009] we say: 200 but serve a FIN
13:31:58 [2771009] client said: b''
13:31:58 [2771009] client disconnected: ('217.21.199.56', 42838)
=
apt-get update -o Debug::Acquire::http=1
=
0% [Connecting to junk.devs.nu] [Connecting to repo.zabbix.com
(2604:a880:2:d0::2062:d001)]GET /zabbix/6.2/ubuntu/dists/jammy/InRelease
HTTP/1.1
Host: repo.zabbix.com
Cache-Control: max-age=0
Accept: text/*
If-Modified-Since: Wed, 01 Feb 2023 15:02:57 GMT
User-Agent: Debian APT-HTTP/1.3 (2.4.9) non-interactive
Answer for: http://repo.zabbix.com/zabbix/6.2/ubuntu/dists/jammy/InRelease
HTTP/1.1 304 Not Modified
Server: nginx/1.14.2
Date: Tue, 21 Feb 2023 12:31:54 GMT
Last-Modified: Wed, 01 Feb 2023 15:02:57 GMT
Connection: keep-alive
ETag: "63da7f21-135e"
Hit:1 http://repo.zabbix.com/zabbix/6.2/ubuntu jammy InRelease
0% [Connecting to junk.devs.nu]GET /ubuntu/dists/jammy/InRelease HTTP/1.1
Host: junk.devs.nu:3851
Cache-Control: max-age=0
Accept: text/*
User-Agent: Debian APT-HTTP/1.3 (2.4.9) non-interactive
Answer for: http://junk.devs.nu:3851/ubuntu/dists/jammy/InRelease
HTTP/1.1 200 OK
date: Fri, 17 Feb 2023 15:11:49 GMT
content-type: octet/stream
content-length: 270087
last-modified: Fri, 17 Feb 2023 13:29:00 GMT
x-original-source: http://de.archive.ubuntu.com/ubuntu/dists/jammy/InRelease
Get:2 http://junk.devs.nu:3851/ubuntu jammy InRelease [270 kB]
0% [2 InRelease 0 B/270 kB 0%]GET /ubuntu/dists/jammy-updates/InRelease HTTP/1.1
Host: junk.devs.nu:3851
Cache-Control: max-age=0
Accept: text/*
User-Agent: Debian APT-HTTP/1.3 (2.4.9) non-interactive
Answer for: http://junk.devs.nu:3851/ubuntu/dists/jammy-updates/InRelease
HTTP/1.1 200 OK
date: Fri, 17 Feb 2023 15:11:49 GMT
content-type: octet/stream
content-length: 118747
last-modified: Fri, 17 Feb 2023 13:29:00 GMT
x-original-source:
http://de.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease
Get:3 http://junk.devs.nu:3851/ubuntu jammy-updates InRelease [119 kB]
Ign:3 http://junk.devs.nu:3851/ubuntu jammy-updates InRelease
0% [Working]
=
ps faxu
=
root 3549798 0.0 0.0 16652 6556 pts/3S+ 12:31 0:00
\_ apt-get update -o Debug::Acquire::http=1
_apt 3549801 0.0 0.0 22068 6540 pts/3S+ 12:31 0:00
\_ /usr/lib/apt/methods/http
_apt 3549802 0.0 0.0 22068 6552 pts/3S+ 12:31 0:00
\_ /usr/lib/apt/methods/http
_apt 3549804 0.0 0.0 15440 5016 pts/3S+ 12:31 0:00
\_ /usr/lib/apt/methods/gpgv
=
netstat
=
tcp1 0 217.21.199.56:44494 178.128.6.101:80CLOSE_WAIT
3549801/http
(this IP belongs to the zabbix repo. the connection to the junk.devs.nu
broken server is already gone.)
=
preliminary info
=
The connection to the zabbix repo is unclosed. The connection to the broken
server is closed. The sequence was:
12:31:58.082726 eth0 In IP 217.21.198.165.3851 > 217.21.199.56.42838: Flags
[F.], seq 270320:270560, ack 349, win 507, options [nop,nop,TS val 4041174334
ecr 558653630], length 240
12:31:58.083017 eth0 Out IP 217.21.199.56.42838 > 217.21.198.165.3851: Flags
[F.], seq 349, ack 270561, win 1022, options
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
It looks like you forgot to add the following to the changelog: - debian/control: + Build-Conflicts on fakeroot (<< 1.25.3-1.1ubuntu1) - debian/sudo[-ldap].manpages: install man/man8/sudo_root.8 - debian/sudo[-ldap].init: delete init scripts, as they are no longer necessary. - debian/etc/pam.d/sudo[-i]: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/etc/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path - debian/tests/control: 03-getroot-ldap: + allow removal of 'sudo' in autopkgtest (SUDO_FORCE_REMOVE=yes) And it looks like you didn't add the BuildConflicts to the debian/control file. Please update the package, thanks! -- 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/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+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 2007698] Re: Please merge 1.9.13p1-1 into lunar
** Attachment added: "sudo autopkgtests" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+attachment/5648890/+files/autopkgtests.gz -- 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/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+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 2007912] Re: PCI/internal sound card not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2007912 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The system cannot use the built-in mini-jack connections as output devices. The device is not listed in the available sound devices. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:04:04 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007912/+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 2007912] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: The system cannot use the built-in mini-jack connections as output devices. The device is not listed in the available sound devices. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:04:04 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/2007912 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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
