[Touch-packages] [Bug 1960583] Re: dpkg error while processing - can't install nor upgrade
** Branch unlinked: lp:~glmark2-dev/glmark2/jellyfish -- 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/1960583 Title: dpkg error while processing - can't install nor upgrade Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Bug description: My current ubuntu version : No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Issue : when `sudo apt update` is ok, all newest package is downloaded but `sudo apt ugprade` show current error : ] sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: librygel-renderer-2.6-2 librygel-server-2.6-2 rygel The following packages will be upgraded: bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath language-pack-en language-pack-gnome-en libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 libnl-route-3-200 libnm0 libnma-common libnma0 libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 libupower-glib3 media-types nano network-manager network-manager-config-connectivity-ubuntu python3-paramiko python3-software-properties simple-scan software-properties-common software-properties-gtk upower 56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 10 not fully installed or removed. Need to get 0 B/94,6 MB of archives. After this operation, 1.928 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Extracting templates from packages: 100% Preconfiguring packages ... Setting up dpkg (1.21.1ubuntu1) ... head: error reading 'dpkg': Is a directory dpkg: error processing package dpkg (--configure): installed dpkg package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dpkg E: Sub-process /usr/bin/dpkg returned an error code (1) i have to resintall all of the package in cache with `sudo dpkg -i /var/cache/apt/archives/*.deb `, but the cache sometimes is not the newest packages and when i rerun `sudo apt upgrade`, there is still not the newest package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960583/+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 1960583] Re: dpkg error while processing - can't install nor upgrade
** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~glmark2-dev/glmark2/jellyfish -- 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/1960583 Title: dpkg error while processing - can't install nor upgrade Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Bug description: My current ubuntu version : No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Issue : when `sudo apt update` is ok, all newest package is downloaded but `sudo apt ugprade` show current error : ] sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: librygel-renderer-2.6-2 librygel-server-2.6-2 rygel The following packages will be upgraded: bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath language-pack-en language-pack-gnome-en libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 libnl-route-3-200 libnm0 libnma-common libnma0 libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 libupower-glib3 media-types nano network-manager network-manager-config-connectivity-ubuntu python3-paramiko python3-software-properties simple-scan software-properties-common software-properties-gtk upower 56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 10 not fully installed or removed. Need to get 0 B/94,6 MB of archives. After this operation, 1.928 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Extracting templates from packages: 100% Preconfiguring packages ... Setting up dpkg (1.21.1ubuntu1) ... head: error reading 'dpkg': Is a directory dpkg: error processing package dpkg (--configure): installed dpkg package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dpkg E: Sub-process /usr/bin/dpkg returned an error code (1) i have to resintall all of the package in cache with `sudo dpkg -i /var/cache/apt/archives/*.deb `, but the cache sometimes is not the newest packages and when i rerun `sudo apt upgrade`, there is still not the newest package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960583/+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 1956112] Re: Livepatch icon is shown on non-Livepatch systems
Yup, I agree it should be shown only when running LTS systems. ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1956112 Title: Livepatch icon is shown on non-Livepatch systems Status in software-properties package in Ubuntu: Triaged Bug description: The icon included with software-properties-gtk is shown in the applications list by default. This consumes screen real estate for something a large number of people cannot or are not using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1956112/+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 1960569] Re: Screen goes dim
Thanks for the bug report. It sounds like Xorg's (fake) brightness setting is being applied repeatedly. I would generally recommend avoiding that feature because it works by degrading color quality (tweaking the gamma ramps / color profile). I recommend using your monitor's brightness setting instead. Otherwise... Please try uninstalling the "brightness-controller app" you mention and reboot, then tell us if that fixes the problem. If it doesn't then we're probably only left with Xorg or MATE to blame. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Low ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960569 Title: Screen goes dim Status in xorg-server package in Ubuntu: Incomplete Bug description: I walk away from the machine; come back hours later to find that the screen is dim. The following command confirms that the cause is something in Ubuntu xrandr --listmonitors --verbose | egrep -3 -i 'gamma|backl|brightn' Has shown value for "Brightness" of 0.11, 0.18, 0.0018, 0.20, and possibly other values. (Gamma is all 1.0.) This occurs on both monitors that I have hooked up, but the values are usually different. I like a Brightness of 0.80, I know how to manually change with xrandr or a brightness-controller app. When the brightness is too low it is very hard to fix things without rebooting. I am currently running 21.10, but I have had mysterious crashes in older versions of Ubuntu; I now wonder if the was going all the way to zero in some of those crashes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 10 15:32:43 2022 DistUpgraded: 2022-02-03 15:56:57,188 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2088] InstallationDate: Installed on 2021-01-25 (381 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Intel(R) Client Systems NUC9V7QNX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=UUID=7374319a-8421-4977-a836-6882e295d7ca ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-03 (6 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QNCFLX70.0059.2020.1130.2122 dmi.board.name: NUC9V7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K47180-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.39 dmi.modalias: dmi:bvnIntelCorp.:bvrQNCFLX70.0059.2020.1130.2122:bd11/30/2020:br5.13:efr24.39:svnIntel(R)ClientSystems:pnNUC9V7QNX:pvrK47174-402:rvnIntelCorporation:rnNUC9V7QNB:rvrK47180-402:cvnIntelCorporation:ct35:cvr2.0:skuBKNUC9V7QNX: dmi.product.family: QN dmi.product.name: NUC9V7QNX dmi.product.sku: BKNUC9V7QNX dmi.product.version: K47174-402 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960569/+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 1960569] Re: Screen goes dim
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960569 Title: Screen goes dim Status in xorg package in Ubuntu: New Bug description: I walk away from the machine; come back hours later to find that the screen is dim. The following command confirms that the cause is something in Ubuntu xrandr --listmonitors --verbose | egrep -3 -i 'gamma|backl|brightn' Has shown value for "Brightness" of 0.11, 0.18, 0.0018, 0.20, and possibly other values. (Gamma is all 1.0.) This occurs on both monitors that I have hooked up, but the values are usually different. I like a Brightness of 0.80, I know how to manually change with xrandr or a brightness-controller app. When the brightness is too low it is very hard to fix things without rebooting. I am currently running 21.10, but I have had mysterious crashes in older versions of Ubuntu; I now wonder if the was going all the way to zero in some of those crashes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 10 15:32:43 2022 DistUpgraded: 2022-02-03 15:56:57,188 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2088] InstallationDate: Installed on 2021-01-25 (381 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Intel(R) Client Systems NUC9V7QNX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=UUID=7374319a-8421-4977-a836-6882e295d7ca ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-03 (6 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QNCFLX70.0059.2020.1130.2122 dmi.board.name: NUC9V7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K47180-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.39 dmi.modalias: dmi:bvnIntelCorp.:bvrQNCFLX70.0059.2020.1130.2122:bd11/30/2020:br5.13:efr24.39:svnIntel(R)ClientSystems:pnNUC9V7QNX:pvrK47174-402:rvnIntelCorporation:rnNUC9V7QNB:rvrK47180-402:cvnIntelCorporation:ct35:cvr2.0:skuBKNUC9V7QNX: dmi.product.family: QN dmi.product.name: NUC9V7QNX dmi.product.sku: BKNUC9V7QNX dmi.product.version: K47174-402 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1960569/+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 1960569] [NEW] Screen goes dim
You have been subscribed to a public bug: I walk away from the machine; come back hours later to find that the screen is dim. The following command confirms that the cause is something in Ubuntu xrandr --listmonitors --verbose | egrep -3 -i 'gamma|backl|brightn' Has shown value for "Brightness" of 0.11, 0.18, 0.0018, 0.20, and possibly other values. (Gamma is all 1.0.) This occurs on both monitors that I have hooked up, but the values are usually different. I like a Brightness of 0.80, I know how to manually change with xrandr or a brightness-controller app. When the brightness is too low it is very hard to fix things without rebooting. I am currently running 21.10, but I have had mysterious crashes in older versions of Ubuntu; I now wonder if the was going all the way to zero in some of those crashes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 10 15:32:43 2022 DistUpgraded: 2022-02-03 15:56:57,188 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2088] InstallationDate: Installed on 2021-01-25 (381 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Intel(R) Client Systems NUC9V7QNX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=UUID=7374319a-8421-4977-a836-6882e295d7ca ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-03 (6 days ago) dmi.bios.date: 11/30/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QNCFLX70.0059.2020.1130.2122 dmi.board.name: NUC9V7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K47180-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.39 dmi.modalias: dmi:bvnIntelCorp.:bvrQNCFLX70.0059.2020.1130.2122:bd11/30/2020:br5.13:efr24.39:svnIntel(R)ClientSystems:pnNUC9V7QNX:pvrK47174-402:rvnIntelCorporation:rnNUC9V7QNB:rvrK47180-402:cvnIntelCorporation:ct35:cvr2.0:skuBKNUC9V7QNX: dmi.product.family: QN dmi.product.name: NUC9V7QNX dmi.product.sku: BKNUC9V7QNX dmi.product.version: K47174-402 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish possible-manual-nvidia-install ubuntu -- Screen goes dim https://bugs.launchpad.net/bugs/1960569 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1959508] Re: enable BMFF support in exiv2
> > I am uploading exiv2 now to Ubuntu as packaged in Debian. > I just looked at https://ftp.debian.org/debian/pool/main/e/exiv2/exiv2_0.27.5-1.debian.tar.xz and I don't think it enables BMFF at build time, so I don't think this will enable CR3 support: $ grep ENABLE debian/rules -DEXIV2_ENABLE_NLS=ON \ -DEXIV2_ENABLE_VIDEO=ON \ -DEXIV2_ENABLE_WEBREADY=ON \ > Could you ask exiv2 why they don't enable the feature by default? > BMFF support was not enabled by default in 0.27-5 out of an abundance of caution at the time that this feature was being worked on and possible legal implications were being investigated. The situation has clarified since then and it will be enabled by default in future Exiv2 versions. See the discussion at https://github.com/Exiv2/exiv2/issues/1679 Thanks On Fri, Feb 11, 2022 at 9:20 AM Jeremy Bicha <1959...@bugs.launchpad.net> wrote: > I am uploading exiv2 now to Ubuntu as packaged in Debian. > > Could you ask exiv2 why they don't enable the feature by default? > > ** Summary changed: > > - Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS > + enable BMFF support in exiv2 > > ** Changed in: exiv2 (Ubuntu) >Status: Confirmed => Incomplete > > ** Tags removed: upgrade-software-version > ** Tags added: jammy > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1959508 > > Title: > enable BMFF support in exiv2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions > > ** Bug watch added: github.com/Exiv2/exiv2/issues #1679 https://github.com/Exiv2/exiv2/issues/1679 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Incomplete Status in exiv2 package in Debian: New Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1960544] Re: External Monitors Not Detected Anymore
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: Invalid Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1960544] Re: External Monitors Not Detected Anymore
You are right, updating the kernel did solve the problem. Thanks a lot for your swift answer! -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: Invalid Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1959508] Re: enable BMFF support in exiv2
I am uploading exiv2 now to Ubuntu as packaged in Debian. Could you ask exiv2 why they don't enable the feature by default? ** Summary changed: - Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS + enable BMFF support in exiv2 ** Changed in: exiv2 (Ubuntu) Status: Confirmed => Incomplete ** Tags removed: upgrade-software-version ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Incomplete Status in exiv2 package in Debian: New Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1892825] Re: update-locale not perform correctly sanity checks
Hello bs, or anyone else affected, Accepted glibc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.5 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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: New Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
Hello Matthias, or anyone else affected, Accepted glibc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.5 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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957909] Re: NetworkManager connectivity check fails
Hello?? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1957909 Title: NetworkManager connectivity check fails Status in network-manager package in Ubuntu: New Bug description: I randomly receive "No internet connection available" notification, even if my internet connection is stable. (Not the exact term) In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint http://connectivity-check.ubuntu.com./ is used. I manually pinged the endpoint. I live in europe and the server is located in the US. The latency is about 160ms. Usually I have an approximate latency of 15ms. It is not a problem of my ISP, I receive this notification on different locations in Germany and Switzerland. I propose to use another endpoint or provide another server for the same endpoint for europe. So the DNS servers in europe provide the IP of a server located in europe. The config comes from the package "network-manager-config- connectivity-ubuntu" version 1.32.12-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1957909/+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 1960458] Re: patch git_socket_dir.patch causing FTBFS in gspell
Thanks Jeremy for fixing gspell, but it feels like a regression in at- spi-core still, things were building without setting NO_AT_BRIDGE=1 before that patch ** Changed in: at-spi2-core (Ubuntu) Status: Fix Released => New ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: New Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+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 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Xenial has reached end of standard support. ** Changed in: dnsmasq (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq source package in Xenial: Won't Fix Status in dnsmasq source package in Bionic: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal
Trusty has reached its end of standard support. ** Changed in: krb5 (Ubuntu Trusty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1817955 Title: Getting new "DN is out of the realm subtree" error on adding principal Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Trusty: Won't Fix Bug description: Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-2ubuntu5.4), and started getting errors when adding new principals to LDAP. Obfuscated example: kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\" testuser" now gives: Authenticating as principal root/ad...@test.example.com with password. NOTICE: no policy specified for testu...@test.example.com; assigning "default" add_principal: DN is out of the realm subtree while creating "testu...@test.example.com". This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to CVE-2018-5729 or CVE-2018-5730. I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+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 1960544] Re: External Monitors Not Detected Anymore
you need to update again and run 'apport-collect 1960544' also, test 21.10 live image to see if it works there -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: New Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1960544] Re: External Monitors Not Detected Anymore
that's unlikely, mesa has little to do with driving displays, the kernel does -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: New Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1960544] [NEW] External Monitors Not Detected Anymore
Public bug reported: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: - Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the - update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, - libglapi, libdrm etc.), external monitors (here connected via DELL USB - Dock) are not detected anymore. I had to restore the old version with - Timeshift. + On Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of + mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm + etc.), external monitors (here connected via DELL USB Dock) are not + detected anymore. I had to restore the old version with Timeshift. ** Description changed: - On Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of + On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm etc.), external monitors (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. ** Description changed: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of - mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm - etc.), external monitors (here connected via DELL USB Dock) are not - detected anymore. I had to restore the old version with Timeshift. + mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), + external monitors (here connected via DELL USB Dock) are not detected + anymore. I had to restore the old version with Timeshift. ** Description changed: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), - external monitors (here connected via DELL USB Dock) are not detected + external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: New Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1692302] Re: Can't connect on external monitor or projector
Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm etc.), external monitors (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. -- 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/1692302 Title: Can't connect on external monitor or projector Status in mesa package in Ubuntu: New Bug description: after update the mesa driver, my notebook (HP af118au AMD a8-7410 radeon R5) can't connect on projector or external monitor, but this update make some game can running more smooth and playable, I hope this problem can fix immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1692302/+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 1959085] Re: Ubuntu 21.10 boot stuck in initramfs
Dimitri, can you take a look at this? ** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1959085 Title: Ubuntu 21.10 boot stuck in initramfs Status in initramfs-tools package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
there is no python-is-python2 in jammy anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Confirmed Status in six package in Ubuntu: Invalid Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+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 1960508] [NEW] glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386
Public bug reported: After running "sudo apt upgrade" and approving the listed packages, the following error occurred after unpacking a number of packages: dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however: Package libmount1:i386 is not configured yet. output from "dpkg-reconfigure libmount1:i386": /usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully installed output from "sudo apt install libmount1:i386": Reading package lists... Done Building dependency tree... Done Reading state information... Done libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2). ... output from "sudo apt reinstall libmount1:i386": E: Internal Error, No file name for libmount1:i386 ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960508 Title: glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386 Status in glib2.0 package in Ubuntu: New Bug description: After running "sudo apt upgrade" and approving the listed packages, the following error occurred after unpacking a number of packages: dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however: Package libmount1:i386 is not configured yet. output from "dpkg-reconfigure libmount1:i386": /usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully installed output from "sudo apt install libmount1:i386": Reading package lists... Done Building dependency tree... Done Reading state information... Done libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2). ... output from "sudo apt reinstall libmount1:i386": E: Internal Error, No file name for libmount1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960508/+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 1953052] Re: In Jammy sound level reset after reboot
Problem disappeared after today updates(?) on my 2 desktop 3 different install of Jammy. but NOT disappeared on my laptop also updated today. Let me know what useful information I can provide. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
OK thanks. I'll consult with others on the SRU team on this - I've added it to our meeting agenda. If it's decided that this is OK then I'll make sure it's documented to avoid holding you up on it again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) Status in lxc package in Ubuntu: In Progress Bug description: LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to line things up in focal. [Impact] The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up with what's currently in jammy. We've been skipping a few of the bugfix releases in focal so far, mostly catching up when we're starting to see problems with the older version. In this case, we've seen a number of issues when running with the HWE kernels as well as autopkgtest issues on foreign architectures (arm64 and s390x), all those will go away with this bump as we've confirmed everything is clean in jammy. Changelog: * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * New upstream bugfix release (4.0.10): (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) - Fix issues with less common architectures - Support for additional idmap mounts - nft support in lxc-net - Cleaner mount entries for sys:mixed - Switched GPG server to keyserver.ubuntu.com * New upstream bugfix release (4.0.9): (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) - Fix incorrect personality setting when running 32bit containers on 64bit * New upstream bugfix release (4.0.8): - Fix CGroup attach against older running containers * New upstream bugfix release (4.0.7): - Testing improvements including fixes from oss-fuzz - Rework of the attach codepath - Cgroup handling rework * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) Just like Ubuntu itself, upstream releases long term support releases, e.g. 4.0, and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor/micro upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. [Test Plan] lxc has autopkgtests which will assert that the binaries built in -proposed are functional. [Where problems could occur] This is catching up a fair bit on recent kernel API changes, including cgroup1/cgroup2 support, handling of nftables, riscv64 and core scheduling which were all needed to properly handle the most recent HWE kernels especially as we're getting ready for Ubuntu 22.04's 5.15 to get pushed to focal. We've had all that code running on well over a million of LXD snap users for a few months now without seeing any issues (or more precisely, those issues we found have been all been resolved as of 4.0.12). However what LXD exercises isn't 100% of LXC and it's certainly possible that we missed a corner case in one of those changes. The good news is that this would most likely be triggered by a HWE kernel, so a viable workaround in many cases would be to temporarily go back to the original kernel (5.4) while the issue is sorted out in a follow up SRU. It's also worth noting that LXD CI runs daily tests against over a dozen different kernels coming from various distros which helps us identify such issues quite
[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+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 1955997] Re: The airplane hotkey has no function on a HP platform
Hi Robie, I think we are talking about Jammy as comment#11. and yes, as I mentioned in "Where problems could occur": >also each DM still need to deal with multi-rfkill events because upstream >changes[2]. From what I learned from HP, there are some old platforms have both Intel-HID and HPQ6001 components but I don't have the one in my side. I have 1. HPQ6001 HP laptop 2. Intel-HID HP laptop I shared what I can imaged when problems will occur, some check points and workaround in the bug description. Hope it can cover what you concerning. ** Description changed: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. + + In some old HP platforms (contains Intel-HID and HPQ6001 in same + machine), the user will aware the airplane mode toggled very quickly + e.g. turn-on and turn-off immediately (or works good without problem, + depends on how DM handles multiple rfkill events). + + In this case, you could check: + 1. sudo evtest + # You probably could see + # ... + # /dev/input/event8: Intel HID events + # ... + # /dev/input/event11: Wireless hotkeys + # or "HP Wireless hotkeys" depends on your kernel version + + 2. try to listen these events when pressing airplane key, you will + probably see these two events will send the keycode out. + + 3. check the components own this event + $ sudo udevadm info -a /dev/input/event11 + # ... + # ATTRS{phys}=="hpq6001/input0" + + $ sudo udevadm info -a /dev/input/event8 + # ... + #DRIVERS=="intel-hid" + + 4. check your hwdb is affect. + $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb + # If you didn't see anything then it means your intel-hid is unmask. + + 5. You could report a bug to your DM for dealing with two rfkill events (same as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as workaround (but it will be overwritten in next upgrade) by adding: + ``` + evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* + ``` + to /lib/udev/hwdb.d/60-keyboard.hwdb + + then + $ systemd-hwdb update + $ udevadm trigger [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda -- 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/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Impish: In Progress Status in systemd source package in Jammy: Fix Released Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. In some old HP platforms (contains Intel-HID and HPQ6001 in same machine), the user will aware the airplane mode toggled very quickly e.g. turn-on and turn-off immediately (or works good
[Touch-packages] [Bug 1944107] Re: No archive files for static compilation are included in the -dev package
This bug was fixed in the package libdrm - 2.4.107-8ubuntu1~20.04.1 --- libdrm (2.4.107-8ubuntu1~20.04.1) focal; urgency=medium * Backport to focal. (LP: #1949553) -- Timo Aaltonen Wed, 03 Nov 2021 09:15:14 +0200 ** Changed in: libdrm (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1944107 Title: No archive files for static compilation are included in the -dev package Status in libdrm package in Ubuntu: Fix Released Bug description: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+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 1949553] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1949553 Title: Backport packages for 20.04.4 HWE stack Status in libdrm package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Released Status in mesa source package in Focal: Fix Released Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] These are needed for 20.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: adds some new api, no changes to old stuff mesa: a new major release, but we'll pull the final stable release of 21.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1949553] Re: Backport packages for 20.04.4 HWE stack
This bug was fixed in the package mesa - 21.2.6-0ubuntu0.1~20.04.1 --- mesa (21.2.6-0ubuntu0.1~20.04.1) focal; urgency=medium * Backport to focal. (LP: #1949553) mesa (21.2.6-0ubuntu0.1) impish; urgency=medium * New bugfix release. (LP: #1956915) - Enable llvm for riscv64 still, to avoid installation issues -- Timo Aaltonen Mon, 10 Jan 2022 10:28:45 +0200 ** Changed in: mesa (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: libdrm (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1949553 Title: Backport packages for 20.04.4 HWE stack Status in libdrm package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Released Status in mesa source package in Focal: Fix Released Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] These are needed for 20.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: adds some new api, no changes to old stuff mesa: a new major release, but we'll pull the final stable release of 21.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1949553] Re: Backport packages for 20.04.4 HWE stack
This bug was fixed in the package libdrm - 2.4.107-8ubuntu1~20.04.1 --- libdrm (2.4.107-8ubuntu1~20.04.1) focal; urgency=medium * Backport to focal. (LP: #1949553) -- Timo Aaltonen Wed, 03 Nov 2021 09:15:14 +0200 -- 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/1949553 Title: Backport packages for 20.04.4 HWE stack Status in libdrm package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Released Status in mesa source package in Focal: Fix Released Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] These are needed for 20.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: adds some new api, no changes to old stuff mesa: a new major release, but we'll pull the final stable release of 21.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+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 1956915] Re: New bugfix release 21.2.6
This bug was fixed in the package mesa - 21.2.6-0ubuntu0.1~20.04.1 --- mesa (21.2.6-0ubuntu0.1~20.04.1) focal; urgency=medium * Backport to focal. (LP: #1949553) mesa (21.2.6-0ubuntu0.1) impish; urgency=medium * New bugfix release. (LP: #1956915) - Enable llvm for riscv64 still, to avoid installation issues -- Timo Aaltonen Mon, 10 Jan 2022 10:28:45 +0200 -- 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/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Status in mesa source package in Impish: Fix Released Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1956915] Re: New bugfix release 21.2.6
This bug was fixed in the package mesa - 21.2.6-0ubuntu0.1 --- mesa (21.2.6-0ubuntu0.1) impish; urgency=medium * New bugfix release. (LP: #1956915) - Enable llvm for riscv64 still, to avoid installation issues mesa (21.2.6-1) unstable; urgency=medium * New upstream release. mesa (21.2.5-1) unstable; urgency=medium * New upstream release. mesa (21.2.4-1) unstable; urgency=medium * New upstream release. mesa (21.2.3-2) unstable; urgency=medium * Revert back to llvm 12. (Closes: #995835) mesa (21.2.3-1) unstable; urgency=medium [ Timo Aaltonen ] * New upstream release. * rules: Build with -O2 for ppc64el. * Build with llvm 13. [ Aurelien Jarno ] * Disable LLVM support on riscv64, it doesn't have JIT. (Closes: #995618) -- Timo Aaltonen Mon, 10 Jan 2022 10:15:10 +0200 ** Changed in: mesa (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: mesa (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Status in mesa source package in Impish: Fix Released Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1956915] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Status in mesa source package in Impish: Fix Released Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1960460] Re: Fails to import ZFS rpool during boot
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- 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/1960460 Title: Fails to import ZFS rpool during boot Status in systemd package in Ubuntu: New Bug description: Fresh install using 20220202 Daily ISO with ZFS + Encryption selected from the installer The system ends up in busybox after entering the unlock key. Here is a part of the logs captured from the screen, the complete log can be found as an attachement: find: /dev/zvol/: No such file or directory /init: line 971: dirname: not found BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary. Usage: basename FILE [SUFFIX] Strip directory path and SUFFIX from FILE Please unlock disk keystore-:_ Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied Error: 1 Failed to mount rpool/ROOT/ubuntu ui69ph on /root//. Manually mount the filesystem and exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960460/+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 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
If the USB device is one of these: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b then see bug 1960377. -- 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/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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