[Touch-packages] [Bug 1835315] Re: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835315 Title: Vulkan funcionality broken when mesa is compiled with LLVM 8 in some programs Status in mesa package in Ubuntu: Expired Bug description: Ubuntu version: 18.04.2 LTS Mesa version: 19.0.2 Mesa-vulkan-driver version: 19.0.2, POLARIS10, DRM 3.27.0, 5.0.0-20-generic, LLVM 8.0.0) Video card: AMD RX 580 8GB, There is an issue when the Vulkan mesa RADV drivers are compiled with LLVM 8, due to an LLVM 8 bug, resulting in no visual output in some programs using the RADV Vulkan backend Upgrading to a mesa build compiled with LLVM 9, or reverting back to the bionic version from bionic-updates (which uses LLVM 6) fixes the problem. Using the AMDVLK vulkan driver workarounds the problem too. The program I have personally tested is RPCS3 I could put additional info about the LLVM bug but at this moment I do not have the upstream reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835315/+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 1858199] Re: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1858199 Title: bugs in libvdpau_radeonsi.so and amdgpu(or radeon) driver freeze the system Status in mesa package in Ubuntu: Expired Bug description: 1. In 4.15 kernel serires ,vlc or mpv video player with hardware acceleration output will freeze the system in minutes ,the desktop screen display content was frozen ,but sometime the audio will continue to play for about 10 seconds to one miniute,then the system dead。I have to reset the machine to reboot. When upgrade to 5.3.24 kernel,amdgpu still hanged immediately,but play video through vdpau in radeon driver the system will no hang immediately,the freqency of hanging is about serveral times a day。 some times web browser in virtualbox guest randomly hangs the system。 2. installing amdgpu-pro driver download from amd official site (version of 18.40-697810,18.50-756341,19.10-785425,19.30-934563) are all the same problem with above. 3. remove libvdpau_radeonsi.so.1.0.0 in the system from ubuntu or installed in /opt/amdgpu by amdgpu-pro driver solved the problem . the system has never been freezing for several weeks ,but the problem happened again when I restore the libvdpau_radeonsi.so file。 4.When use amdgpu driver the vlc output sound via display output port (through an active hdmi adaptor to hdmi monitor) was glitches ,the sound seem missing or dropped in every 2~3 seconds，but when use radeon driver the sound was normal.the audio problem is the same with 4.15 kernel when using kernel 5.3.24. But mplayer sound is always good ,testing with audio output of pulseaduio and alsa ,the kernel driver only affected the sound of vlc (tested with all available audio output ),the other applications was normal. 5. Test with the ubuntu 19.10 live image desktop is the same problem。 6. My system have four monitors,graphics card is R7 360 ,recognized as (from lspci) : 6.02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]. infomation from uname -a : Linux smzhou-desktop 5.3.0-24-lowlatency #26~18.04.2-Ubuntu SMP PREEMPT Tue Nov 26 14:39:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1858199/+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 1873562] Re: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installi
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1873562 Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux- gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error Status in mesa package in Ubuntu: Expired Bug description: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1873562/+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 1889052] Re: 20.10: vlc crashes with seg fault when a video should be played
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1889052 Title: 20.10: vlc crashes with seg fault when a video should be played Status in mesa package in Ubuntu: Expired Bug description: When I try to play "any" video vlc crashes with a seg fault. Tested: - mkv + h.264 - mp4 + h.264 - wmv Maybe it's a good idea to choose a different vlc release for the repos? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vlc 3.0.9.2-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 27 17:27:42 2020 SourcePackage: vlc UpgradeStatus: Upgraded to focal on 2020-07-24 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1889052/+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 1965608] Re: Crash in gbm_dri_bo_import on ASPEED + AMDGPU system
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1965608 Title: Crash in gbm_dri_bo_import on ASPEED + AMDGPU system Status in mesa package in Ubuntu: Expired Bug description: I have a server machine with an ASPEED BMC (kernel driver `ast`) and a Radeon Pro WX 4100 (driver `amdgpu`). If I try to log into a KDE Wayland session or a Gnome Wayland session, it crashes back to the login screen, with the same innermost level in the traceback. What I'd like to be able to do: if a monitor is connected to the AMD GPU, then show the login screen on that, and maybe duplicate it on the BMC. If no external monitor is connected, show it only on the BMC. Ideally, it should switch on the fly, but at the very least, it shouldn't crash. Note that in Xorg sessions, it doesn't crash, but xrandr only shows outputs from the AMD GPU. If I do xrandr --listproviders, I see that the `ast` has no capabilities. Provider 0: id: 0x58 cap: 0x9, Source Output, Sink Offload crtcs: 5 outputs: 4 associated providers: 0 name:AMD Radeon (TM) Pro WX 4100 @ pci::0e:00.0 Provider 1: id: 0x99 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 name:modesetting It really would be nice to support using it as a dumb output like DisplayLink, even if it has to allow tearing or drop many frames. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgbm1 21.2.6-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 19 00:09:57 2022 DistUpgraded: 2022-03-15 02:09:53,367 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller]) Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d] InstallationDate: Installed on 2016-10-27 (1969 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c4c2bc1a-635a-4890-9b75-207bd66db859 ro usbcore.autosuspend=0 earlycon console=ttyS1,115200n8 console=tty0 intel_iommu=on amd_iommu=on plymouth.ignore-serial-consoles pstore.backend=efi drm.debug=0x104 video=efifb:off thunderbolt.dyndbg pcie_ports=native pci=assign-busses,hpbussize=0x33,realloc,hpmmiosize=256M,hpmmioprefsize=1G RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to impish on 2022-03-15 (3 days ago) dmi.bios.date: 08/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: L1.43 dmi.board.name: X570D4U-2L2T dmi.board.vendor: ASRockRack dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrL1.43:bd08/19/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX570D4U-2L2T:rvr:cvnToBeFilledByO.E.M.:ct2: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 21.2.6-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1892985] Re: package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1892985 Title: package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf Status in mesa package in Ubuntu: Expired Bug description: Keeps reporting when I teamviewer and service also crashses ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] Uname: Linux 4.9.140-tegra aarch64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.16 Architecture: arm64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Aug 26 03:19:43 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4 video=tegrafb no_console_suspend=1 earlycon=tegra_comb_uart,mmio32,0x0c168000 gpt tegra_fbmem=0x80@0xa069c000 lut_mem=0x2008@0xa0697000 usbcore.old_scheme_first=1 tegraid=19.1.2.0.0 maxcpus=8 boot.slot_suffix= boot.ratchetvalues=0.4.2 vpr_resize sdhci_tegra.en_boot_part_access=1quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: mesa Title: package libegl-mesa0 20.0.8-0ubuntu1~18.04.1 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1892985/+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 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
When I manually added these variables to /etc/environment file, accents started to work properly in Wayland session: INPUT_METHOD=ibus GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus -- 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/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in wayland package in Ubuntu: Confirmed Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2040450/+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 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
It seems it is somehow related to Wayland session - bug appears when Wayland session is enabled, and if I switch to X11 session, bug disappears. ** Package changed: libxkbcommon (Ubuntu) => wayland (Ubuntu) -- 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/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in wayland package in Ubuntu: Confirmed Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2040450/+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 2041707] [NEW] Phased updates block release upgrades
Public bug reported: I updated my Kubuntu 23.04 to 23.10 using do-release-upgrade. It finished 100% successfully. But after rebooting into 23.10, I noticed that network-manager was kept back to the 23.04 version due to phased updates. Specifically: # apt policy network-manager network-manager: Installed: 1.42.4-1ubuntu2 Candidate: 1.44.2-1ubuntu1.2 Version table: 1.44.2-1ubuntu1.2 500 (phased 70%) 500 http://gr.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 1.44.2-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages *** 1.42.4-1ubuntu2 100 100 /var/lib/dpkg/status I.e. the phased version (1.44.2-1ubuntu1.2) prevents me from getting the current mantic version (1.44.2-1ubuntu1) and I'm stuck with the lunar version (1.42.4-1ubuntu2). ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2041707 Title: Phased updates block release upgrades Status in apt package in Ubuntu: New Bug description: I updated my Kubuntu 23.04 to 23.10 using do-release-upgrade. It finished 100% successfully. But after rebooting into 23.10, I noticed that network-manager was kept back to the 23.04 version due to phased updates. Specifically: # apt policy network-manager network-manager: Installed: 1.42.4-1ubuntu2 Candidate: 1.44.2-1ubuntu1.2 Version table: 1.44.2-1ubuntu1.2 500 (phased 70%) 500 http://gr.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 1.44.2-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages *** 1.42.4-1ubuntu2 100 100 /var/lib/dpkg/status I.e. the phased version (1.44.2-1ubuntu1.2) prevents me from getting the current mantic version (1.44.2-1ubuntu1) and I'm stuck with the lunar version (1.42.4-1ubuntu2). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2041707/+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 2041700] Re: release upgrade to 23.04 failed on Odroid N2+
** Package changed: ubuntu => python3-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2041700 Title: release upgrade to 23.04 failed on Odroid N2+ Status in python3-defaults package in Ubuntu: New Bug description: Failure during release upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: python3 3.11.2-1 Uname: Linux 5.15.0-odroid-arm64 aarch64 ApportVersion: 2.26.1-0ubuntu2.1 AptOrdering: NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20220423 Date: Fri Oct 27 22:58:30 2023 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: python3-defaults Title: package python3 3.11.2-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to lunar on 2023-10-27 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-06-28T20:42:18.309253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2041700/+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 2041700] [NEW] release upgrade to 23.04 failed on Odroid N2+
You have been subscribed to a public bug: Failure during release upgrade. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: python3 3.11.2-1 Uname: Linux 5.15.0-odroid-arm64 aarch64 ApportVersion: 2.26.1-0ubuntu2.1 AptOrdering: NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: 20220423 Date: Fri Oct 27 22:58:30 2023 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: python3-defaults Title: package python3 3.11.2-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to lunar on 2023-10-27 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-06-28T20:42:18.309253 ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 cloud-image lunar need-duplicate-check -- release upgrade to 23.04 failed on Odroid N2+ https://bugs.launchpad.net/bugs/2041700 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf
After several hours trying to obtain access to an ARM64 machine where I
could test the fix, vorlon kindly provided me with credentials to a
machine that's capable of launching an armhf container.
I could reproduce the bug:
# gdb -q ./a.out -ex 'b 3' -ex r -ex c
Reading symbols from ./a.out...
Breakpoint 1, thumb_func () at 1.c:3
3 return 42;
Continuing.
Program received signal SIGILL, Illegal instruction.
0x00401004 in ?? ()
...
And also verify that Liu's package fixes the problem:
# gdb -q ./a.out -ex 'b 3' -ex r -ex c
Reading symbols from ./a.out...
Breakpoint 1 at 0x4d8: file 1.c, line 3.
Starting program: /root/a.out
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Breakpoint 1, thumb_func () at 1.c:3
3 return 42;
Continuing.
[Inferior 1 (process 2666) exited with code 052]
Therefore, I sponsored the upload for him.
--
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/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
New
Status in gdb source package in Jammy:
New
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2039280] Re: Support IP address protocol
I agree that a merge from debian would be better, since we are quite
behind:
iproute2 | 6.5.0-4 | testing
But we have been at 6.1.0 since at least lunar, so I don't know how long
that would take. I think we can take these patches for noble.
I would ask that you also add this one, though, to update the manpage
with the new option:
commit 1fbb61058d34e3eb9a34f5e9308d90c4a961
Author: Petr Machata
Date: Mon Mar 27 18:12:06 2023 +0200
man: man8: Add man page coverage for "ip address add ... proto"
Signed-off-by: Petr Machata
Signed-off-by: David Ahern
Also, you could perhaps add your test script as a quick DEP8 test, what do you
think? Something like this?
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -3,3 +3,7 @@
Tests: testsuite.sh
Restrictions: allow-stderr, isolation-machine, needs-root, rw-build-tree
Depends: build-essential, locales-all, dpkg-dev, sudo:native, kmod, @builddeps@
+
+Tests: test-protocol-attribute
+Restrictions: isolation-machine, needs-root
+Depends: iproute2
diff --git a/debian/tests/test-protocol-attribute.sh
b/debian/tests/test-protocol-attribute.sh
new file mode 100755
index ..254b2906
--- /dev/null
+++ b/debian/tests/test-protocol-attribute.sh
@@ -0,0 +1,14 @@
+#!/bin/sh
+
+set -e
+
+addr=192.0.2.1/28
+ifr=test-dummy123
+
+ip link add name "$ifr" type dummy
+ip link set "$ifr" up
+
+ip address add dev "$ifr" "$addr" proto 0x99
+
+ip link del "$ifr"
Perhaps improve it with using a random address, and showing the "ip a" output
and checking that "proto 0x99" was truly added.
Finally, it would also be good if the patches have a few more DEP3
headers. In particular, Origin, with a link to the upstream commit, and
also a pointer to this bug here (Bug-Ubuntu: ...). The hash in the
"From" bit in both patches didn't match the upstreams I could find
(git://git.kernel.org/pub/scm/network/iproute2/iproute2.git or
https://github.com/shemminger/iproute2.git), but I did find the commits
using a log search. It would help if the Origin tag were there, then,
with a direct link.
Regarding an SRU, I would have some concerns:
- what is the real user benefit for stable release users? Do we have
bugs filed against iproute2 asking for this feature? How much demand is
there for this? In which kind of deployment would this be most useful?
- I see that the "ip" output changes when this flag is present, with the
new "proto " string. What's the regression potential here for
parsing this output in scripts? I believe the new "proto " text is
only present if there was a protocol assigned, and if not, the default
value (0 I believe?) is not shown. But are there other regression
potentials here? Perhaps in the json output, or when some extra flag is
added to "ip" commands?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
Confirmed
Status in iproute2 source package in Mantic:
Confirmed
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2041396] Re: gdb 12.1 generates SIGILL on armhf
** Merge proposal linked:
https://code.launchpad.net/~liushuyu-011/ubuntu/+source/gdb/+git/gdb/+merge/454654
--
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/2041396
Title:
gdb 12.1 generates SIGILL on armhf
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
New
Status in gdb source package in Jammy:
New
Bug description:
[ Impact ]
* GDB 12.1 introduced a regression where it will break program execution
when the program contains mixed ARM code and THUMB code.
* Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.
[ Test Plan ]
Considering the following C program:
```
__attribute__((target("arm"), noinline))
int thumb_func() {
return 42;
}
__attribute__((target("thumb")))
int main() { return thumb_func(); }
```
If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
GDB using the following commands ...
```
b 3
r
c
```
(you can save the contents above to a file and run GDB using `gdb -x
script ./repro`)
... you will notice GDB broke the program and threw SIGILL.
If you run the program without GDB, the program exits normally.
[ Where problems could occur ]
* GDB is a complex software. As the patch suggests, it may break other use
cases (like single-stepping) entirely.
* Since this is an ARM-only patch, it's unlikely to affect other CPU
architectures. However, it is possible that this fix may break ARM64 execution.
[ Other Info ]
* This bug has been fixed in GDB 13, but the fix was never backported to GDB
12. You can find the upstream bug in the remote bug watch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2039429] Re: Please merge wget 1.21.4 (main) from Debian unstable
Checklist: - preserved delta as needed - correct ubuntu versioning and changelog entries (I updated the release name to noble) - debian changes are ok - upstream changes are ok - upstream gpg signature checks out - test build failed at first locally in a noble lxd, but worked in a launchpad ppa Sponsored: Uploading wget_1.21.4-1ubuntu1.dsc Uploading wget_1.21.4.orig.tar.gz Uploading wget_1.21.4.orig.tar.gz.asc Uploading wget_1.21.4-1ubuntu1.debian.tar.xz Uploading wget_1.21.4-1ubuntu1_source.buildinfo Uploading wget_1.21.4-1ubuntu1_source.changes ** Changed in: wget (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/2039429 Title: Please merge wget 1.21.4 (main) from Debian unstable Status in wget package in Ubuntu: Fix Committed Bug description: Please merge wget 1.21.4 (main) from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2039429/+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 1969365] Re: focal: backport kexec fallback patch
The test case with removing kexec-tools before rebooting works for me. But I can only reproduce the issue by doing that. Can you share more about your setup so we can understand why exactly you hit this? I think that having this fallback makes sense, and is fine for an SRU, but it would be good to understand the root cause better. -- 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/1969365 Title: focal: backport kexec fallback patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Triaged Bug description: It would be great if focal's systemd could have https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3 backported to it. [Impact] We have observed that kexec'ing to another kernel will fail as the drive containing the `kexec` binary has been unmounted by the time systemd attempts to do so, indicated in the console: Starting Reboot via kexec... [ 163.960938] shutdown[1]: (sd-kexec) failed with exit status 1. [ 163.963463] reboot: Restarting system [Test Plan] 1) Launch a 20.04 instance 2) `apt-get install kexec-tools` 3) In `/boot`, filling in whatever needed in your environment: kexec -l vmlinuz --initrd initrd.img --append '' 4) `reboot` (I have reproduced this in a single-disk VM, so I assume it reproduces ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot` could be used to emulate the unmounting.) [Where problems could occur] Users could inadvertently be relying on the current behaviour: if they have configured their systems to kexec, they currently will be rebooting normally, and this patch would cause them to start actually kexec'ing. [Other info] We're currently maintaining a systemd tree with only this patch added to focal's tree: this patch has received a bunch of testing from us in focal. This patch landed in v246, so it's already present in supported releases later than focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2040281] Re: mkhomedir and pam_mount incompatibility
** Changed in: libpam-mount (Ubuntu) Status: Incomplete => Triaged ** Changed in: pam (Ubuntu) Status: Incomplete => Triaged -- 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/2040281 Title: mkhomedir and pam_mount incompatibility Status in libpam-mount package in Ubuntu: Triaged Status in pam package in Ubuntu: Triaged Bug description: Hello I have use realm to join a domain without difficulty and use pam-auth-update --enable mkhomedir, as suggest by the documentation The problem is, when a new user log into the system, the content of /etc/skel is not copy into the new home directory, even if Download Desktop are created. Adduser work normally and the homedirectory is created fine. The problem come from the additional pam module pam_mount, in my case this one try to mount a shared ressource in the homedir of the user. By default in /etc/pam.d/common.session pam_mount is called before pam_mkhomedir.so. If I deplace the pam_mkhomedir line before the pam_mount everything is working fine Thanks for your attention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/2040281/+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 2040281] Re: mkhomedir and pam_mount incompatibility
And the user should be a user of the domain, not a one you add with adduser Le 27/10/2023 à 19:33, Mitchell Dzurick a écrit : > Hi Virginie, I tried to reproduce this in an LXD vm > > $ lxc launch ubuntu:jammy j --vm > $ lxc shell j > # apt install -y sssd-ad sssd-tools realmd adcli > # pam-auth-update --enable mkhomedir > # sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release > -sc) main universe restricted multiverse" > # apt install -y lib_pam_mount > > Now add > mountpoint="/home/%(DOMAIN_USER)/Shared" user="*" > options="username=%(USER),user=%(USER),domain=domaine.local,iocharset=utf8" /> > > Under in /etc/security/pam_mount.conf.xml > > # adduser mitch > # su mitch > $ ls ~/ > shared > > > I see the shared folder in my test, is your issue that you don't see the > shared folder? > > ** Changed in: libpam-mount (Ubuntu) > Status: New => Incomplete > > ** Changed in: pam (Ubuntu) > Status: New => Incomplete > -- 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/2040281 Title: mkhomedir and pam_mount incompatibility Status in libpam-mount package in Ubuntu: Incomplete Status in pam package in Ubuntu: Incomplete Bug description: Hello I have use realm to join a domain without difficulty and use pam-auth-update --enable mkhomedir, as suggest by the documentation The problem is, when a new user log into the system, the content of /etc/skel is not copy into the new home directory, even if Download Desktop are created. Adduser work normally and the homedirectory is created fine. The problem come from the additional pam module pam_mount, in my case this one try to mount a shared ressource in the homedir of the user. By default in /etc/pam.d/common.session pam_mount is called before pam_mkhomedir.so. If I deplace the pam_mkhomedir line before the pam_mount everything is working fine Thanks for your attention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/2040281/+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 2040281] Re: mkhomedir and pam_mount incompatibility
Hi No the bug is not that the shared is not accessible, it is that the homedir is incomplete. For example .bashrc will not be in the homedir of the new user (and any other files in /etc/skel), but the directories in /etc/skel will be correctly copied. Thanks for your attention. Virginie Le 27/10/2023 à 19:33, Mitchell Dzurick a écrit : > Hi Virginie, I tried to reproduce this in an LXD vm > > $ lxc launch ubuntu:jammy j --vm > $ lxc shell j > # apt install -y sssd-ad sssd-tools realmd adcli > # pam-auth-update --enable mkhomedir > # sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release > -sc) main universe restricted multiverse" > # apt install -y lib_pam_mount > > Now add > mountpoint="/home/%(DOMAIN_USER)/Shared" user="*" > options="username=%(USER),user=%(USER),domain=domaine.local,iocharset=utf8" /> > > Under in /etc/security/pam_mount.conf.xml > > # adduser mitch > # su mitch > $ ls ~/ > shared > > > I see the shared folder in my test, is your issue that you don't see the > shared folder? > > ** Changed in: libpam-mount (Ubuntu) > Status: New => Incomplete > > ** Changed in: pam (Ubuntu) > Status: New => Incomplete > -- 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/2040281 Title: mkhomedir and pam_mount incompatibility Status in libpam-mount package in Ubuntu: Incomplete Status in pam package in Ubuntu: Incomplete Bug description: Hello I have use realm to join a domain without difficulty and use pam-auth-update --enable mkhomedir, as suggest by the documentation The problem is, when a new user log into the system, the content of /etc/skel is not copy into the new home directory, even if Download Desktop are created. Adduser work normally and the homedirectory is created fine. The problem come from the additional pam module pam_mount, in my case this one try to mount a shared ressource in the homedir of the user. By default in /etc/pam.d/common.session pam_mount is called before pam_mkhomedir.so. If I deplace the pam_mkhomedir line before the pam_mount everything is working fine Thanks for your attention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/2040281/+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 2041694] [NEW] PAC -mbranch-protection causes seg faults and misbuilds
Public bug reported: In mantic, -mbranch-protection=standard is now a default dpkg compiler flag for arm64 [0]. This breaks libunwind and dependencies [1]. This has not affected any libunwind binaries, since rebuilds have not been performed since this change. >From local testing, the build will complete successfully, but tests will report seg faults. Please make test failures cause FTBFS. [0] https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2040518 [1] https://github.com/libunwind/libunwind/issues/647 ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2041694 Title: PAC -mbranch-protection causes seg faults and misbuilds Status in libunwind package in Ubuntu: New Bug description: In mantic, -mbranch-protection=standard is now a default dpkg compiler flag for arm64 [0]. This breaks libunwind and dependencies [1]. This has not affected any libunwind binaries, since rebuilds have not been performed since this change. From local testing, the build will complete successfully, but tests will report seg faults. Please make test failures cause FTBFS. [0] https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2040518 [1] https://github.com/libunwind/libunwind/issues/647 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2041694/+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 2040281] Re: mkhomedir and pam_mount incompatibility
Hi Virginie, I tried to reproduce this in an LXD vm $ lxc launch ubuntu:jammy j --vm $ lxc shell j # apt install -y sssd-ad sssd-tools realmd adcli # pam-auth-update --enable mkhomedir # sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc) main universe restricted multiverse" # apt install -y lib_pam_mount Now add Under in /etc/security/pam_mount.conf.xml # adduser mitch # su mitch $ ls ~/ shared I see the shared folder in my test, is your issue that you don't see the shared folder? ** Changed in: libpam-mount (Ubuntu) Status: New => Incomplete ** Changed in: pam (Ubuntu) Status: New => Incomplete -- 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/2040281 Title: mkhomedir and pam_mount incompatibility Status in libpam-mount package in Ubuntu: Incomplete Status in pam package in Ubuntu: Incomplete Bug description: Hello I have use realm to join a domain without difficulty and use pam-auth-update --enable mkhomedir, as suggest by the documentation The problem is, when a new user log into the system, the content of /etc/skel is not copy into the new home directory, even if Download Desktop are created. Adduser work normally and the homedirectory is created fine. The problem come from the additional pam module pam_mount, in my case this one try to mount a shared ressource in the homedir of the user. By default in /etc/pam.d/common.session pam_mount is called before pam_mkhomedir.so. If I deplace the pam_mkhomedir line before the pam_mount everything is working fine Thanks for your attention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/2040281/+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 2024009] Re: [PATCH] systemd-resolved can't follow more than 8 CNAMEs
** Description changed: + [Impact] + + Using systemd-resolved to resolve a hostname which has more than 8 CNAME + redirects will fail because of the hard-coded limit. While this case is + somewhat rare, the original reporter demonstrated a real-world scenario + where this happened (although that particular hostname seems to be fixed + now). + + [Test Plan] + + This test plan uses a LXC container to test systemd-resolved on Focal. + If LXD has not been configured on your system, start with: + + $ lxd init --auto + + Then, create a Focal container with: + + $ lxc launch ubuntu-daily:focal focal + + Install dnsmasq-base if needed: + + $ apt install dnsmasq-base + + Stop other DNS servers: + + $ systemctl stop systemd-resolved + $ kill -9 $(pgrep dnsmasq) + + Now, on the host start a new DNS server that listens on lxdbr0, and sets + up an A record, and many CNAME records which ultimately redirect to the + A record: + + $ dnsmasq \ + --cname=test10.lan,test9.lan \ + --cname=test9.lan,test8.lan \ + --cname=test8.lan,test7.lan \ + --cname=test7.lan,test6.lan \ + --cname=test6.lan,test5.lan \ + --cname=test5.lan,test4.lan \ + --cname=test4.lan,test3.lan \ + --cname=test3.lan,test2.lan \ + --cname=test2.lan,test1.lan \ + --cname=test1.lan,test0.lan \ + -k -i lxdbr0 -z -I lo --host-record=test0.lan,$IP + + where $IP is any host on your network. + + Now, obtain a shell in the Focal container: + + $ lxc exec focal bash + + Attempt to resolve test10.lan: + + $ resolvectl query test10.lan + test10.lan: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'test2.lan' + + On an affected system, the above error will be seen. On a patched + system, the hostname should be resolved. + + [Where problems could occur] + + The patch simply increases the maximum CNAME redirects that are allowed + from 8 to 16, so a reasonable limit is still imposed. If an application + specifically relied on systemd-resolved's limit being at 8, then that + application would potentially see new behavior. + + [Original Description] + On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only follows 8 CNAME redirections maximum. So when using a service like Azure Virtual Desktop that has between 9 and 12 redirections, name resolution fails. $ host client.wvd.microsoft.com Host client.wvd.microsoft.com not found: 2(SERVFAIL) $ resolvectl query client.wvd.microsoft.com client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net' On the other hand it's working fine on Ubuntu 20.04 because CNAME loop limit has been raised from 8 to 16. $ host client.wvd.microsoft.com client.wvd.microsoft.com is an alias for client.privatelink-global.wvd.microsoft.com. client.privatelink-global.wvd.microsoft.com is an alias for client.privatelink.wvd.microsoft.com. client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com. rdweb.wvd.microsoft.com is an alias for rdweb.privatelink-global.wvd.microsoft.com. rdweb.privatelink-global.wvd.microsoft.com is an alias for rdweb.privatelink.wvd.microsoft.com. rdweb.privatelink.wvd.microsoft.com is an alias for rdweb-prod-geo.trafficmanager.net. rdweb-prod-geo.trafficmanager.net is an alias for mrs-chnor1c101-rdweb-prod.wvd-ase-chnor1c101-prod.p.azurewebsites.net. mrs-chnor1c101-rdweb-prod.wvd-ase-chnor1c101-prod.p.azurewebsites.net is an alias for waws-prod-zrh-63daa049.sip.p.azurewebsites.windows.net. waws-prod-zrh-63daa049.sip.p.azurewebsites.windows.net is an alias for waws-prod-zrh-63daa049.cloudapp.net. waws-prod-zrh-63daa049.cloudapp.net has address 51.107.69.35 - - Here's a quick fix that raises the max CNAME limit from 8 to 16 like it is in Ubuntu 22.04, it fixes the problem for me. + Here's a quick fix that raises the max CNAME limit from 8 to 16 like it + is in Ubuntu 22.04, it fixes the problem for me. Best regards, Vincent. --- systemd-245.4.ORIG/src/resolve/resolved-dns-query.c 2023-06-15 16:58:25.454156663 +0200 +++ systemd-245.4/src/resolve/resolved-dns-query.c2023-06-01 14:30:09.0 +0200 @@ -10,7 +10,7 @@ - #include "resolved-etc-hosts.h" - #include "string-util.h" - + #include "resolved-etc-hosts.h" + #include "string-util.h" + -#define CNAME_MAX 8 +#define CNAME_MAX 16 - #define QUERIES_MAX 2048 - #define AUXILIARY_QUERIES_MAX 64 + #define QUERIES_MAX 2048 + #define AUXILIARY_QUERIES_MAX 64 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 [modified: usr/lib/sysctl.d/50-default.conf] ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 16:53:19 2023
[Touch-packages] [Bug 2041690] [NEW] Cannot open internal or screen laptop
Public bug reported:
After I use the secondary screen, the primary screen stops working, and
the problem is nvidia
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-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..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12
19:41:24 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 23:58:39 2023
DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:153b]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f9d] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / Max-Q]
[1025:1544]
InstallationDate: Installed on 2023-05-20 (160 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=8806d2d2-440c-4fb8-bfae-fce3d6fc0f20 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-14 (13 days ago)
XorgConf:
dmi.bios.date: 06/22/2022
dmi.bios.release: 1.18
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Kamiq_TLS
dmi.board.vendor: TGL
dmi.board.version: V1.18
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.18
dmi.ec.firmware.release: 1.10
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.18:bd06/22/2022:br1.18:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.18:rvnTGL:rnKamiq_TLS:rvrV1.18:cvnAcer:ct10:cvrV1.18:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN517-54
dmi.product.sku:
dmi.product.version: V1.18
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
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:21.1.7-3ubuntu2.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic 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/2041690
Title:
Cannot open internal or screen laptop
Status in xorg package in Ubuntu:
New
Bug description:
After I use the secondary screen, the primary screen stops working,
and the problem is nvidia
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-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..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12
19:41:24 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 23:58:39 2023
DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
[Touch-packages] [Bug 2041672] Re: glob in mime/packages/freedesktop.org.xml is matching wrong files
removing and sudo update-mime-database /usr/share/mime fixes the issue locally until the next update ** Summary changed: - glob in mime/packages/freedesktop.org.xml is matching wrong files + in mime/packages/freedesktop.org.xml is matching wrong files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2041672 Title: in mime/packages/freedesktop.org.xml is matching wrong files Status in shared-mime-info package in Ubuntu: New Bug description: /usr/share/mime/packages/freedesktop.org.xml line 10466 -> value="import Qt" offset="0:3000" context: is matching python files using Pyside with imports like: from PySide2.QtCore import Qt, QSettings, QSize considering them 'Qt Markup Language files (text/x-qml)' thus wrecking havoc down the line. Maybe just remove this match entry as it seems very broad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+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 2041672] [NEW] glob in mime/packages/freedesktop.org.xml is matching wrong files
Public bug reported: /usr/share/mime/packages/freedesktop.org.xml line 10466 -> value="import Qt" offset="0:3000" context: is matching python files using Pyside with imports like: from PySide2.QtCore import Qt, QSettings, QSize considering them 'Qt Markup Language files (text/x-qml)' thus wrecking havoc down the line. Maybe just remove this match entry as it seems very broad ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: mime pyside pyside2 pyside6 python qt ** Summary changed: - glob in mime/packages/freedesktop.org.xml is matching wron files + glob in mime/packages/freedesktop.org.xml is matching wrong files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2041672 Title: glob in mime/packages/freedesktop.org.xml is matching wrong files Status in shared-mime-info package in Ubuntu: New Bug description: /usr/share/mime/packages/freedesktop.org.xml line 10466 -> value="import Qt" offset="0:3000" context: is matching python files using Pyside with imports like: from PySide2.QtCore import Qt, QSettings, QSize considering them 'Qt Markup Language files (text/x-qml)' thus wrecking havoc down the line. Maybe just remove this match entry as it seems very broad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+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 2034986] Re: some text became unreadable during a distribution upgrade
Hello Brian, or anyone else affected, Accepted ubuntu-release-upgrader into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:23.10.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release
[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
A version containing a fix for this has been uploaded to the Jammy queue to be processed by the SRU team. Thanks, Adrien :) -- 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/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of four bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. [Test plan] An engine is needed to test the fix and I don't think we have many in the archive. This complicates reproducing the issue. I have been relying on user reports which have been very detailled and helpful. The issue has also been reported independently and with another engine (devcrypto). The issue is fixed in openssl 3.0.8 which landed in lunar. [Where problems could occur] I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/issues/18578 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy- sru-0001-Release-the-drbg-in-the-global-default-context- befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 03ffae11c700: 4700bc0,0 #03ffae11c704: b24f00a0ear%r10,%a0 >03ffae11c708: 58102018l%r1,24(%r2) 03ffae11c70c: ebaa002dsllg%r10,%r10,32 03ffae11c712: b24f00a1ear%r10,%a1 03ffae11c716: 5910a0d0c%r1,208(%r10) 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0). Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 0 dumped core.
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
A version containing a fix for this has been uploaded to the Jammy queue to be processed by the SRU team. Thanks, Adrien :) -- 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/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Meta] This bug is part of a series of four bugs for a single SRU. The "central" bug with the global information and debdiff is http://pad.lv/2033422 [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. [Patches] The patches come directly from upstream and apply cleanly. https://github.com/openssl/openssl/pull/18876 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 * https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0 === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
A version containing a fix for this has been uploaded to the Jammy queue to be processed by the SRU team. Thanks, Adrien :) -- 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/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains FOUR changes which are listed in the section below. [Meta] This bug is part of a series of four bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses four issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections The SRU information has been added to the four bug reports and I am attaching the debdiff here only for all four. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. As such, the engine and provider functionality could be broken by these
[Touch-packages] [Bug 2041008] Re: wayland : no uppercase accented characters with capslock
** Package changed: xorg (Ubuntu) => wayland (Ubuntu)
--
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/2041008
Title:
wayland : no uppercase accented characters with capslock
Status in wayland package in Ubuntu:
Confirmed
Bug description:
Until Ubuntu 23.04, with the "french alternative" [français (variante)]
keyboard, capslock gave you directly uppercase accented characters (like É È À)
from the keys 2, 7 and 0 of the fifth row of the keyboard.
With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it
works like before if you connect with Xorg.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 13:36:26 2023
DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850]
[1002:6739] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD
6850] [174b:174b]
InstallationDate: Installed on 2020-04-10 (1294 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
dmi.bios.date: 08/05/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: 970 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3: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 N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2041008/+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 2038894] Autopkgtest regression report (systemd/253.5-1ubuntu6.1)
All autopkgtests for the newly accepted systemd (253.5-1ubuntu6.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: conntrack-tools/unknown (s390x) cryptsetup/unknown (s390x) cups/2.4.6-0ubuntu3 (s390x) dropbear/2022.83-2 (arm64) haproxy/unknown (s390x) mosquitto/2.0.18-1 (s390x) mutter/45.0-3ubuntu3 (s390x) network-manager/1.44.2-1ubuntu1.2 (arm64) puppet-agent/7.23.0-1 (s390x) samba/2:4.18.6+dfsg-1ubuntu2.1 (s390x) 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/mantic/update_excuses.html#systemd [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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: New Status in systemd source package in Mantic: Fix Committed Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0
[Touch-packages] [Bug 2018128] Re: Apport does not collect all logs when the package is HWE kernel
I discussed this topic with Simon and we came up with a less fragile solution: Each kernel binary package can ship a symlink to /usr/share/apport/package-hooks/source_linux.py. Example: linux- image-5.19.0-50-generic should ship /usr/share/apport/package- hooks/linux-image-5.19.0-50-generic.py -> source_linux.py This will work without a regular expression that will break sooner or later. -- 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/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2041523] Re: /usr/share/apport/whoopsie-upload-all: PermissionError: Permission denied: '/bin/systemctl'
** Summary changed: - /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@220:main:call:__init__:_execute_child + /usr/share/apport/whoopsie-upload-all: PermissionError: Permission denied: '/bin/systemctl' -- 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/2041523 Title: /usr/share/apport/whoopsie-upload-all: PermissionError: Permission denied: '/bin/systemctl' Status in apport package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 198, in main if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: File "/usr/lib/python3.10/subprocess.py", line 345, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/bin/systemctl' The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. As of 2023-10-27, there were 1109 instances on Ubuntu 22.04 (jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041523/+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 2041523] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@220:main:call:__init__:_execute_child
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Traceback (most recent call last): - File "/usr/share/apport/whoopsie-upload-all", line 220, in - main() - File "/usr/share/apport/whoopsie-upload-all", line 198, in main - if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: - File "/usr/lib/python3.10/subprocess.py", line 345, in call - with Popen(*popenargs, **kwargs) as p: - File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ - self._execute_child(args, executable, preexec_fn, close_fds, - File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child - raise child_exception_type(errno_num, err_msg, err_filename) + File "/usr/share/apport/whoopsie-upload-all", line 220, in + main() + File "/usr/share/apport/whoopsie-upload-all", line 198, in main + if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: + File "/usr/lib/python3.10/subprocess.py", line 345, in call + with Popen(*popenargs, **kwargs) as p: + File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ + self._execute_child(args, executable, preexec_fn, close_fds, + File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child + raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/bin/systemctl' The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + As of 2023-10-27, there were 1109 instances on Ubuntu 22.04 (jammy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2041523 Title: /usr/share/apport/whoopsie-upload-all: PermissionError: Permission denied: '/bin/systemctl' Status in apport package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 198, in main if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: File "/usr/lib/python3.10/subprocess.py", line 345, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/bin/systemctl' The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. As of 2023-10-27, there were 1109 instances on Ubuntu 22.04 (jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041523/+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 2041518] Re: /usr/share/apport/apport-gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") + This crash is probably a different variant of bug #1842439 but I cannot + reproduce this crash (by running "killall -11 gnome-shell" on a mantic + system). + This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). ** Tags added: rls-nn-incoming ** Tags removed: rls-nn-incoming ** Tags added: rls-mm-incoming -- 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/2041518 Title: /usr/share/apport/apport- gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard Status in apport package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") This crash is probably a different variant of bug #1842439 but I cannot reproduce this crash (by running "killall -11 gnome-shell" on a mantic system). This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041518/+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 2041523] [NEW] /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@220:main:call:__init__:_execute_child
Public bug reported: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 198, in main if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: File "/usr/lib/python3.10/subprocess.py", line 345, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/bin/systemctl' The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/2041523 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@220:main:call:__init__:_execute_child Status in apport package in Ubuntu: New Bug description: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 198, in main if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: File "/usr/lib/python3.10/subprocess.py", line 345, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/bin/systemctl' The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041523/+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 2041523] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@220:main:call:__init__:_execute_child
** Description changed: + Traceback (most recent call last): + File "/usr/share/apport/whoopsie-upload-all", line 220, in + main() + File "/usr/share/apport/whoopsie-upload-all", line 198, in main + if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: + File "/usr/lib/python3.10/subprocess.py", line 345, in call + with Popen(*popenargs, **kwargs) as p: + File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ + self._execute_child(args, executable, preexec_fn, close_fds, + File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child + raise child_exception_type(errno_num, err_msg, err_filename) + PermissionError: [Errno 13] Permission denied: '/bin/systemctl' + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- 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/2041523 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@220:main:call:__init__:_execute_child Status in apport package in Ubuntu: New Bug description: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 198, in main if subprocess.call(['/bin/systemctl', '--quiet', 'is-enabled', 'whoopsie.path'], stdout=subprocess.PIPE) != 0: File "/usr/lib/python3.10/subprocess.py", line 345, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.10/subprocess.py", line 971, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: '/bin/systemctl' The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu82.5, the problem page at https://errors.ubuntu.com/problem/33dc3ae87406bbdcb73219259a63c99781f2993d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041523/+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 2041522] Re: /usr/share/apport/apport:TypeError:/usr/share/apport/apport@47:/usr/lib/python3/dist-packages/apport/__init__.py@7:/usr/lib/python3/dist-packages/apport/packaging_im
Removing apport.packaging_impl.apt_dpkg causes import_module to raise
ModuleNotFoundError, calling importlib.import_module("") raises
"ValueError: Empty module name".
** Description changed:
+ ```
+ Traceback (most recent call last):
+ File "/usr/share/apport/apport", line 47, in
+ import apport.fileutils
+ File "/usr/lib/python3/dist-packages/apport/__init__.py", line 7, in
+ from apport.packaging_impl import impl as packaging
+ File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py",
line 33, in
+ impl = load_packaging_implementation()
+^^^
+ File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py",
line 27, in load_packaging_implementation
+ module = importlib.import_module(
+
+ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
+ return _bootstrap._gcd_import(name[level:], package, level)
+
+ File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py",
line 30, in
+ import http.client
+ File "/usr/lib/python3.11/http/client.py", line 71, in
+ import email.parser
+ File "/usr/lib/python3.11/email/parser.py", line 12, in
+ from email.feedparser import FeedParser, BytesFeedParser
+ File "/usr/lib/python3.11/email/feedparser.py", line 37, in
+ headerRE = re.compile(r'^(From |[\041-\071\073-\176]*:|[\t ])')
+
+ File "/usr/lib/python3.11/re/__init__.py", line 227, in compile
+ return _compile(pattern, flags)
+
+ File "/usr/lib/python3.11/re/__init__.py", line 294, in _compile
+ p = _compiler.compile(pattern, flags)
+ ^
+ File "/usr/lib/python3.11/re/_compiler.py", line 743, in compile
+ p = _parser.parse(p, flags)
+ ^^^
+ File "/usr/lib/python3.11/re/_parser.py", line 982, in parse
+ p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
+ ^^
+ File "/usr/lib/python3.11/re/_parser.py", line 457, in _parse_sub
+ itemsappend(_parse(source, state, verbose, nested + 1,
+ ^^
+ File "/usr/lib/python3.11/re/_parser.py", line 865, in _parse
+ p = _parse_sub(source, state, sub_verbose, nested + 1)
+ ^^
+ File "/usr/lib/python3.11/re/_parser.py", line 457, in _parse_sub
+ itemsappend(_parse(source, state, verbose, nested + 1,
+ ^^
+ File "/usr/lib/python3.11/re/_parser.py", line 545, in _parse
+ subpatternappend((LITERAL, _ord(this)))
+ File "/usr/lib/python3.11/re/_parser.py", line 173, in append
+ self.data.append(code)
+
+ TypeError: 'NoneType' object does not support the context manager protocol
+ ```
+
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.27.0-0ubuntu5, the problem page at
https://errors.ubuntu.com/problem/50cfd7836daa6f7aabb091433cb3f54007c8ced4
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
** Description changed:
+ `load_packaging_implementation` in /usr/lib/python3/dist-
+ packages/apport/packaging_impl/__init__.py calls:
+
+ importlib.import_module("apport.packaging_impl.apt_dpkg")
+
+ There is one crash indicating that Python is the culprit here:
+
```
Traceback (most recent call last):
- File "/usr/share/apport/apport", line 47, in
- import apport.fileutils
- File "/usr/lib/python3/dist-packages/apport/__init__.py", line 7, in
- from apport.packaging_impl import impl as packaging
- File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py",
line 33, in
- impl = load_packaging_implementation()
-^^^
- File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py",
line 27, in load_packaging_implementation
- module = importlib.import_module(
-
- File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
- return _bootstrap._gcd_import(name[level:], package, level)
-
- File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py",
line 30, in
- import http.client
- File "/usr/lib/python3.11/http/client.py", line 71, in
- import email.parser
- File "/usr/lib/python3.11/email/parser.py",
[Touch-packages] [Bug 2041522] [NEW] /usr/share/apport/apport:TypeError:/usr/share/apport/apport@47:/usr/lib/python3/dist-packages/apport/__init__.py@7:/usr/lib/python3/dist-packages/apport/packaging_
Public bug reported: ``` Traceback (most recent call last): File "/usr/share/apport/apport", line 47, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/__init__.py", line 7, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py", line 33, in impl = load_packaging_implementation() ^^^ File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py", line 27, in load_packaging_implementation module = importlib.import_module( File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/usr/lib/python3/dist-packages/apport/packaging_impl/apt_dpkg.py", line 30, in import http.client File "/usr/lib/python3.11/http/client.py", line 71, in import email.parser File "/usr/lib/python3.11/email/parser.py", line 12, in from email.feedparser import FeedParser, BytesFeedParser File "/usr/lib/python3.11/email/feedparser.py", line 37, in headerRE = re.compile(r'^(From |[\041-\071\073-\176]*:|[\t ])') File "/usr/lib/python3.11/re/__init__.py", line 227, in compile return _compile(pattern, flags) File "/usr/lib/python3.11/re/__init__.py", line 294, in _compile p = _compiler.compile(pattern, flags) ^ File "/usr/lib/python3.11/re/_compiler.py", line 743, in compile p = _parser.parse(p, flags) ^^^ File "/usr/lib/python3.11/re/_parser.py", line 982, in parse p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) ^^ File "/usr/lib/python3.11/re/_parser.py", line 457, in _parse_sub itemsappend(_parse(source, state, verbose, nested + 1, ^^ File "/usr/lib/python3.11/re/_parser.py", line 865, in _parse p = _parse_sub(source, state, sub_verbose, nested + 1) ^^ File "/usr/lib/python3.11/re/_parser.py", line 457, in _parse_sub itemsappend(_parse(source, state, verbose, nested + 1, ^^ File "/usr/lib/python3.11/re/_parser.py", line 545, in _parse subpatternappend((LITERAL, _ord(this))) File "/usr/lib/python3.11/re/_parser.py", line 173, in append self.data.append(code) TypeError: 'NoneType' object does not support the context manager protocol ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/50cfd7836daa6f7aabb091433cb3f54007c8ced4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2041522 Title: /usr/share/apport/apport:TypeError:/usr/share/apport/apport@47:/usr/lib/python3/dist- packages/apport/__init__.py@7:/usr/lib/python3/dist- packages/apport/packaging_impl/__init__.py@33:load_packaging_implementation:import_module:/usr/lib/python3/dist- packages/apport/packaging_impl/apt_dpkg.py@30:/usr/lib/python3.11/http/client.py@71:/usr/lib/python3.11/email/parser.py@12:/usr/lib/python3.11/email/feedparser.py@37:compile:_compile:compile:parse:_parse_sub:_parse:_parse_sub:_parse:append Status in apport package in Ubuntu: New Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/apport", line 47, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/__init__.py", line 7, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py", line 33, in impl = load_packaging_implementation() ^^^ File "/usr/lib/python3/dist-packages/apport/packaging_impl/__init__.py", line 27, in load_packaging_implementation module = importlib.import_module( File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level)
[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
The failure mode has changed a little bit in Ubuntu 23.10 (mantic): bug #2041518 -- 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/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in apport source package in Focal: Invalid Status in gtk+3.0 source package in Focal: Triaged Status in apport source package in Lunar: Invalid Status in gtk+3.0 source package in Lunar: Triaged Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Stack trace --- Python: ``` File "apport-gtk", line 703, in app = GTKUserInterface(sys.argv) File "apport-gtk", line 68, in GTKUserInterface.__init__ self.widgets.add_from_file( os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui") ) ``` StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
>From https://www.man7.org/linux/man-pages/man5/systemd.network.5.html If RequiredForOnline=no is set, systemd-networkd-wait-online should skip the interface: The network will be brought up normally (as configured by ActivationPolicy=), but in the event that there is no address being assigned by DHCP or the cable is not plugged in, the link will simply remain offline and be skipped automatically by systemd-networkd-wait-online if "RequiredForOnline=no". -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
Copying from my comment https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/comments/43 systemd 249.11-0ubuntu3.11 doesn't resolve the issue I'm facing (this one). The long delay seems to be caused by systemd-networkd-wait-online not respecting "RequiredForOnline=no". ubuntu@ubuntu:~$ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Link] RequiredForOnline=no [Network] DHCP=yes LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2041518] Re: /usr/share/apport/apport-gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 + "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, + file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", + line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 + <__func__.70> "gtk_style_context_init", + message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a + GtkStyleContext without a display connection") + This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). ** Package changed: glib2.0 (Ubuntu) => gtk+3.0 (Ubuntu) -- 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/2041518 Title: /usr/share/apport/apport- gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard Status in apport package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041518/+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 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2041518] [NEW] /usr/share/apport/apport-gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2041518 Title: /usr/share/apport/apport- gtk:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard Status in apport package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.27.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/196d97dec8fe94e52eebaf9e7da150d1629a1e05 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. g_log_structured_standard (log_domain=log_domain@entry=0x7f7fa9a12014 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, file=file@entry=0x7f7fa9a4e7c0 "../../../gtk/gtkstylecontext.c", line=line@entry=0x7f7fa9a1a381 "348", func=func@entry=0x7f7fa9a849a0 <__func__.70> "gtk_style_context_init", message_format=message_format@entry=0x7f7fa9a4edf0 "Can't create a GtkStyleContext without a display connection") This bug is the top 1 apport bug in Ubuntu 23.10 (mantic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2041518/+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 2040960] Re: I am unable to install mysql package because of the packages issue of ubuntu20.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 This bug report can be converted into a question which is support geared. I've marked it incomplete being support request. ** Changed in: vim (Ubuntu) Status: New => Incomplete ** Changed in: vim (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/vim/+question/708305 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040960 Title: I am unable to install mysql package because of the packages issue of ubuntu20.04 Status in vim package in Ubuntu: Invalid Bug description: On every command mostly, I'm getting the below errors: 1.)Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Preparing to unpack .../5-oem-somerville-meta_20.04ubuntu9_all.deb ... dpkg-maintscript-helper: error: dpkg: error: unknown option --validate-version Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; 2.)You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: fwupd : Depends: libfwupd2 (= 1.7.5-3~20.04.1) but 1.7.9-1~20.04.3 is installed Depends: libfwupdplugin5 (= 1.7.5-3~20.04.1) but 1.7.9-1~20.04.3 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Note: i am running the command 'apt --fix-broken install' but getting the below message: dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/vim_2%3a8.1.2269-1ubuntu5.20_amd64.deb /var/cache/apt/archives/vim-tiny_2%3a8.1.2269-1ubuntu5.20_amd64.deb /var/cache/apt/archives/vim-common_2%3a8.1.2269-1ubuntu5.20_all.deb /var/cache/apt/archives/fwupd_1.7.9-1~20.04.3_amd64.deb /var/cache/apt/archives/oem-somerville-meta_20.04ubuntu9_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Please provide me the solution for this issue as i have wasted too much time, but unable to fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040960/+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 2041496] Re: btmgmt --index broken in Mantic
https://lore.kernel.org/linux- bluetooth/20231026182426.032a776d@gollum/#t Proposed patch: https://lore.kernel.org/linux-bluetooth/20231027055423.13617-1-juerg.haefli...@canonical.com/ -- 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/2041496 Title: btmgmt --index broken in Mantic Status in bluez package in Ubuntu: New Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2041496/+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 2041496] [NEW] btmgmt --index broken in Mantic
Public bug reported: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Description changed: On Mantic: - btmgmt --index 1 info + $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller - addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c - supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration - current settings: powered ssp br/edr le secure-conn - name rpi-5b-rev1d0-f88b - short name + addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c + supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration + current settings: powered ssp br/edr le secure-conn + name rpi-5b-rev1d0-f88b + short name hci0: Configuration options - supported options: public-address - missing options: - + supported options: public-address + missing options: Note the error 'Unable to open...' The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) ** Description changed: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: - Note the error 'Unable to open...' + Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) -- 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/2041496 Title: btmgmt --index broken in Mantic Status in bluez package in Ubuntu: New Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2041496/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
no need for new rust bits, we didn't migrate to llvm-16 ** Changed in: rust-clang-sys (Ubuntu Jammy) Status: New => Invalid ** Changed in: rust-bindgen (Ubuntu Jammy) Status: New => Invalid ** Description changed: [Impact] The graphics HWE stack from kinetic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. - rust-bindgen - - rust-clang-sys - [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.2.x in order to minimize the chance for those. ** Description changed: [Impact] The graphics HWE stack from kinetic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] - This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.2.x in order to minimize the chance for those. + This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: New Status in mesa source package in Jammy: New Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from kinetic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] Install the new mesa on various hw, see that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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
