[Touch-packages] [Bug 1892825] Autopkgtest regression report (glibc/2.31-0ubuntu9.8)
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.8) for focal have finished running. The following regressions have been reported in tests triggered by the package: ruby-stackprof/0.2.15-2 (arm64) sphinxbase/0.8+5prealpha+1-8 (armhf) r-cran-ps/1.3.2-2 (s390x) linux-hwe-5.13/5.13.0-37.42~20.04.1 (armhf) mercurial/5.3.1-1ubuntu1 (armhf, ppc64el) linux-hwe-5.11/5.11.0-61.61 (armhf) mbedtls/2.16.4-1ubuntu2 (s390x) libreoffice/1:6.4.7-0ubuntu0.20.04.4 (armhf) ruby-ferret/0.11.8.7-2 (amd64) cross-toolchain-base/43ubuntu3.1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: Won't Fix Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8 The LANGUAGE=en_US.UTF-8 line should have been replaced by LANGUAGE=en_GB.UTF-8. $ update-locale --locale-file /tmp/locale LANGUAGE The LANGUAGE setting is now commented out. [regression potential] Apart from the general concerns about a glibc rebuild, this is a simple change to a simple script. Performing the test as in the test case section is enough to ensure it still works. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1927192] Autopkgtest regression report (glibc/2.31-0ubuntu9.8)
All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.8) for focal have finished running. The following regressions have been reported in tests triggered by the package: ruby-stackprof/0.2.15-2 (arm64) sphinxbase/0.8+5prealpha+1-8 (armhf) r-cran-ps/1.3.2-2 (s390x) linux-hwe-5.13/5.13.0-37.42~20.04.1 (armhf) mercurial/5.3.1-1ubuntu1 (armhf, ppc64el) linux-hwe-5.11/5.11.0-61.61 (armhf) mbedtls/2.16.4-1ubuntu2 (s390x) libreoffice/1:6.4.7-0ubuntu0.20.04.4 (armhf) ruby-ferret/0.11.8.7-2 (amd64) cross-toolchain-base/43ubuntu3.1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+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 1965219] Re: gnome lock screen does not permit reentering password
Sure, try a different kernel if you know how. There's a selection at: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D Note that the current HWE kernel for 20.04 is version 5.13, not 5.11 anymore. -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: h
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
** Changed in: ubuntu-kernel-tests Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Invalid Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+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 1965811] Re: software-properties-qt does not load driver information
Not an expert here, but the problem appears to be the import apt line 58 in SoftwarePropertiesQt.py. apt.Cache() lacks the packages attribute. Replacing apt with apt_pkg (as seen in the detect.py package and to which the apt_cache is passed) should fix the problem. apt is only called twice in SoftwarePropertiesQt.py and both times, it is used (incorrectly) as follows: self.apt_cache = apt.Cache() If this is the correct approach to fix this issue, I will attempt to submit a patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965811 Title: software-properties-qt does not load driver information Status in software-properties package in Ubuntu: New Status in software-properties source package in Jammy: New Bug description: Driver information is not being loaded by software-properties-qt. This appears to be a python issue, perhaps a python 3.10 compatibility issue. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1024, in detect_drivers self.devices = detect.system_device_drivers(self.apt_cache) File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in system_device_drivers for pkg, pkginfo in system_driver_packages(apt_cache, sys_path, File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in system_driver_packages for p in packages_for_modalias(apt_cache, alias): File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in packages_for_modalias apt_cache_hash = hash(package.get_fullname() for package in apt_cache.packages) AttributeError: 'Cache' object has no attribute 'packages' Exception ignored in: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 11:34:54 2022 InstallationDate: Installed on 2021-03-20 (365 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965811/+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 1958453] Re: clamav-freshclam does not upgrade successfuly
[Expired for ucf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ucf (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1958453 Title: clamav-freshclam does not upgrade successfuly Status in ucf package in Ubuntu: Expired Bug description: When upgrading my email server: Setting up clamav-freshclam (0.103.5+dfsg-1~20.04.1) ... Replacing config file /etc/clamav/freshclam.conf with new version cp: '/var/lib/ucf/hashfile.5' and '/var/lib/ucf/hashfile.6' are the same file dpkg: error processing package clamav-freshclam (--configure): installed clamav-freshclam package post-installation script subprocess returned error exit status 1 I chose to install the package maintainers configuration ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: clamav-freshclam 0.103.5+dfsg-1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-94.106-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: cpuid xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc aufs overlay dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd kvm_amd ccp input_leds kvm macvlan mac_hid k10temp sch_fq_codel w83795 msr ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear radeon i2c_algo_bit ttm drm_kms_helper syscopyarea hid_generic sysfillrect sysimgblt fb_sys_fops usbhid pata_acpi ahci hid pata_atiixp i2c_piix4 drm libahci tg3 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 19 21:19:00 2022 KernLog: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: clamav UpgradeStatus: Upgraded to focal on 2020-12-29 (386 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1958453/+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 1965820] Re: Screen goes black when opening Settings, following error appears
** Package changed: xorg (Ubuntu) => gnome-shell (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/1965820 Title: Screen goes black when opening Settings, following error appears Status in gnome-shell package in Ubuntu: New Bug description: Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012 _load@resource:///org/gnome/shell/ui/background.js:533:14#012 _init@resource:///org/gnome/shell/ui/background.js:282:14#012 Background@resource:///org/gnome/shell/ui/background.js:237:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012 _load@resource:///org/gnome/shell/ui/background.js:533:14#012 _init@resource:///org/gnome/shell/ui/background.js:282:14#012 Background@resource:///org/gnome/shell/ui/background.js:237:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012 _updateBackgrounds@resource:///o] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 20:57:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash Rate] [1458:404c] InstallationDate: Installed on 2022-03-16 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F13h dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF13h:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS MASTER dmi.product.sku: Default string dmi.product.version: Defaul
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Thanks for that. The log in comment #12 shows these errors which may explain it: Mär 22 01:57:12 aletheia systemd[1]: systemd-logind.service: Watchdog timeout (limit 3min)! Mär 22 01:57:12 aletheia systemd[1]: systemd-logind.service: Killing process 1501 (systemd-logind) with signal SIGABRT. ... Mär 22 01:57:12 aletheia systemd[1]: systemd-logind.service: Main process exited, code=killed, status=6/ABRT ... Mär 22 01:57:13 aletheia /usr/lib/gdm3/gdm-x-session[2486]: (EE) Mär 22 01:57:13 aletheia /usr/lib/gdm3/gdm-x-session[2486]: Fatal server error: Mär 22 01:57:13 aletheia /usr/lib/gdm3/gdm-x-session[2486]: (EE) systemd-logind disappeared (stopped/restarted?) ... Mär 22 01:57:13 aletheia systemd-logind[95934]: Failed to restore VT, ignoring: Bad file descriptor And yes we expect "Fn+Ctrl+Alt+F??" to fail in this case because the processes which implement that combo have failed. To be sure we're on the right track, please reboot, wait for the bug to occur again, and then redo: journalctl -b-1 > prevboot.txt ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.3
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
A [ Regression potential ] section was added to the description. @Łukasz Zemczak let me know if there are other details you would like. Thank you! ** Description changed: - [Impact] In some cases, ipconfig can take a longer time than the user-specified timeouts, causing unexpected delays. [Test Plan] Any situation where ipconfig encounters an error sending the DHCP packet, it will automatically set a delay of 10 seconds, which could be longer than the user-specified timeout. It can be reproduced by creating a dummy interface and attempting to run ipconfig on it with a timeout value of less than 10: # ip link add eth1 type dummy # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date Thu Nov 18 04:46:13 EST 2021 IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up Thu Nov 18 04:46:23 EST 2021 ^ Notice above, ipconfig thinks that it waited 2 seconds, but the timestamps show an actual delay of 10 seconds. [Where problems could occur] Please see reproduction steps above. We are seeing this in production too (see comment #2). [Other Info] A patch to fix the issue is being proposed here. It is a safe fix - it only checks before going into sleep that the timeout never exceeds the user-requested value. [Original Description] In some cases, ipconfig can take longer than the user-specified timeouts, causing unexpected delays. in main.c, in function loop(), the process can go into process_timeout_event() (or process_receive_event() ) and if it encounters an error situation, will set an attempt to "try again later" at time equal now + 10 seconds by setting s->expire = now + 10; This can happen at any time during the main event loop, which can end up extending the user-specified timeout if "now + 10" is greater than "start_time + user-specified-timeout". I believe a patch like the following is needed to avoid this problem: --- a/usr/kinit/ipconfig/main.c +++ b/usr/kinit/ipconfig/main.c @@ -437,6 +437,13 @@ static int loop(void) if (timeout > s->expire - now.tv_sec) timeout = s->expire - now.tv_sec; + + /* Compensate for already-lost time */ + gettimeofday(&now, NULL); + if (now.tv_sec + timeout > start + loop_timeout) { + timeout = loop_timeout - (now.tv_sec - start); + printf("Lowered timeout to match user request = (%d s) \n", timeout); + } } I believe the current behaviour is buggy. This is confirmed when the following line is executed: if (loop_timeout >= 0 && now.tv_sec - start >= loop_timeout) { printf("IP-Config: no response after %d " "secs - giving up\n", loop_timeout); rc = -1; goto bail; } 'loop_timeout' is the user-specified time-out. With a value of 2, in case of error, this line prints: IP-Config: no response after 2 secs - giving up So it thinks that it waited 2 seconds - however, in reality it had actually waited for 10 seconds. The suggested code-change ensures that the timeout that is actually used never exceeds the user-specified timeout. + + + [ Regression potential ] + + This change ensures that user-specified timeouts are never exceeded, which is a problem that appears to happen only in case of interface errors. + It may be that someone is relying on current behaviour where they receive DHCP offers after their specified timeout (but within the 10-second error timeout). However, 1) that is buggy behaviour and should be exposed. Such a user would need to update their specified timeout to make it long enough to receive the DHCP offer (setting the timeout to 10 would keep the existing behaviour). 2) I think it is unlikely that such a scenario exists at all. The 10-second timeout problem happens when there are problems with the interface that prevent it from even sending out the DHCP request. I think it is very unlikely (or even, impossible) that DHCP offers would be received on a dead interface. + + Based on the above points, I consider the regression potential to be + very low for this change. I do not expect anyone who is currently using + ipconfig successfully to notice this change. + + I believe the only difference introduced by this is the reduction of + delays caused by dead or problematic network interfaces. Those error + delays are shortened such that they never exceeed user-specified + timeouts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hello @Łukasz Zemczak I understand your concern about breaking existing behaviour. I would like to clarify 2 things: 1) The change introduced here only ensures that user-requested timeouts are never exceeded. That means that if something is currently accepting DHCP offers after the specified timeout has expired, then that is buggy behaviour. It would make sense that such behaviour would change after this change. If such a user exists, they would need to change their timeout values so as to be long enough to receive the DHCP offer that they want. I think it makes sense that such buggy behaviour would get exposed with this fix. 2) That said, I consider it very unlikely for that scenario to even exist. The main reason is that the bug (going over the specified timeout) happens in the case where there is a problem bringing up the interface, so the ipconfig logic simply says "try again in 10 seconds" in that case, even if that 10 seconds is longer than the entire specified timeout. Since this happens when there are interface problems, it can be safely assumed that no DHCP offers will be received anyway on that problematic interface (in fact, no DHCP request was even sent out). These 10 seconds are just dead time, basically. So I would consider it unlikely that anyone who is successfully using ipconfig today would even notice a change. This patch should only affect those 10-seconds delays caused by problematic interfaces not normal functioning interfaces, (and even then, it would only affect them if the user-specified timeout is less than 10 seconds). I am not sure what you mean by how it differs from focal+. The last time I checked, the timeout-bug was affecting ipconfig in both focal and bionic (and upstream HEAD). However, we are only interested in Bionic since Focal does not even use ipconfig it uses dhclient instead. I will add a regression-potential section to the description with more info. Thanks. I will try to expand the regression-potential section with additional info about this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases Status in klibc package in Ubuntu: New Status in klibc source package in Bionic: Incomplete Bug description: [Impact] In some cases, ipconfig can take a longer time than the user-specified timeouts, causing unexpected delays. [Test Plan] Any situation where ipconfig encounters an error sending the DHCP packet, it will automatically set a delay of 10 seconds, which could be longer than the user-specified timeout. It can be reproduced by creating a dummy interface and attempting to run ipconfig on it with a timeout value of less than 10: # ip link add eth1 type dummy # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date Thu Nov 18 04:46:13 EST 2021 IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up Thu Nov 18 04:46:23 EST 2021 ^ Notice above, ipconfig thinks that it waited 2 seconds, but the timestamps show an actual delay of 10 seconds. [Where problems could occur] Please see reproduction steps above. We are seeing this in production too (see comment #2). [Other Info] A patch to fix the issue is being proposed here. It is a safe fix - it only checks before going into sleep that the timeout never exceeds the user-requested value. [Original Description] In some cases, ipconfig can take longer than the user-specified timeouts, causing unexpected delays. in main.c, in function loop(), the process can go into process_timeout_event() (or process_receive_event() ) and if it encounters an error situation, will set an attempt to "try again later" at time equal now + 10 seconds by setting s->expire = now + 10; This can happen at any time during the main event loop, which can end up extending the user-specified timeout if "now + 10" is greater than "start_time + user-specified-timeout". I believe a patch like the following is needed to avoid this problem: --- a/usr/kinit/ipconfig/main.c +++ b/usr/kinit/ipconfig/main.c @@ -437,6 +437,13 @@ static int loop(void) if (timeout > s->expire - now.tv_sec) timeout = s->expire - now.tv_sec; + + /* Compensate for already-lost time */ + gettimeofday(&now, NULL); + if (now.tv_sec + timeout > start + loop_timeout) { + timeout = loop_timeout - (now.tv_sec - start); + printf("Lowered timeout to match user request = (%d s) \n", timeout); + } } I believe the current behaviour is buggy. This is confirmed when the following line is executed:
[Touch-packages] [Bug 1965830] [NEW] apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
Public bug reported: this crash did happen after i successfully submitted my last report. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 18:22:47 2022 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= SHELL=/bin/bash LANG=de_DE.UTF-8 Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm games lpadmin plugdev sudo users vboxusers ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy need-duplicate-check third-party-packages ** Information type changed from Private to Public -- 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/1965830 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in apport package in Ubuntu: New Bug description: this crash did happen after i successfully submitted my last report. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 18:22:47 2022 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= SHELL=/bin/bash LANG=de_DE.UTF-8 Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm games lpadmin plugdev sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1965830/+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 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in g_slice_alloc()
** Information type changed from Private to Public -- 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/1965809 Title: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in g_slice_alloc() Status in gstreamer1.0 package in Ubuntu: New Bug description: Attempting to open videos in multiple formats (tried .webm and .mp4 so far) results in ‘specified movie could not be found’ errors in Videos. I’ve moved them into multiple folders with the same result. If I hit the upper left button ’ < ’ I can see the file just fine ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 14:20:08 2022 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2022-02-17 (32 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f023771dd0c :mov 0x8(%r12),%rax PC (0x7f023771dd0c) ok source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: totem crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1965809/+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 1965791] Re: Update tzdata to version 2022a
** Changed in: tzdata (Ubuntu Impish) Status: New => In Progress ** Changed in: tzdata (Ubuntu Impish) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1965791 Title: Update tzdata to version 2022a Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Impish: In Progress Status in tzdata source package in Jammy: In Progress Bug description: New upstream version affecting the following timestamp: $region/$timezone = Asia/Gaza Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Asia/Gaza | grep 2022 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); print(str(tz.utcoffset(datetime(2022, 3, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965791] Re: Update tzdata to version 2022a
ACK from the security team to pocket-copy to -security. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1965791 Title: Update tzdata to version 2022a Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Impish: In Progress Status in tzdata source package in Jammy: In Progress Bug description: New upstream version affecting the following timestamp: $region/$timezone = Asia/Gaza Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Asia/Gaza | grep 2022 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); print(str(tz.utcoffset(datetime(2022, 3, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965820] [NEW] Screen goes black when opening Settings, following error appears
Public bug reported: Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012 _load@resource:///org/gnome/shell/ui/background.js:533:14#012 _init@resource:///org/gnome/shell/ui/background.js:282:14#012 Background@resource:///org/gnome/shell/ui/background.js:237:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012 _load@resource:///org/gnome/shell/ui/background.js:533:14#012 _init@resource:///org/gnome/shell/ui/background.js:282:14#012 Background@resource:///org/gnome/shell/ui/background.js:237:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012 _updateBackgrounds@resource:///o] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 20:57:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash Rate] [1458:404c] InstallationDate: Installed on 2022-03-16 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F13h dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF13h:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS MASTER dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.
[Touch-packages] [Bug 1965791] Re: Update tzdata to version 2022a
** Also affects: tzdata (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu Jammy) Status: New => In Progress ** Changed in: tzdata (Ubuntu Jammy) Importance: Undecided => High ** Changed in: tzdata (Ubuntu Jammy) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1965791 Title: Update tzdata to version 2022a Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Bionic: New Status in tzdata source package in Focal: New Status in tzdata source package in Impish: New Status in tzdata source package in Jammy: In Progress Bug description: New upstream version affecting the following timestamp: $region/$timezone = Asia/Gaza Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Asia/Gaza | grep 2022 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); print(str(tz.utcoffset(datetime(2022, 3, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965791] Re: Update tzdata to version 2022a
** Description changed: New upstream version affecting the following timestamp: - $region/$timezone = Palestine + $region/$timezone = Asia/Gaza Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] - 1) zdump -v Palestine | grep 2021 + 1) zdump -v Asia/Gaza | grep 2022 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu - 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Palenstine')); print(str(tz.utcoffset(datetime(2021, 9, 26' + 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); print(str(tz.utcoffset(datetime(2022, 3, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1965791 Title: Update tzdata to version 2022a Status in tzdata package in Ubuntu: New Bug description: New upstream version affecting the following timestamp: $region/$timezone = Asia/Gaza Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Asia/Gaza | grep 2022 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); print(str(tz.utcoffset(datetime(2022, 3, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965811] [NEW] software-properties-qt does not load driver information
Public bug reported: Driver information is not being loaded by software-properties-qt. This appears to be a python issue, perhaps a python 3.10 compatibility issue. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1024, in detect_drivers self.devices = detect.system_device_drivers(self.apt_cache) File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in system_device_drivers for pkg, pkginfo in system_driver_packages(apt_cache, sys_path, File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in system_driver_packages for p in packages_for_modalias(apt_cache, alias): File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in packages_for_modalias apt_cache_hash = hash(package.get_fullname() for package in apt_cache.packages) AttributeError: 'Cache' object has no attribute 'packages' Exception ignored in: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 11:34:54 2022 InstallationDate: Installed on 2021-03-20 (365 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago) ** Affects: software-properties (Ubuntu) Importance: Critical Status: New ** Affects: software-properties (Ubuntu Jammy) Importance: Critical Status: New ** Tags: amd64 apport-bug jammy ** Changed in: software-properties (Ubuntu) Importance: Undecided => Critical ** Also affects: software-properties (Ubuntu Jammy) Importance: Critical Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965811 Title: software-properties-qt does not load driver information Status in software-properties package in Ubuntu: New Status in software-properties source package in Jammy: New Bug description: Driver information is not being loaded by software-properties-qt. This appears to be a python issue, perhaps a python 3.10 compatibility issue. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1024, in detect_drivers self.devices = detect.system_device_drivers(self.apt_cache) File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in system_device_drivers for pkg, pkginfo in system_driver_packages(apt_cache, sys_path, File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in system_driver_packages for p in packages_for_modalias(apt_cache, alias): File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in packages_for_modalias apt_cache_hash = hash(package.get_fullname() for package in apt_cache.packages) AttributeError: 'Cache' object has no attribute 'packages' Exception ignored in: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 11:34:54 2022 InstallationDate: Installed on 2021-03-20 (365 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965811/+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 1965141] Re: openssl: package the new bugfix release 3.0.2
[ubuntu/jammy-proposed] openssl 3.0.2-0ubuntu1 (Accepted) Uploaded to proposed, it has to go through the usual process of passing autopkgtests and such. It shouldn't need any additional package rebuilds because of no ABI changes but expect autopkgtests to run hot a while ** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1965141 Title: openssl: package the new bugfix release 3.0.2 Status in openssl package in Ubuntu: Fix Committed Bug description: The latest bugfix release of the 3.0 branch is out, we should package it for Jammy. In the preliminary packaging I've done the test suite fails, i'm trying to track down the cause ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
OK I printed two files successfully with: jbm@curlew:~/test_set$ lp Truloc-211-Retainer.pdf request id is jbm-2810-314 (1 file(s)) jbm@curlew:~/test_set$ lp IMG_4737x.JPG request id is jbm-2810-315 (1 file(s)) The files are enclosed, together with the subsequent error_log. The Trulocpdf file should be the same one that failed whem sent from Document Viewer. On 2022-03-21 17:44, Till Kamppeter wrote: > I your error_log I have found the following: > > D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error- > document-format-error (client-error-document-format-error) > > This looks like that the printer was not able to work with the data it > received. > > The printer reports that it accepts PWG Raster as the only of the known > data formats used for driverless printing (it supports other formats, > too, but these are formats we cannot generate). Therefore we print in > PWG Raster format. > > It is possible that some printers have firmware bugs, not able to print > certain files in standard format. It is less probable that the PWG > Raster provided by us has problems as otherwise I would have received > many more bug reports. > > Now I need also CUPS error_log output from jobs which succeeded for you > and also I need the files which you have actually sent, both succeeding > and failing files. Could you attach these? > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "IMG_4737x.JPG" https://bugs.launchpad.net/bugs/1964095/+attachment/5571377/+files/IMG_4737x.JPG ** Attachment added: "Truloc-211-Retainer.pdf" https://bugs.launchpad.net/bugs/1964095/+attachment/5571378/+files/Truloc-211-Retainer.pdf ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1964095/+attachment/5571379/+files/error_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
OK, that worked; file attached. On 2022-03-21 17:26, Till Kamppeter wrote: > Seems that your version of "driverless" is too old, not yet having the " > --std-ipp-uris" option (see also output of "driverless -h"). > > But I have found the URI you need in your error_log. Please run the > following command: > > ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer- > attributes.test > attrs.txt > > and attach attrs.txt. > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "attrs.txt" https://bugs.launchpad.net/bugs/1964095/+attachment/5571360/+files/attrs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed
I your error_log I have found the following: D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error- document-format-error (client-error-document-format-error) This looks like that the printer was not able to work with the data it received. The printer reports that it accepts PWG Raster as the only of the known data formats used for driverless printing (it supports other formats, too, but these are formats we cannot generate). Therefore we print in PWG Raster format. It is possible that some printers have firmware bugs, not able to print certain files in standard format. It is less probable that the PWG Raster provided by us has problems as otherwise I would have received many more bug reports. Now I need also CUPS error_log output from jobs which succeeded for you and also I need the files which you have actually sent, both succeeding and failing files. Could you attach these? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1965791] [NEW] Update tzdata to version 2022a
Public bug reported: New upstream version affecting the following timestamp: $region/$timezone = Palestine Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Palestine | grep 2021 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Palenstine')); print(str(tz.utcoffset(datetime(2021, 9, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: fr-2121 ** Tags added: fr-2121 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1965791 Title: Update tzdata to version 2022a Status in tzdata package in Ubuntu: New Bug description: New upstream version affecting the following timestamp: $region/$timezone = Palestine Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [Test Case for all releases] 1) zdump -v Palestine | grep 2021 For releases with ICU timezone data verification is done using the following with dates before and after the change: [Test Case for releases >= 20.04 LTS] 1) sudo apt-get install python3-icu 2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Palenstine')); print(str(tz.utcoffset(datetime(2021, 9, 26' Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: [Test Case for releases <= 20.04 LTS] diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1964095] Re: print sent to Epson ET-2810 is not printed
Seems that your version of "driverless" is too old, not yet having the " --std-ipp-uris" option (see also output of "driverless -h"). But I have found the URI you need in your error_log. Please run the following command: ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer- attributes.test > attrs.txt and attach attrs.txt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
Tried the below, but it didn't work for me: jbm@curlew:~$ driverless --std-ipp-uris ERROR: Unable to create PPD file: Could not poll sufficient capability info from the printer (--std-ipp-uris, (null)) via IPP! On 2022-03-21 15:36, Till Kamppeter wrote: > Thanks for the files. > > For the "ipptool -tv ..." command do the following: > > Run > > driverless --std-ipp-uris > > You get an URI for your printer in standard IPP format. Please use that > URI for the "ipptool -tv ..." command of my comment above (comment #2) > and attach the attrs.txt here. > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1965673] Re: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- 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/1965673 Title: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Status in ibus: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 20/03/2022 Journal logs spam a lot of lines like these: mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x7f896cf7cad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x557a992efd20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Probably regression bug upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5147 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:34:37 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1965673/+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 1964095] Re: print sent to Epson ET-2810 is not printed
Also note that the web interface of Launchpad only allows one attached file per comment. If you want to attach more files, simply post more comments, where the actual comment field can also stay empty in case you wrote everything already in the comment of the first file. e-mail answers seem to allow any number of attachments though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed
Thanks for the files. For the "ipptool -tv ..." command do the following: Run driverless --std-ipp-uris You get an URI for your printer in standard IPP format. Please use that URI for the "ipptool -tv ..." command of my comment above (comment #2) and attach the attrs.txt here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
Hi Till Kamppeter. Thanks for looking into my bug report. I have replied via Launchpad, but wasn't able to confirm that I managed to attach the files you asked for, so I attach them here, too. --jan On 2022-03-20 17:54, Till Kamppeter wrote: > Could you also attach your file > > /etc/cups/ppd/EPSON_ET_2810_Series.ppd > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1964095/+attachment/5571317/+files/error_log ** Attachment added: "jbm-2810.ppd" https://bugs.launchpad.net/bugs/1964095/+attachment/5571318/+files/jbm-2810.ppd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1965141] Re: openssl: package the new bugfix release 3.0.2
I've got some extra cycles later today, so I'll happily help the Security team out and get this uploaded later today (Eastern US time for clarity sake when I say "later today") ** Changed in: openssl (Ubuntu) Assignee: (unassigned) => Thomas Ward (teward) ** Changed in: openssl (Ubuntu) Status: New => In Progress -- 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/1965141 Title: openssl: package the new bugfix release 3.0.2 Status in openssl package in Ubuntu: In Progress Bug description: The latest bugfix release of the 3.0 branch is out, we should package it for Jammy. In the preliminary packaging I've done the test suite fails, i'm trying to track down the cause ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+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 1964095] Re: print sent to Epson ET-2810 is not printed
In response to advice 2022_03_20: jbm@curlew:~/Desktop$ driverless ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ jbm@curlew:~/Desktop$ ipptool -tv ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ get-printer-attributes.test > attrs.test ipptool: Unable to connect to "EPSON ET-2810 Series._ipp._tcp.local" on port 631 - Name or service not known I suppose this might possibly have failed because I have assigned a new name to the printer after the debug report using: lpadmin -p jbm-2810 -v ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ - E -m driverless:ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ Since then I have had good experience printing pdf- and jpg-files from a terminal window using the lp command; printing e-mail and pdf-attachments from Thunderbird also works; printing pdf-files from Document Viewer and jpg-files from Image Viewer fails. jbm@curlew:~/Desktop$ cupsctl --debug-logging Attepted to print a file called "Truloc-211-Retainer.pdf" from Document Viewer to jbm-2810; it appears to be placed in the print queue and toleave the print queue but no print emerges from the printer. I have tried to attach the cups/error_log file and the jbm-2810.ppd file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1965141] Re: openssl: package the new bugfix release 3.0.2
This update will fix CVE-2022-0778, so the security team is interested in seeing it in jammy. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0778 -- 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/1965141 Title: openssl: package the new bugfix release 3.0.2 Status in openssl package in Ubuntu: New Bug description: The latest bugfix release of the 3.0 branch is out, we should package it for Jammy. In the preliminary packaging I've done the test suite fails, i'm trying to track down the cause ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
Could you clarify what exactly you are trying to achieve? You mention both a VPN and the RDP protocol. Knowing exactly which software you're using could help us track down some more logs to know more about the failure. Without more information there isn't much we can do. -- 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/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: New Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
See bug 1965758 this also breaks focal-backports - please upload the fix there as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade Status in debconf package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in docker.io package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Released Status in debconf source package in Jammy: Fix Released Status in debhelper source package in Jammy: Fix Released Status in docker.io source package in Jammy: Fix Released Status in libvirt source package in Jammy: Fix Released Status in debconf package in Debian: New Status in debhelper package in Debian: New Bug description: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-stop-on-upgrade (or its deprecated alias --no- restart-on-upgrade), restart anyway. Please note: this is nothing to do with the --no-restart-after-upgrade flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open-iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1712223] Re: open-vm-tools does not work under wayland
Hello Alexander, note that Xorg is available in Jammy both as the native graphical session and via xwayland. On this bug report: could you please elaborate more on what exactly happens? In particular could you guide us into reproducing the problem on a clean Jammy install, making clear "what should happen" and "what actually happens" when facing the problem? As we're waiting for more information here I'm marking this bug report as Incomplete. Thanks! ** Changed in: open-vm-tools (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1712223 Title: open-vm-tools does not work under wayland Status in open-vm-tools package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: At first I thought this bug was caused with the recent changes in open-vm-tools 10.1.10; however, after restoring my VM to the snapshot that had 17.04 and re-performing the dist-upgrade with open-vm-tools and open-vm-tools-desktop held at 10.1.5 I am experiencing the same issue where VMWare Workstation no longer can interact with display resolution detection of the host monitor(s). Multiple monitor support is also lost in the update process. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 17:09:59 2017 DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components: {'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful': {'multiverse', 'restricted', 'universe', 'main'}, 'artful-security': {'multiverse', 'restricted', 'universe', 'main'}} DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-30 (264 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 21 16:27:55 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.versio
[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
Still no activity in the upstream issue, however I think OpenSSH 8.9 offers a mechanism that can help avoiding hitting MaxAuthTries in some cases: "destination constraints", see documentation for -h in ssh- add(1). AIUI constraining should limit the number of keys tried against a given host, making reaching MaxAuthTries more difficult. More info: https://www.openssh.com/agent-restrict.html https://lwn.net/Articles/880458/ It is not clear to me if setting destination constraints also affects the order in which keys are tried (narrower scope => higher priority). Another workaround is preventing ssh to reach the agent: SSH_AUTH_SOCK= ssh -i -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1872145/+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 1965141] Re: openssl: package the new bugfix release 3.0.2
Attached is the debdiff for the upgrade. You can also find the package at https://launchpad.net/~schopin/+archive/ubuntu/test- ppa/+sourcepub/13390252/+listing-archive-extra (mind the version number). Note the new Ubuntu-specific patch to disable some tests that use a configuration that's invalid under our changes (TLS 1.1 + seclevel 3). ** Patch added: "openssl.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+attachment/5571287/+files/openssl.debdiff -- 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/1965141 Title: openssl: package the new bugfix release 3.0.2 Status in openssl package in Ubuntu: New Bug description: The latest bugfix release of the 3.0 branch is out, we should package it for Jammy. In the preliminary packaging I've done the test suite fails, i'm trying to track down the cause ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+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 1712223] Re: open-vm-tools does not work under wayland
Thanks for the ping on this old case Alexander! Can you confirm that this is what you see on 22.04 with the there recent 2:11.3.5-1ubuntu4 version of open-vm-tools? I have subscribed John Wolfe who looks after open-vm-tools from VMwares side and might have more details. Further I added a bug task for "wayland" so that the Desktop team can have a look as well. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1712223 Title: open-vm-tools does not work under wayland Status in open-vm-tools package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: At first I thought this bug was caused with the recent changes in open-vm-tools 10.1.10; however, after restoring my VM to the snapshot that had 17.04 and re-performing the dist-upgrade with open-vm-tools and open-vm-tools-desktop held at 10.1.5 I am experiencing the same issue where VMWare Workstation no longer can interact with display resolution detection of the host monitor(s). Multiple monitor support is also lost in the update process. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 17:09:59 2017 DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components: {'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful': {'multiverse', 'restricted', 'universe', 'main'}, 'artful-security': {'multiverse', 'restricted', 'universe', 'main'}} DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-30 (264 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 21 16:27:55 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputVirtualPS/2 VMware VMMouse MOUSE, id 8 inputVirtualPS/2 VMware VMMouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: vmware To manage notifications about this bu
[Touch-packages] [Bug 1965750] [NEW] [jammy regression] No sound from onboard audio (playback / record)
Public bug reported: After updates I applied last friday, my onboard audio has ceased to function. No audio comes out the laptop speakers and no audio goes in the internal microphone (built in audio). If I connect my bluetooth headset (Bose NC700) the audio works, but only ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono. I tried switching from pulseaudio to pipewire and pipewire-pulse, and I kind of made it work - the bluetooth headset works correctly, and the onboard audio works again after switching default inputs and outputs a number of times. I just want to stress my laptop's audio has worked fine for years in all versions of ubuntu including Jammy, but only up until Friday Jan the 18th 2022. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Mon Mar 21 11:48:25 2022 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965750 Title: [jammy regression] No sound from onboard audio (playback / record) Status in alsa-driver package in Ubuntu: New Bug description: After updates I applied last friday, my onboard audio has ceased to function. No audio comes out the laptop speakers and no audio goes in the internal microphone (built in audio). If I connect my bluetooth headset (Bose NC700) the audio works, but only ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono. I tried switching from pulseaudio to pipewire and pipewire-pulse, and I kind of made it work - the bluetooth headset works correctly, and the onboard audio works again after switching default inputs and outputs a number of times. I just want to stress my laptop's audio has worked fine for years in all versions of ubuntu including Jammy, but only up until Friday Jan the 18th 2022. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Mon Mar 21 11:48:25 2022 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
** Changed in: zlib (Ubuntu Jammy) Status: In Progress => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1961427 Title: zlib: compressBound() returns an incorrect result on z15 Status in Ubuntu on IBM z Systems: Incomplete Status in zlib package in Ubuntu: Incomplete Status in zlib source package in Focal: New Status in zlib source package in Impish: New Status in zlib source package in Jammy: Incomplete Bug description: SRU Justification: == [Impact] * zlib: compressBound() returns an incorrect result on IBM z15 hardware. * Passing the result of compressBound() to compress() results in an error code. * This is because compressBound() is not adjusted for DFLTCC. [Fix] * Adjust compressBound() for DFLTCC like it's already done for deflateBound(). * Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is b25781e735363e04f6c56e21431c47e4afc50b17. * The fix extracted out of the above is: https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff [Test Plan] * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine) with Ubuntu Server 21.10 (or 22.04). * A test can be done based on the following C test program: #include #include #include int main() { Bytef in_buf[128], out_buf[1024]; for (size_t i = 0; i < sizeof(in_buf); i++) in_buf[i] = rand(); uLongf dest_len = compressBound(sizeof(in_buf)); assert(dest_len <= sizeof(out_buf)); int ret = compress(out_buf, &dest_len, in_buf, sizeof(in_buf)); assert(ret == Z_OK); } * The test needs to be done by IBM, due to the requirements for the special z15 hardware. * A successful test was just completed, based on the version in jammy- proposed, which is at the same code level that the impish version this SRU is targeted for. [Where problems could occur] * If the adjustment of compressBound() for DFLTCC is done erroneously the issue can still be present or in worst case even affect Z systems other than z15 only. * The compression can become errorneous with the new changes, e.g. in compressBound. * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN, (incl. the bit definitions), may cause various and unforseen defects. * Any build time issues that might have been introduced by this patch can be identified by a test build; this was done and is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427 [Other Info] * Ubuntu jammy, impish and focal are affected. __ Description: zlib: compressBound() returns an incorrect result on z15 Symptom: Passing the result of compressBound() to compress() results in an error code. Problem: compressBound() is not adjusted for DFLTCC. Solution: Adjust compressBound() for DFLTCC like it's already done for deflateBound(). Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is b25781e735363e04f6c56e21431c47e4afc50b17. Reproduction: z15 only: #include #include #include int main() { Bytef in_buf[128], out_buf[1024]; for (size_t i = 0; i < sizeof(in_buf); i++) in_buf[i] = rand(); uLongf dest_len = compressBound(sizeof(in_buf)); assert(dest_len <= sizeof(out_buf)); int ret = compress(out_buf, &dest_len, in_buf, sizeof(in_buf)); assert(ret == Z_OK); } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/417157 ** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/417158 -- 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/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
Sorry, this slipped off my radar -- I'll get on with the required PRs today -- 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/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
Currently dropping 1:1.2.11.dfsg-2ubuntu8 from jammy-proposed per the uploader's request: 09:55 < fheimes> Dear ubuntu-release team, could you please drop/remove zlib 2.11.dfsg-2ubuntu8 from jammy-proposed (LP#1961427)? 09:55 < fheimes> An incompatibility with HTSlib was detected, I'm in contact with the initial reporter and author of the patch to get that solved, but this might take a while (hence I restart from scratch on this is probably best). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1961427 Title: zlib: compressBound() returns an incorrect result on z15 Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: New Status in zlib source package in Impish: New Status in zlib source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * zlib: compressBound() returns an incorrect result on IBM z15 hardware. * Passing the result of compressBound() to compress() results in an error code. * This is because compressBound() is not adjusted for DFLTCC. [Fix] * Adjust compressBound() for DFLTCC like it's already done for deflateBound(). * Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is b25781e735363e04f6c56e21431c47e4afc50b17. * The fix extracted out of the above is: https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff [Test Plan] * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine) with Ubuntu Server 21.10 (or 22.04). * A test can be done based on the following C test program: #include #include #include int main() { Bytef in_buf[128], out_buf[1024]; for (size_t i = 0; i < sizeof(in_buf); i++) in_buf[i] = rand(); uLongf dest_len = compressBound(sizeof(in_buf)); assert(dest_len <= sizeof(out_buf)); int ret = compress(out_buf, &dest_len, in_buf, sizeof(in_buf)); assert(ret == Z_OK); } * The test needs to be done by IBM, due to the requirements for the special z15 hardware. * A successful test was just completed, based on the version in jammy- proposed, which is at the same code level that the impish version this SRU is targeted for. [Where problems could occur] * If the adjustment of compressBound() for DFLTCC is done erroneously the issue can still be present or in worst case even affect Z systems other than z15 only. * The compression can become errorneous with the new changes, e.g. in compressBound. * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN, (incl. the bit definitions), may cause various and unforseen defects. * Any build time issues that might have been introduced by this patch can be identified by a test build; this was done and is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427 [Other Info] * Ubuntu jammy, impish and focal are affected. __ Description: zlib: compressBound() returns an incorrect result on z15 Symptom: Passing the result of compressBound() to compress() results in an error code. Problem: compressBound() is not adjusted for DFLTCC. Solution: Adjust compressBound() for DFLTCC like it's already done for deflateBound(). Since zlib project does not accept patches at the moment, the fix has been integrated into the DFLTCC pull request: https://github.com/madler/zlib/pull/410 The commitid is b25781e735363e04f6c56e21431c47e4afc50b17. Reproduction: z15 only: #include #include #include int main() { Bytef in_buf[128], out_buf[1024]; for (size_t i = 0; i < sizeof(in_buf); i++) in_buf[i] = rand(); uLongf dest_len = compressBound(sizeof(in_buf)); assert(dest_len <= sizeof(out_buf)); int ret = compress(out_buf, &dest_len, in_buf, sizeof(in_buf)); assert(ret == Z_OK); } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+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 1965740] [NEW] BlueZ 5.64 release
Public bug reported: http://www.bluez.org/release-of-bluez-5-64/ At least for 22.10, but maybe for 22.04 too. ** Affects: bluez (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: needs-packaging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1965740 Title: BlueZ 5.64 release Status in bluez package in Ubuntu: Triaged Bug description: http://www.bluez.org/release-of-bluez-5-64/ At least for 22.10, but maybe for 22.04 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1965740/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
@simon unfortunately the but is still there -- 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/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: New Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1965657] Re: Ubuntu 20.04 loses monitor resolution after waking from sleep
Thanks for the bug report. Please clarify: * which monitor you mean * what is the expected resolution? * what resolution do you see instead? Also the current/preferred information in Xrandr.txt seems to be incomplete so please run: xrandr > xrandr2.txt when the resolution is WRONG, and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1965657 Title: Ubuntu 20.04 loses monitor resolution after waking from sleep Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 loses monitor resolution after waking from sleep ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 20 13:39:08 2022 DistUpgraded: 2022-02-08 01:01:24,407 DEBUG running apport_crash() DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-30-generic, x86_64: installed virtualbox, 6.1.32, 5.13.0-35-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] InstallationDate: Installed on 2021-04-27 (326 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) LightdmDisplayLog: (EE) event5 - SEMICO USB Gaming Keyboard : client bug: event processing lagging behind by 28ms, your system is too slow (EE) event5 - SEMICO USB Gaming Keyboard : client bug: event processing lagging behind by 13ms, your system is too slow (EE) event5 - SEMICO USB Gaming Keyboard : WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. (EE) event4 - USB OPTICAL MOUSE : client bug: event processing lagging behind by 11ms, your system is too slow (EE) event4 - USB OPTICAL MOUSE : client bug: event processing lagging behind by 14ms, your system is too slow MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=40d7f55a-4639-417b-ac6b-41fd4a9d344b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-07 (40 days ago) dmi.bios.date: 01/29/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CRESCENTBAY dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd01/29/2015:br5.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnCRESCENTBAY:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1965657/+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 1965639] Re: purple screen after login using fingerprint
Thanks for the bug report. Next time the screen stays purple, please: 1. Wait 10 seconds. 2. Reboot and login with password. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 6. If step 5 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1965639 Title: purple screen after login using fingerprint Status in gnome-shell package in Ubuntu: Incomplete Bug description: I updated the machine yesterday, and additionally added the fingerprint to pam using pam-auth-update. The screen now stays purple after logging in using the finger, but works fine after logging in using the password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 21:37:43 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294] InstallationDate: Installed on 2020-12-10 (464 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NN002NGE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2021 dmi.bios.release: 1.89 dmi.bios.vendor: LENOVO dmi.bios.version: N2LET89W (1.89 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NN002NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga: dmi.product.family: ThinkPad X390 Yoga dmi.product.name: 20NN002NGE dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga dmi.product.version: ThinkPad X390 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965639/+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 1965728] [NEW] default bashrc contains invalid ternary statement
Public bug reported: Shellcheck detected an instance of https://github.com/koalaman/shellcheck/wiki/SC2015 in the .bashrc that ships with Ubuntu. Here is the existing code: test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" It appears to be intended to behave like a ternary statement. The existing code evaluates `eval "$(dircolors -b)"` if `test -r ~/.dircolors` is true and `eval "$(dircolors -b ~/.dircolors)"` is false, which at face value doesn't appear to be the intention. According to Shellcheck, it should instead be: if [ -r ~/.dircolors ]; then eval "$(dircolors -b ~/.dircolors)" else eval "$(dircolors -b)" fi This ensures that the else case only executes when test -r ~/.dircolors is false. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bash 5.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 00:28:18 2022 InstallationDate: Installed on 2020-12-09 (467 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: Upgraded to impish on 2021-10-18 (154 days ago) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1965728 Title: default bashrc contains invalid ternary statement Status in bash package in Ubuntu: New Bug description: Shellcheck detected an instance of https://github.com/koalaman/shellcheck/wiki/SC2015 in the .bashrc that ships with Ubuntu. Here is the existing code: test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" It appears to be intended to behave like a ternary statement. The existing code evaluates `eval "$(dircolors -b)"` if `test -r ~/.dircolors` is true and `eval "$(dircolors -b ~/.dircolors)"` is false, which at face value doesn't appear to be the intention. According to Shellcheck, it should instead be: if [ -r ~/.dircolors ]; then eval "$(dircolors -b ~/.dircolors)" else eval "$(dircolors -b)" fi This ensures that the else case only executes when test -r ~/.dircolors is false. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bash 5.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 00:28:18 2022 InstallationDate: Installed on 2020-12-09 (467 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: Upgraded to impish on 2021-10-18 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1965728/+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 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Any updates for this issue ? Thanks -- 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/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket Status in systemd package in Ubuntu: Confirmed Bug description: Problem: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket Analysis Compared with Ubuntu 21.04 desktop image, there is a difference in /usr/lib/systemd/system/systemd-networkd.socket, "shutdown.target" is added to Before and Conflicts options. Ubuntu 22.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target shutdown.target Conflicts=shutdown.target Ubuntu 21.04 [Unit] Description=Network Service Netlink Socket Documentation=man:systemd-networkd.service(8) man:rtnetlink(7) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no Before=sockets.target After removed "shutdown.target" from /usr/lib/systemd/system/systemd- networkd.socket in ubuntu 22.04 desktop, this issue did NOT reproduce since systemd-networkd.service starts much earlier So the root cause of the issue is that adding 'shutdown.target' leads systemd-networkd.service starts late which makes customization command '/usr/sbin/netplan apply' fail. Not sure why adding 'shutdown.target' to file /usr/lib/systemd/system/systemd-networkd.socket ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+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 1926256] Re: Pasted text in the terminal is always highlighted and selected
** Changed in: mate-terminal (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Invalid Status in readline package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal
The log message in comment #2 is bug 1965673. I'm seeing it in everyone's logs today, including my own. And without using password dialogs. So unassigning ibus here. Use bug 1965673 for that. ** No longer affects: ibus (Ubuntu) -- 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/1964442 Title: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal Status in gnome-shell package in Ubuntu: Confirmed Bug description: This is a regression not seen until this week (not seen until March 4 at least). Calling debsign from a terminal pops up the window to enter the key, but the terminal is sent continuous keys and the terminal scrolls down with empty input lines. You can still sign the file, however you end up with an empty scroll buffer if the signing takes too long time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+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 1965673] Re: Object 0x557aa9440850 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management
** Bug watch added: github.com/ibus/ibus/issues #2387 https://github.com/ibus/ibus/issues/2387 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2387 Importance: Unknown Status: Unknown ** Summary changed: - Object 0x557aa9440850 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management + Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- 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/1965673 Title: Object 0x... of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Status in ibus: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in ibus package in Ubuntu: New Bug description: Ubuntu 22.04 development branch @ 20/03/2022 Journal logs spam a lot of lines like these: mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x7f896cf7cad0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mrt 20 13:36:38 R00TB00K gnome-shell[3452]: Object 0x557a992efd20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management Probably regression bug upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5147 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 13:34:37 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1965673/+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