[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
This didn't work for me: sudo apt install opensc-pkcs11 sudo snap refresh --edge firefox sudo snap connect firefox:pcscd cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common I need to use a proprietary module, called libaetpkss.so.3.5.4112, from safesign. It works in chrome (deb), and used to work in un-snapped firefox. I changed the steps above to copy that module instead of opensc-pkcs11 to the snap/firefox/common directory. I then try to load it from firefox, but it then says "unable to load module". Nothing in dmesg/apparmor, and the ownership of the file is correct. This module needs old libraries, like openssl1 and gdbm_compat.so.3, which I have in /usr/lib/*. Mayube I need to copy these over too? $ ldd libaetpkss.so.3.5.4112 linux-vdso.so.1 (0x7ffd31bfe000) libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x73f12aa0) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x73f12b8c4000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x73f12b8bf000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x73f12b8ba000) libpcsclite.so.1 => /lib/x86_64-linux-gnu/libpcsclite.so.1 (0x73f12b8ae000) libgdbm_compat.so.3 => /lib/x86_64-linux-gnu/libgdbm_compat.so.3 (0x73f12a40) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x73f12a00) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x73f12b87f000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x73f129c0) /lib64/ld-linux-x86-64.so.2 (0x73f12b8df000) libgdbm.so.3 => /lib/x86_64-linux-gnu/libgdbm.so.3 (0x73f12960) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x73f12b794000) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged Bug description: We believe the best solution/work-around at the moment is: sudo apt install opensc-pkcs11 sudo snap refresh --edge firefox sudo snap connect firefox:pcscd cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common Then load the module from that path, i.e. $HOME/snap/firefox/common/opensc-pkcs11.so. If you get "unable to load module" make sure you are the owner of the file: chown "$(id -u)" $HOME/snap/firefox/common/opensc-pkcs11.so Please report whether this solves the issue. The part of copying the module to a snap-readable location is clumsy and we will work on a more proper solution to that. I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux- gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
The current apparmor profile for digikam in oracular has these rules: /usr/lib/x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, /usr/lib/arm-linux-gnueabihf/qt5/libexec/QtWebEngineProcess cx -> &digikam//QtWebEngineProcess, There is not even a qt6 path, which in oracular is indeed without the architecture path component: $ apt-file find QtWebEngineProcess apparmor: /etc/apparmor.d/QtWebEngineProcess libqt5webenginecore5: /usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess libqt6webenginecore6-bin: /usr/lib/qt6/libexec/QtWebEngineProcess nsight-compute: /usr/lib/nsight-compute/host/linux-desktop-t210-a64/libexec/QtWebEngineProcess nsight-systems: /usr/lib/nsight-systems/host-linux-armv8/libexec/QtWebEngineProcess -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in Wike: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Fix Committed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Triaged Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in foliate package in Ubuntu: Fix Committed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Fix Released Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Fix Released Status in guix package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Fix Released Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Fix Released Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Fix Released Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Fix Released Status in qutebrowser package in Ubuntu: Fix Released Status in rssguard package in Ubuntu: Fix Released Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Fix Released Status in tellico package in Ubuntu: Fix Released Status in tor package in Ubuntu: Confirmed Status in wike package in Ubuntu: Fix Committed Status in apparmor source package in Noble: Fix Committed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078254] Re: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163.
This was uploaded. ** Changed in: pppconfig (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppconfig in Ubuntu. https://bugs.launchpad.net/bugs/2078254 Title: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163. Status in pppconfig package in Ubuntu: Fix Committed Status in pppconfig package in Debian: New Bug description: From the oracular archive rebuild ppa: https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular- amd64.pppconfig_2.3.28_BUILDING.txt.gz ... UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xEA" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE8" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xA0" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353. make: *** [debian/rules:12: build-stamp] Error 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppconfig/+bug/2078254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
Finally, and pardon my ignorance, but could /dev/dri/card0 be used for non-graphical things, like servers doing gpu calculations? And in that case, removing it could break that workload? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
During boot, when does exactly "/bin/rm /dev/dri/card0" run? Would that run in the initrd environment? I ask because of comment #37, which said they lost the display during the luks password prompt. Although I believe that's because of the workaround they were using then, which was to disable simpledrm via the kernel command line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
This regression potential concerns me, thank you for raising it: """ Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. """ It may be obvious to you that it's safe to remove /dev/dri/card0 (see comment #71), but it's not clear to me what creates that device, why, and when. Also, the test plan still does not cover non-nvidia platforms, and it sounds to me like that would be crucial. Finally, don't systems with multiple video cards exist, and couldn't one be using /dev/dri/card0? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desk
[Desktop-packages] [Bug 2078254] Re: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163.
Allesandro, subscribing you to this bug because of your PR at https://github.com/mquinson/po4a/pull/515 I'm willing to upload pppconfig with the debdiff you provided in the debian bug, and also po4a with the patch in your github PR[2], to unblock this FTBFS in Oracular. I can do follow-up uploads after a final fix is reached. What do you think? 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1072606;filename=pppconfig_2.3.29.debdiff;msg=10 2. https://github.com/mquinson/po4a/pull/515 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppconfig in Ubuntu. https://bugs.launchpad.net/bugs/2078254 Title: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163. Status in pppconfig package in Ubuntu: Triaged Status in pppconfig package in Debian: Unknown Bug description: From the oracular archive rebuild ppa: https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular- amd64.pppconfig_2.3.28_BUILDING.txt.gz ... UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xEA" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE8" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xA0" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353. make: *** [debian/rules:12: build-stamp] Error 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppconfig/+bug/2078254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078254] Re: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163.
Probably needs Fix (debdiff) proposed in Debb #1072606 ** Bug watch added: Debian Bug tracker #1072606 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072606 ** Also affects: pppconfig (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072606 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppconfig in Ubuntu. https://bugs.launchpad.net/bugs/2078254 Title: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163. Status in pppconfig package in Ubuntu: Triaged Status in pppconfig package in Debian: Unknown Bug description: From the oracular archive rebuild ppa: https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular- amd64.pppconfig_2.3.28_BUILDING.txt.gz ... UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xEA" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE8" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xA0" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353. make: *** [debian/rules:12: build-stamp] Error 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppconfig/+bug/2078254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078254] [NEW] ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163.
Public bug reported: >From the oracular archive rebuild ppa: https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular- amd64.pppconfig_2.3.28_BUILDING.txt.gz ... UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xEA" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE8" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xA0" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353. make: *** [debian/rules:12: build-stamp] Error 25 ** Affects: pppconfig (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: Triaged ** Tags: ftbfs server-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppconfig in Ubuntu. https://bugs.launchpad.net/bugs/2078254 Title: ftbfs: UTF-8 "\xAB" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 163. Status in pppconfig package in Ubuntu: Triaged Bug description: From the oracular archive rebuild ppa: https://launchpadlibrarian.net/745205685/buildlog_ubuntu-oracular- amd64.pppconfig_2.3.28_BUILDING.txt.gz ... UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 464. UTF-8 "\xEA" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE9" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xE8" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 509. UTF-8 "\xA0" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353. make: *** [debian/rules:12: build-stamp] Error 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppconfig/+bug/2078254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2067240] Re: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS
Hi Atlas, thanks for your verification. Following the request in comment #12, though: > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the > package you tested, Could you please clarify the version of the package you tested? ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2067240 Title: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS Status in OEM Priority Project: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information, and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops. (lp: #2045276) [ Test Plan ] Under Jammy environment, with latest linux-oem kernel installed, check output of `mmcli -L` to see if the modems are properly recognized. Modems to check: - EM061K-GL - EM160 - EM160 [ Where problems could occur ] EM160R-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs EM061K-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs RM520N-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones. Noble contains these changes, so, only SRU jammy and mantic. [ Other Info ] These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2072574] Update Released
The verification of the Stable Release Update for ubuntu-settings 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 Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2072574 Title: Drop obsolete evolution-data-server notify-with-tray override Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Released Bug description: Impact -- Calendar notifications currently pop up a full app window instead of as a normal notification. The normal notifications respect the Do Not Disturb setting, but the full app window does not. Test Case 1 --- From Ubuntu Desktop… 1. Add your Google account to GNOME Settings > Online Accounts 2. Add a calendar event to Google Calendar with a notification in advance 3. When it is time for the notification, you should see a GNOME Shell notification. You can click on the notification to see the full Reminders window. Test Case 2 --- From Ubuntu Unity 24.04 LTS… 1. Open a terminal and run this command: sudo apt install gnome-online-accounts-gtk 2. Close the terminal 3. Add a calendar event to Google Calendar with a notification in advance 4. When it is time for the notification, you should see a notification pop-up. You can click OK on the notification to see the full Reminders window. What Could Go Wrong --- The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far as the desktop experience goes with one additional GNOME Shell extension to sort the Show Apps view alphabetically. This is a small default change that can be easily changed (see Revert instructions below). I guess this could go bad if someone counts on getting event notifications even though they have turned on Do Not Disturb. I'm sorry but it is intended that Do Not Disturb not show notifications like this. Other Info -- I believe this override was originally added in 2011 for Unity's benefit LP: #757805 It was also helpful for GNOME in early GNOME 3 days with the unusual messaging tray that was later dropped. These days, GNOME Shell notifications work well, better than a separate popup window. Revert to Previous Behavior --- If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following: 1. Run this in a terminal: gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false 2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and Tasks, turn on "Display Reminder window with notifications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2072596] Update Released
The verification of the Stable Release Update for gnome-remote-desktop 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 Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2072596 Title: long delay when first installing version 46 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Noble: Fix Released Status in gnome-remote-desktop package in Debian: Fix Released Bug description: Impact -- There is a 90 second timeout delay during the upgrade to gnome-remote-desktop (as in the upgrade from Ubuntu Desktop 22.04 LTS or 23.10 to 24.04 LTS) More Details This SRU replaces the "automatic" postinst rules from dh_installsysusers and dh_installtmpfiles with custom postint rules that ensure that the sysusers and tmpfiles commands are run before dbus is reloaded. This is similar to what polkitd.postinst does but the new gnome-remote-desktop postinst is much simpler than what polkitd does. dh_installsysusers also adds Depends: systemd | systemd-standalone-sysusers | systemd-sysusers. (It appears like dh_installtmpfiles does not add similar dependencies). Because we only support systemd, I have manually added: Depends: systemd | systemd-sysusers, systemd | systemd-tmpfiles Test Case - From Ubuntu Desktop 24.04 LTS: 1. sudo apt remove gnome-remote-desktop 2. sudo systemctl stop gnome-remote-desktop 3. sudo deluser gnome-remote-desktop 4. sudo rm -fr /etc/gnome-remote-desktop /var/lib/gnome-remote-desktop Those steps will undo adding the user that systemd-sysusers is configured to add and undo adding the directories that systemd- tmpfiles adds. Then install the update. Verify that the update happens at normal speed without a long delay before completion. Alternate Test Case (Not Required) --- You could do an upgrade from 23.10 to 24.04 LTS but it requires much more time and attention to verify that there isn't an arbitrary delay while apt configures gnome-remote-desktop. Therefore, the other test case is recommended. What Could Go Wrong --- If a postinst command fails, then the system can be unable to finish installing gnome-remote-desktop. This can be a pain to clean up. In this case, the commands are protected by " || true". Other Info -- This issue is a follow-up for LP: #206 In that bug, gnome-remote-desktop wouldn't work at all for upgraders. This bugfix is being bundled with a new upstream release with more testing LP: #2072771 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2072596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2072771] Update Released
The verification of the Stable Release Update for gnome-remote-desktop 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 Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2072771 Title: Update gnome-remote-desktop to 46.3 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Noble: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 46 series It includes a crash fix Changes since the current Ubuntu 24.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/46.2...46.3 Test Cases -- Complete the Basic RDP Test Case and Basic Remote Login Test Case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2072771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Update Released
The verification of the Stable Release Update for livecd-rootfs 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 Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
This is just one day short of the aging period of 7 days, and there is another livecd-rootfs upload in unapproved[0]. Given that livecd-rootfs is "a frequent target of SRUs as part of development of changes to image builds for the target series, and is not intended for general installation on end-user systems. The risk of user-affecting regression is lower as a result, because the impact of changes to this package to end users is mediated by way of image builds"[1] and all other checks are green, I'm releasing this one day earlier. 0. https://launchpadlibrarian.net/742542501/livecd-rootfs_2.765.46_source.changes 1. https://wiki.ubuntu.com/StableReleaseUpdates#livecd-rootfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073054] Update Released
The verification of the Stable Release Update for libreoffice 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 Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073054 Title: [SRU] libreoffice 24.2.5 for noble Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Noble: Fix Released Bug description: [Impact] * LibreOffice 24.2.5 is in its fifth bugfix release of the 24.2 line: https://wiki.documentfoundation.org/ReleasePlan/24.2#24.2.5_release * Version 24.2.4 is currently released in noble. For a list of fixed bugs compared to 24.2.4 see the list of bugs fixed in the release candidates of 24.2.5 (that's a total of 78 bugs): https://wiki.documentfoundation.org/Releases/24.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/24.2.5/RC2#List_of_fixed_bugs 24.2.5 RC2 is identical to the 24.2.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_242/1277/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/16265079/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/amd64/libr/libreoffice/20240713_153605_52297@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/arm64/libr/libreoffice/20240713_160156_7ef87@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/armhf/libr/libreoffice/20240713_164543_bd1c9@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/ppc64el/libr/libreoffice/20240713_145657_249c9@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-noble-libreoffice-libreoffice-prereleases/noble/s390x/libr/libreoffice/20240713_153908_6c9ec@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice * Packaging changes are staged at https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/noble-24.2 [Regression Potential] * A minor release with a total of 78 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2072574] Re: Drop obsolete evolution-data-server notify-with-tray override
Hello Jeremy, or anyone else affected, Accepted ubuntu-settings into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/24.04.4 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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-settings (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2072574 Title: Drop obsolete evolution-data-server notify-with-tray override Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Noble: Fix Committed Bug description: Impact -- Calendar notifications currently pop up a full app window instead of as a normal notification. The normal notifications respect the Do Not Disturb setting, but the full app window does not. Test Case 1 --- From Ubuntu Desktop… 1. Add your Google account to GNOME Settings > Online Accounts 2. Add a calendar event to Google Calendar with a notification in advance 3. When it is time for the notification, you should see a GNOME Shell notification. You can click on the notification to see the full Reminders window. Test Case 2 --- From Ubuntu Unity 24.04 LTS… 1. Open a terminal and run this command: sudo apt install gnome-online-accounts-gtk 2. Close the terminal 3. Add a calendar event to Google Calendar with a notification in advance 4. When it is time for the notification, you should see a notification pop-up. You can click OK on the notification to see the full Reminders window. What Could Go Wrong --- The ubuntu-settings package is shipped by default with Ubuntu Desktop, Ubuntu Unity, and Edubuntu. Edubuntu is practically the same as Ubuntu Desktop as far as the desktop experience goes with one additional GNOME Shell extension to sort the Show Apps view alphabetically. This is a small default change that can be easily changed (see Revert instructions below). I guess this could go bad if someone counts on getting event notifications even though they have turned on Do Not Disturb. I'm sorry but it is intended that Do Not Disturb not show notifications like this. Other Info -- I believe this override was originally added in 2011 for Unity's benefit LP: #757805 It was also helpful for GNOME in early GNOME 3 days with the unusual messaging tray that was later dropped. These days, GNOME Shell notifications work well, better than a separate popup window. Revert to Previous Behavior --- If you prefer the original Ubuntu 24.04 LTS behavior, do one of the following: 1. Run this in a terminal: gsettings set org.gnome.evolution-data-server.calendar notify-with-tray false 2. Or install Evolution. In ☰ > Edit > Preferences > Calendar and Tasks, turn on "Display Reminder window with notifications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2072574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2067240] Re: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS
Hello Atlas, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: modemmanager (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2067240 Title: [SRU] Add Quectel EM061K-GL/EM160/RM520N PID information to support WWAN LVFS Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM061K-GL/EM160/RM520N PID information, and the modemmanger won't recognize these WWAN modems on some next-gen Lenovo laptops. (lp: #2045276) [ Test Plan ] Under Jammy environment, with latest linux-oem kernel installed, check output of `mmcli -L` to see if the modems are properly recognized. Modems to check: - EM061K-GL - EM160 - EM160 [ Where problems could occur ] EM160R-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1059/diffs EM061K-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1057/diffs RM520N-GL(1.22.0): https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1052/diffs https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/1077/diffs All these changes are merged, and they only introduce new PIDs for initial supports, which do not affect existing ones. Noble contains these changes, so, only SRU jammy and mantic. [ Other Info ] These patches are proved work with the test version on my PPA: https://launchpad.net/~pseudoc/+archive/ubuntu/nate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy
Please clarify the testing that was done, and *with which version exactly* (as requested in comment #12). This package had to go through a revert in the previous attempt to update to 1.72.4 (see version 1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2), and we need more confidence. ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
> /usr/lib/systemd/systemd --switched-root --system --deserialize=40 splash Ok, --switched-root is there in PID 1, it's something I was looking to confirm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE Status in apparmor package in Ubuntu: New Status in cups package in Ubuntu: Confirmed Status in rsyslog package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Bug description: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064370] Re: Blank screen after boot in raspberry pi 4
** Package changed: software-properties (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 Status in linux-raspi package in Ubuntu: New Bug description: I just flashed noble arm64+raspi image and booted it in my raspberry pi 4, and after initial rainbow screen kernel boots with 4 raspberries on the top and boot text appears as normal. But then, before it finishes booting, the screen goes blank. Image is ubuntu-24.04-preinstalled-server-arm64+raspi.img.xz downloaded at Apr/30. ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux I know the system booted because I can access it over the network and I even plugged a usb-serial adapter in the uart GPIOs and from there I can see the boot does progress to completion and offers me a prompt where I can use the system normally. But the HDMI screen stays blank. The funny thing is that I have been trying daily builds for quite some time now and they used to work well, this is the first one that does this (the official release). After testing some config options I found that if I change "dtoverlay=vc4-kms-v3d" for "dtoverlay=vc4-fkms-v3d" in config.txt then it boots ok and the screen stays on (note the change from kms to fkms). I also tried appending ",cma-128" to that line (it is present on other lines -- like for pi3 and pi0 -- but not on this one), it does not help. I don't think the issue is with my monitor since it works well for a long time. Also I checked EDIDs, they are detected when using fkms but they are blank when using kms: With KMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid EDID of '/sys/class/drm/card0-HDMI-A-1/edid' was empty. With fKMS: ubuntu@ubuntu:~$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00 01 1a 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24 .. (supressed) I do not use a graphical environment on this unit so I don't know the consequences of this change (to me it just fixes the issue, but I guess it was there for a reason). Let me know if you need any other information from the environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
** Description changed: + What's known so far: + - 24.04 desktop deployed with TPM+FDE shows this bug + - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode + - only after running aa-disable can the service start fine + - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/.." + - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism + - comment #2 also states that azure CVM images are also impacted + + + Original description follows: + This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: - LANG=en_GB.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/.." - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - + - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode + - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/.." + - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is cont
[Desktop-packages] [Bug 2064096] Re: rsyslog service timeout on noble numbat
I think neither rsyslog, nor cups, or sssd, are the correct packages for this bug, but I agree that spreading out the investigation over two different bugs is not good. I'll mark https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088 as a duplicate, and add cups and sssd tasks to this one for tracking purposes, but I suspect the fix will be elsewhere in the end. ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Summary changed: - rsyslog service timeout on noble numbat + Services fail to start in noble deployed with TPM+FDE ** Changed in: sssd (Ubuntu) Status: New => Confirmed ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE Status in cups package in Ubuntu: Confirmed Status in rsyslog package in Ubuntu: Confirmed Status in sssd package in Ubuntu: Confirmed Bug description: What's known so far: - 24.04 desktop deployed with TPM+FDE shows this bug - services confined with apparmor that need to access something in /run/systemd (like the notify socket) fail to do so, even if the apparmor profile is in complain mode. And the apparmor profile does already have rules to allow that access - only after running aa-disable can the service start fine - paths logged by the apparmor DENIED or ALLOWED messages are missing the "/run" prefix from "/run/systemd/..". - When we add rules to the profile using "/systemd/" (i.e., also dropping the /run prefix), then it works - other access in /run/systemd/ are also blocked, but the most noticeable one is the notify mechanism - comment #2 also states that azure CVM images are also impacted - comment #4 has instructions on how to create such a VM locally with LXD vms Original description follows: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2064096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058687] Please test proposed package
Hello Rico, or anyone else affected, Accepted libreoffice into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/4:7.6.6-0ubuntu0.23.10.1 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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2058687 Title: [SRU] libreoffice 7.6.6 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Committed Bug description: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of 39 bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1898/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 39 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 2058687] Re: [SRU] libreoffice 7.6.6 for mantic
translations tarball verified help tarball verified tarballs tarball: @@ -14,12 +14,13 @@ tiff-4.6.0.tar.xz libepubgen-0.1.1.tar.xz a39f6c07ddb20d7dd2ff1f95fa21e2cd-raptor2-2.0.15.tar.gz +libxslt-1.1.39.tar.xz freetype-2.13.0.tar.xz beeca87be45ec87d241ddd0e1bad80c1-bsh-2.0b6-src.zip openldap-2.6.6.tgz gpgme-1.18.0.tar.bz2 libodfgen-0.1.8.tar.xz -liblangtag-0.6.3.tar.bz2 +liblangtag-0.6.7.tar.bz2 libatomic_ops-7.6.8.tar.gz xmlsec1-1.2.37.tar.gz breakpad-b324760c7f53667af128a6b77b790323da04fcb9.tar.xz @@ -30,12 +31,10 @@ Firebird-3.0.7.33374-0.tar.bz2 frozen-1.1.1.tar.gz 3404ab6b1792ae5f16bbd603bd1e1d03-libformula-1.1.7.zip -zlib-1.3.tar.xz 1f5def51ca0026cd192958ef07228b52-rasqal-0.9.33.tar.gz lxml-4.1.1.tgz odfvalidator-0.9.0-RC2-SNAPSHOT-jar-with-dependencies-2726ab578664434a545f8379a01a9faffac0ae73.jar 5ade6ae2a99bc1e9e57031ca88d36dad-hyphen-2.8.8.tar.gz -libxslt-1.1.38.tar.xz libmwaw-0.3.21.tar.xz libmspub-0.1.4.tar.xz mDNSResponder-878.200.35.tar.gz @@ -59,12 +58,12 @@ libwps-0.4.14.tar.xz 3ade8cfe7e59ca8e65052644fed9fca4-epm-3.7.tar.gz poppler-23.09.0.tar.xz +zlib-1.3.1.tar.xz libetonyek-0.1.10.tar.xz 17410483b5b5f267aa18b7e00b65e6e0-hsqldb_1_8_0.zip d8bd5eed178db6e2b18eeed243f85aa8-flute-1.1.6.zip ba2930200c9f019c2d93a8c88c651a0f-flow-engine-0.9.4.zip glm-0.9.9.8.zip -libxml2-2.11.4.tar.xz 1725634df4bb3dcb1b2c91a6175f8789-GentiumBasic_1102.zip a7983f859eafb2677d7ff386a023bc40-xsltml_2.1.2.zip libabw-0.1.3.tar.xz @@ -75,6 +74,7 @@ dragonbox-1.1.3.tar.gz pixman-0.42.2.tar.gz libexttextcat-3.4.6.tar.xz +libxml2-2.12.5.tar.xz libpng-1.6.40.tar.xz f543e6e2d7275557a839a164941c0a86e5f2c3f2a0042bfc434c88c6dde9e140-opens___.ttf libffi-3.4.4.tar.gz So the changes are: libxslt 1.1.38 -> 1.1.39: verified liblangtag: 0.6.3 -> 0.6.7: verified zlib 1.3 -> 1.3.1: verified libxml2 2.11.4 -> 2.12.5: verified Tarballs of the same version didn't change. ** Changed in: libreoffice (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2058687 Title: [SRU] libreoffice 7.6.6 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Committed Bug description: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of 39 bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1898/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz * General smoke testing of all
[Desktop-packages] [Bug 2058687] Re: [SRU] libreoffice 7.6.6 for mantic
I downloaded the original tarballs from https://download.documentfoundation.org/libreoffice/src/7.6.6/ and: - verified their signatures - matched 7.6.6.orig.tar.xz to upstream's 7.6.6.3 (it's a versioning quirk to call 7.6.6rc3 7.6.6.3 in the end): $ sha256sum libreoffice_7.6.6.orig.tar.xz upstream/libreoffice-7.6.6.3.tar.xz 41a83a7f09c539e22c873107d5d4088ac7cdf1a299ad9e9de15e30600fe521b6 libreoffice_7.6.6.orig.tar.xz 41a83a7f09c539e22c873107d5d4088ac7cdf1a299ad9e9de15e30600fe521b6 upstream/libreoffice-7.6.6.3.tar.xz I also verified the packaging changes in debian/* via debdiff. The extra repacked tarballs from the source package are a bit harder to verify, I'm trying to do that next. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2058687 Title: [SRU] libreoffice 7.6.6 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: In Progress Bug description: [Impact] * LibreOffice 7.6.6 is in its sixth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.6_release * Version 7.6.5 is currently released in mantic. For a list of fixed bugs compared to 7.6.5 see the list of bugs fixed in the release candidates of 7.6.6 (that's a total of 39 bugs): https://wiki.documentfoundation.org/Releases/7.6.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.6/RC3#List_of_fixed_bugs 7.6.6 RC3 is identical to the 7.6.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1898/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15869507/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240323_001335_50e00@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240324_215819_0b108@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240322_202324_f628d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240322_145135_f3904@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240322_140411_ca6c5@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 39 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
https://launchpad.net/ubuntu/+source/cups/2.4.7-1.2ubuntu6 is in noble- proposed claiming to fix this bug. Comment #6 above says there is a missing patch still. In any case, doesn't look like there is anything to sponsor here, so unsubscribing ubuntu-sponsors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git Status in cups package in Ubuntu: In Progress Bug description: While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5), I noticed that cupsd crashes consistently after closing my Firefox tab / window. The title of the crash (from the bug-report window) is "cupsd crashed with SIGSEGV in ???()" I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying some updates from the noble and noble-proposed pockets. Reproduction steps: 1. Open Firefox and manage CUPS on http://localhost:631 2. Go to Administration -> Printers -> Add Printer and choose your printer 3. Add your printer (I used the ipps:// protocol to manage the printer) 4. After clicking the "Add printer" button, immediately close your Firefox tab 5. cupsd will crash and Ubuntu will display a bug-report popup Versions: Firefox - 124.0.1-1 r4033 CUPS - 2.4.7-1.2ubuntu5 Printer: Lexmark MS415dn (supported) I am unable to reproduce this bug on versions prior to 2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2). Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from the 2.4.x upstream git branch, so I also opened an issue on GitHub: https://github.com/OpenPrinting/cups/issues/934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
And unsubscribing sponsors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: Fix Committed Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
At the moment, noble-proposed has https://launchpad.net/ubuntu/+source/upower/1.90.3-1, uploaded a few hours ago: upower (1.90.3-1) unstable; urgency=medium * New upstream version 1.90.3 * Drop patches, merged upstream * Bump Build-Depends on meson to (>= 0.60.0) and libglib2.0-dev to (>= 2.66) as per meson.build * Switch Build-Depends on pkg-config to pkgconf * Bump Standards-Version to 4.7.0 -- Michael Biebl Mon, 08 Apr 2024 09:42:45 +0200 According to https://autopkgtest.ubuntu.com/packages/u/upower/noble/arm64 arm64 tests with that version have passed already: (...) 905s Ran 67 tests in 174.527s 905s 905s OK 905s PASS: upower/upower-integration.test 905s SUMMARY: total=1; passed=1; skipped=0; failed=0; user=11.5s; system=4.9s; maxrss=33304 906s autopkgtest [06:17:15]: test installed-tests: ---] 907s installed-tests PASS Closing bug (fix committed, since it's not yet in the release pocket). ** Changed in: upower (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: Fix Committed Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
The test failure on armhf persists: 939s # Running test: mutter-13/fullscreen-maximize.test 940s # Executing: mutter-13/fullscreen-maximize.test 941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code 1) 941s not ok - mutter-13/fullscreen-maximize.test -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
The test failure on armhf persists: 939s # Running test: mutter-13/fullscreen-maximize.test 940s # Executing: mutter-13/fullscreen-maximize.test 941s # FAIL: mutter-13/fullscreen-maximize.test (Child process exited with code 1) 941s not ok - mutter-13/fullscreen-maximize.test -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
There is an armhf DEP8 failure that I just retriggered, let's see if it passes in the next run. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
There is an armhf DEP8 failure that I just retriggered, let's see if it passes in the next run. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2052925] Update Released
The verification of the Stable Release Update for cups 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 Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2052925] Re: lpoptions -d as root
I noticed this SRU was prepared without the SRU Template[1] filled in. While most of the data we want is in the bug description as is (what's wrong, test plan), it's lacking an analysis of what could go wrong. That boat has sailed now, and doing an analysis of the patch right now, basically what could go wrong is if someone was relying on the old behavior, of the command only changing the local user's (root in this case) config, instead of system-wide. The lpoptions[1] manpage doesn't really special case root when the -d option is used: -d destination[/instance] Sets the user default printer to destination. If instance is supplied then that particular instance is used. This option overrides the system default printer for the current user. But later down, in "FILES", we see: ~/.cups/lpoptions - user defaults and instances created by non-root users. /etc/cups/lpoptions - system-wide defaults and instances created by the root user. So it does seem the intention of that option when used by the root user was to update the system-wide /etc/cups/lpoptions file instead. So even if someone was relying on the previous behavior, it was incorrect, and the documentation (which could be clearer, but isn't) seems to agree that the previous behavior was incorrect. That's the kind of analysis we would like to see in "what could go wrong", and "other info" sections of the SRU template. 1. https://manpages.ubuntu.com/manpages/jammy/en/man1/lpoptions.1.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21
[Desktop-packages] [Bug 2054111] Update Released
The verification of the Stable Release Update for libreoffice 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 Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2054111 Title: [SRU] libreoffice 7.6.5 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.4 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of 94 bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC2 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15791929/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240216_132420_3c270@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240216_140709_197f6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240216_222053_83134@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240216_130131_fd665@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240216_141429_f0d16@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 94 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055300] [NEW] DEP8 failures in noble/armhf with samba 4.19.5
Public bug reported: https://autopkgtest.ubuntu.com/packages/adsys/noble/armhf I did multiple retries already, but the failures look persistent. The tests passed in other architectures, but also needed one retry on arm64. In armhf, there have been 5 retries already. ** Affects: adsys (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2055300 Title: DEP8 failures in noble/armhf with samba 4.19.5 Status in adsys package in Ubuntu: New Bug description: https://autopkgtest.ubuntu.com/packages/adsys/noble/armhf I did multiple retries already, but the failures look persistent. The tests passed in other architectures, but also needed one retry on arm64. In armhf, there have been 5 retries already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2055300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055198] [NEW] RM: please remove libmail-dkim-perl 1.20240124-1 from noble-proposed
Public bug reported: Discussion: https://code.launchpad.net/~mirespace/ubuntu/+source/libmail-dkim- perl/+git/libmail-dkim-perl/+merge/460681 We want to ship noble with libmail-dkim-perl 1.20230212-1 which does not have Ed25519 support, and thus does not depend on libcryptx-perl which is in universe. The current situation with libmail-dkim-perl 1.20240124-1 creates a component mismatch because it depends on libcryptx-perl which is in universe. libmail-dkim-perl 1.20230212-1 which is in noble release at the moment does not depend on libcryptx-perl. The second part of this plan is to upload a no-change rebuild of libmail-dkim-perl 1.20230212-1ubuntu1 as soon as this removal is done, to block automatic syncs from debian which would just try to update it to 1.20240124-1 again. ** Affects: libmail-dkim-perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmail-dkim-perl in Ubuntu. https://bugs.launchpad.net/bugs/2055198 Title: RM: please remove libmail-dkim-perl 1.20240124-1 from noble-proposed Status in libmail-dkim-perl package in Ubuntu: New Bug description: Discussion: https://code.launchpad.net/~mirespace/ubuntu/+source/libmail-dkim- perl/+git/libmail-dkim-perl/+merge/460681 We want to ship noble with libmail-dkim-perl 1.20230212-1 which does not have Ed25519 support, and thus does not depend on libcryptx-perl which is in universe. The current situation with libmail-dkim-perl 1.20240124-1 creates a component mismatch because it depends on libcryptx-perl which is in universe. libmail-dkim-perl 1.20230212-1 which is in noble release at the moment does not depend on libcryptx-perl. The second part of this plan is to upload a no-change rebuild of libmail-dkim-perl 1.20230212-1ubuntu1 as soon as this removal is done, to block automatic syncs from debian which would just try to update it to 1.20240124-1 again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dkim-perl/+bug/2055198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054111] Re: [SRU] libreoffice 7.6.5 for mantic
Hello Rico, or anyone else affected, Accepted libreoffice into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/4:7.6.5-0ubuntu0.23.10.1 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: libreoffice (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2054111 Title: [SRU] libreoffice 7.6.5 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Committed Bug description: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.4 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of 94 bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC2 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15791929/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240216_132420_3c270@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240216_140709_197f6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240216_222053_83134@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240216_130131_fd665@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240216_141429_f0d16@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 94 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to:
[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop 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: Fix Committed Status in mesa source package in Jammy: Fix Committed 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 mantic 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] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Technically, the verification from prior comments was performed on 23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they need to be done on the mesa package that is in proposed now, which is .2. -- You received this bug notification because you are a member of Desktop 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: Fix Committed Status in mesa source package in Jammy: Fix Committed 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 mantic 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] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037604] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop 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: Fix Committed Status in mesa source package in Jammy: Fix Committed 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 mantic 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] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
Hello Lee, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
Please amend the test case to test with both the GA and the (affected) 6.1 OEM kernels. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Update Released
The verification of the Stable Release Update for modemmanager 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 Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
Thank you for the detailed and unambiguous verification! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Update Released
The verification of the Stable Release Update for transmission 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 Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Released Status in transmission source package in Lunar: Fix Released Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
mantic verification I used mutter from mantic-proposed: andreas@nsnx2:~$ apt-cache policy mutter mutter: Installed: 45.2-0ubuntu2~really45.0 Candidate: 45.2-0ubuntu2~really45.0 Version table: *** 45.2-0ubuntu2~really45.0 100 100 http://br.archive.ubuntu.com/ubuntu mantic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 45.2-0ubuntu1 500 (phased 0%) 500 http://br.archive.ubuntu.com/ubuntu mantic-updates/universe amd64 Packages 45.0-3ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages I installed gnome-session gnome-shell-extensions. I did not install budgie, because the test plan at https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter says it's not needed for 23.10. Each login, I selected a different session from this list: GNOME, GNOME Classic, Ubuntu, Ubuntu on Xorg. In each session, I did: - play 4k youtube video in full screen in firefox and chrome. For the next steps, I left firefox playing that video while conducting the other checks - verified that firefox was using hardware acceleration (chrome isn't, that's known) - sent a notification via notify-send, observed it was displayed - did a large file copy with the file manager. First, locally, then over the network using SMB. I did not observe any stuttering during these verifications, nor any other ill effect. The hardware this was tested on is a ThinkPad X1 Carbon Gen 10 with an Intel Alderlake_p (Gen12) video system. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This is a regression introduced upstream in mutter 45.1 (8f27ebf8), although it only hurts the triple buffering patch so that's where it's fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
The DEP8 tests are green now. I'm going to verify this revert for mantic, which is currently in mantic-proposed. But note I have NOT been able to reproduce the stuttering in firefox with the mutter package from mantic-updates (45.2-0ubuntu1). I tried: - wayland - xorg - native resolution (2880x1800)) and 1920x1200 - youtube playback, full screen, windows, 4k resolution. I also observed hardware acceleration was being used - I have even set MUTTER_DEBUG_TRIPLE_BUFFERING to "auto" in /etc/environment, which is what the bug description says should NOT be done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This is a regression introduced upstream in mutter 45.1 (8f27ebf8), although it only hurts the triple buffering patch so that's where it's fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
I see this was filed on the 13th. Had this been mentioned in the 45.2 mantic SRU bug[1], I wouldn't have released the package to updates on the 14th :/ 1. https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Bug description: There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This is a regression introduced upstream in mutter 45.1 (8f27ebf8), although it only hurts the triple buffering patch so that's where it's fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
Hello shine, or anyone else affected,
Accepted gnome-shell into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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 added: verification-needed-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1915929
Title:
gnome-shell-calendar-server assert failure on arm64: double free or
corruption (fasttop)
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Focal:
Fix Committed
Status in gnome-shell source package in Hirsute:
Fix Released
Bug description:
[ Impact ]
gnome-shell-calendar-server crashes (and it seems to happen more in
aarch64).
https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1
[ Test case ]
There's not a clear test case, but this is relevant:
- Configure a supported calendar in your online accounts
- GNOME shell should show your events in the calendar (under notifications
panel)
[ Regression potential ]
gnome-shell-calendar-server may leak memory.
---
M1 Mac mini
Parallels Ubuntu VM
ProblemType: CrashDistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic aarch64
ApportVersion: 2.20.11-0ubuntu58
Architecture: arm64
AssertionMessage: double free or corruption (fasttop)
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 04:34:36 2021
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-calendar-server
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
InstallationDate: Installed on 2021-02-17 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
ProcCmdline: /usr/libexec/gnome-shell-calendar-server
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANG=en_US.UTF-8
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
Signal: 6SourcePackage: gnome-shell
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
malloc_printerr (str=str@entry=0x81240c08 "double free or corruption
(fasttop)") at malloc.c:5389
_int_free (av=, p=0xe9eee300, have_lock=0) at
malloc.c:4298
g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-shell-calendar-server assert failure: double free or corruption
(fasttop)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small
Hello Kai-Chuan, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.9-0ubuntu0.20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. ** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small Status in Mutter: Fix Released Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] Touchscreen touches at the left or bottom edges (within 20px) of the screen are not treated as mouse clicks. Icons only get highlighted, not launched. [ Test Plan ] 0. Find a touchscreen. 1. Set Ubuntu Dock in Panel mode (the default mode) if not already. 2. Touch as close to the edge of the screen as possible. Aim for the gap between the icon and the edge of the screen. Expect: The app launch animation occurs for each tap. Icons aren't just highlighted. [ Where problems could occur ] Anywhere in touchscreen gesture tracking or even regular touchscreen usage. As this bug demonstrates, the former is able to interfere with even simple touchscreen actions. [ Workaround ] Size the Ubuntu Dock adequately large so it is unlikely the user will touch less than 20 pixels from the edge of the screen. [ Original description ] On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043000] Update Released
The verification of the Stable Release Update for mutter 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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Update Released
The verification of the Stable Release Update for mutter 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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Released Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Update Released
The verification of the Stable Release Update for mutter 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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
Fix Released
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
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..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor:
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
> I wanted to test the updated version of mutter so a couple of days ago I > enabled the `proposed` > repository, but I didn't receive any updates. Jeremie, you also have to pass "-t mantic-proposed" in the apt command line. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043000] Re: Update mutter to 45.2
Also, before release, please someone clarify this statement about a mesa regression in noble with 45.1 presumably: "It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
Hello Jeremie, or anyone else affected, Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1 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: mutter (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043000] Re: Update mutter to 45.2
Hello Jeremy, or anyone else affected, Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1 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: mutter (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Hello Gonzalo, or anyone else affected, Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu1 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: mutter (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043027 Title: Wacom Intuos S stop working after upgrading to Ubuntu 23.10 Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Mantic: Fix Committed Bug description: Impact -- Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 sessions Test Case - One of the people affected by this issue will verify whether their Wacom tablet is working noticably better with the upgraded Mutter packages What Could Go Wrong --- The fix for this issue is included in upstream's mutter 45.2 release so please see bug 2043000 as the master bug for this upgrade Original Bug Report --- Tablet seems to work until I open Krita (as I could read on Internet, it may be related with Qt Apps). When Krita is open, mouse movement works ok with the tablet, but when it comes to click action it doesn't work and any further action with mouse is not captured (even outside Krita!). To regain control of the mouse I have to Alt+Tab and then I can click again. Some details that may be handy: - I've got two monitors - Maybe Qt apps related - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535 Thanks for your effort. I love Ubuntu! 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..06.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 17:20:34 2023 DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [
[Desktop-packages] [Bug 2043000] Re: Update mutter to 45.2
noble-proposed still only has 45.1-2ubuntu1, btw. It should get 45.2 before this update is released to mantic. I updated the main bug status to reflect that noble isn't fixed nor committed yet. ** Changed in: mutter (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043000 Title: Update mutter to 45.2 Status in mutter package in Ubuntu: Triaged Status in mutter source package in Mantic: In Progress Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Ubuntu 24.04 "Noble" has mutter 45.1 with all the non translation commits cherry-picked. It will get updated to 45.2 (and eventually to 46) after a mesa regression is handled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Hello Chuck, thanks for the verification. Can you please confirm the package version? The output of the command below is enough: apt-cache policy transmission-daemon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041716] Re: [SRU] libreoffice 7.5.8 for lunar
I'm OK with releasing this one day short of the 7-day aging period. I don't think there is any gain in waiting an extra day for this update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2041716 Title: [SRU] libreoffice 7.5.8 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release * Version 7.5.7 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of 21 bugs): https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs 7.5.8 RC2 is identical to the 7.5.8 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1762/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 21 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2041716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041716] Update Released
The verification of the Stable Release Update for libreoffice 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 Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2041716 Title: [SRU] libreoffice 7.5.8 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release * Version 7.5.7 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of 21 bugs): https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs 7.5.8 RC2 is identical to the 7.5.8 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1762/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 21 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2041716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043015] Update Released
The verification of the Stable Release Update for gnome-shell 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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2043015 Title: Update gnome-shell to 45.1 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Mantic: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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 Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038783] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock 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 Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Released Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file:///foo/bar/baz echo $? An error should be shown and the return code should be 1 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js handler file://$HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042394] Re: Support goodix fingerprint [27c6:6582]
Marking as incomplete pending the completion of what was requested in comment #2 above. I also added tasks for the missing ubuntu releases. ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Noble) Importance: High Status: New ** Also affects: libfprint (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Incomplete ** Changed in: libfprint (Ubuntu Jammy) Status: Incomplete => New ** Changed in: libfprint (Ubuntu Lunar) Status: New => Incomplete ** Changed in: libfprint (Ubuntu Mantic) Status: New => Incomplete ** Changed in: libfprint (Ubuntu Noble) Status: New => Incomplete ** Changed in: libfprint (Ubuntu Jammy) Status: New => Triaged ** Changed in: libfprint (Ubuntu Jammy) Importance: Undecided => High ** Changed in: libfprint (Ubuntu Lunar) Importance: Undecided => High ** Changed in: libfprint (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2042394 Title: Support goodix fingerprint [27c6:6582] Status in OEM Priority Project: Triaged Status in libfprint package in Ubuntu: Incomplete Status in libfprint source package in Jammy: Triaged Status in libfprint source package in Lunar: Incomplete Status in libfprint source package in Mantic: Incomplete Status in libfprint source package in Noble: Incomplete Bug description: [27c6:6582] include in https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/447 [Impact] * Support goodix [27c6:6582] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Sponsored for jammy and lunar. Mantic has 4.0 which is not affected. Unsubscribing sponsors. ** Changed in: transmission (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: New Status in transmission source package in Lunar: New Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
** Description changed: - Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on - a Raspberry Pi 4. + [ Impact ] + + There is a memory leak in transmission-daemon that was introduced by a + faulty openssl3 patch. It has been reported that it's noticeable after a + few hours of seeding/downloading torrent files, less than a day. + + + [ Test Plan ] + + Being a memory leak, there is no immediate/quick test that can be + performed, other than letting it run for a few hours and measure memory + consumption "before" and "after". comment #5 mentions about 1Gb of RAM + after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how + long it was running. + + I'd suggest a 24h test and that it should stay under 1Gb of RAM. + + [ Where problems could occur ] + + The patch loads the default and legacy openssl3 providers. This will + potentially change the set of algorithms available to the application, + compared to what was there before. That being said, the legacy provider + is a conservative approach, and the likely result is that *more* + algorithms will become available, and not less. This is also the + approach I have seen in other applications that were rebuilt using + openssl3 instead of openssl1.1. + + It does seem safer than the original patch, which was manually handling + ciphers, in particular RC4, and, well, introduced the memory leak. + + + [ Other Info ] + + Patch came from gentoo. + + + [ Original Description ] + Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. - Description:Ubuntu 22.04 LTS Release:22.04 ** Description changed: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. - [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. + + comment #20 says that after 24h using the patched version from a PPA + build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. + [ Other Info ] - [ Other Info ] - Patch came from gentoo. - [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Status in transmission source package in Jammy: New Status in transmission source package in Lunar: New Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest
[Desktop-packages] [Bug 2039804] Update Released
The verification of the Stable Release Update for qpdf 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 Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/2039804 Title: Data loss: qpdf discards the character in a binary string following an octal quoted character with 1 or 2 digits Status in Qpdf: Fix Released Status in qpdf package in Ubuntu: Fix Released Status in qpdf source package in Lunar: Fix Released Status in qpdf source package in Mantic: Fix Released Status in qpdf package in Debian: Fix Released Bug description: Notes: * I am the upstream author and debian maintainer for qpdf. * This bug has been fixed in debian unstable and testing with version 11.6.3, but because 24.04 is not yet open, it has not synced. This should not block fixing 23.04 and 22.04. I have uploaded 11.6.3 to my ppa: https://launchpad.net/~qpdf/+archive/ubuntu/qpdf * I am attaching debdiffs for lunar and mantic Upstream bug https://github.com/qpdf/qpdf/issues/1050 revealed a bug in qpdf's lexical layer that would cause qpdf to discard the character in a binary string following an octal quoted character with 1 or 2 digits. The PDF spec allows octal digits to be \d, \dd, or \ddd, and allows the first two forms if the next character is other than an octal digit. Most PDF writers never use the \d or \dd forms, but some do. With default options, qpdf does not parse or alter strings inside content streams, so this bug is not likely to affect page content. However, binary strings of this sort are common in the document /ID and may also appear in metadata for encrypted files. In some cases, such as the file in #1050, this bug can cause error, in this case, because the discarded character was the string end delimiter. In most case, this bug results in silent data loss. The fix is very small and locally contained. The upstream fix includes several new test cases, but the patch I will include to fix the issue only includes the relevant code change. I also reported this as a debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1054158 It was approved as a stable update by debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054119 [ Impact ] The bug could result in silent corruption of binary strings in PDF metadata. It could also result in failure of qpdf to process a valid file. Data loss justifies a stable update. [ Test Plan ] The test file in https://github.com/qpdf/qpdf/issues/1050 can be used to prove that the bug exists in versions >= 11.0.0 and <= 11.6.2 and that the bug is fixed in 11.6.3. The upstream fix includes several additional automated test cases. These are not included in the patch, but they are included in the upstream commit that fixes the bug: https://github.com/qpdf/qpdf/commit/1ecc6bb29e24a4f89470ff91b2682b46e0576ad4 How to test the SRU package on Ubuntu manually (copied from Jay's comment #6 below): Running `qpdf --check 018.pdf` where `018.pdf` is the file attached to the upstream bug will reproduce the issue. With the current version in 22.04 and 23.04, you will see something like this: ``` WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110340): EOF while reading token WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): unexpected EOF WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): parse error while reading object WARNING: /tmp/z/018.pdf (xref stream: object 17 1, offset 110830): expected endobj WARNING: /tmp/z/018.pdf: file is damaged WARNING: /tmp/z/018.pdf (offset 110267): xref not found WARNING: /tmp/z/018.pdf: Attempting to reconstruct cross-reference table qpdf: /tmp/z/018.pdf: unable to find trailer dictionary while recovering damaged file ``` After the fix, you will see ``` checking /home/ejb/Downloads/018.pdf PDF Version: 1.7 File is not encrypted File is not linearized No syntax or stream encoding errors found; the file may still contain errors that qpdf cannot detect ``` (obviously with the full paths based on whatever you call the file). [ Where problems could occur ] This fix has a very low risk of causing a regression. The fix is very localized to qpdf's lexical layer and is in a code path that only occurs when a 1-digit or 2-digit octal quoted character is terminated by other than an octal digit. This is the first bug in qpdf's lexical layer in many years. It was introduced by a pull request from a reliable and
[Desktop-packages] [Bug 2038907] Re: Ubuntu patch incorrect disable the thunderbolt and security panels
Noble also has 1:45.0-1ubuntu3, with the same fix. This all started before noble was released, hence the version collision, but I'm pretty sure that throughout the devel cycle, noble will get a gnome-control- center version bump, so no harm in releasing mantic with this version now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038907 Title: Ubuntu patch incorrect disable the thunderbolt and security panels Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Mantic: Fix Released Bug description: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038907] Update Released
The verification of the Stable Release Update for gnome-control-center 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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038907 Title: Ubuntu patch incorrect disable the thunderbolt and security panels Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Mantic: Fix Released Bug description: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Update Released
The verification of the Stable Release Update for mutter 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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C
I still get this error in Ubuntu Lunar, with kernel 6.2.0-35-generic. Sample: $ sudo dmesg -T|grep Atomic [qua nov 1 05:52:03 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=78023 end=78024) time 305 us, min 1783, max 1799, scanline start 1753, end 1804 [qua nov 1 06:15:56 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=161109 end=161110) time 209 us, min 1783, max 1799, scanline start 1775, end 1811 [qua nov 1 22:22:34 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=50827 end=50828) time 270 us, min 1783, max 1799, scanline start 1767, end 1812 [qua nov 1 22:32:50 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=90592 end=90593) time 278 us, min 1783, max 1799, scanline start 1768, end 1814 [qua nov 1 22:35:42 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=100359 end=100360) time 168 us, min 1783, max 1799, scanline start 1779, end 1807 [qua nov 1 23:29:19 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=259865 end=259866) time 276 us, min 1783, max 1799, scanline start 1770, end 1817 [qui nov 2 03:54:09 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=317370 end=317371) time 264 us, min 1783, max 1799, scanline start 1756, end 1801 [qui nov 2 03:57:36 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=331393 end=331394) time 279 us, min 1783, max 1799, scanline start 1769, end 1816 [qui nov 2 04:00:05 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe C (start=317726 end=317727) time 255 us, min 2146, max 2159, scanline start 2140, end 2173 [qui nov 2 04:48:44 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe C (start=492825 end=492826) time 272 us, min 2146, max 2159, scanline start 2123, end 2159 Hardware is a lenovo x1 10th gen, with intel "alderlake gen12" according to intel_gpu_top, and I'm running xorg (not wayland). ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86]
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Marius, Andrey thanks for your contribution! I uploaded jammy and lunar packages to this ppa[1], with amd64 and arm64 builds, with the gentoo patch replacing the one we had in the package. Marius, I changed the d/changelog text a bit, I hope you don't mind, but please let me know if you have concerns. I want to make sure to give credit to everybody involved, and keep your name in the changelog entry so this upload goes to you when it's sponsored. The PPAs are a bit slow, since we just opened the next ubuntu release (noble) for development, so give them some time. Here are the branches from which I built these packages: - jammy: https://code.launchpad.net/~ahasenack/ubuntu/+source/transmission/+git/transmission/+ref/jammy-transmission-memleak-1973084 - lunar: https://code.launchpad.net/~ahasenack/ubuntu/+source/transmission/+git/transmission/+ref/lunar-transmission-memleak-1973084 Mantic and later are at version 4.0.2, and focal and earlier are at 2.94, so I believe they are not affected. The problematic openssl3 patch is in neither. If these work for you guys, then we can start preparing for an SRU, which would definitely be worth it. 1. https://launchpad.net/~ahasenack/+archive/ubuntu/transmission- memleak-1973084/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Status in transmission source package in Jammy: New Status in transmission source package in Lunar: New Status in transmission package in Debian: New Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
** Also affects: transmission (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: transmission (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Status in transmission source package in Jammy: New Status in transmission source package in Lunar: New Status in transmission package in Debian: Unknown Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946215] Re: transmission: Fail to build against OpenSSL 3.0
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084 is the memleak bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1946215 Title: transmission: Fail to build against OpenSSL 3.0 Status in transmission package in Ubuntu: Fix Released Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099409/+files/buildlog_ubuntu- impish-amd64.transmission_3.00-1ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 This has been fixed upstream, currently on master: https://github.com/transmission/transmission/pull/1788 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1946215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
** Bug watch added: Debian Bug tracker #1051056 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051056 ** Also affects: transmission (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051056 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Status in transmission package in Debian: Unknown Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore
Hi Nathan, I see that the discussion on the upstream PR[1] is still ongoing, and there isn't consensus yet. I think it's best to put this on hold until a conclusion is reached, and then this can move forward. I'll therefore unsubscribe sponsors for now. Please subscribe again once a decision has been reached on how to proceed. 1. https://github.com/flatpak/xdg-desktop-portal-gtk/pull/447 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk source package in Focal: New Status in xdg-desktop-portal-gtk source package in Jammy: New Status in xdg-desktop-portal-gtk source package in Lunar: New Status in xdg-desktop-portal-gtk source package in Mantic: Confirmed Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019045] Re: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar
I installed ubuntu-fonts-classic from mantic on my lunar desktop (it's not available for lunar). It removed ubuntu-fonts, but the fonts look ok now in google docs. Got some differences in my desktop too, but still looks ok. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2019045 Title: [snap] New Ubuntu font with normal weight displayed as bold in Google Docs in Chromium after upgrading to Lunar Status in chromium-browser package in Ubuntu: Triaged Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: I am experiencing a rendering regression after upgrading from Kinetic to Lunar. Google Docs using the Ubuntu font family are displayed incorrectly in Chromium: the normal weight font is rendered identically to the bold weight one, instead of being thicker than light and thinner than medium. Printing is also affected, unless I use Google Docs' download to PDF function, although that probably triggers a server-side rendering. This issue does not occur in Firefox or Google Chrome. One thing that may be relevant: if I force-refresh my test Google Doc I see all four Ubuntu font lines initially being rendered as bold. The light and medium lines are then re-rendered with the correct weight. It's as if bold was the default weight and the normal variant disappeared. As far as I can tell I was already running Chromium 112.0.5615.49 in Kinetic, and with Chromium being a snap I don't quite understand why the Ubuntu series would matter. I have also tried version 114.0.5735.16 (in latest/beta at the moment); the symptoms are identical. The attachments show the rendering error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2019045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
This bug is ready for verification. Due to the status mantic was in when the package was accepted, the tooling failed to add the template comment to this bug, and add the tags, and I did all of that manually now. ** Tags added: verification-needed verification-needed-mantic ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed ** Also affects: gnome-shell-extension-tiling-assistant (Ubuntu Mantic) Importance: Undecided Assignee: Jeremy Bícha (jbicha) Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038783] Re: Exit code of locations mount script is not respecting error
This bug is ready for verification. Due to the status mantic was in when the package was accepted, the tooling failed to add the template comment to this bug, and add the tags, and I did all of that manually now. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2038783 Title: Exit code of locations mount script is not respecting error Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] When mounting an external location a script is used to get the current default app for a type, its return error is parsed by the dock to provide users a feedback, but the returned code is not valid in case of error. [ Test case ] Run: gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js /foo/bar/baz echo $? An error should be shown and the return code should be 15 Doing instead gjs -m /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locationsWorker.js $HOME echo $? The file manager desktop-id should be printed and the script should return 0. [ Regression Potential ] Some locations may not have a default handler and so not being launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2038783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038907] Re: Ubuntu patch incorrect disable the thunderbolt and security panels
This bug is ready for verification. Due to the release status mantic was in when the package was accepted, the tooling failed to add the template comment to this bug, and add the tags, and I did all of that manually now. ** Also affects: gnome-control-center (Ubuntu Mantic) Importance: High Assignee: Sebastien Bacher (seb128) Status: In Progress ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2038907 Title: Ubuntu patch incorrect disable the thunderbolt and security panels Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Mantic: In Progress Bug description: * Impact After an upstream reorganisation the patch to disable the microcophone/camera panels incorrectly disable also the rest of the device section, including thunderbolt and security which should be displayed * Testcase $ gnome-control-center privacy The right page should have a devices section listing thunderbolt (if the corresponding hardware is available) and security * Regression potential The change is a simple tweak to the .ui of the privacy panel, any bug would show in that panel. Also the thunderbolt and security panel haven't got recent testing due to this issue so they could be buggy (but it wouldn't be a regression over having the functionality not available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2038907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Hi Georgia, is this still pending an evince fix? Your PPA has an updated evince package, but I don't think it was uploaded to unapproved yet, without the recommends. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
The jammy build of 1:0.9.6.2~0.22.04.6 is still failing[1] in arm64
after a retry:
FAIL: test_system_driver_packages_force_install_nvidia
(test_ubuntu_drivers.DetectTest)
system_driver_packages() force install config points to an older version.
--
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/mock.py", line 1379, in patched
return func(*newargs, **newkeywargs)
File "/<>/tests/test_ubuntu_drivers.py", line 1495, in
test_system_driver_packages_force_install_nvidia
self.assertEqual(set(packages), set(['nvidia-driver-470']))
AssertionError: Items in the first set but not the second:
'nvidia-driver-510'
Items in the second set but not the first:
'nvidia-driver-470'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common
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 Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.6.2~0.22.04.6 in jammy-proposed has no closing bug, and the
changes file should include version 22.04.5 too I believe. There is also
a build failure for arm64 (due to a build-time test failing). I will
retrigger it, but I'm thinking we need a new upload to fix the changes
file at least, and perhaps the build failure if it persists.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Committed
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037274] Re: [SRU] libreoffice 7.5.7 for lunar
For the next SRUs, if you have to add a patch or make other changes to something under debian/, please document it so that the SRU review can be quicker. In this particular case here, there is a patch being added that has no DEP3 header, no upstream bug, no origin, etc, which makes the review take more time. For the record, Rico pasted this information to me on irc, about this patch: ahasenack, the commit itself points to the troublesome bug report and the mailing list discussion of this aarch64 regression, as seen at https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/lunar-7.5 Related: https://git.libreoffice.org/core/+/e2397a57ca66a06950a669a3971fbc55b8f5f979%5E%21 ** Changed in: libreoffice (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2037274 Title: [SRU] libreoffice 7.5.7 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.7 is in its seventh bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.7_release * Version 7.5.6 is currently released in lunar. For a list of fixed bugs compared to 7.5.6 see the list of bugs fixed in the release candidates of 7.5.7 (that's a total of 14 bugs): https://wiki.documentfoundation.org/Releases/7.5.7/RC1#List_of_fixed_bugs 7.5.7 RC1 is identical to the 7.5.7 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1697/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15171690/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20230925_122613_dc43d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20230925_154920_2e924@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20230926_164913_a0855@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20230925_123824_567d4@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20230925_131148_33d08@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 14 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037274] Please test proposed package
Hello Rico, or anyone else affected, Accepted libreoffice into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.7-0ubuntu0.23.04.1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2037274 Title: [SRU] libreoffice 7.5.7 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.7 is in its seventh bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.7_release * Version 7.5.6 is currently released in lunar. For a list of fixed bugs compared to 7.5.6 see the list of bugs fixed in the release candidates of 7.5.7 (that's a total of 14 bugs): https://wiki.documentfoundation.org/Releases/7.5.7/RC1#List_of_fixed_bugs 7.5.7 RC1 is identical to the 7.5.7 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1697/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15171690/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20230925_122613_dc43d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20230925_154920_2e924@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20230926_164913_a0855@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20230925_123824_567d4@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20230925_131148_33d08@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 14 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 2037581] Re: Missing font when viewing some google docs
** Description changed: In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND - The document is selecting the "Ubuntu" font, that seems to be the - culprit. + The document is using the "Ubuntu" font, that seems to be the culprit. ** Summary changed: - Missing font when viewing some google docs + Missing ubuntu font when viewing some google docs ** Description changed: - In chromium, some documents render with an incorrect font. It looks all - "bold". I can provide a link in PVT if needed, but see attached - screenshots for chrome, and chromium. + chromium snap + chromium 118.0.5993.11 2645 latest/edge canonical✓ - + + + In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. ** Description changed: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - - - In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. + In chromium, some google doc documents render with an incorrect font. It + looks all "bold". I can provide a link in PVT if needed, but see + attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037581] Re: Missing font when viewing some google docs
** Attachment added: "chrome.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+attachment/5704999/+files/chrome.png ** Tags added: snap ** Description changed: In chromium, some documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND + + The document is selecting the "Ubuntu" font, that seems to be the + culprit. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037581] [NEW] Missing ubuntu font when viewing some google docs
Public bug reported: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Attachment added: "chromium.png" https://bugs.launchpad.net/bugs/2037581/+attachment/5704998/+files/chromium.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2037581 Title: Missing ubuntu font when viewing some google docs Status in chromium-browser package in Ubuntu: New Bug description: chromium snap chromium 118.0.5993.11 2645 latest/edge canonical✓ - In chromium, some google doc documents render with an incorrect font. It looks all "bold". I can provide a link in PVT if needed, but see attached screenshots for chrome, and chromium. The chromium console log also shows a lot of these 404 errors for *.woff2 fonts: GET filesystem:https://docs.google.com/persistent/docs/fonts/KFO8CneDtsqEr0keqCMhbCc_Mn33tY0.woff2 net::ERR_FILE_NOT_FOUND The document is using the "Ubuntu" font, that seems to be the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Chromium played a local video just fine, and that video was recognized like this by mpv: (+) Video --vid=1 (*) (h264 1920x1080 60.000fps) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : de
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
I used that snap in a few long calls already, and did not experience the Pxms leak. Closing the browser after such calls also did not leave xorg at 100% cpu like before. Haven't checked x264 playback yet, but as Daniel said, I doubt it would regress because of this patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ub
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Please ping here when a new chromium snap is available in latest/edge. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.ne
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
Upstream bug got an update: https://bugs.chromium.org/p/chromium/issues/detail?id=1467689#c41 Patch? https://chromium.googlesource.com/chromium/src/+/42d57d016f5fb6d2a1a354743b9be911c1be87e8%5E%21/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list
[Desktop-packages] [Bug 2033643] Update Released
The verification of the Stable Release Update for libreoffice 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 Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033643 Title: [SRU] libreoffice 7.5.6 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Released Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 53 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033643] Re: [SRU] libreoffice 7.5.6 for lunar
ACK on releasing this one day early. Given the test results, I don't see a benefit from another day of aging, which, given the Friday rule, would actually push this release to next monday. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033643 Title: [SRU] libreoffice 7.5.6 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Released Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 (that's a total of 53 bugs): https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs 7.5.6 RC2 is identical to the 7.5.6 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 53 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
This bug is easy to reproduce, what we need now is a fix ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video Status in chromium-browser package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Opinion Bug description: https://crbug.com/1467689 --- chromium 118.0.5966.0 2604 latest/edge Whenever I use chromium in a video session (meet, youtube) that used hardware acceleration, for a long time (like 20min or more), and then close it, the whole desktop freezes, and the laptop fan turns on. Logging in remotely I see that Xorg is at 100% CPU. The rest of the system is operational, but nothing graphical is. Just the mouse cursor moves around. SOMETIMES, if I wait a few minutes, Xorg resumes behaving normally, and I can use the desktop again, but most of the time I have to login remotely and kill -9 xorg (plain kill won't do it). With wayland, this does not happen. This could very well be an Xorg bug, but filing here first for visibility. $ lsgpu card0Intel Alderlake_p (Gen12) drm:/dev/dri/card0 └─renderD128 $ lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Vendor ID: GenuineIntel Model name:12th Gen Intel(R) Core(TM) i7-1270P CPU family: 6 Model: 154 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 1 Stepping:3 CPU(s) scaling MHz: 41% CPU max MHz: 4800, CPU min MHz: 400, BogoMIPS:4992,00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdp e1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqd q dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 448 KiB (12 instances) L1i: 640 KiB (12 instances) L2:9 MiB (6 instances) L3:18 MiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-15 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence Srbds: Not affected Tsx async abort: Not affected ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 16:47:30 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-pack
