[Touch-packages] [Bug 1720039] Re: The bug is not reproducible, so it is likely a hardware or OS problem
I marked the bug report as incomplete as it does not contain enough information to reproduce it. It is unclear which code you try to compile. It is unclear on which architecture and distribution you are experiencing the problems. ** Changed in: modemmanager (Ubuntu) Status: New => Incomplete ** Package changed: modemmanager (Ubuntu) => gcc-defaults-ports (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1720039 Title: The bug is not reproducible, so it is likely a hardware or OS problem Status in gcc-defaults-ports package in Ubuntu: Incomplete Bug description: This is happening when I frequently build my gcc compiler for RISCV-64 cross compilation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults-ports/+bug/1720039/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
libgl1-mesa-dri_22.0.5-0ubuntu0.1_ppc64el.deb is available in Jammy. libgl1-mesa-dri_22.1.3-1ubuntu1_riscv64.deb us available in Kinetic. Therefore marking as fix released. ** Changed in: mesa (Ubuntu Jammy) Status: New => Fix Released ** Changed in: mesa (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Released Status in mesa source package in Kinetic: Fix Released Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980386/+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 1933796] Re: resume from suspend while connected to power results in roaring fans
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1933796 Title: resume from suspend while connected to power results in roaring fans Status in systemd package in Ubuntu: Expired Bug description: since upgrade to ubuntu 20.10 my thinkpad x1 carbon gen5 resumes from suspend with a roaring fan. i have to make sure to start the resume while the power cord is not connected, let it wake up fully and only then connect the power cord. this is quite an annoying regression, still persisting in ubuntu 21.04, since there is no way to calm the fan noise except to do a complete shutdown and power on cycle (reboot still keeps the fan at max). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 27 18:20:13 2021 InstallationDate: Installed on 2021-05-10 (48 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 1199:9079 Sierra Wireless, Inc. EM7455 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HR0068GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=6e4248be-ae78-4e70-a7c0-88bada1c53a8 ro mitigations=off quiet SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HR0068GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:br1.24:efr1.17:svnLENOVO:pn20HR0068GE:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR0068GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HR0068GE dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1933796/+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 1984327] Re: Component mismatch: new lerc support requires universe package
This bug was fixed in the package tiff - 4.4.0-4ubuntu1 --- tiff (4.4.0-4ubuntu1) kinetic; urgency=medium * d/control, d/libtiff5.symbols: drop liblerc-dev build-dependency and the TIFFInitLERC symbol since that library is in universe and tiff is in main (LP: #1984327) -- Andreas Hasenack Wed, 10 Aug 2022 15:40:59 -0300 ** Changed in: tiff (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 tiff in Ubuntu. https://bugs.launchpad.net/bugs/1984327 Title: Component mismatch: new lerc support requires universe package Status in tiff package in Ubuntu: Fix Released Bug description: tiff is in sync with debian, and version tiff 4.4.0-1[1] enabled lerc support. Unfortunately lerc[2] is in ubuntu universe, and tiff is in main, so we either MIR lerc, or disable it in tiff. For now, let's disable lerc support. 1. https://launchpad.net/ubuntu/+source/tiff/4.4.0-1 2. https://launchpad.net/ubuntu/+source/lerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1984327/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
** Tags added: fr-2601 ** Also affects: avahi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: avahi (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: avahi (Ubuntu Kinetic) Importance: High Status: Confirmed ** Changed in: avahi (Ubuntu Focal) Importance: Undecided => High ** Changed in: avahi (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Focal: New Status in avahi source package in Jammy: New Status in avahi source package in Kinetic: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1971523] Re: Static build does not work for libmnl (-lmnl)
Hi Lars,
As you probably know, that bug has been fixed in kinetic. Therefore, I might
prepare backporting and upload changes into Jammy.
The bug heat measure is low and I need additional data whether there are others
affected by that bug. The process of backporting (SRU) bears the risk so impact
on users is the additional factor which might convince the SRU team to backport
it. So the more people affected by it, the better.
I would like to ask you then to test the changes that would be made by
backporting fix according to the steps mentioned in the SRU bug report
that would be prepared.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/1971523
Title:
Static build does not work for libmnl (-lmnl)
Status in libmnl package in Ubuntu:
Fix Released
Status in libmnl source package in Jammy:
Triaged
Status in libmnl package in Debian:
Fix Committed
Bug description:
[Test Case]
$ cat > /tmp/hello.c <
int main() {
printf("Hello world! (and LP: #1971523)\n");
}
EOF
$ gcc -o /tmp/hello /tmp/hello.c -lmnl
(dynamic libs work)
$ gcc -static -o /tmp/hello /tmp/hello.c -lmnl
/usr/bin/ld: cannot find -lmnl: No such file or directory
[Original Report]
My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for
static builds. This is very awkward during the transition 20.04->22.04 when
both should be supported.
I compensated in Ubuntu 20.04 by building netfilter_queue locally;
https://github.com/Nordix/nfqueue-loadbalancer#build
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libmnl0:amd64 1.0.4-3build2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed May 4 07:33:26 2022
InstallationDate: Installed on 2018-09-07 (1334 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: libmnl
UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.
This bug was fixed in the package apt - 2.4.7 --- apt (2.4.7) jammy; urgency=medium * Mark broken reverse depends for upgrade (LP: #1974196) -- Julian Andres Klode Thu, 28 Jul 2022 09:26:24 +0200 ** Changed in: apt (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1974196 Title: Installing libudev1 on a new Jammy installation uninstalls many packages. Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Released Status in apt source package in Kinetic: Fix Released Bug description: [Impact] On an Ubuntu 22.04 desktop system created using the current installation image without enabling package updates over the network, installing the package libudev1 results in a large number of critical packages being removed and rendering the system essentially unusable. [Test plan] Comprehensive regression test suite validating a full solver dump with the issue is run as autopkgtest. [Where problems could occur] We could break other things from resolving. The solver is a bit finicky. Hopefully this is isolated enough. [Other info] https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile which also demonstrates the issue. Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, and then running `apt install libudev1` in the generated image results in The following packages will be REMOVED: libnss-systemd libpam-systemd systemd-timesyncd udev The following packages will be upgraded: libudev1 This is completely prevented by ensuring that updates are installed from the jammy-updates repository before installing any additional packages and that is almost certainly the correct thing to do. But this is a punishing result for such a mistake. I would expect the installation to either force the upgrade of the other systemd packages or refuse to install libudev1 at the incorrect version relative to the other systemd packages until the system is upgraded. We found this out via a user report for ROS 2 Humble which is releasing on top of Ubuntu 22.04 next week: https://github.com/ros2/ros2/issues/1272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1974196] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1974196 Title: Installing libudev1 on a new Jammy installation uninstalls many packages. Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Released Status in apt source package in Kinetic: Fix Released Bug description: [Impact] On an Ubuntu 22.04 desktop system created using the current installation image without enabling package updates over the network, installing the package libudev1 results in a large number of critical packages being removed and rendering the system essentially unusable. [Test plan] Comprehensive regression test suite validating a full solver dump with the issue is run as autopkgtest. [Where problems could occur] We could break other things from resolving. The solver is a bit finicky. Hopefully this is isolated enough. [Other info] https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile which also demonstrates the issue. Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, and then running `apt install libudev1` in the generated image results in The following packages will be REMOVED: libnss-systemd libpam-systemd systemd-timesyncd udev The following packages will be upgraded: libudev1 This is completely prevented by ensuring that updates are installed from the jammy-updates repository before installing any additional packages and that is almost certainly the correct thing to do. But this is a punishing result for such a mistake. I would expect the installation to either force the upgrade of the other systemd packages or refuse to install libudev1 at the incorrect version relative to the other systemd packages until the system is upgraded. We found this out via a user report for ROS 2 Humble which is releasing on top of Ubuntu 22.04 next week: https://github.com/ros2/ros2/issues/1272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1970449] Update Released
The verification of the Stable Release Update for software-properties has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Status in software-properties source package in Kinetic: Fix Released Bug description: [Impact] software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. [Test Plan] 1. Launch software-properties-gtk 2. Click on the "Authentication" tab 3. At least one key should be listed [Where problems could occur] I fail to come up with possible problems. The failures was a regression and the fixed version has a test case. [Other Infos] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader 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/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
This bug was fixed in the package software-properties - 0.99.22.3 --- software-properties (0.99.22.3) jammy; urgency=medium * Fix GPG keys are not shown in Software and Updates (LP: #1970449) * Fix spelling mistake of repository -- Benjamin Drung Tue, 26 Jul 2022 13:37:33 +0200 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Status in software-properties source package in Kinetic: Fix Released Bug description: [Impact] software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. [Test Plan] 1. Launch software-properties-gtk 2. Click on the "Authentication" tab 3. At least one key should be listed [Where problems could occur] I fail to come up with possible problems. The failures was a regression and the fixed version has a test case. [Other Infos] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader 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/1970449/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
** Tags added: fr-2601 ** Tags removed: fr-2601 rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1958059] Re: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available.
Improved wording of that error message: https://github.com/canonical/apport/commit/d2cf6a98167e5dafc2a51b4878cd5f13b3e022c9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1958059 Title: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. Status in Apport: Fix Committed Status in apport package in Ubuntu: Expired Bug description: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. This is clean fresh 32-bit 18.04.6 updated from 18.04.5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:29:27 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1958059/+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 1958059] Re: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available.
Improved wording of that error message: https://github.com/canonical/apport/commit/d2cf6a98167e5dafc2a51b4878cd5f13b3e022c9 ** Changed in: apport Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1958059 Title: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. Status in Apport: Fix Committed Status in apport package in Ubuntu: Expired Bug description: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. This is clean fresh 32-bit 18.04.6 updated from 18.04.5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:29:27 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1958059/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.
This was fixed by upstream in april. See https://sourceware.org/bugzilla/show_bug.cgi?id=28980 ** Bug watch added: Sourceware.org Bugzilla #28980 https://sourceware.org/bugzilla/show_bug.cgi?id=28980 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. Status in gdb package in Ubuntu: Confirmed Bug description: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1958059] Re: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available.
** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Importance: Undecided => Low ** Changed in: apport Milestone: None => 2.23.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1958059 Title: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. Status in Apport: New Status in apport package in Ubuntu: Expired Bug description: apport-collect doesnt work- ERROR: The python3-launchpadlib package is not installed. This functionality is not available. This is clean fresh 32-bit 18.04.6 updated from 18.04.5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 05:29:27 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1958059/+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 1871465] Re: ssh_config(5) contains outdated information
With Michal: Marked block-proposed, added SRU content, re-reviewed and sponsored the upload to Focal-unapproved. -- 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/1871465 Title: ssh_config(5) contains outdated information Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Won't Fix Status in openssh source package in Impish: Won't Fix Bug description: [Impact] The problem here is straightforward. The case is to fix manpages. They need to reflect a change done to the code some time ago. That problem might be annoying for users before being fixed. Backport upstream fix to Focal Origin: https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636 [Test Plan] Make a container for testing: First option: $ lxc launch images:ubuntu/bionic focal-test $ lxc shell focal-test Simply install the openssh package using ‘apt install’ and check both ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ in these files. [Where problems could occur] Any code change might change the behavior of the package in a specific situation and cause other errors. Next things which might cause regression are new dependencies which might not align and it is obvious the dependencies are upgraded and it might be a problem, but it is really unlikely. Even none of the rather generic cases above does apply here as we only change non-functional content in the form of the man page; Therefore the only risk is out of re-building the package which could pick up something from e.g. a changed toolchain. [Other Info] Fixing this is nice for the users, but OTOH very low severity and would cause a package download and update on almost every Ubuntu in the world. Therefore we will mark this as block-proposed and keep it in focal-proposed so that a later real update (security or functional) will pick this up from -proposed and then fix it in the field for real. original report--- The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list of CACertificateAlgorithms. However the latest `openssh-client` still ships the man page for ssh_config(5) that contains the following description: CASignatureAlgorithms Specifies which algorithms are allowed for signing of certificates by certificate authorities (CAs). The default is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa ssh(1) will not accept host certificates signed using algorithms other than those specified. As far as I am concerned, `ssh-rsa` should be dropped from the list so as to match the behavior of ssh(1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1871465/+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 1983794] Re: Evolution not deleting autosave files
Further analysis by Milan Crha shows that the issue under Xorg seems to
be caused by Ubuntu's gtk3, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972#note_1524307.
** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #1972
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in evolution package in Ubuntu:
Confirmed
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1871465] Re: ssh_config(5) contains outdated information
** Description changed: + [Impact] + + The problem here is straightforward. + The case is to fix manpages. They need to reflect a change done to the code some time ago. That problem might be annoying for users before being fixed. + + Backport upstream fix to Focal + Origin: + https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636 + + + [Test Plan] + + Make a container for testing: + + First option: + $ lxc launch images:ubuntu/bionic focal-test + $ lxc shell focal-test + + Simply install the openssh package using ‘apt install’ and check both ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ in these files. + + + + [Where problems could occur] + + Any code change might change the behavior of the package in a specific + situation and cause other errors. + + Next things which might cause regression are new dependencies which + might not align and it is obvious the dependencies are upgraded and it + might be a problem, but it is really unlikely. + + Even none of the rather generic cases above does apply here as we only + change non-functional content in the form of the man page; Therefore the + only risk is out of re-building the package which could pick up + something from e.g. a changed toolchain. + + + [Other Info] + + + Fixing this is nice for the users, but OTOH very low severity and would cause a package download and update on almost every Ubuntu in the world. Therefore we will mark this as block-proposed and keep it in focal-proposed so that a later real update (security or functional) will pick this up from -proposed and then fix it in the field for real. + + original + report--- + The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list of CACertificateAlgorithms. However the latest `openssh-client` still ships the man page for ssh_config(5) that contains the following description: CASignatureAlgorithms - Specifies which algorithms are allowed for signing of certificates - by certificate authorities (CAs). The default is: + Specifies which algorithms are allowed for signing of certificates + by certificate authorities (CAs). The default is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa - ssh(1) will not accept host certificates signed using algorithms - other than those specified. + ssh(1) will not accept host certificates signed using algorithms + other than those specified. As far as I am concerned, `ssh-rsa` should be dropped from the list so as to match the behavior of ssh(1). -- 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/1871465 Title: ssh_config(5) contains outdated information Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Won't Fix Status in openssh source package in Impish: Won't Fix Bug description: [Impact] The problem here is straightforward. The case is to fix manpages. They need to reflect a change done to the code some time ago. That problem might be annoying for users before being fixed. Backport upstream fix to Focal Origin: https://github.com/openssh/openssh-portable/commit/53ea05e09b04fd7b6dea66b42b34d65fe61b9636 [Test Plan] Make a container for testing: First option: $ lxc launch images:ubuntu/bionic focal-test $ lxc shell focal-test Simply install the openssh package using ‘apt install’ and check both ssh_config.5 and sshd_config.5 files. You should be able to spot the ‘ssh_rsa’ in these files. [Where problems could occur] Any code change might change the behavior of the package in a specific situation and cause other errors. Next things which might cause regression are new dependencies which might not align and it is obvious the dependencies are upgraded and it might be a problem, but it is really unlikely. Even none of the rather generic cases above does apply here as we only change non-functional content in the form of the man page; Therefore the only risk is out of re-building the package which could pick up something from e.g. a changed toolchain. [Other Info] Fixing this is nice for the users, but OTOH very low severity and would cause a package download and update on almost every Ubuntu in the world. Therefore we will mark this as block-proposed and keep it in focal-proposed so that a later real update (security or functional) will pick this up from -proposed and then fix it in the field for real. original report---
[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel
@Jarno OK I was wrong, new apt pulls in new libapt-pkg5.0. What happens instead is that the cache built by the old version does not include information about available kernels, we essentially need to bump the cache minor version, if we can do that, I don't know, I lost track of what major version is what version. Later versions embed the apt version into the cache hash so they always rebuilt after an apt upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information
** Tags added: block-proposed -- 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/1871465 Title: ssh_config(5) contains outdated information Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Focal: Triaged Status in openssh source package in Hirsute: Won't Fix Status in openssh source package in Impish: Won't Fix Bug description: The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list of CACertificateAlgorithms. However the latest `openssh-client` still ships the man page for ssh_config(5) that contains the following description: CASignatureAlgorithms Specifies which algorithms are allowed for signing of certificates by certificate authorities (CAs). The default is: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa ssh(1) will not accept host certificates signed using algorithms other than those specified. As far as I am concerned, `ssh-rsa` should be dropped from the list so as to match the behavior of ssh(1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1871465/+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 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)
This bug was fixed in the package sudo - 1.9.10-3ubuntu1 --- sudo (1.9.10-3ubuntu1) kinetic; urgency=medium * Merge from Debian unstable. Remaining changes: - debian/control: + Build-Conflicts on fakeroot (<< 1.25.3-1.1ubuntu1) - debian/sudo[-ldap].manpages: install man/man8/sudo_root.8 - debian/sudo[-ldap].init: delete init scripts, as they are no longer necessary. - debian/etc/pam.d/sudo[-i]: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/etc/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path - debian/tests/control: 03-getroot-ldap: + allow removal of 'sudo' in autopkgtest (SUDO_FORCE_REMOVE=yes) * Dropped changes (applied in Debian): - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag * Add XDG_CURRENT_DESKTOP to initial_keepenv_table for Qt to determine the correct theme (LP: #1958055) sudo (1.9.10-3) unstable; urgency=medium * some changes to 03-getroot-ldap autopkgtest to find out about ppc64el failure sudo (1.9.10-2) unstable; urgency=medium * upload to unstable (fixed autopkgtest is needed to allow adduser to migrate) sudo (1.9.10-1) experimental; urgency=medium * new upstream version * unverified upstream changelog * implement workaround if /proc/self/stat is invalid. (Closes: #940533) * Fix compilation problem on kFreeBSD. (Closes: #1004909) (different fix than the Debian patch, disable Debian patch) * get rid of e-mails "problem with defaults entries" in sss configurations. (Closes: #793660) * regular expression support for sudoers. (Closes: #945366) * handle /proc/self/fd in qemu. * Apply Upstream Patch to allow test suite with non-english LANG https://bugzilla.sudo.ws/show_bug.cgi?id=1025 * Apply Upstream Patch to allow test suite with faketime * re-introduce MVPROG patch that got lost in dh migration. Thanks to Vagrant Cascadian (Closes: #976307) * revert back to directly shipping the mask symlink in the package. Thanks to Michael Biebl (Closes: #1004730) * adopt configure changes from Ubuntu --without-lecture --with-tty-tickets --enable-admin-flag (Closes: #1006273) * fix wrong handling of --with-systemd-tmpfiles.d * bring OPTIONS up to date. * have upstream install docs directly to correct directory * let debhelper handle the upstream changelog * remove LICENSE.md in both packages * autopkgtest: send deluser stderr to null in cleanup * Add cron to autopkgtest 03-getroot-ldap dependencies * improve lintian overrides -- Benjamin Drung Wed, 03 Aug 2022 10:45:04 +0200 ** Changed in: sudo (Ubuntu) Status: Fix Committed => Fix Released ** Bug watch added: bugzilla.sudo.ws/ #1025 http://bugzilla.sudo.ws/show_bug.cgi?id=1025 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1958055 Title: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP) Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Jammy: Fix Committed Bug description: [Impact] Running ubuntu-bug as normal user has the correct theme (see screenshots attached to bug #1881640), but running "sudo ubuntu-bug" has a different, non-matching theme (see attached screenshot). This applies to all Qt applications. [Test Plan] This problem can be reproduce by running a KDE application on Ubuntu Desktop (GNOME): 1. Launch ubuntu-22.04-desktop-amd64.iso 2. Install apport-kde 3. Run: /usr/share/apport/apport-kde -f 4. Run: sudo /usr/share/apport/apport-kde -f 5. Compare both windows. They have different icons and font size. Same result with KDE: 1. Use kubuntu-22.04-desktop-amd64.iso 2. Run ubuntu-bug -f 3. Run: sudo ubuntu-bug -f [Analysis] Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme, but XDG_CURRENT_DESKTOP is not in the list of environment variables to preserve (and not in env_keep in /etc/sudoers). On other other hand, sudo preserves the DISPLAY environment variable: $ sudo env | grep -Ev '^(LC|LS|SUDO|LANG|COLOR|TERM|PATH)' XAUTHORITY=/run/user/1000/gdm/Xauthority DISPLAY=:0 MAIL=/var/mail/root LOGNAME=root USER=root HOME=/root SHELL=/bin/bash [Workaround] Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f [Other Info] This changes was accepted upstream: https://github.com/sudo- project/sudo/pull/165 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux
[Touch-packages] [Bug 1983128] Re: linux-lowlatency fails to build on arm64 due to kernel option settings
** Summary changed:
- linux-lowlatency fals to build on arm64 due to kernel option settings
+ linux-lowlatency fails to build on arm64 due to kernel option settings
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1983128
Title:
linux-lowlatency fails to build on arm64 due to kernel option settings
Status in linux-lowlatency package in Ubuntu:
New
Status in zlib package in Ubuntu:
New
Bug description:
The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a
kinetic-proposed migration process (for zlib) and runs into a 'regression':
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64:
Regression ♻"
The regression is highly likely not due to zlib itself, but due to NEW kernel
options, that don't have a default yet and a check-config FAIL, see:
...
check-config:
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian/build/build-lowlatency/.config:
loading config
check-config:
/tmp/autopkgtest.ZQs9si/build.cYo/src/debian.lowlatency/config/annotations
loading annotations
check-config: FAIL (n != -): CONFIG_KCOV policy<{'amd64': 'n', 'arm64':
-, 'armhf': 'n', 'ppc64el': '-', 'riscv64': 'n', 's390x': '-'}>
check-config: 11323/11324 checks passed -- exit 1
...
Shadow Call Stack (SHADOW_CALL_STACK) [N/y/?] (NEW)
Error in reading or end of file.
...
Initialize kernel stack variables at function entry
> 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE)
2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) (NEW)
3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) (NEW)
choice[1-3?]:
Error in reading or end of file.
...
Full log is here:
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/l/linux-lowlatency/20220728_135536_c2061@/log.gz
(this might be caused by the recent compiler update)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1983128/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
The zlib patch is already waiting in Jammy's unapproved queue, so I'm
marking it "In Progress".
** Changed in: zlib (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
In Progress
Status in bedtools package in Ubuntu:
Fix Released
Status in htslib package in Ubuntu:
Invalid
Status in zlib package in Ubuntu:
Fix Committed
Status in bedtools source package in Focal:
Invalid
Status in htslib source package in Focal:
Fix Committed
Status in zlib source package in Focal:
Fix Committed
Status in bedtools source package in Impish:
Won't Fix
Status in htslib source package in Impish:
Won't Fix
Status in zlib source package in Impish:
Won't Fix
Status in bedtools source package in Jammy:
New
Status in htslib source package in Jammy:
Invalid
Status in zlib source package in Jammy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
* On top of this actual zlib fix, there is another patch needed:
'Remove compressBound assertions. (PR #1258)' for htslib.
* But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, &dest_len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected by the zlib issue.
* The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.
* The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.
* Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
htt
