[Touch-packages] [Bug 1972718] Re: ubuntu-bug should provide option to copy link instead of always opening
1. Run `ubuntu-bug apport` 2. Complete the steps 3. A browser window opens without any option to copy a link instead. The link is also not shown in the terminal output. 4. It goes to https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/UUID/+login 5. Because my default Firefox container had nothing, it asks me to log in 6. Copy and pasting the link in the right container says: "You are already logged in". It does not allow me to complete the bug report. A fix can be to pop up a window to ask the user if it should open a new tab directly or just copy the link instead. Or at minimum output the initial link to standard output so that the user can do that manually. -- 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/1972718 Title: ubuntu-bug should provide option to copy link instead of always opening Status in apport package in Ubuntu: New Bug description: Currently it always opens another tab directly via the web browser, which opens in the wrong Firefox container for me. It then always redirects and asks for me to sign in without the option of moving the tab inside the correct container. If I simply open it again in the correct tab, it tells me that no sign in is necessary and doesn't let me complete the original bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972718/+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 1433787] Re: rsync corrupts systematically jpg files when copying from jmtpfs
[Expired for rsync (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rsync (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1433787 Title: rsync corrupts systematically jpg files when copying from jmtpfs Status in rsync package in Ubuntu: Expired Bug description: rsync corrupts systematically jpg files when copying from jmtpfs I am filing the bug with rsync because neither cp nor scp show the problem. They copy the images just fine. Therefore I assume it is not a problem of jmtpfs. When I want to view the jpg files after a copy with rsync I get the following error: "Error interpreting JPEG image file (Application transferred too few scanlines)". Rsync runs through though and does not output any error nor warning. root@kimera:~# lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 root@kimera:~# apt-cache policy rsync rsync: Installed: 3.1.1-2 Candidate: 3.1.1-2 Version table: *** 3.1.1-2 0 500 http://ch.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: rsync 3.1.1-2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Mar 18 21:47:32 2015 InstallationDate: Installed on 2015-01-14 (63 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1433787/+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 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy Status in network-manager package in Ubuntu: Expired Bug description: I'm trying to connect to an open (i.e. no ecryption) WLAN with network-manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the following error message (after selecting the network from the network- manager applet prompt): Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: [1646733004.4425] audit: op="connection-add-activate" pid=12122 uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it" I haven't changed any of the default settings for network-manager and this network worked on 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+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 1978349] Re: Monitors sometimes permanently blanked after resume
** Package changed: ubuntu => xorg (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/1978349 Title: Monitors sometimes permanently blanked after resume Status in xorg package in Ubuntu: New Bug description: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic 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: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: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.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2012
[Touch-packages] [Bug 1978349] [NEW] Monitors sometimes permanently blanked after resume
You have been subscribed to a public bug: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic 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: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: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.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1978361] [NEW] package console-setup-linux 1.108ubuntu15.5 failed to install/upgrade: 正试图覆盖 /lib/systemd/system/console-setup.service，它同时被包含于软件包 keyboard-configuration 1.108ubunt
Public bug reported: I want to pip install git,so I sudo apt-get upgrade,then I find this bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: console-setup-linux 1.108ubuntu15.5 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 Date: Sat Jun 11 07:17:39 2022 ErrorMessage: 正试图覆盖 /lib/systemd/system/console-setup.service，它同时被包含于软件包 keyboard-configuration 1.108ubuntu15.5 InstallationDate: Installed on 2022-06-10 (0 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 2.0.9 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.5 failed to install/upgrade: 正试图覆盖 /lib/systemd/system/console-setup.service，它同时被包含于软件包 keyboard-configuration 1.108ubuntu15.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1978361 Title: package console-setup-linux 1.108ubuntu15.5 failed to install/upgrade: 正试图覆盖 /lib/systemd/system/console-setup.service，它同时被包含于软件包 keyboard- configuration 1.108ubuntu15.5 Status in console-setup package in Ubuntu: New Bug description: I want to pip install git,so I sudo apt-get upgrade,then I find this bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: console-setup-linux 1.108ubuntu15.5 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 Date: Sat Jun 11 07:17:39 2022 ErrorMessage: 正试图覆盖 /lib/systemd/system/console-setup.service，它同时被包含于软件包 keyboard-configuration 1.108ubuntu15.5 InstallationDate: Installed on 2022-06-10 (0 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 2.0.9 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.5 failed to install/upgrade: 正试图覆盖 /lib/systemd/system/console-setup.service，它同时被包含于软件包 keyboard-configuration 1.108ubuntu15.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1978361/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices
Thank you, I am away on holiday until next wednesday but I will test during the second half of next week -- 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/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: In Progress Bug description: [Impact] * TPM2/FIDO cannot be used to unlock luks encrpyted block devices * due to missing build-time support in systemd * Error message: "TPM2 not supported on this build." [Test Plan] # 1: check no new binary deps have been introduced to the systemd package, other than "libssl3", which is already installed by default. # Compare to this version of systemd 249.11-0ubuntu3.1: $ apt-cache depends systemd systemd PreDepends: libblkid1 PreDepends: libc6 PreDepends: libcap2 PreDepends: libgcrypt20 PreDepends: liblz4-1 PreDepends: liblzma5 PreDepends: libselinux1 PreDepends: libzstd1 Depends: libacl1 Depends: libapparmor1 Depends: libaudit1 Depends: libcrypt1 Depends: libcryptsetup12 Depends: libgnutls30 Depends: libgpg-error0 Depends: libip4tc2 Depends: libkmod2 Depends: liblz4-1 Depends: libmount1 Depends: libpam0g Depends: libseccomp2 Depends: libsystemd0 Depends: util-linux Depends: mount Depends: adduser Conflicts: Conflicts: Conflicts: Breaks: resolvconf Breaks: udev |Recommends: dbus Recommends: dbus-broker dbus Recommends: networkd-dispatcher |Recommends: systemd-timesyncd Recommends: chrony ntp ntpsec openntpd systemd-timesyncd Suggests: systemd-container Suggests: policykit-1 # 2: check that systemd-cryptenroll doesn't have any undefined symbols that prevent it from running: $ systemd-cryptenroll --help # this should not crash systemd-cryptenroll [OPTIONS...] BLOCK-DEVICE Enroll a security token or authentication credential to a LUKS volume. -h --helpShow this help --version Show package version --passwordEnroll a user-supplied password --recovery-keyEnroll a recovery key --pkcs11-token-uri=URI Specify PKCS#11 security token URI --fido2-device=PATH Enroll a FIDO2-HMAC security token --fido2-with-client-pin=BOOL Whether to require entering a PIN to unlock the volume --fido2-with-user-presence=BOOL Whether to require user presence to unlock the volume --fido2-with-user-verification=BOOL Whether to require user verification to unlock the volume --tpm2-device=PATH Enroll a TPM2 device --tpm2-pcrs=PCR1+PCR2+PCR3+… Specify TPM2 PCRs to seal against --wipe-slot=SLOT1,SLOT2,… Wipe specified slots See the systemd-cryptenroll(1) man page for details. # initial setup $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cur3 Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo mkfs.ext4 /dev/mapper/volume $ sudo mount /dev/mapper/volume /mnt $ sudo touch /mnt/TPM_TEST $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. drwx-- 2 root root 16384 Jun 7 15:06 lost+found -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST $ sudo umount /dev/mapper/volume $ sudo cryptsetup luksClose volume $ ls -la /mnt # empty # 3: check non-TPM use cases (--password & --recovery-key) of systemd-cryptenroll have not regressed. # enroll additional password $ systemd-cryptenroll --password encrypted.img Please enter current passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3 Please enter new passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cr3t Please enter new passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img (repeat): s0s3cr3t New password enrolled as key slot 1. $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cr3t Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo cryptsetup luksClose volume $ systemd-cryptenroll --wipe-slot=1 encrypted.img Wiped slot 1. # enroll additional recovery-key $ systemd-cryptenroll --recovery-key encrypted.img Please
[Touch-packages] [Bug 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf
Thanks Marques, do you know if this affects Debian as well? I wonder if they already saw this and fixed it, or if they don't yet know about it. THanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown puts .domains TLD in resolv.conf Status in ifupdown package in Ubuntu: New Bug description: The bug described in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all is a security vulnerability because DNS names that would normally fail are now attempted as "foo.domains". ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, WA. "google.com.domains" is registered, for example. So is "test.domains". For users with ifupdown, any Internet request (especially that does not involve some cryptographic payload and destination signature verification) is potentially sending packets to an unintended audience. It's impossible to say, but likely, that malicious registrants are squatting sensitive and common names in the .domains TLD. The ifupdown package is still used by some cloud providers that have not adopted netplan. This vulnerability affects 22.04 and potentially other releases. This issue has not been corrected in 0.8.36+nmu1ubuntu4. With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the resolv.conf looks like the following (which is vulnerable to mitm attacks): ``` root@foo:~# cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search DOMAINS ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures ** Information type changed from Private Security to Public Security ** Tags added: community-security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown puts .domains TLD in resolv.conf Status in ifupdown package in Ubuntu: New Bug description: The bug described in https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878?comments=all is a security vulnerability because DNS names that would normally fail are now attempted as "foo.domains". ".domains" is a real TLD, with the registrar "Donuts, Inc." based in Bellvue, WA. "google.com.domains" is registered, for example. So is "test.domains". For users with ifupdown, any Internet request (especially that does not involve some cryptographic payload and destination signature verification) is potentially sending packets to an unintended audience. It's impossible to say, but likely, that malicious registrants are squatting sensitive and common names in the .domains TLD. The ifupdown package is still used by some cloud providers that have not adopted netplan. This vulnerability affects 22.04 and potentially other releases. This issue has not been corrected in 0.8.36+nmu1ubuntu4. With 0.8.36+nmu1ubuntu3 and after an update to 0.8.36+nmu1ubuntu4, the resolv.conf looks like the following (which is vulnerable to mitm attacks): ``` root@foo:~# cat /etc/resolv.conf # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search DOMAINS ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1978351/+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 1976258] Re: icu ftbfs in the jammy release pocket
Hello Matthias, or anyone else affected, Accepted icu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/icu/70.1-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: icu (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1976258 Title: icu ftbfs in the jammy release pocket Status in icu package in Ubuntu: Fix Released Status in icu source package in Jammy: Fix Committed Bug description: [Impact] * icu is currently FTBFS in the jammy release pocket [Test Plan] * Build the package from -proposed against the jammy -proposed pocket * I have built it in a ppa: https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages [Regression Potential] * The Canonical IDs for timezones change periodically. If a change made to them here is reverted in new uploads of tzdata, they will have to be updated again. * The change is in a build-time test only, and therefore will not affect users. [Original Description] as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy- amd64.icu_70.1-2_BUILDING.txt.gz [...] make[4]: Leaving directory '/<>/source/test/cintltst' - | *** FAILING TEST SUMMARY FOR: intltest TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest --- ALL TESTS SUMMARY: ok: testdata iotest cintltst = ERRS: intltest make[3]: *** [Makefile:91: check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+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 1976258] Re: icu ftbfs in the jammy release pocket
** Changed in: icu (Ubuntu) Status: New => Fix Released ** Tags added: block-proposed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1976258 Title: icu ftbfs in the jammy release pocket Status in icu package in Ubuntu: Fix Released Status in icu source package in Jammy: Fix Committed Bug description: [Impact] * icu is currently FTBFS in the jammy release pocket [Test Plan] * Build the package from -proposed against the jammy -proposed pocket * I have built it in a ppa: https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages [Regression Potential] * The Canonical IDs for timezones change periodically. If a change made to them here is reverted in new uploads of tzdata, they will have to be updated again. * The change is in a build-time test only, and therefore will not affect users. [Original Description] as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy- amd64.icu_70.1-2_BUILDING.txt.gz [...] make[4]: Leaving directory '/<>/source/test/cintltst' - | *** FAILING TEST SUMMARY FOR: intltest TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest --- ALL TESTS SUMMARY: ok: testdata iotest cintltst = ERRS: intltest make[3]: *** [Makefile:91: check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+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 1969375] Please test proposed package
Hello Dean, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: In Progress Bug description: [Impact] * TPM2/FIDO cannot be used to unlock luks encrpyted block devices * due to missing build-time support in systemd * Error message: "TPM2 not supported on this build." [Test Plan] # 1: check no new binary deps have been introduced to the systemd package, other than "libssl3", which is already installed by default. # Compare to this version of systemd 249.11-0ubuntu3.1: $ apt-cache depends systemd systemd PreDepends: libblkid1 PreDepends: libc6 PreDepends: libcap2 PreDepends: libgcrypt20 PreDepends: liblz4-1 PreDepends: liblzma5 PreDepends: libselinux1 PreDepends: libzstd1 Depends: libacl1 Depends: libapparmor1 Depends: libaudit1 Depends: libcrypt1 Depends: libcryptsetup12 Depends: libgnutls30 Depends: libgpg-error0 Depends: libip4tc2 Depends: libkmod2 Depends: liblz4-1 Depends: libmount1 Depends: libpam0g Depends: libseccomp2 Depends: libsystemd0 Depends: util-linux Depends: mount Depends: adduser Conflicts: Conflicts: Conflicts: Breaks: resolvconf Breaks: udev |Recommends: dbus Recommends: dbus-broker dbus Recommends: networkd-dispatcher |Recommends: systemd-timesyncd Recommends: chrony ntp ntpsec openntpd systemd-timesyncd Suggests: systemd-container Suggests: policykit-1 # 2: check that systemd-cryptenroll doesn't have any undefined symbols that prevent it from running: $ systemd-cryptenroll --help # this should not crash systemd-cryptenroll [OPTIONS...] BLOCK-DEVICE Enroll a security token or authentication credential to a LUKS volume. -h --helpShow this help --version Show package version --passwordEnroll a user-supplied password --recovery-keyEnroll a recovery key --pkcs11-token-uri=URI Specify PKCS#11 security token URI --fido2-device=PATH Enroll a FIDO2-HMAC security token --fido2-with-client-pin=BOOL Whether to require entering a PIN to unlock the volume --fido2-with-user-presence=BOOL Whether to require user presence to unlock the volume --fido2-with-user-verification=BOOL Whether to require user verification to unlock the volume --tpm2-device=PATH Enroll a TPM2 device --tpm2-pcrs=PCR1+PCR2+PCR3+… Specify TPM2 PCRs to seal against --wipe-slot=SLOT1,SLOT2,… Wipe specified slots See the systemd-cryptenroll(1) man page for details. # initial setup $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cur3 Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo mkfs.ext4 /dev/mapper/volume $ sudo mount /dev/mapper/volume /mnt $ sudo touch /mnt/TPM_TEST $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 ..
[Touch-packages] [Bug 1969375] Re: systemd-cryptenroll does not support TPM2 devices
> "libssl3", but fortunately that one is already installed by default, > so should still be fine. For changes to so fundamental of a package, I think we want to be careful to have a higher standard than just "installed by default". In fact it is not possible to remove libssl3 from a jammy system without breaking it quite badly. - it is a dependency of ubuntu-minimal. - it is Priority: required - it is transitively essential: yes via login -> libpam-modules -> libnsl2 -> libtirpc3 -> libgssapi-krb5-2 -> libkrb5-3 -> libssl3 (it is unfortunate that this is true and it is not the case in kinetic, but for SRU purposes it works to our advantage). So I'm good with this from an SRU perspective. ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: In Progress Bug description: [Impact] * TPM2/FIDO cannot be used to unlock luks encrpyted block devices * due to missing build-time support in systemd * Error message: "TPM2 not supported on this build." [Test Plan] # 1: check no new binary deps have been introduced to the systemd package, other than "libssl3", which is already installed by default. # Compare to this version of systemd 249.11-0ubuntu3.1: $ apt-cache depends systemd systemd PreDepends: libblkid1 PreDepends: libc6 PreDepends: libcap2 PreDepends: libgcrypt20 PreDepends: liblz4-1 PreDepends: liblzma5 PreDepends: libselinux1 PreDepends: libzstd1 Depends: libacl1 Depends: libapparmor1 Depends: libaudit1 Depends: libcrypt1 Depends: libcryptsetup12 Depends: libgnutls30 Depends: libgpg-error0 Depends: libip4tc2 Depends: libkmod2 Depends: liblz4-1 Depends: libmount1 Depends: libpam0g Depends: libseccomp2 Depends: libsystemd0 Depends: util-linux Depends: mount Depends: adduser Conflicts: Conflicts: Conflicts: Breaks: resolvconf Breaks: udev |Recommends: dbus Recommends: dbus-broker dbus Recommends: networkd-dispatcher |Recommends: systemd-timesyncd Recommends: chrony ntp ntpsec openntpd systemd-timesyncd Suggests: systemd-container Suggests: policykit-1 # 2: check that systemd-cryptenroll doesn't have any undefined symbols that prevent it from running: $ systemd-cryptenroll --help # this should not crash systemd-cryptenroll [OPTIONS...] BLOCK-DEVICE Enroll a security token or authentication credential to a LUKS volume. -h --helpShow this help --version Show package version --passwordEnroll a user-supplied password --recovery-keyEnroll a recovery key --pkcs11-token-uri=URI Specify PKCS#11 security token URI --fido2-device=PATH Enroll a FIDO2-HMAC security token --fido2-with-client-pin=BOOL Whether to require entering a PIN to unlock the volume --fido2-with-user-presence=BOOL Whether to require user presence to unlock the volume --fido2-with-user-verification=BOOL Whether to require user verification to unlock the volume --tpm2-device=PATH Enroll a TPM2 device --tpm2-pcrs=PCR1+PCR2+PCR3+… Specify TPM2 PCRs to seal against --wipe-slot=SLOT1,SLOT2,… Wipe specified slots See the systemd-cryptenroll(1) man page for details. # initial setup $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cur3 Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo mkfs.ext4 /dev/mapper/volume $ sudo mount /dev/mapper/volume /mnt $ sudo touch /mnt/TPM_TEST $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. drwx-- 2 root root 16384 Jun 7 15:06 lost+found -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST $ sudo umount /dev/mapper/volume $ sudo cryptsetup luksClose volume $ ls -la /mnt # empty # 3: check non-TPM use cases (--password & --recovery-key) of systemd-cryptenroll have not regressed. # enroll additional password $ systemd-cryptenroll --password encrypted.img Please enter
[Touch-packages] [Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
Hello Alejandro, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1964494 Title: Setting DuplicateAddressDetection=none doesn't disable DAD for link- local IPs Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [impact] manual disabling of ipv4 DAD (IACD) for static link-local address does not work in jammy [test case] see 'Reproducer' in original description below [regression potential] failure to disable DAD, or incorrect disabling of DAD, or networkd issues around parsing of DAD config parsing [scope] this is needed for j and k introduced upstream by commit 1cf4ed142d6c1e2b9dc6a0bc74b6a83ae30b0f8e, first included in v249, so this bug does not affect impish or earlier fixed upstream by commit 2859932bd64d61a89f85fa027762bc16961fcf53 [original description] A customer reported network disconnections on their storage servers when running 'netplan apply'. The culprit was that they have link-local addresses configured and the Duplicate Address Detection (DAD) mechanism was delaying the interfaces from coming back up. As a workaround we tried to disable DAD for the interfaces but that's not working in Ubuntu 22.04: I've noticed that setting DuplicateAddressDetection=none for an interface with a link-local address (e.g., 169.254.*) via a .network file added to /etc/systemd/network/ doesn't really disable Duplicate Address Detection. OS and package versions: - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04 - systemd 249.5-2ubuntu4 Reproducer: --- 1- Set up Ubuntu 22.04 VM 2- Increase systemlog level: mkdir -p /etc/systemd/system/systemd-networkd.service.d/ cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf
[Touch-packages] [Bug 1967576] Re: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units
Hello Nick, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1967576 Title: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units Status in systemd package in Ubuntu: In Progress Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Committed Bug description: [Impact] * The "tests-in-lxd/boot-and-services/test_no_failed" autopkgtest fails * it did not stand out due to LP: #1976607 * we want to have proper autopkgtest coverage for systemd in Jammy LTS [Test Plan] * check autopkgtest logs on autopkgtest.ubuntu.com and make sure all instances of "boot-and-services" PASS (especially the "test_no_failed" test case. This includes running the test natively in autopkgtest and inside the "tests-in-lxd" container. [Where problems could occur] * other/new snapd-*.mount regressions could be hidden. * but snapd is being removed during systemd's tests anyway (introducing this failure) [Other Info] * The issue was not visible up to now, as the whole tests-in-lxd autopkgtests has been skipped: LP: #1976607 === original description === This build log provides an example of the problem: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz. During setup for tests-in-lxd, an attempt is made to purge snapd, but this fails: [ ... ] Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ... Stopping snap.lxd.activate.service Stopping unit snap.lxd.activate.service Waiting until unit snap.lxd.activate.service is stopped [attempt 1] snap.lxd.activate.service is stopped. Removing snap.lxd.activate.service Stopping snap.lxd.daemon.service Stopping unit snap.lxd.daemon.service Waiting until unit snap.lxd.daemon.service is stopped [attempt 1] snap.lxd.daemon.service is stopped. Removing snap.lxd.daemon.service Stopping snap.lxd.user-daemon.service Stopping unit snap.lxd.user-daemon.service Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1] snap.lxd.user-daemon.service is stopped. Removing snap.lxd.user-daemon.service Stopping snap-core20-1378.mount Stopping unit snap-core20-1378.mount Waiting until unit snap-core20-1378.mount is stopped [attempt 1] snap-core20-1378.mount is stopped. Removing snap core20 and revision 1378 Removing snap-core20-1378.mount Stopping snap-lxd-22672.mount Stopping unit snap-lxd-22672.mount Waiting until unit snap-lxd-22672.mount is stopped [attempt 1] snap-lxd-22672.mount is stopped. Removing snap lxd and revision 22672 rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function not implemented rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': Function not implemented rm: cannot remove
[Touch-packages] [Bug 1976607] Re: tests-in-lxd autopkgtest is skipped, due to missing 'lxd' deb
Hello Lukas, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1976607 Title: tests-in-lxd autopkgtest is skipped, due to missing 'lxd' deb Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: In Progress Bug description: [Impact] * The deb to snap transitional 'lxd' package was removed post feature-freeze in Jammy * this leads to systemd's 'tests-in-lxd' autopkgtest being skipped: * "tests-in-lxd SKIP installation fails and skip-not-installable set" * It reduces systemd's test coverage, which is bad. [Test Plan] * run systemd's autopkgtest * observe the logs * "tests-in-lxd SKIP installation fails and skip-not-installable set" should not be there * "tests-in-lxd PASS" should be there [Where problems could occur] * The change only affects systemd's 'test-in-lxd' autopkgtest * it does not have any impact outside the test suite [Other Info] * https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964786 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1976607/+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 1976371] Re: SRU for evolution-data-server 3.44.2
** Also affects: evolution (Ubuntu) Importance: Undecided Status: New ** Changed in: evolution (Ubuntu) Status: New => Fix Released ** Changed in: evolution (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1976371 Title: SRU for evolution-data-server 3.44.2 Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Jammy: Incomplete Status in evolution-data-server source package in Jammy: Incomplete Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.2/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1976371/+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 1962454] Re: Oops pages show wrong time window in JournalErrors
This bug was fixed in the package apport - 2.21.0-0ubuntu2 --- apport (2.21.0-0ubuntu2) kinetic; urgency=medium * tests: Use unlimited core ulimit for SIGQUIT test * data/apport: Fix log file writing if chown/chmod fails -- Benjamin Drung Fri, 10 Jun 2022 15:39:32 +0200 ** Changed in: apport (Ubuntu) Status: Triaged => Fix Released -- 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/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: Fix Released Status in Errors: Invalid Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Triaged Bug description: For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. But it should be possible to tell journalctl to collect entries starting *before* the crash and cover the full crash timeframe. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Oh, now I remember why this one was more complicated: it's for the pi *desktop specifically*. Can't add this to ubuntu-raspi-settings directly as that'll pull in zstd, z3fold, and all the zswap stuff on the server images too, which increases the memory burden on the minimal Zero 2 and 3A+ platforms. So (for my own notes): this requires the creation of a new ubuntu-raspi- settings-desktop package (src:ubuntu-settings) and the addition of that package to the desktop-raspi seed in the ubuntu seed repo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in linux-raspi package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1976371] Re: SRU for evolution-data-server 3.44.2
> As a component of GNOME core, How do I confirm that this is the case? https://wiki.ubuntu.com/StableReleaseUpdates/GNOME points to https://gitlab.gnome.org/GNOME/gnome-build- meta/-/tree/master/elements/core which does not list it. It does not appear in the discourse discussion at https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/3. I see that there have certainly been microrelease updates of eds in stable Ubuntu releases in the past, but I don't see how it's covered by the current (known-incomplete) microrelease exception. ** Changed in: evolution-data-server (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1976371 Title: SRU for evolution-data-server 3.44.2 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Incomplete Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.2/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1976371/+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 1978093] Re: openssl: FTBFS due to expired certificates
This bug was fixed in the package openssl - 3.0.3-5ubuntu3 --- openssl (3.0.3-5ubuntu3) kinetic; urgency=medium * d/p/lp1978093/*: renew some expiring test certificates (LP: #1978093) -- Simon Chopin Thu, 09 Jun 2022 13:20:55 +0200 ** Changed in: openssl (Ubuntu Kinetic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1978093 Title: openssl: FTBFS due to expired certificates Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Status in openssl source package in Focal: New Status in openssl source package in Impish: New Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Fix Released Bug description: [Impact] Some certificates in the openssl package expired on 2022-06-01, making the test suite fail. This needs to be fixed to facilitate future security updates. [Test Plan] Build the package. It currently fails with the following test summary: 80-test_ssl_new.t(Wstat: 256 Tests: 30 Failed: 1) Failed test: 12 Non-zero exit status: 1 [Where problems could occur] I supposed this could break the build even worse. [Other Info] This currently prevents 3.0.2-0ubuntu1.3 in Jammy from publication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1978093/+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 1977939] Re: logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock
> What's the market name of this dock? Lenovo ThinkPad USB-C Dock 40A90090EU -- 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/1977939 Title: logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock Status in systemd package in Ubuntu: New Bug description: lsusb identifies my docking station as: ID 17ef:3060 Lenovo ThinkPad Dock But when booting with the lid closed the laptop suspends before showing the login prompt with these settings; /etc/systemd/logind.conf [Login] #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore The following is a workaround: /etc/systemd/logind.conf.d/10-lid.conf [Login] HandleLidSwitchExternalPower=ignore But I think discovering the USB device ID should be enough to stop suspending the laptop. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977939/+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 1978325] [NEW] Color profile applied to only half of a MST display
Public bug reported: I have a Dell UP3214Q monitor, which uses display port multi stream transport, to support the full 4K resolution. After updating from Ubuntu 20.04 to 22.04 the two halves of the monitor suddenly show different colors. After fiddling around for quite a while I realized that the problem goes away, when adding and activating the "Standard Space - sRGB" profile in the Gnome color settings panel. By default it uses the "Automatic - DELL UP3214Q" profile. It seems any selected profile gets applied only to the first of the two display port transport streams, although they both belong to the same display. This took quite a while to figure out, because either removing the "Automatic" profiles or just using the toggle switch in the color settings panel did not disable the color-management for the corresponding display. So there seems to be another bug. I am running on Xorg using the Nvidia 510 drivers, but I saw the same problem, when switching to the Intel drivers. colord: 1.4.6-1 xorg: 1:7.7+23ubuntu2 nvidia-driver-510: 510.73.05-0ubuntu0.22.04.1 ** Affects: colord (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1978325 Title: Color profile applied to only half of a MST display Status in colord package in Ubuntu: New Bug description: I have a Dell UP3214Q monitor, which uses display port multi stream transport, to support the full 4K resolution. After updating from Ubuntu 20.04 to 22.04 the two halves of the monitor suddenly show different colors. After fiddling around for quite a while I realized that the problem goes away, when adding and activating the "Standard Space - sRGB" profile in the Gnome color settings panel. By default it uses the "Automatic - DELL UP3214Q" profile. It seems any selected profile gets applied only to the first of the two display port transport streams, although they both belong to the same display. This took quite a while to figure out, because either removing the "Automatic" profiles or just using the toggle switch in the color settings panel did not disable the color-management for the corresponding display. So there seems to be another bug. I am running on Xorg using the Nvidia 510 drivers, but I saw the same problem, when switching to the Intel drivers. colord: 1.4.6-1 xorg: 1:7.7+23ubuntu2 nvidia-driver-510: 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1978325/+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 1966562] Re: ubuntu-minimal should not depend on isc-dhcp-client
Thanks for the explanation and pointer to the ML thread, makes sense to me now. -- 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/1966562 Title: ubuntu-minimal should not depend on isc-dhcp-client Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-minimal already depends on `init` which depends on `systemd- sysv` which depends on `systemd` which comes with `systemd-networkd` that has a DHCP client in it. Having the isc-dhcp-client package feels redundant. # Additional information $ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ apt-cache policy ubuntu-minimal ubuntu-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1966562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
Hello Alexander, or anyone else affected, Accepted wpa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wpa (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
** Description changed: + * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server + + * Test case + try to connect to a TLS <= 1.1 access point + + * Regression potential + the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels + + --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html - Workaround are described in #22 and #36 by basically using + Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978316] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Went to execute update. Got the report ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 10 14:19:09 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1978316 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Went to execute update. Got the report ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 10 14:19:09 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1978316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level
I updated the ssl packages to 3.0.2-0ubuntu1.4, and confirmed the updated openssl.cnf with the new directives: --- ssl-orig/openssl.cnf2022-03-16 09:35:51.0 +0100 +++ ssl/openssl.cnf 2022-06-09 13:20:55.0 +0200 @@ -52,6 +52,7 @@ tsa_policy3 = 1.2.3.4.5.7 [openssl_init] providers = provider_sect +ssl_conf = ssl_sect # List of providers to load [provider_sect] @@ -388,3 +389,9 @@ oldcert = $insta::certout # insta.cert.p # Certificate revocation cmd = rr oldcert = $insta::certout # insta.cert.pem + +[ssl_sect] +system_default = system_default_sect + +[system_default_sect] +CipherString = DEFAULT:@SECLEVEL=2 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Fix Released Status in openssl package in Debian: Fix Released Bug description: [Impact] The OpenSSL 3.0 lead to a lot of broken setups. Some of them are regressions, but others are simply broken due to the use of outdated algorithms, such as SHA-1 signature on certificates. Changing the security level is a common action to identify and work around such cases, and as such the user should be able to change it easily in the default config file. The fix is to partially revert our delta that ignored a Debian patch: instead of ignoring the patch entirely, we modify it to only affect the default configuration file, and in a way that matches our patchset. Using this approach will allow us to pick up on Debian's changes more easily during subsequent merges. [Test Plan] To easily check that the setting is taken into account, one can use 'openssl ciphers -s' $ openssl ciphers -v -s | wc -l # Uses the default value 30 $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l 30 $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l 24 $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3 $ openssl ciphers -v -s | wc -l # Uses the new value from the config file 24 [Where problems could occur] The changes could break the overall configuration of OpenSSL! [Origin report] openssl.cnf as provided misses some directive, which make it a bit difficult to change security level, which since openssl 3 disables SHA1 signatures. See also this Debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1010360 and the committed fix: https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4 Can you please sync this change in Ubuntu openssl? This way one should just add a single directive to change the security level. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd
Ok... this looks to resolve what ever was changed THANK YOU! I will make a note to add this to our config changes for our base images I take it that 22.10 didn't get this yet??? So this will be needed going forward or 22.10 solves this glitch??? This is way above my pay grade... I'd just like to get some clarity and understanding on part of this. My question on this is: My BASE 22.04 VM image what we use to create a new 22.04 VM, is cloned/copied... to a VM.. then updated then. setup So in that cycle testing it power up, check that it still honors the pin/hold/reject file... OK, works, power down... come back to it a day later, rinse repeat, and IT WAS NOT HONORING THE PIN FILE! NO UPDATES were performed, ie: sudo apt-get update, upgrade, dist-upgrade, nothing. Just sudo apt-get -s install snapd to test.auto-upgrades are blocked in the various config files... so what triggers this fails as expected initially, then exhibits the same behavior... that tells me something is updating stealthy that should not. Which I need to disable. We don't want anything updating till I tell it to via sudo apt-get update, upgrade|dist-upgrade etc... Thank you again, for the solution, and I look forward to the educational reply to understand this more.. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1978125 Title: apt ignoring pin/block/hold files in preferences.d for snapd Status in apt package in Ubuntu: Triaged Bug description: Did some upgrades on a new box on 22.04, and had previously removed snapd and BLOCKED via a file in /etc/apt/preferences.d/ And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had to repurge it again! I had done this previously, and it appears that apt or something is IGNORING any pin/holds of snapd I use preferences.d files as using: sudo apt-mark hold snapd This has never worked on any package, ever... I have: /etc/apt/preferences.d$ cat snapd Package: snapd Pin: origin * Pin-Priority: -1 And that previously resulted in an error on apt in any attempt to install snapd, including using -s... NOW it will still attempt to install snapd! I've tried several variants of this as well, which other 22.04 and 20.04 boxes have, same on 22.04, it will allow snapd install! Did sudo apt-get update, apt update several times, rebooted several times, had various levels of the Pin-Priority from -1 to -, still will attempt to install snapd, versus the expected error sudo apt-get -s install snapd Expected error: Reading package lists... Done Building dependency tree Reading state information... Done Package snapd is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'snapd' has no installation candidate 20.04 boxes still seem to fail correctly with this pin file,. Checking my BASE VM IMAGE of 22.04 and this still works there, as its not been touched, this pin file blocks snapd from installing as expected... this is apt 2.3.15, updated one is 2.4.5 If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block file, and change the name to that package, it blocks it from installing! Anything but snapd this works for! 1)$ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 2) sudo apt-cache policy apt apt: Installed: 2.4.5 Candidate: 2.4.5 Version table: *** 2.4.5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What I expect to happen? HONOR MY BLOCK on snapd! It works for any random package chosen, EXCEPT snadp! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1978129] Re: Incomplete support for DT_RELR relocations on Ubuntu 22.04
** Tags added: fr-2459 -- 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/1978129 Title: Incomplete support for DT_RELR relocations on Ubuntu 22.04 Status in The Ubuntu-power-systems project: New Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: New Status in binutils source package in Kinetic: New Bug description: == Comment: #0 - Matheus Salgueiro Castanho - 2022-06-09 09:32:29 == ---Problem Description--- Latest glibc uses DT_RELR relocations, but linker support is incomplete as of binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated into the upstream 2.38 branch: PowerPC64 DT_RELR relative reloc addresses https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858 As mentioned in the binutils mailing list when this patch was discussed, this fixes several glibc regressions: https://sourceware.org/pipermail/binutils/2022-March/119921.html Contact Information = Matheus Castanho/mscasta...@ibm.com ---uname output--- N/A Machine Type = N/A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- git clone git://sourceware.org/git/glibc.git mkdir build && cd build ../glibc/configure --prefix=/usr && make -j8 && make check Userspace tool common name: binutils The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na *Additional Instructions for Matheus Castanho/mscasta...@ibm.com: -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1978129/+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 1977939] Re: logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock
What's the market name of this dock? -- 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/1977939 Title: logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock Status in systemd package in Ubuntu: New Bug description: lsusb identifies my docking station as: ID 17ef:3060 Lenovo ThinkPad Dock But when booting with the lid closed the laptop suspends before showing the login prompt with these settings; /etc/systemd/logind.conf [Login] #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore The following is a workaround: /etc/systemd/logind.conf.d/10-lid.conf [Login] HandleLidSwitchExternalPower=ignore But I think discovering the USB device ID should be enough to stop suspending the laptop. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977939/+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 1953720] Re: OSError: [Errno 30] Read-only file system: '/var/crash/...
No, /var is not mounted read-only. And no, no file-system failure. -- 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/1953720 Title: OSError: [Errno 30] Read-only file system: '/var/crash/... Status in apport package in Ubuntu: Incomplete Bug description: Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 408, in Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: main() Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 152, in main Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: if not dispatch(client, servers, config): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 239, in check Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: send_digest(digested, mock_runner, servers) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 262, in send_digest Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: _send_digest(runner, servers[0], digested) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 253, in _send_digest Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: runner.run(server, (digested, server)) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/pyzor/client.py", line 258, in run Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: response = self.routine(*args, **kwargs) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/pyzor/client.py", line 120, in _mock_check Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: msg = (b"Code: %s\nDiag: OK\nPV: %s\nThread: 1024\nCount: 0\n" Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'int' Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Error in sys.excepthook: Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: with os.fdopen(os.open(pr_filename, Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: OSError: [Errno 30] Read-only file system: '/var/crash/_usr_bin_pyzor.122.crash' 1) due to an encoding error, pyzor is throwing an exception. 2) /usr/lib/python3/dist-packages/apport_python_hook.py is the exception handler invoked (belonging to the python3-apport package) 3) This exception handler tries to write to /var/crash/_usr_bin_pyzor.122.crash, which fails I checked the permissions: # ls -l /var/crash total 0 # ls -ld /var/crash drwxrwxrwt 2 root root 4096 Dec 8 16:45 /var/crash # ls -ld /var/ drwxr-xr-x 18 root root 4096 Jun 23 2020 /var/ # ls -ld / drwxr-xr-x 24 root root 4096 Nov 30 06:19 / /var/crash is sticky, so why can't it write? # cat /proc/mounts |fgrep crash # ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-apport 2.20.11-0ubuntu27.21 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 09:39:40 2021 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2021-04-07 (245 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1953720/+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 1978307] [NEW] gwenview aborts with a std::out_of_range exception raised in libexiv2
Public bug reported: This bug seems to be a regression of KDE bug 441121: https://bugs.kde.org/show_bug.cgi?id=441121 When opening certain JPG files, gwenview aborts with an uncaught C++ exception std::out_of_range System is Ubuntu 18.04.6 LTS x86 with up-to-date packages. Terminal output and gdb backtrace follow. terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) Thread 1 "gwenview" received signal SIGABRT, Aborted. 0xf7fd5079 in __kernel_vsyscall () (gdb) bt #0 0xf7fd5079 in __kernel_vsyscall () #1 0xf5d1ea02 in __libc_signal_restore_set (set=0xbe8c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 #2 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 #3 0xf5d1fe91 in __GI_abort () at abort.c:79 #4 0xf5f3b97d in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #5 0xf5f43174 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #6 0xf5f431dd in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #7 0xf5f434dc in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #8 0xf5f6defa in std::__throw_out_of_range_fmt(char const*, ...) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #9 0xf5881da3 in ?? () from /usr/lib/i386-linux-gnu/libexiv2.so.14 Packages: libexiv2-14:i3860.25-3.1ubuntu0.18.0 i386 gwenview4:17.12.3-0ubuntu1 i386 ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Affects: gwenview (Ubuntu) Importance: Undecided Status: New ** Also affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1978307 Title: gwenview aborts with a std::out_of_range exception raised in libexiv2 Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: This bug seems to be a regression of KDE bug 441121: https://bugs.kde.org/show_bug.cgi?id=441121 When opening certain JPG files, gwenview aborts with an uncaught C++ exception std::out_of_range System is Ubuntu 18.04.6 LTS x86 with up-to-date packages. Terminal output and gdb backtrace follow. terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) Thread 1 "gwenview" received signal SIGABRT, Aborted. 0xf7fd5079 in __kernel_vsyscall () (gdb) bt #0 0xf7fd5079 in __kernel_vsyscall () #1 0xf5d1ea02 in __libc_signal_restore_set (set=0xbe8c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 #2 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 #3 0xf5d1fe91 in __GI_abort () at abort.c:79 #4 0xf5f3b97d in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #5 0xf5f43174 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #6 0xf5f431dd in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #7 0xf5f434dc in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #8 0xf5f6defa in std::__throw_out_of_range_fmt(char const*, ...) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #9 0xf5881da3 in ?? () from /usr/lib/i386-linux-gnu/libexiv2.so.14 Packages: libexiv2-14:i3860.25-3.1ubuntu0.18.0 i386 gwenview4:17.12.3-0ubuntu1 i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1978307/+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 1950828] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear().
** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Marcos Casquero (mcasquero) ** Changed in: ibus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1950828 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear(). Status in ibus package in Ubuntu: Fix Released Bug description: Bug report generated after logging in. Nothing other then the log in was done. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-2build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 15:58:02 2021 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2021-10-27 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211025) ProcCmdline: ibus-daemon --panel disable ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1950828/+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 1978288] Re: Totem "The specified movie could not be found" for a .mov
** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978288 Title: Totem "The specified movie could not be found" for a .mov Status in gstreamer-vaapi package in Ubuntu: New Bug description: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1978288/+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 1953720] Re: OSError: [Errno 30] Read-only file system: '/var/crash/...
The error says "Read-only file system". Is / (or /var) mounted read- only? Did you had a file-system failure where the kernel remounted the file system in read-only mode? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1953720 Title: OSError: [Errno 30] Read-only file system: '/var/crash/... Status in apport package in Ubuntu: Incomplete Bug description: Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 408, in Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: main() Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 152, in main Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: if not dispatch(client, servers, config): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 239, in check Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: send_digest(digested, mock_runner, servers) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 262, in send_digest Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: _send_digest(runner, servers[0], digested) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 253, in _send_digest Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: runner.run(server, (digested, server)) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/pyzor/client.py", line 258, in run Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: response = self.routine(*args, **kwargs) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/pyzor/client.py", line 120, in _mock_check Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: msg = (b"Code: %s\nDiag: OK\nPV: %s\nThread: 1024\nCount: 0\n" Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'int' Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Error in sys.excepthook: Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: with os.fdopen(os.open(pr_filename, Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: OSError: [Errno 30] Read-only file system: '/var/crash/_usr_bin_pyzor.122.crash' 1) due to an encoding error, pyzor is throwing an exception. 2) /usr/lib/python3/dist-packages/apport_python_hook.py is the exception handler invoked (belonging to the python3-apport package) 3) This exception handler tries to write to /var/crash/_usr_bin_pyzor.122.crash, which fails I checked the permissions: # ls -l /var/crash total 0 # ls -ld /var/crash drwxrwxrwt 2 root root 4096 Dec 8 16:45 /var/crash # ls -ld /var/ drwxr-xr-x 18 root root 4096 Jun 23 2020 /var/ # ls -ld / drwxr-xr-x 24 root root 4096 Nov 30 06:19 / /var/crash is sticky, so why can't it write? # cat /proc/mounts |fgrep crash # ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-apport 2.20.11-0ubuntu27.21 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 09:39:40 2021 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2021-04-07 (245 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1953720/+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 1442512] Re: Apport-kde crash when reporting bugs
It looks like nobody experiencing this any more. Closing this bug. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid ** Changed in: apport Status: Confirmed => Invalid -- 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/1442512 Title: Apport-kde crash when reporting bugs Status in Apport: Invalid Status in apport package in Ubuntu: Invalid Status in apport source package in Vivid: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.17-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac contains more details. Update 2022-04-20: Last seen in apport 2.19.2-0ubuntu5 on Ubuntu 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1442512/+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 1970013] Re: Totem Video player displays distorted video (Intel Ivy Bridge)
** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #519 https://gitlab.gnome.org/GNOME/totem/-/issues/519 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/-/issues/519 Importance: Unknown Status: Unknown ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed ** Changed in: totem (Ubuntu) Status: Incomplete => Confirmed ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1176 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1176 ** Also affects: gstreamer1.0 via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1176 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1970013 Title: Totem Video player displays distorted video (Intel Ivy Bridge) Status in Gstreamer1.0: Unknown Status in Totem: Unknown Status in gstreamer1.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra package. Default totem player unable to play videos properly. videos looks distorted. Forwarding videos does not work. Video get stopped once forwarded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 11:02:49 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9] InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 34601F4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.release: 2.59 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 34601F4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 34601F4 dmi.product.sku: LENOVO_MT_3460 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1970013/+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.
What do you expect to happen? Should I improve the error message to: "ERROR: The python3-launchpadlib package is not installed. Please install it."? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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 package in Ubuntu: Incomplete 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/ubuntu/+source/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 1972718] Re: ubuntu-bug should provide option to copy link instead of always opening
Can you provide steps to reproduce? -- 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/1972718 Title: ubuntu-bug should provide option to copy link instead of always opening Status in apport package in Ubuntu: New Bug description: Currently it always opens another tab directly via the web browser, which opens in the wrong Firefox container for me. It then always redirects and asks for me to sign in without the option of moving the tab inside the correct container. If I simply open it again in the correct tab, it tells me that no sign in is necessary and doesn't let me complete the original bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972718/+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 1978153] Re: Video plays back as grayscale and compressed on left
Sounds like you're the lucky one because other people aren't getting as far with gstreamer1.0-vaapi installed (bug 1962630). ** Package changed: gst-plugins-base1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) ** No longer affects: totem (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gstreamer-vaapi package in Ubuntu: New Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1978153/+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 1978301] [NEW] Broken contact URL in German translation
Public bug reported: "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. ** Affects: apport Importance: Undecided Status: New ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: apport (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.22.0 ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1978301 Title: Broken contact URL in German translation Status in Apport: New Status in apport package in Ubuntu: New Status in apport source package in Jammy: New Bug description: "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying: firefox wird durch einen von mozilla veröffentlichten Snap bereitgestellt. Für Hilfe gehen Sie über https://support.mozilla.org/kb/file-bug-report-or-feature-request- mozilla. The dot at the end is included in the URL link. The dot makes the URL link broken. The regular expression in gtk/apport-gtk for http URLs should become smarter. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1978301/+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 1970942] Re: ubuntu-bug firefox gives error "No contact address has been provided"
As of today, the firefox snap (version 101.0-2) provides the contact address. So closing this bug. ** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1970942 Title: ubuntu-bug firefox gives error "No contact address has been provided" Status in apport package in Ubuntu: Invalid Bug description: When I try to report a bug in Firefox on 22.04 with the Firefox Snap, it gives an error: "The problem cannot be reported: firefox is provided by a snap published by mozilla. No contact address has been provided; visit the forum at https://forum.snapcraft.io/ for help." I understand this is unexpected, as they do provide a contact address: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla and that this is the link that others are offered when running ubuntu-bug firefox ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82 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 CrashReports: 640:1001:124:9413623:2022-04-29 13:39:08.158073186 +0100:2022-04-29 13:39:09.174077949 +0100:/var/crash/_usr_bin_totem.1001.crash 600:117:124:37:2022-04-29 13:50:19.497838008 +0100:2022-04-29 13:38:42.086254937 +0100:/var/crash/_usr_bin_totem.1001.uploaded 664:1001:124:0:2022-04-29 13:39:09.158073230 +0100:2022-04-29 13:39:09.158073230 +0100:/var/crash/_usr_bin_totem.1001.upload CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 14:26:27 2022 InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1970942/+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 1029189] Re: ProcMaps.txt may contain private information such as username
** Branch unlinked: lp:~nik90/ubuntu-clock-app/1-fix-trunk-tests -- 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/1029189 Title: ProcMaps.txt may contain private information such as username Status in apport package in Ubuntu: Triaged Bug description: The ProcMaps.txt file that gets uploaded to Launchpad may contain private information such as username that can be obtained from the path of the home directory. 7fbd44c33000-7fbd44c34000 r--s 08:01 1306557 /home/alice/.local/share/mime/mime.cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1029189/+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 504340] Re: ubuntu-bug can't report bugs on kernel threads
This bug was fixed in 1.19 a long time ago. ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/504340 Title: ubuntu-bug can't report bugs on kernel threads Status in apport package in Ubuntu: Fix Released Bug description: I'm trying to report a bug where 'iwlagn' hogs my CPU PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 903 root 15 -5 000 R 99 0.0 104:05.39 iwlagn However, iwlagn being not a program, I can't use ubuntu-bug in any ways: ubuntu-bug 903 The specified process ID does not belong to a program. ubuntu-bug iwalgn Package iwlagn does not exist and worse than that, clicking on the "report a bug" button on the right in this page https://bugs.launchpad.net/ubuntu/ leads me back to this https://help.ubuntu.com/community/ReportingBugs instead of a bug submission form. And I can't find a way to submit a new bug outside of a package in Ubuntu... ProblemType: Bug Architecture: i386 Date: Thu Jan 7 11:54:18 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: apport 1.9.3-0ubuntu4.2 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=fr_CA.UTF-8 SHELL=/usr/bin/tcsh ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: apport Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/504340/+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 1962454] Re: Oops pages show wrong time window in JournalErrors
** Changed in: apport Assignee: Brian Murray (brian-murray) => Benjamin Drung (bdrung) -- 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/1962454 Title: Oops pages show wrong time window in JournalErrors Status in Apport: Fix Released Status in Errors: Invalid Status in apport package in Ubuntu: Triaged Status in apport source package in Jammy: Triaged Bug description: For example, I just experienced a crash at: Feb 28 17:31:12 And the JournalErrors entries are: Feb 28 17:31:30 - Feb 28 17:31:41 So don't relate to the crash. But it should be possible to tell journalctl to collect entries starting *before* the crash and cover the full crash timeframe. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1962454/+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 1978093] Re: openssl: FTBFS due to expired certificates
** Tags added: block-proposed-bionic block-proposed-focal block- proposed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1978093 Title: openssl: FTBFS due to expired certificates Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: New Status in openssl source package in Focal: New Status in openssl source package in Impish: New Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Kinetic: Confirmed Bug description: [Impact] Some certificates in the openssl package expired on 2022-06-01, making the test suite fail. This needs to be fixed to facilitate future security updates. [Test Plan] Build the package. It currently fails with the following test summary: 80-test_ssl_new.t(Wstat: 256 Tests: 30 Failed: 1) Failed test: 12 Non-zero exit status: 1 [Where problems could occur] I supposed this could break the build even worse. [Other Info] This currently prevents 3.0.2-0ubuntu1.3 in Jammy from publication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1978093/+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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)
I forwarded d/p/apply-ttl-to-records.patch to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012606 ** Bug watch added: Debian Bug tracker #1012606 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012606 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1977982 Title: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main) Status in keyutils package in Ubuntu: Confirmed Bug description: The Ubuntu delta contains two patches: * d/p/private-priv.patch: This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was a C++ project and would include the header file from libkeyutils-dev. Unfortunately, the header file contains variables named "private" - which is a keyword in C++ but not in C. The last version of nuxwdog from the archive is in Bionic so I am tempted to drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was removed from the archive: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011 If we drop this, there is a chance, however, that other packages would FTBFS if they build-depends on libkeyutils-dev and include the C header in C++ code. Here is the list of packages that build-depends on libkeyutils-dev: * bcachefs-tools * ceph * cifs-utils * ecryptfs-utils * gdm3 * gssproxy * ima-evm-utils * kafs-client * krb5 * kstart * ndctl * nfs-utils * python-keyutils * sssd * stress-ng All these packages are in Debian unstable today and are not FTBFS, so I'd assume it's fine to drop the patch. * d/p/apply-ttl-to-records.patch: This patch was applied recently (from upstream) to fix #1962453. I think we need to keep this patch and I'm considering forwarding it to Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1978153] Re: Video plays back as grayscale and compressed on left
removing gstreamer1.0-vaapi solves also the problem https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978288 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978153] Re: Video plays back as grayscale and compressed on left
after removing gstreamer1.0-vaapi the problem DISAPPEAR -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978288] Re: Totem "The specified movie could not be found" for a .mov
after removing gstreamer1.0-vaapi the problem DISAPPEAR see https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1978153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978288 Title: Totem "The specified movie could not be found" for a .mov Status in gstreamer1.0 package in Ubuntu: New Bug description: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978288/+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 1978153] Re: Video plays back as grayscale and compressed on left
with gst-play-1.0 --videosink="glsinkbin sink=gtkglsink" ... i have the same problem ** Attachment added: "Screenshot from 2022-06-10 09-57-17.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1978153/+attachment/5596283/+files/Screenshot%20from%202022-06-10%2009-57-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
k, let's try to keep pushing for 1.18 first ** Changed in: modemmanager (Ubuntu) Importance: Undecided => Low ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released -- 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/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: Fix Released Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like send 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+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 1978153] Re: Video plays back as grayscale and compressed on left
Do you get the issue if you do $ gst-play-1.0 --videosink="glsinkbin sink=gtkglsink" video.webm (where video.webm is the filename of what you try to play) Does uninstalling gstreamer1.0-vaapi fixes the issue? ** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978288] [NEW] Totem "The specified movie could not be found" for a .mov
Public bug reported: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978288 Title: Totem "The specified movie could not be found" for a .mov Status in gstreamer1.0 package in Ubuntu: New Bug description: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978288/+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 1910913] Re: Deprecating gdebi
Oh, wait, so are you saying gdebi contains a graphical interface?? Sorry, I never knew that. I used to only ever seeing suggestions about gdebi in the context of command line usage. That kind of changes everything. Yeah, sure, in this case it would make sense to keep gdebi in the repo. I'll close the bug in this case. > gdebi is / was a graphical enough utility for that purpose, but… see picture attached. That's sad indeed. I think that deserves a separate bugreport though. ** Changed in: gdebi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1910913 Title: Deprecating gdebi Status in gdebi package in Ubuntu: Invalid Bug description: Purpose of gdebi is to allow installing packages from a file. However, it's been 6 years since apt supported installation from a file¹. Let's make it easier on both maintainers and the people who have to install/use `gdebi` and then may need to search nuances, like passing options to dpkg. As far as I read gdebi man page, its functional seems fully covered by apt. The only thing I'm a bit in doubts about is the `root` option. But from my reading of docs, it seems that `gdebi --root=/foo myfile.deb` would be analogous to `apt install -o Dpkg::Options::="-- root=/foo" ./myfile.deb`. So, my suggesttion: installing gdebi on currently supported releases should print a deprecation notice that explains how a user can install local files with `apt` instead. Then eventually remove gdebi from repositories. I tried contacting maintainers of gdebi to ask whether it's worth adding a deprecation notice, but haven't found any ways to do that, and so I went straight to creating a report here. 1: https://mvogt.wordpress.com/2015/11/30/apt-1-1-released/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1910913/+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
