[Touch-packages] [Bug 239010] Re: Characters missing in special character selection window
Not reproducible with Vera’s successor DejaVu and OOo’s successor
LibreOffice on Lunar. The missing glyphs on the Special Characters
window could be explained by the fact OOo used to display that grid with
the thinnest font weight, inexplicably, which didn’t match the font file
displayed at the bottom left of the dialog, again, for no good reason.
** Package changed: ttf-bitstream-vera (Ubuntu) => fonts-dejavu (Ubuntu)
** Changed in: fonts-dejavu (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu.
https://bugs.launchpad.net/bugs/239010
Title:
Characters missing in special character selection window
Status in fonts-dejavu package in Ubuntu:
Fix Released
Bug description:
Binary package hint: openoffice.org
Hi,
I'm using Openoffice.org 2.4.1~rc2-1ubuntu1 on Ubuntu 8.04 Hardy
AMD64.
In the special character selection window ("Insert", "Special
Character"), the displayed table of characters contains gaps, i.e.
Unicode character 2248 is displayed correctly. The next character
displayed right next to the previous should of course be 2249. But
this is not always the case. E.g. the next character as in my attached
screenshot is in fact 2260! This means that several characters are not
displayed at all.
Selecting a special subset of Unicode characters in the top right
selection box doesn't change the table of characters. The Gaps still
exist, and other characters from a different subset are still
displayed instead.
Additionally, some characters show up only in form of a small rectangle, but
only in the table on the left. They are displayed correctly on the right side
of the window.
A screenshot is available under:
http://datenparkplatz.de/DiesUndDas/spCharacterProblem.png
This affects many important mathematical characters useful in all
language versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/239010/+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 239010] [NEW] Characters missing in special character selection window
You have been subscribed to a public bug:
Binary package hint: openoffice.org
Hi,
I'm using Openoffice.org 2.4.1~rc2-1ubuntu1 on Ubuntu 8.04 Hardy AMD64.
In the special character selection window ("Insert", "Special
Character"), the displayed table of characters contains gaps, i.e.
Unicode character 2248 is displayed correctly. The next character
displayed right next to the previous should of course be 2249. But this
is not always the case. E.g. the next character as in my attached
screenshot is in fact 2260! This means that several characters are not
displayed at all.
Selecting a special subset of Unicode characters in the top right
selection box doesn't change the table of characters. The Gaps still
exist, and other characters from a different subset are still displayed
instead.
Additionally, some characters show up only in form of a small rectangle, but
only in the table on the left. They are displayed correctly on the right side
of the window.
A screenshot is available under:
http://datenparkplatz.de/DiesUndDas/spCharacterProblem.png
This affects many important mathematical characters useful in all
language versions.
** Affects: fonts-dejavu (Ubuntu)
Importance: Low
Status: Fix Released
--
Characters missing in special character selection window
https://bugs.launchpad.net/bugs/239010
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to fonts-dejavu in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1995405] Re: Add SUPPORT_END to os-release
The approximate end of support date is known for the non-LTS releases. I think it's possible for Ubuntu Pro enablement to update /etc/os-release Some parts of /etc/os-release are very useful (almost essential); other fields are less practical. Perhaps it's not worth the work to support this new field. ** Changed in: base-files (Ubuntu) Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1995405 Title: Add SUPPORT_END to os-release Status in base-files package in Ubuntu: Triaged Bug description: There is a new suggested field to the os-release file: SUPPORT_END=-MM-DD If it is set, systemd 252 apparently sets a "support-ended" taint flag once that date has been reached. https://manpages.debian.org/unstable/os-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1995405/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Same for me on Ubuntu Mate 22.04 5.15.0-52-generic and Cinnamon 5.2.7 /etc/X11/Xsession.d/30x11-common_xresources: ligne 16: has_option : commande introuvable /etc/X11/Xsession.d/75dbus_dbus-launch: ligne 9: has_option : commande introuvable -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version
** Branch unlinked: lp:ubuntu/trusty-proposed/software-properties -- 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/1257505 Title: Create Unity Control Center so can remain on old GNOME Control Center version Status in Empathy: Fix Released Status in Eye of GNOME: Fix Released Status in GNOME Color Manager: Incomplete Status in GNOME media utilities: Expired Status in gThumb: Fix Released Status in Nautilus: Fix Released Status in Unity: Fix Released Status in activity-log-manager package in Ubuntu: Fix Released Status in chromium-browser package in Ubuntu: Won't Fix Status in compiz package in Ubuntu: Fix Released Status in deja-dup package in Ubuntu: Fix Released Status in empathy package in Ubuntu: Fix Released Status in eog package in Ubuntu: Fix Released Status in gnome-color-manager package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center-signon package in Ubuntu: Fix Released Status in gnome-media package in Ubuntu: Fix Released Status in gthumb package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in landscape-client package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in system-config-printer package in Ubuntu: Fix Released Status in ubuntuone-control-panel package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in webaccounts-browser-extension package in Ubuntu: Fix Released Bug description: Ubuntu/Unity uses GNOME Control Center as the application to configure the Unity session. We've made a lot of changes appropriate for Ubuntu and Unity (61 patches) which makes it hard to maintain and creates a conflict for Ubuntu GNOME to use the control center. Unity 7 will be replaced by Unity 8 in the future which has a new settings interface. So we can continue to remain on the current version of GNOME Control Center but allow Ubuntu GNOME to continue to update we will create a new project lp:unity-control-center which is a copy of GNOME Control Center 3.6 but with appropriate renaming so both can be installed. A number of packages that refer to gnome-control-center need to be updated to refer to unity-control-center (see bug tasks). A PPA for testing is https://launchpad.net/~ubuntu- desktop/+archive/unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1257505/+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 1381050] Re: "Import Key File" fails when the path of the file has special characters
** Branch unlinked: lp:ubuntu/trusty-proposed/software-properties
--
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/1381050
Title:
"Import Key File" fails when the path of the file has special
characters
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Trusty:
Triaged
Bug description:
[Impact]
Importing a key that is in a path that contains special characters
(like "/home/$USER/Transferências") fails silently.
[Test Case]
1. Download a PGP key for a Debian repository (for example, the VideoLAN
team's key: download.videolan.org/pub/debian/videolan-apt.asc)
2. Move the key file to a folder that contains special characters, or rename
the file to contain them (example: VídeoLAN.asc).
3. Open "Software & Updates" from the Dash, then select the Authentication
tab.
4. Press the "Import Key File..." button and then choose the key file.
Admin authentication should then be requested, so authenticate yourself.
If the bug is fixed: the key should now appear in the list of keys.
If not: the key was not added.
[Regression Potential]
If the fix is not correct, I suppose it could potentially break the
"import key" feature even more, so it wouldn't work even in "normal"
paths.
[Original Report]
The "Import Key File..." button in the "Authentication" tab fails
silently when the path of the selected key file includes special
characters.
I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is
named "/home/$USER/Transferências" here.
Adding a key from that folder fails, but adding a key from "/home/$USER" (no
special characters) succeeds.
The problem is that, in
softwareproperties/gtk/SoftwarePropertiesGtk.py in method
SoftwarePropertiesGtk.add_key_clicked() at around line 952:
if res == Gtk.ResponseType.ACCEPT:
try:
if not self.backend.AddKey(chooser.get_filename()):
error(self.window_main,
_("Error importing selected file"),
_("The selected file may not be a GPG key file "
"or it might be corrupt."))
except dbus.DBusException as e:
if e._dbus_error_name ==
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
logging.error("Authentication canceled, changes have not
been saved")
"self.backend.AddKey(chooser.get_filename())" throws a
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with
special characters.
This is probably a side effect of switching from Python 2 to 3 (and 'bytes'
now being used in network communications where 'str' was previously used).
Another issue is that the error isn't reported to the user, and it
should be.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 14 13:22:21 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1995405] [NEW] Add SUPPORT_END to os-release
On Tue, Nov 01, 2022 at 03:48:54PM -, Jeremy Bicha wrote: > Public bug reported: > There is a new suggested field to the os-release file: SUPPORT_END=- > MM-DD > If it is set, systemd 252 apparently sets a "support-ended" taint flag > once that date has been reached. "support" is a property of the product committments made around the OS, that cannot definitively be known at the time of the GA release. Encoding it in a file in the OS therefore carries an implicit obligation to update that file whenever changes are made to the support committments. This does not sound like something we want (in addition to already having to update distro-info-data). Why is it valuable for systemd to set this taint flag? We already have Ubuntu-native mechanisms for notifying users they are out of support. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1995405 Title: Add SUPPORT_END to os-release Status in base-files package in Ubuntu: Triaged Bug description: There is a new suggested field to the os-release file: SUPPORT_END=-MM-DD If it is set, systemd 252 apparently sets a "support-ended" taint flag once that date has been reached. https://manpages.debian.org/unstable/os-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1995405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971715] Re: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8
** Description changed: + [ Impact ] + + idn cannot handle non-ASCII characters + + [ Test Plan ] + + Existing state in 22.04: + + $ echo ü | idn + idn: could not convert from ASCII to UTF-8 + + Fixed output: + + $ echo ü | idn + xn--tda + + [ Where problems could occur ] + + The patch enables an extra autotools features, so the most likely + problem is a build failure. Currently non-ASCII characters are entirely + unhandled, so there's no risk of regression there, but this could + potentially turn clean failures into crashes or incorrect output. + + [Original report] + On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII - Expected: + Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 - Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 - root@test:~# apt-cache policy idn idn: - Installed: 1.38-4build1 - Candidate: 1.38-4build1 - Version table: - *** 1.38-4build1 500 - 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.38-4build1 + Candidate: 1.38-4build1 + Version table: + *** 1.38-4build1 500 + 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages + 100 /var/lib/dpkg/status ** Also affects: libidn (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: libidn (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libidn (Ubuntu Jammy) Status: New => Confirmed ** Changed in: libidn (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libidn (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1971715 Title: 22.04 idn -a domain.com idn: could not convert from ASCII to UTF-8 Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Jammy: Confirmed Status in libidn source package in Kinetic: Fix Released Bug description: [ Impact ] idn cannot handle non-ASCII characters [ Test Plan ] Existing state in 22.04: $ echo ü | idn idn: could not convert from ASCII to UTF-8 Fixed output: $ echo ü | idn xn--tda [ Where problems could occur ] The patch enables an extra autotools features, so the most likely problem is a build failure. Currently non-ASCII characters are entirely unhandled, so there's no risk of regression there, but this could potentially turn clean failures into crashes or incorrect output. [Original report] On Ubuntu 22.04 Jammy: idn -a "xxx-tést.eu" idn: could not convert from ASCII to UTF-8 And idn -u "xn--xxx-tst-fya.eu" idn: could not convert from UTF-8 to ASCII Expected: Successfully conversion from ASCII to UTF-8 Ubuntu 20.04 / 18.04 it works fine Also with idn2 from UTF-8 to ASCII works as expected how ever support lacks from ASCII to UTF-8 Description: Ubuntu 22.04 LTS Release: 22.04 root@test:~# echo $LC_ALL C.UTF-8 root@test:~# apt-cache policy idn idn: Installed: 1.38-4build1 Candidate: 1.38-4build1 Version table: *** 1.38-4build1 500 500 https://mirror.hetzner.com/ubuntu/packages jammy/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1971715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
Hi Jérôme, Apparently I missed your message as well. These patches have been included in kernel v5.7, and oem-6.0 has EOL-ed. ** No longer affects: bluez (Ubuntu) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-6.0 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-6.0 source package in Bionic: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-6.0 source package in Focal: Won't Fix Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823076/+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 1995405] [NEW] Add SUPPORT_END to os-release
Public bug reported: There is a new suggested field to the os-release file: SUPPORT_END=- MM-DD If it is set, systemd 252 apparently sets a "support-ended" taint flag once that date has been reached. https://manpages.debian.org/unstable/os-release ** Affects: base-files (Ubuntu) Importance: Low Status: Triaged ** Tags: lunar ** Description changed: - There is a new suggested field to the os-release file: SUPPORT_END + There is a new suggested field to the os-release file: SUPPORT_END=- + MM-DD If it is set, systemd 252 apparently sets a "support-ended" taint flag once that date has been reached. https://manpages.debian.org/unstable/os-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1995405 Title: Add SUPPORT_END to os-release Status in base-files package in Ubuntu: Triaged Bug description: There is a new suggested field to the os-release file: SUPPORT_END=-MM-DD If it is set, systemd 252 apparently sets a "support-ended" taint flag once that date has been reached. https://manpages.debian.org/unstable/os-release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1995405/+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 1971901] Re: dlltool uses non-unique temp filenames
binutils fix publised to jammy-updates on 2022-10-24, binutils-mingw-w64 would just need a recompile against binutils-source 2.38-4ubuntu2 to fix this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1971901 Title: dlltool uses non-unique temp filenames Status in binutils: Fix Released Status in Wine: Won't Fix Status in binutils package in Ubuntu: Fix Released Status in binutils-mingw-w64 package in Ubuntu: Triaged Status in binutils source package in Jammy: Fix Committed Status in binutils-mingw-w64 source package in Jammy: Triaged Bug description: Description:Ubuntu 22.04 LTS Release:22.04 binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1 /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.delay.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Assembler messages: Error: can't open winmm_dll_t.s for reading: No such file or directory /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited with status 1 /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: winmm_dll_t.o: No such file or directory winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1 make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1 make: *** Waiting for unfinished jobs tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.cross.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for it's temp file - these are not unique when building libwinmm.delay.a and libwinmm.cross.a in parallel. (This can of course affect any dll wine is building import libs for, winmm is just the one I happaned to get caught on). This is regression newly introduced in binutils 2.38 vs older versions which used getpid() as the basis of their temp name. We just encountered it as part of updating our CI for a winelib application from focal to jammy, but it seems to have been discovered by others already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885 There is an upstream fix on master (2.39) which is already backported to the binutils-2_38 branch: https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just be a matter of cherry-picking. Hopefully the fact it's a regression from impish->jammy and that upstream already backported it to 2.38 might make this a candidate for jammy-updates? To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1971901/+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 1995157] Re: Permission Denied while using lates verions of Openssh client
Thank you for taking the time to file this report and helping to make Ubuntu better. I think you're probably affected by this: https://askubuntu.com/questions/1409105/ubuntu-22-04-ssh-the-rsa-key- isnt-working-since-upgrading-from-20-04 Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1995157 Title: Permission Denied while using lates verions of Openssh client Status in openssh package in Ubuntu: Incomplete Bug description: Hi, I am having issues in connecting to OpenSSH Server. Error message is Permission Denied (publickey) I am having following versions of OpenSSH Packages : 1) Windows 10 Client : OpenSSH_8.5p1, OpenSSL 1.1.1k 25 Mar 2021 (Installed via Git - older version) 1) Windows 11 Client : OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022(Installed via Git 2.38.1 ) 2) Windows 11 Client : OpenSSH_for_Windows_8.6p1 LibreSSL 3.4.3 (Installed via Windows 11 ) 3) Ubuntu 14.04 Server : OpenSSH_6.6.1p1 OpenSSL 1.0.1f 4) Ubuntu 22 Server : OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022 I have recenty upgraded my WIndows Desktop & installed latest Windows 11 along with latest version of Git. I am having several servers running Ubuntu 14.04 & connecting through git-bash. In my previous windows 10 version of OpenSSH I am able to successfully connect to Ubuntu 14.04 servers. But after upgrading git to ver 9.0p1 I am unable to connect. This latest version I can connect to Ubuntu 22 Servers successfully. I am having single set of public & private keys which are properly installed. Old version of OpenSSH Client (8.5 / 8.6) can connect properly to both servers Ubuntu 14.04 & 22 New version of OpenSSH Client 9.0p1 can connect only to Ubuntu 22 Servers. On 14.04 server getting Permission Denied (publickey) message Thanks Ravi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1995157/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
-> If an user somehow met this issue, then the system is not able to boot. It can boot, if it did previously, and this issue will get fixed pretty quick IMHO in the updates repository given it impacts current 20.04, 22.04 and 22.10. Here is just the workaround part, for current 22.10 or 22.04 to help people stuck on boot that used to have a working system. 1) Hold the SHIFT key on boot, and select the 2nd newest kernel from the advanced list in the grub menu: i.e. for myself, 5.19 broke, so using the older 5.15 allowed me to boot. 2) Open a terminal, sudo -i to root, and run these commands to download, install, and prevent upgrades to last version of initramfs-tools before the compression rates were changed, which allows you to regenerate your initrd image with the previously working smaller size. Download: wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools-bin_0.140ubuntu12_amd64.deb wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools-core_0.140ubuntu12_all.deb wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools_0.140ubuntu12_all.deb Install: dpkg -i initramfs-tools-bin_0.140ubuntu12_amd64.deb dpkg -i initramfs-tools-core_0.140ubuntu12_all.deb dpkg -i initramfs-tools_0.140ubuntu12_all.deb Hold Upgrades: apt-mark hold initramfs-tools-bin apt-mark hold initramfs-tools-core apt-mark hold initramfs-tools Re-generate current initrd image: update-initramfs -u A reboot should just bring you up in 5.19. To restore the system to a normal state once the problem has been fixed in the current versions, unhold those same packages using the steps below, and the new ones will automatically be downloaded and installed. apt-mark unhold initramfs-tools-bin apt-mark unhold initramfs-tools-core apt-mark unhold initramfs-tools Some additional notes, not for the workaround above follow. Do NOT issue the "update-initramfs -k all" command, if you have been thinking about it as a first triage step. The reason being, if you have not applied some kind of fix or workaround prior, this will rebuild all your old previously working kernel initrd images with the new low compression directive, which might render them all unbootable, further complicating matters. If you get to this state, and you need a working live ISO, to chroot and fix, make sure to choose one prior with the older, increased initrd compresssion which must be 20.04.4 LTS or older. Current 20.05.5, and all 22.04 and 22.10 releases use the lower compression that can cause this issue and may not work. Impatient new installers may find this info useful as well. Another simpler workaround for more advanced users with 4K screens is to pass GFXMODE=640x480 in grub defaults and update-grub as mentioned here: http://savannah.gnu.org/bugs/?61058 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver
[Touch-packages] [Bug 1992454] Re: iptables: segfault when renaming a chain
I think we will need newer version numbers. iptables | 1.8.7-1ubuntu6 | kinetic | source iptables | 1.8.7-1ubuntu6 | lunar | source And kinetic has 1ubuntu7 in unapproved, because it was uploaded while kinetic was the development release. We will need 1ubuntu7 in lunar, and 1ubuntu6.1 in kinetic. Whoever sponsors these can take care of this small adjustment version anyway, just a heads up. Lunar is still in a bit of a freeze at the moment anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: In Progress Status in iptables source package in Bionic: In Progress Status in iptables source package in Focal: In Progress Status in iptables source package in Jammy: In Progress Status in iptables source package in Kinetic: In Progress Bug description: This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. Commit 97bf4e68fc0794adba3243fd96f40f4568e7216f fixes this bug upstream. This bug is to have the fix included in Ubuntu in order to avoid such segmentation faults. For Jammy and onward, iptables uses the new nft libraries so the problem does not appear unless the -legacy commands are used. The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket #behind which is dereferenced later when inserting the chain again with new #name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug
Details on how to reproduce this are: Install dnsmasq on ubuntu focal. Start dnsmasq with for example: dnsmasq --server 8.8.8.8 Try to resolve hosts that are known to not exist on the authoritative name server that is used with dnsmasq. for i in srv txt a a txt srv; do host -t $i test.foo. 127.0.0.1 | tail -n 1; done Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) test.foo has no A record Host test.foo. not found: 3(NXDOMAIN) test.foo has no A record test.foo has no TXT record test.foo has no SRV record Expected is that all tests are returning NXDOMAIN but they dont because of the bug. Same test on a ubuntu jammy installation with dnsmasq 2.86: for i in srv txt a a txt srv; do host -t $i test.foo. 127.0.0.1 | tail -n 1; done Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) Host test.foo. not found: 3(NXDOMAIN) The real world problem where we found this was with the autopath plugin from coredns in kubernetes. Because dnsmasq in version 2.80 sometimes returns NODATA the search path of autopath gets interrupted and the name resolution for normally working records fails. ** Changed in: dnsmasq (Ubuntu Focal) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1995260 Title: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Focal: New Bug description: We upgraded our openstack containers which host dnsmasq services from bionic to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN. This is already fixed upstream with the following commit [1]. The Ubuntu dnsmasq 2.80 package should get a backport with a release for the focal packages which includes this bug fix. [1] https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1995260/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug
Thanks for taking the time to report this bug and trying to make Ubuntu better. I added a task for Focal, and marked the development release as Fix Released. Could you please provided detailed steps on how to reproduce this issue? We would need that if we decide to try to update Focal with the patch you mentioned. I am setting the Focal task as Incomplete until you provide information to reproduce the bug, once you do that please set it back to New. ** Also affects: dnsmasq (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu) Status: New => Invalid ** Changed in: dnsmasq (Ubuntu) Status: Invalid => Fix Released ** Changed in: dnsmasq (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1995260 Title: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Focal: Incomplete Bug description: We upgraded our openstack containers which host dnsmasq services from bionic to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN. This is already fixed upstream with the following commit [1]. The Ubuntu dnsmasq 2.80 package should get a backport with a release for the focal packages which includes this bug fix. [1] https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1995260/+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 1995247] Re: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources
** Changed in: apt (Ubuntu Kinetic) Status: Triaged => In Progress ** Changed in: apt (Ubuntu Jammy) Status: Triaged => In Progress -- 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/1995247 Title: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: In Progress Status in apt source package in Kinetic: In Progress Status in apt source package in Lunar: Fix Committed Bug description: [Impact] When keys are embedded into deb822 sources files as Signed-By, apt writes them to a temporary file, but the code to delete them accidentally had an if (0) in front of the deletion, so they don't get deleted and accumulate with each `apt update` run. [Test plan] Including a test case for this in our comprehensive integration test suite which runs as autopkgtest, so passing autopkgtest = good. [Where problems could occur] Files could end up being removed too soon if the code is otherwise wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995247/+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 1995310] Re: Hash and size mismatch with http://ppa.launchpad.net/alessandro-strada/ppa/ubuntu bionic/main amd64
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: apt (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/apt/+question/703672 -- 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/1995310 Title: Hash and size mismatch with http://ppa.launchpad.net/alessandro- strada/ppa/ubuntu bionic/main amd64 Status in apt package in Ubuntu: Invalid Bug description: I have a student who is trying to run apt-get update and running into errors Ubuntu config on her machine: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic She is getting the following error: http://ppa.launchpad.net/alessandro-strada/ppa/ubuntu bionic/main amd64 Packages File has unexpected size (1343 != 1118). Mirror sync in progress? [IP: 185.125.190.52 80] Hashes of expected file: - Filesize:1118 [weak] - SHA256:d36fc206b1928d13d762d6ed9a0ed0cd1dcccb025d423efc25b9e660a45db3ff - SHA1:b41e1915a1b3d8caaf5492ff4d153cddc1c9462e [weak] - MD5Sum:5dfc938c95774e97205f8fa4cd626171 [weak] Release file created at: Fri, 28 Oct 2022 20:07:43 + I have tried to research a workaround for similar errors but most say to just wait and it will fix itself. However, I saw a similar bug being raised https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1975865 Please could someone advise on a workaround of if this needs to be fixed somehow? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995310/+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 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic
This bug was fixed in the package software-properties - 0.99.27.1 --- software-properties (0.99.27.1) kinetic; urgency=medium * softwareproperties/qt/SoftwarePropertiesQt.py: Don't crash if the driver package does not have a matching modules package (LP: #1993370) -- Brian Murray Wed, 19 Oct 2022 07:38:40 -0700 ** Changed in: software-properties (Ubuntu) Status: In Progress => 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/1993370 Title: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic Status in software-properties package in Ubuntu: Fix Released Bug description: Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel Core i5, UEFI, no secure boot, Broadcom WiFi. OS: Ubuntu Studio Kinetic, Final ISO Steps to reproduce: 1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the system normally. (No encryption, allow Internet access during installation using some method of connectivity other than WiFi.) 2. Reboot and log into the newly installed system. 3. Open a terminal and run "sudo software-properties-kde". 4. Click "Additional Drivers" in the window that pops up. 5. Click "Using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)". Expected result: The Apply Changes button should become clickable, allowing the user to install the driver. Actual result: The button remains grayed out, and the following error message is printed in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1063, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.27 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Oct 18 21:33:51 2022 InstallationDate: Installed on 2022-10-19 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+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 )
Good to hear that the issue is kind of resolved for you. The logging improvements you mentioned should be addressed by upstream, if you manage to find patches to achieve this we could take a look if it would worth a Stable Release Update (SRU). -- 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 1995329] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995329 Title: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Recently upgraded to 22.10 (from I believe 20.04, not actually completely sure) and both of my Bluetooth devices have stopped working. They can pair and connect initially, but disconnect after 4-5 seconds. My headphones worked a while, but have not since been able to have them stay connected. Here's an output from bluetoothctl, which doesn't say much? Agent registered [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D TxPower: -21 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00 ...1..t@ 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 87 04 02 48 e2 09 0e 30 0b 11 7a .H...0..z [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [NEW] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 88 b5 06 90 44 00 8d e6 00 11 30 ..D.0 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [bluetooth]# [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00 ...1..t` 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 14 08 8e 2b 3a 42 02 89 00 11 74 .+:Bt [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [DEL] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D
[Touch-packages] [Bug 1995329] Re: [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect
** Summary changed: - Devices pair and connect, but immediately (4-5 secs) disconnect + [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [HP HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect + [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995329 Title: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Recently upgraded to 22.10 (from I believe 20.04, not actually completely sure) and both of my Bluetooth devices have stopped working. They can pair and connect initially, but disconnect after 4-5 seconds. My headphones worked a while, but have not since been able to have them stay connected. Here's an output from bluetoothctl, which doesn't say much? Agent registered [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D TxPower: -21 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00 ...1..t@ 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 87 04 02 48 e2 09 0e 30 0b 11 7a .H...0..z [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [NEW] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 88 b5 06 90 44 00 8d e6 00 11 30 ..D.0 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [bluetooth]# [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00 ...1..t` 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 14 08 8e 2b 3a 42 02 89 00 11 74 .+:Bt [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG]
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
I think fix will be released in systemd 253.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Triaged
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection {
group {
wan
lan
[Touch-packages] [Bug 1995236] Re: Xsessions has_option code error with fix
Bug 1922414 covers one of the issues with has_option so please reword
this bug to cover one other issue only.
--
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/1995236
Title:
Xsessions has_option code error with fix
Status in xorg package in Ubuntu:
New
Bug description:
Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
reports and failed fixes for this over several years and releases.
There are a couple of problems in /etc/X11/Xsessions where it fails to
handle options, causing bogus error messages and, doubtless, many
errors.
The first bug is that the entire options file, including comments, is
read into a variable.
Where the variable "OPTIONS" is assigned;
Replacing "cat" with "grep" strips out comments and blank lines;
$ diff Xsession Xsession.orig
65c65
< grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
---
> cat "$OPTIONFILE"
The second problem is that checking for a non-existent directory
inside a command substitution does not work. It just appends garbage
onto the output string.
That is probably a bug in BASH, but I defer to your opinion there.
The immediate work around is to create an empty directory so that the
test does not fail. Better still, force the creation of the directory
and remove the test.
eg. change this;
OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d
'\n' cat
fi
)"
to this;
OPTIONSDIR=/etc/X11/Xsession.options.d
mkdir --parents ${OPTIONSDIR}
OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d
'\n' cat
)"
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Oct 31 16:33:14 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series /
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega
Series / Radeon Vega Mobile Series] [1002:15dd]
InstallationDate: Installed on 2022-10-20 (11 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4
fbcon=rotate:2 initrd=\initrd.img
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.C0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
[Touch-packages] [Bug 1995216] Re: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system
** Package changed: xorg (Ubuntu) => mate-desktop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in mate-desktop package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1995216/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
This revised patch addresses Steve's review comments. ** Patch added: "openssh_9.0p1-1ubuntu8-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+attachment/5628224/+files/openssh_9.0p1-1ubuntu8-v2.debdiff -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Triaged Bug description: [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The ssh.socket configuration should be fixed, and /etc/systemd/system/ssh.socket.d/addresses.conf should contain: [Socket] ListenStream= ListenStream=0.0.0.0:1234 4. On a Kinetic system which was incorrectly migrated to ssh socket activation (e.g. test case #2, prior to being patched), installing the new package reverts to the previous behavior. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails,
[Touch-packages] [Bug 1995196] Re: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1
Incomplete only because we need a reason for the failure... See also bug 1901115 and bug 1769800 ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995196 Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 Status in bluez package in Ubuntu: Incomplete Bug description: From a release upgrade from 22.04 to 22.10 (many moons ago) I had previously enabled pipewire on the 22.04 install with the following: sudo apt install pipewire-audio-client-libraries libspa-0.2-bluetooth libspa-0.2-jack sudo apt install wireplumber pipewire-media-session- sudo apt remove pulseaudio-module-bluetooth systemctl --user --now enable wireplumber.service ProblemType: Package DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Oct 28 07:09:19 2022 ErrorMessage: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2022-10-19 (9 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20V9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: bluez Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (0 days ago) dmi.bios.date: 05/10/2022 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: F9CN50WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G2 ITL dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrF9CN50WW:bd05/10/2022:br1.50:efr1.44:svnLENOVO:pn20V9:pvrThinkBook13sG2ITL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG2ITL:skuLENOVO_MT_20V9_BU_idea_FM_ThinkBook13sG2ITL: dmi.product.family: ThinkBook 13s G2 ITL dmi.product.name: 20V9 dmi.product.sku: LENOVO_MT_20V9_BU_idea_FM_ThinkBook 13s G2 ITL dmi.product.version: ThinkBook 13s G2 ITL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 64:79:F0:9D:09:A8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:21280 acl:17 sco:0 events:3348 errors:0 TX bytes:816597 acl:17 sco:0 commands:3319 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1995196/+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 1995294] Re: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty
** Also affects: openssh (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Kinetic) Status: New => Triaged ** Changed in: openssh (Ubuntu Kinetic) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => Low -- 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/1995294 Title: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Triaged Bug description: [Impact] If a user a has an existing drop-in config for ssh.socket in /etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh- server.postint determines it should *not* perform migration to socket- activated ssh, they will receive an error from dpkg: Errors were encountered while processing: openssh-server Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. E:Sub-process /usr/bin/dpkg returned an error code (1) Setting up openssh-server (1:9.0p1-1ubuntu7) ... rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server [Test Plan] * On a Jammy machine, install openssh-server if necessary. Edit /etc/ssh/sshd_config to contain the following: $ cat /etc/ssh/sshd_config [... defaults everywhere else ...] #Port 22 #AddressFamily any ListenAddress 0.0.0.0 ListenAddress :: [... defaults everywhere else ...] * Create a trivial drop-in override for ssh.socket: $ systemctl edit ssh.socket $ cat /etc/systemd/system/ssh.socket.d/override.conf [Unit] Description=Testing * Now perform an upgrade to Kinetic, and observe the dpkg error. [Where problems could occur] The solution should be to use rmdir's --ignore-fail-on-empty flag. If the flag was mis-spelled, that would produce a new error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1995294/+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 1995160] Re: Some problem with graphic card driver
Thanks for the bug report. It looks like you don't have a working graphics driver installed. Please open the 'Additional Drivers' app and use it to install the latest NVIDIA driver. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1995160 Title: Some problem with graphic card driver Status in Ubuntu: Incomplete Bug description: One day, I suddenly got the trouble with the graphics card driver. I tried to switch almost the Nvidia driver but it's still not working. I got the error message nvidia-gpu ic2 timeout error then only one screen worked. Hence I have to use Xorg the default driver then it works. But when I share screen, it display black screen, I can't share, and performance when I use the default graphic driver is not good as well. Please take a look my trouble ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15 Uname: Linux 5.17.0-1020-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 29 12:44:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03: added GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1660 Ti] [1043:8840] InstallationDate: Installed on 2022-06-30 (120 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. B660M Pro RS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1020-oem root=UUID=53a88101-e9f6-4e5f-ac27-9c925fc462c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.04 dmi.board.name: B660M Pro RS dmi.board.vendor: ASRock 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:bvnAmericanMegatrendsInternational,LLC.:bvr5.04:bd03/28/2022:br5.24:svnToBeFilledByO.E.M.:pnB660MProRS:pvrToBeFilledByO.E.M.:rvnASRock:rnB660MProRS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B660M Pro RS dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1995160/+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 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-520 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1995173 Title: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: The device is Lenovo Legion 7. This laptop has a mux switch to switch between dynamic/hybrid or discrete graphics mode. This laptop has a high resolution with high pixel density than the other displays out there, but I don't know the exact number. Additionally, this laptop can adjust the display refresh rate between 60 and 165 Hz. --- There were 1 problem I encountered in dynamic/hybrid graphics mode: - The widgets shown were too small. Details: The resolution was correct, at 2560x1600, but all widgets shown were too small. I suspected this was due to the laptop screen high pixel density and the widget size calculation didn't make use of physical dimension, but in terms of pixel. I thought installing NVIDIA driver would fix this, but no; this worked in OpenSUSE Leap with KDE Plasma and I think it was because of the inclusion of NVIDIA OpenGL driver. The current workaround was to scale by 200% in "Display Settings", although the login screen isn't affected by the scaling at all. --- There were 3 problems I encountered in discrete graphics mode: - The widgets were are too small, like the hybrid graphics mode issue. - The DE seemed to use wrong screen refresh rate. The refresh rate was fixed at 93 Hz in the "Display Settings". Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't update the 93 Hz in the "Display Settings". This didn't happen in the hybrid graphics mode. OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I think it may be either GNOME DE or xorg misconfigurations. - Screen brightness was fixed at 100%. Details: Screen brightness could be adjusted by the keyboard Fn keys, but the brightness was fixed at 100%. This didn't happen in the hybrid graphics mode. This is the most annoying problem and have forced me to use the hybrid graphics mode which I don't like. My first thought was either a specific NVIDIA issue or xorg misconfigurations. So I tried adding "acpi_backlight=vendor" and "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but didn't work at all. --- In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed below: Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading X.509 certificate -65 Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529) In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above except that there was no: Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX Open Kernel Module for x86_64 520.56.06 Release Build (dvs-builder@U16-T12-10-2) Thu Oct 6 21:33:54 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 29 18:50:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant:
[Touch-packages] [Bug 1995021] Re: Boot and shutdown take several minutes
Thanks for the bug report. Next time you experience a slow boot, please then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Tags added: jammy ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1995021 Title: Boot and shutdown take several minutes Status in Ubuntu: Incomplete Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1995021/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
vi0oss came up with a clever workaround for getting this spamware off our systems. > Can it be overridden with an additional package which Provides, Breaks and > Conflicts with ubuntu-advantage-tools? (From this comment https://old.reddit.com/r/assholedesign/comments/yg97tk/ubuntu_includes_ads_in_system_update_theyre/iuj7hug/ -- I went ahead and attached the deb here for posterity, but it's also in that thread) So far the deb they created is working for me. Long term solution being to switch to a distro that respects their users. ** Attachment added: "fake-ubuntu-advantage-tools.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+attachment/5628220/+files/fake-ubuntu-advantage-tools.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
** Description changed: [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. - * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). + * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. - * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). + * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The ssh.socket configuration should be fixed, and /etc/systemd/system/ssh.socket.d/addresses.conf should contain: [Socket] ListenStream= ListenStream=0.0.0.0:1234 4. On a Kinetic system which was incorrectly migrated to ssh socket activation (e.g. test case #2, prior to being patched), installing the new package reverts to the previous behavior. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The socket-activated ssh migration should be reverted, and ssh.service should be running as before upgrade to Kinetic. [Where problems could occur] These changes are in the openssh-server.postinst script, specifically in the
[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
** Description changed: - [NOTE FOR SRU TEAM] - - I would prefer that vorlon review the attached patch before the upload - is accepted. I will remove this note when that has happened. - [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The ssh.socket configuration should be fixed, and /etc/systemd/system/ssh.socket.d/addresses.conf should contain: [Socket] ListenStream= ListenStream=0.0.0.0:1234 4. On a Kinetic system which was incorrectly migrated to ssh socket activation (e.g. test case #2, prior to being patched), installing the new package reverts to the previous behavior. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The socket-activated ssh migration should be reverted, and ssh.service should be running as before upgrade to Kinetic. [Where problems could occur] These changes are in the openssh-server.postinst script, specifically in the socket-activated ssh migration logic. Regressions would be seen in the migration logic, for example breaking a previously-working migration scenario. [Original Description] update
[Touch-packages] [Bug 1993478] Proposed package upload rejected
An upload of openssh to kinetic-proposed has been rejected from the upload queue for the following reason: "patch to be revised". -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Triaged Bug description: [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The ssh.socket configuration should be fixed, and /etc/systemd/system/ssh.socket.d/addresses.conf should contain: [Socket] ListenStream= ListenStream=0.0.0.0:1234 4. On a Kinetic system which was incorrectly migrated to ssh socket activation (e.g. test case #2, prior to being patched), installing the new package reverts to the previous behavior. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The socket-activated ssh migration should be reverted, and ssh.service should be running as before upgrade to Kinetic. [Where problems could
[Touch-packages] [Bug 1993785] Re: Wrong loader path defined in pkgconfig
Installing libgdk-pixbuf-2.0-dev 2.42.8+dfsg-1ubuntu0.2 $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders $ ls -lh /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders -rwxr-xr-x 1 root root 15K říj 21 09:26 /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders The pixbuf loaders are still working as expected in for example the filemanager or viewer Marked as verified ** 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 gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1993785 Title: Wrong loader path defined in pkgconfig Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Jammy: Fix Committed Bug description: * Impact The .pc references to a wrong location for the loaders binary. That's because the file is moved from the packaging .install which the build system doesn't know about. * Testcase $ pkg-config --variable=gdk_pixbuf_query_loaders gdk-pixbuf-2.0 should return '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf- query-loaders' matching where the file is installed * What could go wrong The change is only patching the .pc there is no code change. If the patch was wrong the path returned could still not match the actual binary location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1993785/+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 1995329] Re: Devices pair and connect, but immediately (4-5 secs) disconnect
I've tried manual connecting in bluetoothctl, and it shows the following then: CHG] Device CB:78:4F:E1:45:7D RSSI: -42 [CHG] Device CB:78:4F:E1:45:7D RSSI: -41 [CHG] Device CB:78:4F:E1:45:7D RSSI: -41 [CHG] Device CB:78:4F:E1:45:7D RSSI: -43 [CHG] Device CB:78:4F:E1:45:7D RSSI: -44 [bluetooth]# connect 94:DB:56:4F:20:7F Attempting to connect to 94:DB:56:4F:20:7F Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable [CHG] Device CB:78:4F:E1:45:7D RSSI: -43 [CHG] Device CB:78:4F:E1:45:7D RSSI: -42 [bluetooth]# connect 94:DB:56:4F:20:7F [CHG] Device CB:78:4F:E1:45:7D RSSI: -44 [CHG] Device CB:78:4F:E1:45:7D RSSI: -42 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995329 Title: Devices pair and connect, but immediately (4-5 secs) disconnect Status in bluez package in Ubuntu: New Bug description: Recently upgraded to 22.10 (from I believe 20.04, not actually completely sure) and both of my Bluetooth devices have stopped working. They can pair and connect initially, but disconnect after 4-5 seconds. My headphones worked a while, but have not since been able to have them stay connected. Here's an output from bluetoothctl, which doesn't say much? Agent registered [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D TxPower: -21 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00 ...1..t@ 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 87 04 02 48 e2 09 0e 30 0b 11 7a .H...0..z [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [NEW] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 88 b5 06 90 44 00 8d e6 00 11 30 ..D.0 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [bluetooth]# [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00 ...1..t` 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 14 08 8e 2b 3a 42 02 89 00 11 74 .+:Bt [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D
[Touch-packages] [Bug 1995329] [NEW] Devices pair and connect, but immediately (4-5 secs) disconnect
Public bug reported: Recently upgraded to 22.10 (from I believe 20.04, not actually completely sure) and both of my Bluetooth devices have stopped working. They can pair and connect initially, but disconnect after 4-5 seconds. My headphones worked a while, but have not since been able to have them stay connected. Here's an output from bluetoothctl, which doesn't say much? Agent registered [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D TxPower: -21 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00 ...1..t@ 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 87 04 02 48 e2 09 0e 30 0b 11 7a .H...0..z [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [NEW] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 88 b5 06 90 44 00 8d e6 00 11 30 ..D.0 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [bluetooth]# [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00 ...1..t` 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 14 08 8e 2b 3a 42 02 89 00 11 74 .+:Bt [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [DEL] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 Seems all it says is "Connected: Yes" and then "Connected: No" Description:Ubuntu 22.10 Release:22.10 apt-cache policy bluez bluez: Installerad: 5.65-0ubuntu1 Kandidat:5.65-0ubuntu1 Versionstabell: *** 5.65-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3
[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
+if dpkg --compare-versions "$2" lt-nl 1:9.0p1-1ubuntu8~ && [ -n "$NO_SOCKET_MIGRATION" ]; then I'm going to ask that we be ultra-conservative here. It is very difficult in general to un-do in a maintainer script something that we think we did previously, because the admin may have done who-knows-what in between and we may be undoing things that weren't actually ours. So whenever it's possible to detect that it wasn't us that did a thing, we should avoid trying to undo it. In the case of this particular failure, the state of the system of a user hit by this bug will be: - /etc/systemd/system/ssh.service.d/00-socket.conf and /etc/systemd/system/ssh.socket.d/addresses.conf both exist - $2 argument to postinst will be LESS than 1:9.0p1-1ubuntu8~ because the release version of openssh-server will have failed to configure So I suggest the following instead: if dpkg --compare-versions "$2" lt-nl 1:9.0p1-1ubuntu7~ \ && [ -e /etc/systemd/system/ssh.socket.d/addresses.conf ] \ && [ -e /etc/systemd/system/ssh.service.d/00-socket.conf ] \ && [ -n "$NO_SOCKET_MIGRATION" ]; then This ensures that if, for any other reason the user has enabled the ssh.socket unit but our script says NO_SOCKET_MIGRATION, we don't mangle the systemd units to disable socket activation that might not have been enabled by us in the first place. (As a bonus, it will simplify and shorten the de-migration code overall.) -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Triaged Bug description: [NOTE FOR SRU TEAM] I would prefer that vorlon review the attached patch before the upload is accepted. I will remove this note when that has happened. [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that
