[Desktop-packages] [Bug 1991724] Re: system monitor fails with Nvideo multi-monitor
** No longer affects: gnome-shell (Ubuntu) -- 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/1991724 Title: system monitor fails with Nvideo multi-monitor Status in mutter package in Ubuntu: New Bug description: I have four monitors attached to my Nvideo card, and when I try to run the system monitor it does not come up. The icon in the left panel shows that one instance is running, but there is no way to bring up the actual window (a picture of the activated window appears in the icon's "All Windows" section, but it is only a picture). If I unplug all monitors except my main monitor, system monitor works without problems, showing that the problem is caused by some incompatibility between Nvideo multi-monitor support and Ubuntu desktop support. I'm using Ubuntu 22.04.1 LTS, with whatever version of System Monitor and Xorg comes with this. Video card is GeForce RTX 2080 SUPER, installed in Lenovo workstation running Windows 11. What I expected to happen is the System Manager window is displayed. What happened instead is only the icon is displayed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:36:49 2022 DistUpgraded: 2022-09-03 17:37:53,959 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-47-generic, x86_64: installed nvidia/470.141.03, 5.15.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 SUPER] [1462:c72c] InstallationDate: Installed on 2021-02-27 (584 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 90Q8000HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76867cf7-9235-4502-89e5-2731189d3e21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-03 (31 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: O4LKT1CA dmi.board.name: 3715 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305329971172 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4LKT1CA:bd08/11/2021:br1.28:efr1.13:svnLENOVO:pn90Q8000HUS:pvrLegionT734IMZ5:rvnLENOVO:rn3715:rvrSDK0T08861WIN3305329971172:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_90Q8_BU_Lenovo_FM_LegionT734IMZ5: dmi.product.family: Legion T7 34IMZ5 dmi.product.name: 90Q8000HUS dmi.product.sku: LENOVO_MT_90Q8_BU_Lenovo_FM_Legion T7 34IMZ5 dmi.product.version: Legion T7 34IMZ5 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1991724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1991678] Re: X seems to lag at random intervals
Thanks for the bug report. Most of "lag" issues were fixed in Ubuntu 22.04 so please try that as soon as you can: https://ubuntu.com/download/desktop ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991678 Title: X seems to lag at random intervals Status in Ubuntu: Incomplete Bug description: Hey, I trust you are well. I just noticed odd behaviour probably related to video resources which causes the entire GUI to lag for typing or to transition between screens and apps especially if there's a notification or any other new graphical interaction. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 11:30:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2022-06-09 (116 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0YRH3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/24/2022:br1.19:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0YRH3X:rvrA00:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1991678/+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 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click
I'm not totally sure that's a fix, but let's assume it is. ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-gtk-3.24.35 fixed-upstream ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/602 Importance: Unknown Status: Unknown ** No longer affects: mutter -- 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/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click Status in GTK+: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1991724] Re: system monitor fails with Nvideo multi-monitor
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991724 Title: system monitor fails with Nvideo multi-monitor Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have four monitors attached to my Nvideo card, and when I try to run the system monitor it does not come up. The icon in the left panel shows that one instance is running, but there is no way to bring up the actual window (a picture of the activated window appears in the icon's "All Windows" section, but it is only a picture). If I unplug all monitors except my main monitor, system monitor works without problems, showing that the problem is caused by some incompatibility between Nvideo multi-monitor support and Ubuntu desktop support. I'm using Ubuntu 22.04.1 LTS, with whatever version of System Monitor and Xorg comes with this. Video card is GeForce RTX 2080 SUPER, installed in Lenovo workstation running Windows 11. What I expected to happen is the System Manager window is displayed. What happened instead is only the icon is displayed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:36:49 2022 DistUpgraded: 2022-09-03 17:37:53,959 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-47-generic, x86_64: installed nvidia/470.141.03, 5.15.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 SUPER] [1462:c72c] InstallationDate: Installed on 2021-02-27 (584 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 90Q8000HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76867cf7-9235-4502-89e5-2731189d3e21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-03 (31 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: O4LKT1CA dmi.board.name: 3715 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305329971172 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4LKT1CA:bd08/11/2021:br1.28:efr1.13:svnLENOVO:pn90Q8000HUS:pvrLegionT734IMZ5:rvnLENOVO:rn3715:rvrSDK0T08861WIN3305329971172:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_90Q8_BU_Lenovo_FM_LegionT734IMZ5: dmi.product.family: Legion T7 34IMZ5 dmi.product.name: 90Q8000HUS dmi.product.sku: LENOVO_MT_90Q8_BU_Lenovo_FM_Legion T7 34IMZ5 dmi.product.version: Legion T7 34IMZ5 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1991724] Re: system monitor fails with Nvideo multi-monitor
Forgot to mention, this is not specific to System Monitor. I observed the same problem (windows not displayed) when running another application. But most applications work without this glitch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991724 Title: system monitor fails with Nvideo multi-monitor Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have four monitors attached to my Nvideo card, and when I try to run the system monitor it does not come up. The icon in the left panel shows that one instance is running, but there is no way to bring up the actual window (a picture of the activated window appears in the icon's "All Windows" section, but it is only a picture). If I unplug all monitors except my main monitor, system monitor works without problems, showing that the problem is caused by some incompatibility between Nvideo multi-monitor support and Ubuntu desktop support. I'm using Ubuntu 22.04.1 LTS, with whatever version of System Monitor and Xorg comes with this. Video card is GeForce RTX 2080 SUPER, installed in Lenovo workstation running Windows 11. What I expected to happen is the System Manager window is displayed. What happened instead is only the icon is displayed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:36:49 2022 DistUpgraded: 2022-09-03 17:37:53,959 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-47-generic, x86_64: installed nvidia/470.141.03, 5.15.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 SUPER] [1462:c72c] InstallationDate: Installed on 2021-02-27 (584 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 90Q8000HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76867cf7-9235-4502-89e5-2731189d3e21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-03 (31 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: O4LKT1CA dmi.board.name: 3715 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305329971172 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4LKT1CA:bd08/11/2021:br1.28:efr1.13:svnLENOVO:pn90Q8000HUS:pvrLegionT734IMZ5:rvnLENOVO:rn3715:rvrSDK0T08861WIN3305329971172:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_90Q8_BU_Lenovo_FM_LegionT734IMZ5: dmi.product.family: Legion T7 34IMZ5 dmi.product.name: 90Q8000HUS dmi.product.sku: LENOVO_MT_90Q8_BU_Lenovo_FM_Legion T7 34IMZ5 dmi.product.version: Legion T7 34IMZ5 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1991724] [NEW] system monitor fails with Nvideo multi-monitor
Public bug reported: I have four monitors attached to my Nvideo card, and when I try to run the system monitor it does not come up. The icon in the left panel shows that one instance is running, but there is no way to bring up the actual window (a picture of the activated window appears in the icon's "All Windows" section, but it is only a picture). If I unplug all monitors except my main monitor, system monitor works without problems, showing that the problem is caused by some incompatibility between Nvideo multi-monitor support and Ubuntu desktop support. I'm using Ubuntu 22.04.1 LTS, with whatever version of System Monitor and Xorg comes with this. Video card is GeForce RTX 2080 SUPER, installed in Lenovo workstation running Windows 11. What I expected to happen is the System Manager window is displayed. What happened instead is only the icon is displayed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:36:49 2022 DistUpgraded: 2022-09-03 17:37:53,959 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-47-generic, x86_64: installed nvidia/470.141.03, 5.15.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] [10de:1e81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2080 SUPER] [1462:c72c] InstallationDate: Installed on 2021-02-27 (584 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 90Q8000HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=76867cf7-9235-4502-89e5-2731189d3e21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-09-03 (31 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: O4LKT1CA dmi.board.name: 3715 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305329971172 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4LKT1CA:bd08/11/2021:br1.28:efr1.13:svnLENOVO:pn90Q8000HUS:pvrLegionT734IMZ5:rvnLENOVO:rn3715:rvrSDK0T08861WIN3305329971172:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_90Q8_BU_Lenovo_FM_LegionT734IMZ5: dmi.product.family: Legion T7 34IMZ5 dmi.product.name: 90Q8000HUS dmi.product.sku: LENOVO_MT_90Q8_BU_Lenovo_FM_Legion T7 34IMZ5 dmi.product.version: Legion T7 34IMZ5 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991724 Title: system monitor fails with Nvideo multi-monitor Status in xorg package in Ubuntu: New Bug description: I have four monitors attached to my Nvideo card, and when I try to run the system monitor it does not come up. The icon in the left panel shows that one instance is running, but there is no way to bring up the actual window (a picture of the activated window appears in the icon's "All Windows" section, but it is only a picture). If I unplug all
[Desktop-packages] [Bug 1980781] Re: SRU of ubuntu-advantage-desktop-daemon to older series
This bug was fixed in the package ubuntu-advantage-desktop-daemon -
1.10~18.04.1
---
ubuntu-advantage-desktop-daemon (1.10~18.04.1) bionic; urgency=medium
* Backport the ubuntu-advantage-desktop-daemon service to 18.04
(lp: #1980781)
-- Sebastien Bacher Tue, 20 Sep 2022 18:27:07
+0200
** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-advantage-desktop-daemon in
Ubuntu.
https://bugs.launchpad.net/bugs/1980781
Title:
SRU of ubuntu-advantage-desktop-daemon to older series
Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Xenial:
Fix Committed
Status in ubuntu-advantage-desktop-daemon source package in Bionic:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Focal:
Fix Released
Bug description:
[Impact]
ubuntu-advantage-desktop-daemon is a service we added in 22.04 to let
desktop application interact easily with Ubuntu Advantage
adsys makes use of is to check if the system is connected to UA. This is
supported in 20.04 LTS but until now the daemon was not available there.
Installing the daemon enables advanced usages (scripts, privilege
delegation…) which require an Ubuntu Pro account
Ubuntu Pro integration is being added to software-properties which
also require the service to be available.
[Test Plan]
A. Verify the service
1. Install:
$ sudo apt install ubuntu-advantage-desktop-daemon
2. Check able to access daemon
$ gdbus call --system --dest com.canonical.UbuntuAdvantage --object-path
/com/canonical/UbuntuAdvantage/Manager --method
org.freedesktop.DBus.Properties.GetAll 'com.canonical.UbuntuAdvantage.Manager'
({'Attached': , 'DaemonVersion': <'1.8'>},)
B. Software-properties
Verify that the new 'Ubuntu Pro' page is working as expected, SRU bug
#, especially that it reflects the correct status and that
attaching/detaching a token and enabling/disabling services is working
C. Adsys (focal)
1. Ensure that you have an Ubuntu Advantage subcription enabled.
2. Setup some scripts under AD to be executed, one for machine scripts (on
startup), one for user scripts (on login). Those scripts can create some
temporary files under /tmp for instance.
3. Reboot and login on the Ubuntu laptop connected with AD by adsys.
4. Check that the scripts were executed by testing that the created file
under /tmp are present.
[Where problems could occur]
This is a code that has not previously been used on 20.04 and thus
could trigger new bugs. It has been used for since jammy though
without major issues.
A. The service itself
The service shouldn't be active unless it's needed. If you don't have ubuntu
advantage nor adsys configured check that the service is not loaded.
The service should low on resource usage, check that it's the case by
checking the RAM and CPU consumption.
B. Software-properties
The Ubuntu Pro tab didn't exist before so there should be no
regression possible there due to the service. The livepatch enablement
is handled through the service as part of UA now so check that
livepatch is correctly working still on upgraded systems
C. Adsys (focal)
The behaviour change in adsys should be limited to enabling features
which weren't available in focal before but we should ensure those are
correctly working and not providing a buggy user experience
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1980781/+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 1991526] Re: Laptop panel freezes on return from screensaver with external monitor attached
** Summary changed: - Panel freezes on return from screensaver with external monitor attached + Laptop panel freezes on return from screensaver with external monitor attached ** Changed in: ubuntu Status: Incomplete => New ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1991526 Title: Laptop panel freezes on return from screensaver with external monitor attached Status in gnome-shell package in Ubuntu: New Bug description: My setup is composed of a Dell XPS13 9320, with one (or two) external USB-C monitors attached. The laptop panel is the primary screen. I'm using gnome on Wayland. Everything is working fine, except when resuming from screensaver: the prompt for password is shown on the laptop panel, and I start typing the password. At this point, the laptop panel freezes. This can happen almost immediately (I will see for example two or three dots as I typed the first characters of my password) or this can happen a few seconds later (meanwhile the screen has been unlocked, the panel shows the desktop, then it freezes). Interestingly, the external monitors are woken up, desktop is unlocked, and will continue working, while the laptop panel is frozen. After that, let's say 40% of the time, the panel will un-freeze itself after 30 seconds or so. 40% of the time it will remain frozen, and 20% of the time the whole display will freeze (including the external monitors). When it happens, I can recover by either un-plugging / re-plugging one of the external monitors, or by typing Ctrl-Alt-F1, then retyping my password, then everything is fine again... until the next screen lock. This bug is reproducible more or less 50% of the time (one in two screen locks causes freezes). Deactivating the dash-to-panel gnome extension made it less reproducible, but it still happens. I didn't see any interesting error message in the logs, but maybe I didn't look at the correct place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 13:54:42 2022 ExecutablePath: /usr/libexec/gdm-wayland-session InstallationDate: Installed on 2022-07-20 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fr_FR.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991526/+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 1991526] [NEW] Laptop panel freezes on return from screensaver with external monitor attached
You have been subscribed to a public bug: My setup is composed of a Dell XPS13 9320, with one (or two) external USB-C monitors attached. The laptop panel is the primary screen. I'm using gnome on Wayland. Everything is working fine, except when resuming from screensaver: the prompt for password is shown on the laptop panel, and I start typing the password. At this point, the laptop panel freezes. This can happen almost immediately (I will see for example two or three dots as I typed the first characters of my password) or this can happen a few seconds later (meanwhile the screen has been unlocked, the panel shows the desktop, then it freezes). Interestingly, the external monitors are woken up, desktop is unlocked, and will continue working, while the laptop panel is frozen. After that, let's say 40% of the time, the panel will un-freeze itself after 30 seconds or so. 40% of the time it will remain frozen, and 20% of the time the whole display will freeze (including the external monitors). When it happens, I can recover by either un-plugging / re-plugging one of the external monitors, or by typing Ctrl-Alt-F1, then retyping my password, then everything is fine again... until the next screen lock. This bug is reproducible more or less 50% of the time (one in two screen locks causes freezes). Deactivating the dash-to-panel gnome extension made it less reproducible, but it still happens. I didn't see any interesting error message in the logs, but maybe I didn't look at the correct place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 13:54:42 2022 ExecutablePath: /usr/libexec/gdm-wayland-session InstallationDate: Installed on 2022-07-20 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fr_FR.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy multimonitor wayland-session -- Laptop panel freezes on return from screensaver with external monitor attached https://bugs.launchpad.net/bugs/1991526 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"
While others are commenting on this, it's worth noting that during this freeze issue on the lockscreen the computer may still be responsive to keyboard input when a correct password + enter was inputted. For example, if I have an application (e.g. calendar reminder notifications, or a browser + url bar active), I'll notice the related responses to my keystrokes during the freeze (calendar - sounds for most keystrokes, browser url - keystroke presses observed after freeze/unlock) if I enter the correct password. -- 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/1975884 Title: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added" Status in gnome-shell package in Ubuntu: Confirmed Bug description: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've also seen it happen when having touch / gesture input switch between displaying the user name and the password field - where the screen can get stuck in the animation in an interstitial state for a number of seconds. I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. What I may eventually try: - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+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 1991709] Re: gnome-shell memory leak
Moving to private to avoid "me too" comments from other users. Everyone should log their own separate bugs. ** Information type changed from Public to Private ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1991709 Title: gnome-shell memory leak Status in gnome-shell package in Ubuntu: Incomplete Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991709/+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 1991709] Re: gnome-shell memory leak
It appears you also have extension 'removeappm...@dragon8oy.com' enabled. Please start by deleting all local extensions: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again and tell us if the leak still happens. If you find the leak is still happening then please run: ps auxw | grep gnome-shell > psout.txt and attach the resulting text file here. Please also note there is still a major leak in 22.04 known to be caused by screenshots: bug 1973638 ** Tags added: gnome-shell-leak -- 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/1991709 Title: gnome-shell memory leak Status in gnome-shell package in Ubuntu: Incomplete Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991709/+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 1970031] Re: Grey (gray) appears as pink in Ubuntu 22.04
That issue was being tracked in bug 1943558 too... I don't think any patching is necessary here. The very low rate of reports of this issue, and the simplicity of the workaround, indicate that we don't need to prioritise this bug. ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1970031 Title: Grey (gray) appears as pink in Ubuntu 22.04 Status in GNOME Settings Daemon: New Status in GNOME Shell: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Grey (gray) appears as pink in Ubuntu 22.04 WORKAROUND: Settings > Colour > YOUR MONITOR = OFF ORIGINAL DESCRIPTION: i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my monitor started showing a gray-pink color. I can't take a screenshot because it will just be gray on your monitor (i checked the screenshot in windows 11). Did the developers break something in the video card driver or why did it happen? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Apr 23 19:54:00 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1970031/+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 1973748] Re: Updating any gsettings key makes user dconf database unreadable
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1973751] Re: Machines or Users scripts are not executed
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982330] Re: Cannot apply policies from uppercase class path like "MACHINE"
This bug was fixed in the package adsys - 0.9.2~22.04
---
adsys (0.9.2~22.04) jammy; urgency=medium
* Backport to jammy
adsys (0.9.2) kinetic; urgency=medium
* Update generators to fix FTBFS
- shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's
filesystem hijacking and cause unexpected behavior
* Update dependencies to latest:
- github.com/golangci/golangci-lint
- google.golang.org/protobuf
adsys (0.9.1) kinetic; urgency=medium
[ Didier Roche ]
[ Gabriel Nagy ]
* Fix loading policy content from uppercase folders (LP: #1982330)
* Add GSettings power management keys (LP: #1982349)
* Allow parsing policy entries with empty values (LP: #1982342)
* Allow parsing policies with unsupported types (LP: #1982343)
* Allow parsing policy entries with no data (LP: #1982345)
* Lowercase target name when normalizing (LP: #1982347)
* Annotate policies that require Ubuntu Pro (LP: #1982348)
* Update dependencies to latest:
- github.com/spf13/cobra
- github.com/spf13/viper
- github.com/stretchr/testify
- github.com/charmbracelet/bubbletea
- github.com/charmbracelet/bubbles
- google.golang.org/grpc
- github.com/golangci/golangci-lint
- github.com/sirupsen/logrus
adsys (0.9.0) kinetic; urgency=medium
[ Jean-Baptiste Lallement ]
[ Didier Roche ]
[ Gabriel Nagy ]
* Add Active Directory Watch Daemon - adwatchd: (LP: #1982351)
- Implement a Windows daemon that watches a list of configured directories
for changes and bumps the relevant GPT.INI files.
- Add adsys-windows binary package which includes the Windows daemon
executable and the admx/adml policies.
* Config detection now includes current executable directory
* Fixes in generator build race
* Update dependencies to latest:
- github.com/spf13/cobra
- github.com/stretchr/testify
* CI updates:
- switch to Go setup v3
- bump to really build with Golang 1.18
adsys (0.8.6) kinetic; urgency=medium
* Fix new build failures on 32 bits due to libsmbclient-dev no longer sets
the large file support cflags in libsmbclient.h.
Update to latest libsmbclient-go.
* Update dependencies to latest:
- google.golang.org/grpc
- gopkg.in/ini.v1
- github.com/golangci/golangci-lint
- github.com/spf13/viper
- github.com/stretchr/testify
-- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200
--
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/1982330
Title:
Cannot apply policies from uppercase class path like "MACHINE"
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
Fix Released
Status in adsys source package in Jammy:
Fix Released
Bug description:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g.
Machine), but they are uppercase (e.g. MACHINE). This prevents any
GPOs from being applied.
This is a common occurence with GPOs created by Microsoft, like the
Default Domain Policy.
[Test Plan]
Reproduction:
* Mark the Default Domain Policy as active for the client, and set some
Ubuntu policy entries.
* Restart and/or manually sync the client machine.
* Observe the log message indicating that parsing the GPO failed:
Policy "Default Domain Policy" doesn't have any policy for class
"user" open
/var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol:
no such file or directory
* Observe that the Ubuntu policies were not applied.
To confirm the bug is fixed, repeat the steps above after applying the
fix, and the policies should be applied.
[Where problems could occur]
* Fixing this bug will allow adsys to parse, and possibly fail when
applying policies from an uppercase path, whereas before it silently
ignored them. Fixes for these potential bugs have also been submitted.
[Other Info]
The issue was initially reported on GitHub:
https://github.com/ubuntu/adsys/issues/346
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982330/+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 1973752] Re: Fix privilege permission which can not be set to disabled
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982342] Re: Cannot parse policies with empty values
This bug was fixed in the package adsys - 0.9.2~22.04 --- adsys (0.9.2~22.04) jammy; urgency=medium * Backport to jammy adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify -- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200 -- 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/1982342 Title: Cannot parse policies with empty values Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Released Status in adsys source package in Jammy: Fix Released Bug description: [Impact] In addition to empty data, some Microsoft policy entries happen to have empty values as well. See the following entry: // [key;value;type;size;data] : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. This fails hard when parsing, returning an `empty value` error, rendering the remaining policies unparsable. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not support policy entries with empty values, we must still be able to parse them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982342/+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 1982330] Re: Cannot apply policies from uppercase class path like "MACHINE"
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982342] Re: Cannot parse policies with empty values
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1961458] Re: chown of script directory and contents
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982343] Re: Cannot parse policy entries with unsupported types
This bug was fixed in the package adsys - 0.9.2~22.04 --- adsys (0.9.2~22.04) jammy; urgency=medium * Backport to jammy adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify -- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200 -- 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/1982343 Title: Cannot parse policy entries with unsupported types Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Released Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Policies with unsupported types are currently unable to be parsed. Even if Ubuntu doesn't support these types we should still be able to parse the Microsoft ones - otherwise we are unable to apply any of the GPOs. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu supports a limited subset of types, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982343/+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 1982343] Re: Cannot parse policy entries with unsupported types
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982345] Re: Cannot parse policy entries with no data
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982345] Re: Cannot parse policy entries with no data
This bug was fixed in the package adsys - 0.9.2~22.04 --- adsys (0.9.2~22.04) jammy; urgency=medium * Backport to jammy adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify -- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200 -- 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/1982345 Title: Cannot parse policy entries with no data Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Released Status in adsys source package in Jammy: Fix Released Bug description: [Impact] The Default Domain Policy for Computers has a bunch of SystemCertificates keys with no data which adsys fails to parse. Here are some examples: Software\Policies\Microsoft\SystemCertificates\ACRS\Certificates Software\Policies\Microsoft\SystemCertificates\ACRS\CRLs Software\Policies\Microsoft\SystemCertificates\ACRS\CTLs Software\Policies\Microsoft\SystemCertificates\CA\Certificates Software\Policies\Microsoft\SystemCertificates\CA\CRLs Software\Policies\Microsoft\SystemCertificates\CA\CTLs Software\Policies\Microsoft\SystemCertificates\Disallowed\Certificates Software\Policies\Microsoft\SystemCertificates\Disallowed\CRLs Software\Policies\Microsoft\SystemCertificates\Disallowed\CTLs Software\Policies\Microsoft\SystemCertificates\DPNGRA\Certificates When examined with a hex editor, these look like the following: : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. The last field of the [key;value;type;size;data] stanza is entirely empty (semicolon succeeded immediately by a closing brace) whereas we expect a null character. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not have policy entries with no data, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy for Computers on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before
[Desktop-packages] [Bug 1982347] Re: Username is case sensitive when applying policies on login
This bug was fixed in the package adsys - 0.9.2~22.04 --- adsys (0.9.2~22.04) jammy; urgency=medium * Backport to jammy adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify -- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200 -- 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/1982347 Title: Username is case sensitive when applying policies on login Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Released Status in adsys source package in Jammy: Fix Released Bug description: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] Reproduction: * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases * Observe multiple files created at /var/cache/adsys/policies With the fix applied, remove *all* cached policies at /var/cache/adsys/policies and attempt to login with different case combinations of the AD account, e.g.: administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz As root, check the contents of /var/cache/adsys/policies - you should only see a lowercase entry: administra...@warthogs.biz [Where problems could occur] Target name normalization is exercised by the code that dumps policies applied for a given user, and by the code that updates or creates a policy for a given user. If this happens to cause a bug, it will render the core part of adsys unusable. We believe this is highly unlikely given that in some cases, adsys already used the lowercase
[Desktop-packages] [Bug 1961459] Re: adsys pam issues
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1962510] Re: failing tests with new sssd, blocks python3-defaults
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1973745] Re: adsys windows admx/adml lts only does not include 22.04
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982351] Re: [SRU] Backport adsys-windows binary package
This bug was fixed in the package adsys - 0.9.2~22.04 --- adsys (0.9.2~22.04) jammy; urgency=medium * Backport to jammy adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify -- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200 -- 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/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Released Status in adsys source package in Jammy: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+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 1982347] Re: Username is case sensitive when applying policies on login
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982348] Re: Describe if a key requires an Ubuntu Pro subscription
This bug was fixed in the package adsys - 0.9.2~22.04 --- adsys (0.9.2~22.04) jammy; urgency=medium * Backport to jammy adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify -- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200 -- 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/1982348 Title: Describe if a key requires an Ubuntu Pro subscription Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Released Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Before applying policies, adsys checks for the existence of an Ubuntu Pro subscription. If not found, all keys with the exception of dconf keys are filtered, as they require Ubuntu Pro. Annotate the generated ADMX/ADML files with this information. [Test Plan] * Open the Group Policy Management Editor * Navigate to User Configuration > Administrative Templates > Ubuntu > Session Management > User Scripts > Logoff scripts * The description should contain the following line: An Ubuntu Pro subscription on the client is required to apply this policy. [Where problems could occur] This is a purely visual change that only impacts generated XML files. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982348/+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 1982351] Re: [SRU] Backport adsys-windows binary package
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982348] Re: Describe if a key requires an Ubuntu Pro subscription
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1982349] Re: Manage energy profile settings
This bug was fixed in the package adsys - 0.9.2~22.04
---
adsys (0.9.2~22.04) jammy; urgency=medium
* Backport to jammy
adsys (0.9.2) kinetic; urgency=medium
* Update generators to fix FTBFS
- shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's
filesystem hijacking and cause unexpected behavior
* Update dependencies to latest:
- github.com/golangci/golangci-lint
- google.golang.org/protobuf
adsys (0.9.1) kinetic; urgency=medium
[ Didier Roche ]
[ Gabriel Nagy ]
* Fix loading policy content from uppercase folders (LP: #1982330)
* Add GSettings power management keys (LP: #1982349)
* Allow parsing policy entries with empty values (LP: #1982342)
* Allow parsing policies with unsupported types (LP: #1982343)
* Allow parsing policy entries with no data (LP: #1982345)
* Lowercase target name when normalizing (LP: #1982347)
* Annotate policies that require Ubuntu Pro (LP: #1982348)
* Update dependencies to latest:
- github.com/spf13/cobra
- github.com/spf13/viper
- github.com/stretchr/testify
- github.com/charmbracelet/bubbletea
- github.com/charmbracelet/bubbles
- google.golang.org/grpc
- github.com/golangci/golangci-lint
- github.com/sirupsen/logrus
adsys (0.9.0) kinetic; urgency=medium
[ Jean-Baptiste Lallement ]
[ Didier Roche ]
[ Gabriel Nagy ]
* Add Active Directory Watch Daemon - adwatchd: (LP: #1982351)
- Implement a Windows daemon that watches a list of configured directories
for changes and bumps the relevant GPT.INI files.
- Add adsys-windows binary package which includes the Windows daemon
executable and the admx/adml policies.
* Config detection now includes current executable directory
* Fixes in generator build race
* Update dependencies to latest:
- github.com/spf13/cobra
- github.com/stretchr/testify
* CI updates:
- switch to Go setup v3
- bump to really build with Golang 1.18
adsys (0.8.6) kinetic; urgency=medium
* Fix new build failures on 32 bits due to libsmbclient-dev no longer sets
the large file support cflags in libsmbclient.h.
Update to latest libsmbclient-go.
* Update dependencies to latest:
- google.golang.org/grpc
- gopkg.in/ini.v1
- github.com/golangci/golangci-lint
- github.com/spf13/viper
- github.com/stretchr/testify
-- Didier Roche Thu, 04 Aug 2022 11:23:01 +0200
--
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/1982349
Title:
Manage energy profile settings
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
Fix Released
Status in adsys source package in Jammy:
Fix Released
Bug description:
[Impact]
Adsys cannot currently manage GSettings power management keys, such
as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
* Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
* Double click on the last entry: Whether to hibernate ...
* Enable it, set the value to "hibernate"
* On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
* Observe the logs that indicate the parsing of the dconf key:
DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
* Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
This code is located in the dconf policy application manager and
restricted to it. The negative impact in case of a new bug will be
seen by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1982349] Re: Manage energy profile settings
This bug was fixed in the package adsys - 0.9.2~20.04 --- adsys (0.9.2~20.04) focal; urgency=medium * Backport to focal - Build with Go 1.16 - Move debhelper compat to 12 - Do not recommends ubuntu-advantage-desktop-daemon as it’s not available on focal yet. adsys (0.9.2) kinetic; urgency=medium * Update generators to fix FTBFS - shell out to mkdir instead of go's os.Mkdir which can bypass fakeroot's filesystem hijacking and cause unexpected behavior * Update dependencies to latest: - github.com/golangci/golangci-lint - google.golang.org/protobuf adsys (0.9.1) kinetic; urgency=medium [ Didier Roche ] [ Gabriel Nagy ] * Fix loading policy content from uppercase folders (LP: #1982330) * Add GSettings power management keys (LP: #1982349) * Allow parsing policy entries with empty values (LP: #1982342) * Allow parsing policies with unsupported types (LP: #1982343) * Allow parsing policy entries with no data (LP: #1982345) * Lowercase target name when normalizing (LP: #1982347) * Annotate policies that require Ubuntu Pro (LP: #1982348) * Update dependencies to latest: - github.com/spf13/cobra - github.com/spf13/viper - github.com/stretchr/testify - github.com/charmbracelet/bubbletea - github.com/charmbracelet/bubbles - google.golang.org/grpc - github.com/golangci/golangci-lint - github.com/sirupsen/logrus adsys (0.9.0) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] [ Gabriel Nagy ] * Add Active Directory Watch Daemon - adwatchd: (LP: #1982351) - Implement a Windows daemon that watches a list of configured directories for changes and bumps the relevant GPT.INI files. - Add adsys-windows binary package which includes the Windows daemon executable and the admx/adml policies. * Config detection now includes current executable directory * Fixes in generator build race * Update dependencies to latest: - github.com/spf13/cobra - github.com/stretchr/testify * CI updates: - switch to Go setup v3 - bump to really build with Golang 1.18 adsys (0.8.6) kinetic; urgency=medium * Fix new build failures on 32 bits due to libsmbclient-dev no longer sets the large file support cflags in libsmbclient.h. Update to latest libsmbclient-go. * Update dependencies to latest: - google.golang.org/grpc - gopkg.in/ini.v1 - github.com/golangci/golangci-lint - github.com/spf13/viper - github.com/stretchr/testify adsys (0.8.5) kinetic; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mechanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). adsys (0.8.4) jammy; urgency=medium * Sync refresh timer with Windows * Some lint fixes due to Go 1.18 * Fix image reference in documentation adsys (0.8.3) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Use ua attached instead of a specific ua feature to gate optional features. * Added and updated documentation for privilege escalation and scripts support. * New linter version trigger fix. * Dependencies update for latest bug fixes: - github.com/golangci/golangci-lint - github.com/spf13/cobra-1.4.0 - github.com/stretchr/testify-1.7.1 - google.golang.org/protobuf-1.28.0 - google.golang.org/grpc-1.45.0 adsys (0.8.2) jammy; urgency=medium * Fix flaky "pick up config changes" tests on armhf and arm64 adsys (0.8.1) jammy; urgency=medium * Change chown logic on script directory and parents to avoid potential vulnerability.
[Desktop-packages] [Bug 1991117] Re: 13.3.0-3build1 fails to build from source
This bug was fixed in the package xserver-xorg-video-vmware -
1:13.3.0-3ubuntu1
---
xserver-xorg-video-vmware (1:13.3.0-3ubuntu1) kinetic; urgency=medium
* d/p/fix-missing-array-notation.patch:
- cherry pick an upstream change to fix the build with the new gcc
(LP: #1991117).
-- Nathan Pratta Teodosio Wed, 28 Sep
2022 10:33:17 -0300
** Changed in: xserver-xorg-video-vmware (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1991117
Title:
13.3.0-3build1 fails to build from source
Status in xserver-xorg-video-vmware package in Ubuntu:
Fix Released
Bug description:
[Log]
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz
[Error]
../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+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 1982330] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1982330
Title:
Cannot apply policies from uppercase class path like "MACHINE"
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
Fix Committed
Status in adsys source package in Jammy:
Fix Committed
Bug description:
[Impact]
ADSys cannot update GPOs on Jammy Jellyfish 22.04 because of misnamed
folders. adsysctl expects the folders to be title cased (e.g.
Machine), but they are uppercase (e.g. MACHINE). This prevents any
GPOs from being applied.
This is a common occurence with GPOs created by Microsoft, like the
Default Domain Policy.
[Test Plan]
Reproduction:
* Mark the Default Domain Policy as active for the client, and set some
Ubuntu policy entries.
* Restart and/or manually sync the client machine.
* Observe the log message indicating that parsing the GPO failed:
Policy "Default Domain Policy" doesn't have any policy for class
"user" open
/var/cache/adsys/sysvol/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/User/Registry.pol:
no such file or directory
* Observe that the Ubuntu policies were not applied.
To confirm the bug is fixed, repeat the steps above after applying the
fix, and the policies should be applied.
[Where problems could occur]
* Fixing this bug will allow adsys to parse, and possibly fail when
applying policies from an uppercase path, whereas before it silently
ignored them. Fixes for these potential bugs have also been submitted.
[Other Info]
The issue was initially reported on GitHub:
https://github.com/ubuntu/adsys/issues/346
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982330/+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 1962170] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Tests are failing with the samba version in jammy. We want people using focal be able to upgrade to newer samba and still be compatible with adsys. [Test Plan] 1. Ensure that DEP8 tests are passing once uploaded to proposed and ready to be migrated [Where problems could occur] The functionalities failing are only on tests running (DEP8 or tests during package builds), but we want to be able to run our tests with newer versions of samba on focal too without regressing existing testsuite. -- The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+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 1961458] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1961458 Title: chown of script directory and contents Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Potential security issues in ApplyPolicy due to race when scripts are enabled. [Test Plan] 1. Attach your machine to Ubuntu Advantage to get script support. 2. Add a script to one GPO for user login/logout 3. Login as an user, starting a new user session (no session should be currently running for that given user). 4. Check the permissions are following what is described from the discussion below. [Where problems could occur] Script support was added recently, and it needs Ubuntu Advantage enablement to be activated. However, to this day, there is still no official ubuntu-advantage-desktop-daemon packaged on focal. ./internal/policies/scripts/scripts.go ApplyPolicy() unsafe owner changes: Changing the scripts directory owner allows any user processes to create symbolic links within, and then they can take ownership of any file on writable mounts. If the files must be owned by the user, the best way is to switch to the user's uid before creating the files. fchown(2) of the file descriptor before closing it should also work. I lose track of what's happening around the "Running machine startup scripts" -- it looks to me like adsys is also *executing* the scripts that were moments ago given to the user to modify. It is not safe for root to run user-owned files. Does the user *have* to own the directory and scripts? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961458/+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 1962510] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962510 Title: failing tests with new sssd, blocks python3-defaults Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Fix some flaky tests to ensure that future SRUs are easier to release [Test Plan] 1. Have the package build (tests are running) and that DEP8 tests are passing. [Where problems could occur] The fix is only impacting some tests that were flaky and asking for a rerun. Fixes are only located in this test code to make them more reliable and less racy, even in VM environments. - adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962510/+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 1961459] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1961459 Title: adsys pam issues Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Bug description: [Impact] Memory leaks in adsys pam modules. [Test Plan] 1. Install SRU version of adsys 2. Login as an user 3. Ensure that you can still login successfully. [Where problems could occur] Login can be disabled due to the PAM module crashing. There is only one code path leading to that, so easy to detect. -- These may not be security issues but it's possible I overlooked something; since they live in a security boundary I thought it worth reporting with a bit of hassle. If you'd rather work on this in the open, feel free to open this. pam_adsys.c update_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to work but I don't think that's how that API is supposed to be used pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961459/+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 1982342] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982342 Title: Cannot parse policies with empty values Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] In addition to empty data, some Microsoft policy entries happen to have empty values as well. See the following entry: // [key;value;type;size;data] : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. This fails hard when parsing, returning an `empty value` error, rendering the remaining policies unparsable. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not support policy entries with empty values, we must still be able to parse them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982342/+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 1982343] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982343 Title: Cannot parse policy entries with unsupported types Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Policies with unsupported types are currently unable to be parsed. Even if Ubuntu doesn't support these types we should still be able to parse the Microsoft ones - otherwise we are unable to apply any of the GPOs. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu supports a limited subset of types, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982343/+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 1982345] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982345 Title: Cannot parse policy entries with no data Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] The Default Domain Policy for Computers has a bunch of SystemCertificates keys with no data which adsys fails to parse. Here are some examples: Software\Policies\Microsoft\SystemCertificates\ACRS\Certificates Software\Policies\Microsoft\SystemCertificates\ACRS\CRLs Software\Policies\Microsoft\SystemCertificates\ACRS\CTLs Software\Policies\Microsoft\SystemCertificates\CA\Certificates Software\Policies\Microsoft\SystemCertificates\CA\CRLs Software\Policies\Microsoft\SystemCertificates\CA\CTLs Software\Policies\Microsoft\SystemCertificates\Disallowed\Certificates Software\Policies\Microsoft\SystemCertificates\Disallowed\CRLs Software\Policies\Microsoft\SystemCertificates\Disallowed\CTLs Software\Policies\Microsoft\SystemCertificates\DPNGRA\Certificates When examined with a hex editor, these look like the following: : 5052 6567 0100 5b00 5300 6f00 6600 PReg[.S.o.f. 0010: 7400 7700 6100 7200 6500 5c00 5000 6f00 t.w.a.r.e.\.P.o. 0020: 6c00 6900 6300 6900 6500 7300 5c00 4d00 l.i.c.i.e.s.\.M. 0030: 6900 6300 7200 6f00 7300 6f00 6600 7400 i.c.r.o.s.o.f.t. 0040: 5c00 5300 7900 7300 7400 6500 6d00 4300 \.S.y.s.t.e.m.C. 0050: 6500 7200 7400 6900 6600 6900 6300 6100 e.r.t.i.f.i.c.a. 0060: 7400 6500 7300 5c00 4100 4300 5200 5300 t.e.s.\.A.C.R.S. 0070: 5c00 4300 6500 7200 7400 6900 6600 6900 \.C.e.r.t.i.f.i. 0080: 6300 6100 7400 6500 7300 3b00 c.a.t.e.s...;... 0090: 3b00 3b00 3b00 5d00 ;.;.;.]. The last field of the [key;value;type;size;data] stanza is entirely empty (semicolon succeeded immediately by a closing brace) whereas we expect a null character. This is a common occurence on Microsoft's policies like the Default Domain Policy. Even if Ubuntu does not have policy entries with no data, we must still be able to parse all of them in case a Group Policy has both Ubuntu and non-Ubuntu entries. [Test Plan] * Attempt to apply the Default Domain Policy for Computers on a client [Where problems could occur] Adsys already excluded non-Ubuntu keys before applying policies, so this change has no impact other than letting all policies be parsed. If an error occurs in parsing an Ubuntu entry, it will be surfaced before policies are applied instead of at parsing time. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/384 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982345/+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 1982351] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982351 Title: [SRU] Backport adsys-windows binary package Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: As part of our entreprise desktop offering, there is the request to backport the adsys-windows binary package to 20.04 LTS and 22.04 LTS. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. adsys-windows contains Windows-specific files including a Windows executable (the Active Directory Watch Daemon), and XML files (ADMX/ADML) that are to be used solely on Windows. The package is provided as a safe way for Windows administrators to source the required adsys files that are needed on Windows. [Impact] * adsys-windows is a new binary package. Impact is thus only for people installing. * This is a enterprise feature requested by desktop customers running LTS. [Test Plan] 1. Install the adsys-windows package 2. Copy the adwatchd.exe executable from /usr/share/adsys/windows on a Windows machine and run it: 3. Set a path where the configuration file will be written 4. Input a list of policy scripts directories to be watched The executable will then install itself as a Windows Service and start monitoring the given directories for changes. Whenever it notices a change it will attempt to bump the version in the GPT.INI file at the root of the watched directory. If a GPT.INI is not found, the daemon will create one. For more information refer to the documentation at: https://github.com/ubuntu/adsys/wiki/11.-Active-Directory-Watch-Daemon [Where problems could occur] * As this is a separate, versioned, new package, no impact on existing installations. * Moreover the package has no files that are used in any way on Linux. It's just data to be copied on Windows machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982351/+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 1982348] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982348 Title: Describe if a key requires an Ubuntu Pro subscription Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] Before applying policies, adsys checks for the existence of an Ubuntu Pro subscription. If not found, all keys with the exception of dconf keys are filtered, as they require Ubuntu Pro. Annotate the generated ADMX/ADML files with this information. [Test Plan] * Open the Group Policy Management Editor * Navigate to User Configuration > Administrative Templates > Ubuntu > Session Management > User Scripts > Logoff scripts * The description should contain the following line: An Ubuntu Pro subscription on the client is required to apply this policy. [Where problems could occur] This is a purely visual change that only impacts generated XML files. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982348/+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 1982349] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1982349
Title:
Manage energy profile settings
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Focal:
Fix Committed
Status in adsys source package in Jammy:
Fix Committed
Bug description:
[Impact]
Adsys cannot currently manage GSettings power management keys, such
as:
/org/gnome/settings-daemon/plugins/power/ambient-enabled
/org/gnome/settings-daemon/plugins/power/idle-brightness
/org/gnome/settings-daemon/plugins/power/idle-dim
/org/gnome/settings-daemon/plugins/power/lid-close-ac-action
/org/gnome/settings-daemon/plugins/power/lid-close-battery-action
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
/org/gnome/settings-daemon/plugins/power/power-button-action
/org/gnome/settings-daemon/plugins/power/power-saver-profile-on-low-battery
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
[Test Plan]
* Open the Group Policy Management Editor for a configured policy
* Navigate to Computer Configuration > Administrative Templates > Ubuntu >
Client management > Power Management
* Double click on the last entry: Whether to hibernate ...
* Enable it, set the value to "hibernate"
* On a client with adsys, while connected on an AD account, run sudo adsysctl
update -m -vv
* Observe the logs that indicate the parsing of the dconf key:
DEBUG Analyzing entry
{Key:org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-type
Value:hibernate Disabled:false Meta:s Strategy: Err:}
* Observe the output of the following command (it should print 'hibernate'):
gsettings get org.gnome.settings-daemon.plugins.power
sleep-inactive-battery-type
[Where problems could occur]
This code is located in the dconf policy application manager and
restricted to it. The negative impact in case of a new bug will be
seen by gsettings key not being applied.
[Other Info]
This issue was initially reported on GitHub at
https://github.com/ubuntu/adsys/issues/135
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982349/+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 1982347] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1982347 Title: Username is case sensitive when applying policies on login Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Bug description: [Impact] When logging in (either via login or ssh) to an AD account using different case combinations, adsysd uses the specified account name instead of the lowercase one reported by getent/whoami to apply the GPOs. I believe this comes from the pam_get_item call here: https://github.com/ubuntu/adsys/blob/e3316e5e37970a07f09fa6df553ddac096c91255/pam/pam_adsys.c#L266 This works but has the unintended side effect of producing multiple dconf profile files for each variant of the username, and caching policies as well: root@ubuntu2204:~# ls /etc/dconf/profile/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz root@ubuntu2204:~# ls /var/cache/adsys/policies/ | grep -i administrator administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz Of course this all stems from the username retrieved by PAM so there might be more unintended side-effects, the dconf one being the easiest to observe. To ensure an unified experience, when a target name is normalized from e.g. DOMAIN\User to User@DOMAIN, it will also be lowercased. [Test Plan] Reproduction: * With adsys set up, log in on the Ubuntu client using an AD account, alternating cases * Observe multiple files created at /var/cache/adsys/policies With the fix applied, remove *all* cached policies at /var/cache/adsys/policies and attempt to login with different case combinations of the AD account, e.g.: administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz administra...@warthogs.biz As root, check the contents of /var/cache/adsys/policies - you should only see a lowercase entry: administra...@warthogs.biz [Where problems could occur] Target name normalization is exercised by the code that dumps policies applied for a given user, and by the code that updates or creates a policy for a given user. If this happens to cause a bug, it will render the core part of adsys unusable. We believe this is highly unlikely given that in some cases, adsys already used the lowercase variant of the username to apply and display policies. [Other Info] This issue was initially reported on GitHub at https://github.com/ubuntu/adsys/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1982347/+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 1988786] Re: system does not boot after full-upgrade on kinetic
I think comment #5 is describing bug 1988488. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1988786 Title: system does not boot after full-upgrade on kinetic Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Hi, After a full upgrade on a kinetic system, the system no longer boots normally. When I power the computer on, I get a prompt to decrypt my disk. I insert the password, and am redirected to a screen saying a fschk is running. It spend hours in that screen with apparently no activity. Pressing ctrl+C does not help at that point. Booting through recovery mode and then requesting to proceed to boot works fine. A regular fschk also suceeds. Here is what I could extract from my journal: Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 'ca.desrt.dconf' Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 comm="/usr/libexec/gsd-sharing" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service... Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 05 16:10:57 castor systemd[1]: Started Hostname Service. Sep 05 16:10:57 castor kernel: rfkill: input handler disabled Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated successfully. Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
I have seen this problem on several different computers. The problem occurred on at least one computer on which I installed kubuntu 2024 from "scratch", not as an upgrade to an existing installation. In that case, I believe the icon was there through several reboots of the machine. I am guessing that it disappeared as a consequence of one of the subsequent updates. -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+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 1991293] Re: sane-backends 1.1.1-5 FTBFS
** Changed in: sane-backends Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1991293 Title: sane-backends 1.1.1-5 FTBFS Status in sane-backends: Fix Released Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends package in Debian: Fix Released Bug description: FTBFS[1]: ---> minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::Pixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::RawPixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::PixelFormat’) <--- Since this happens in testsuite/, my suggested workaround is to simply disable the offending call, responsible for a diagnostic message. [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic- amd64.sane-backends_1.1.1-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1991293/+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 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"
I have the same problem on 2 installs out of 3. And no "Removing a network device that was not added" in /var/log/syslog. I also found that the problem does not seem to occur on Xorg, only on Wayland. And I also found that the work around is to go to a console and then back using (e.g.) ctrl-alt-F1 then ctrl-alt-F2. -- 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/1975884 Title: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added" Status in gnome-shell package in Ubuntu: Confirmed Bug description: As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1769981/comments/25 , I've been observing an issue when unlocking my computer (usually from a screen lock state, not hibernation/sleep) where after entering the first few characters of my password the screen freezes for 10-20 seconds before I can do any type of input (mouse, touch, keyboard). I've also seen it happen when having touch / gesture input switch between displaying the user name and the password field - where the screen can get stuck in the animation in an interstitial state for a number of seconds. I've largely been noticing this since upgrading from Ubuntu 21.10 to 22.04. It doesn't happen all the time, but often enough to file an issue for. So far I've tried: - Disabling the 'blur my shell' extension - still encountered the issue again eventually. - Looking for anything associated with this in /var/crash - couldn't find anything. - Looking for anything associated at errors.ubuntu.com for my id. What I may eventually try: - Seeing if this may depend on having too many browser tabs / apps open. Currently not in a position to do this. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 19:19:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (315 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975884/+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 1970031] Re: Grey (gray) appears as pink in Ubuntu 22.04
This is the GNOME issue tracking this upstream. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071 It was introduced into GNOME 40 by this commit. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/e90a75fd59ac41aa331f53492a84712e43bcbce2 There was an attempt to revert it here, that was eventually abandoned as the color transform matrix code was moved to mutter. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/293 I think Ubuntu should patch out this change. Monitors with unreliable EDID, of which there are many, end up with distorted colors. Potentially, monitors with good EDID may have slightly reduced color accuracy, but only to the threshold of GNOME pre-40. Someone for whom that matters is likely manually calibrating their color already. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4071 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1970031 Title: Grey (gray) appears as pink in Ubuntu 22.04 Status in GNOME Settings Daemon: New Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Grey (gray) appears as pink in Ubuntu 22.04 WORKAROUND: Settings > Colour > YOUR MONITOR = OFF ORIGINAL DESCRIPTION: i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my monitor started showing a gray-pink color. I can't take a screenshot because it will just be gray on your monitor (i checked the screenshot in windows 11). Did the developers break something in the video card driver or why did it happen? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Apr 23 19:54:00 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1970031/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition
I've also experienced this bug and it's a show-stopper for either upgrading or requires changing distro, and makes Ubuntu unusable for many enterprises. We don't accept user/password combination so a fallback to that from Kerberos isn't possible and moving the ccache isn't possible or supported either. Also, since the snap:ification, the browser doesn't use system certificates store anymore, which makes certificates break for all websites when for example intermediate certs are rotated in the system store, which is a security issue since users will be taught to accept expired certificates. -- 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/1849346 Title: [snap] kerberos GSSAPI no longer works after deb->snap transition Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged Bug description: I configure AuthServerWhitelist as documented: https://www.chromium.org/developers/design-documents/http- authentication and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPNEGO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849346/+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 1991493] Re: Data ciphers are not properly configured with openvpn 2.6
The attachment "nmo.diff" seems to be a debdiff. The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff. If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
Triaged
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1991713] [NEW] FFe: update gnome-text-editor to 43
Public bug reported: Impact -- The Ubuntu Desktop Team has a release goal of shipping GNOME 43 in its entirety for Ubuntu 22.10. This was done for everything that GNOME released as of GNOME 43 Release Candidate except for gnome-text-editor. gnome-text-editor switched from a bundled copy of editorconfig-core to using the system library. Upon noticing the dependency change, I immediately began the Main Inclusion Process for that library. Some upstream issues were detected during the review and it's not likely that they will be fixed in time for Ubuntu 22.10. Therefore, we are requesting a Feature Freeze Exception to upgrade gnome-text-editor from 42 to 43 and add a patch to revert the unbundling commit. Ubuntu Desktop is the only Ubuntu flavor that ships gnome-text-editor by default. ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1991713 Title: FFe: update gnome-text-editor to 43 Status in gnome-text-editor package in Ubuntu: New Bug description: Impact -- The Ubuntu Desktop Team has a release goal of shipping GNOME 43 in its entirety for Ubuntu 22.10. This was done for everything that GNOME released as of GNOME 43 Release Candidate except for gnome-text-editor. gnome-text-editor switched from a bundled copy of editorconfig-core to using the system library. Upon noticing the dependency change, I immediately began the Main Inclusion Process for that library. Some upstream issues were detected during the review and it's not likely that they will be fixed in time for Ubuntu 22.10. Therefore, we are requesting a Feature Freeze Exception to upgrade gnome-text-editor from 42 to 43 and add a patch to revert the unbundling commit. Ubuntu Desktop is the only Ubuntu flavor that ships gnome-text-editor by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1991713/+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 1991709] [NEW] gnome-shell memory leak
Public bug reported: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1991709 Title: gnome-shell memory leak Status in gnome-shell package in Ubuntu: New Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991709/+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 1990886] Re: Security updates missing after 91.11.0
Thunderbird 102.2.2 was finally released to
{bionic,focal,jammy}-{updates,security}. Thank you for your patience,
and please excuse the delay.
I am now working on the 102.3.1 update.
** Changed in: thunderbird (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1990886
Title:
Security updates missing after 91.11.0
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Upstream released Thunderbird 91.11.0 on June 28, 2022.
It's now at 91.13.1 from September 19, 2022. The release notes say:
"By popular demand, Thunderbird 91.13.1 contains important security updates
that shipped in Thunderbird 102.2.1. Users are encouraged to update as soon as
possible."
Source: https://www.thunderbird.net/en-US/thunderbird/91.13.1/releasenotes/
Ubuntu 22.04 Jammy (but also the other supported LTS) still has Thunderbird
91.11.0 (1:91.11.0+build2-0ubuntu0.22.04.1) without the security fixes after
91.11.0.
The package should be updated to 91.13.1.
Given that it has been three months without security updates, there
seems to be some general friction with following upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1990886/+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 1948539] Re: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1948539 Title: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB. Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: System Monitor is showing wrong Memory info. Actual is 8(7.6) GB showing 8.2 GB. Current OS version - Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1948539/+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 1948539] Re: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB.
I'm having the same issue on 22.04.1 LTS with gnome-system-monitor version 42. I have 32GB of RAM installed and system monitor reports 33.4GB for some reason. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1948539 Title: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB. Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: System Monitor is showing wrong Memory info. Actual is 8(7.6) GB showing 8.2 GB. Current OS version - Ubuntu 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1948539/+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 1991707] [NEW] The update interval for the resources tab is multiplied by 10.
Public bug reported: This is for version 42.0 of gnome-system-monitor on Ubuntu 22.04 LTS. The update interval setting is off by one decimal place specifically for the setting that affects the resources tab. So if the update interval is set to 0.10 seconds, it will refresh every second. If it's left at the default value of 1 second, it updates once every 10 seconds and appears frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 14:29:40 2022 InstallationDate: Installed on 2022-07-09 (87 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to jammy on 2022-08-13 (52 days ago) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1991707 Title: The update interval for the resources tab is multiplied by 10. Status in gnome-system-monitor package in Ubuntu: New Bug description: This is for version 42.0 of gnome-system-monitor on Ubuntu 22.04 LTS. The update interval setting is off by one decimal place specifically for the setting that affects the resources tab. So if the update interval is set to 0.10 seconds, it will refresh every second. If it's left at the default value of 1 second, it updates once every 10 seconds and appears frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 14:29:40 2022 InstallationDate: Installed on 2022-07-09 (87 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to jammy on 2022-08-13 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1991707/+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 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490
@arutyun-akopov, can you try the workaround detailed in comment #1? ** Changed in: systemd (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1896540 Title: Incorrectly specified Touchpad size for Lenovo T490 Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Incomplete Bug description: The vertical sensitivity of the touchpad on my laptop Lenovo T490 seemed significantly higher than the horizontal sensitivity. After doing some research I found out that the touchpad size is incorrectly listed by the kernel. Touchpad size listed by the kernel: 77x107mm The real size of the touchpad: 68x100mm Description: Ubuntu 20.04.1 LTS Release: 20.04 Systemd version: 245.4-4ubuntu3.2 Output from the touchpad-edge-detector: miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 /dev/input/event5 Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5 Move one finger around the touchpad to detect the actual edges Kernel says: x [1266..5678], y [1162..4694] Touchpad sends: x [1266..5678], y [1161..4694] -^C Touchpad size as listed by the kernel: 77x107mm User-specified touchpad size: 68x100mm Calculated ranges: 4412/3533 Suggested udev rule: # evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:* EVDEV_ABS_00=1266:5678:65 EVDEV_ABS_01=1161:4694:35 EVDEV_ABS_35=1266:5678:65 EVDEV_ABS_36=1161:4694:35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1896540/+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 1545811] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1545811 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: Confirmed Bug description: ubuntu 16.04 alpha. ibus-daemon crashed popped up after testing another bug ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: ibus 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 15 18:57:55 2016 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2013-09-28 (870 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to xenial on 2016-02-11 (4 days ago) UserGroups: adm cdrom dip disk fax lp lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1545811/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
** Changed in: thunderbird (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: Fix Committed Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1991699] Re: ibus-daemon crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1545811 *** https://bugs.launchpad.net/bugs/1545811 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545811, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991699/+attachment/5621138/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991699/+attachment/5621140/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991699/+attachment/5621143/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991699/+attachment/5621144/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991699/+attachment/5621145/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991699/+attachment/5621146/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991699/+attachment/5621147/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1545811 ibus-daemon crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1991699 Title: ibus-daemon crashed with SIGABRT in g_assertion_message_expr() Status in ibus package in Ubuntu: New Bug description: Opened logs, clicked one of them. A new small window popped up with further information. I couldn't close that window, so I logged out. Logging back in, bug report was created. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7 Uname: Linux 5.19.0-18-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 4 19:50:17 2022 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2022-08-28 (36 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220828) ProcCmdline: ibus-daemon --panel disable -r --xim ProcEnviron: LANG=en_US.UTF-8 Signal: 6 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991699/+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 1991493] Re: Data ciphers are not properly configured with openvpn 2.6
Cherry-pick of the commits mentioned by
https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46#note_1566186.
** Patch added: "nmo.diff"
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1991493/+attachment/5621148/+files/nmo.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
Triaged
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1991698] [NEW] package chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned erro
Public bug reported: This happened during the OS upgrade to 20.4. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLYELTktLMDQYAQOAPSN4Kl+xoldPoigPUFS/74BxT4EAgcCBgJUAqcCzAAEBBHQAMPJwWoCwWIoAYFkhAAAe/QAYSx5aHgAKICAgICAg/ABVMjhENTkwCiAgICAg/wBIVFBGQzAwNzU5CiAgAakCAyPxSJAEHxMDEiAiIwkHB4MBAABtAwwAEACAPCAQYAECAwI6gBhxOC1AWCxFAGBZIQAAHgI6gNByOC1AECxFgGBZIQAAHgEdAHJR0B4gbihVAGBZIQAAHlZeAKCgoClQMCA1AGBZIQAAGgAARw== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGr+0mAAAcAQSlIhN4AsY1o1ZSnigKUFQBAQEBAQEBAQEBAQEBAQEBFDeAtHA4JkBsMKoAWMIQAAAaECyAtHA4JkBsMKoAWMIQAAAa/gBHSFcxS4BCMTU2SEFOAAADQQKeABoBCiAgAAI= modes: 1920x1080 1920x1080 Date: Tue Oct 4 12:22:48 2022 Desktop-Session: 'None' 'None' 'None' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00+beaver-+X00 Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-01-06 (635 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 InstalledPlugins: Load-Avg-1min: 2.18 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Precision 3550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-126-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-10-04 (0 days ago) dmi.bios.date: 09/07/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0XK86F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: MTTESTPC dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd09/07/2022:svnDellInc.:pnPrecision3550:pvr:rvnDellInc.:rn0XK86F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3550 dmi.product.sku: 09A2 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1991698 Title: package chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: This happened during the OS upgrade to 20.4. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 105.0.5195.102-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLYELTktLMDQYAQOAPSN4Kl+xoldPoigPUFS/74BxT4EAgcCBgJUAqcCzAAEBBHQAMPJwWoCwWIoAYFkhAAAe/QAYSx5aHgAKICAgICAg/ABVMjhENTkwCiAgICAg/wBIVFBGQzAwNzU5CiAgAakCAyPxSJAEHxMDEiAiIwkHB4MBAABtAwwAEACAPCAQYAECAwI6gBhxOC1AWCxFAGBZIQAAHgI6gNByOC1AECxFgGBZIQAAHgEdAHJR0B4gbihVAGBZIQAAHlZeAKCgoClQMCA1AGBZIQAAGgAARw== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440
[Desktop-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click
looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070 addresses this in gtk3 apps, can it (and/or the next gtk release) be added to the ubuntu package and the snap package that contains gtk3 (gnome-* snap?) -- 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/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click Status in GTK+: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1991665] Re: Ubuntu 22.04 screensaver unlock issue with NFS drives
** Package changed: ubuntu => gnome-screensaver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1991665 Title: Ubuntu 22.04 screensaver unlock issue with NFS drives Status in gnome-screensaver package in Ubuntu: New Bug description: When unlocking A screen in gnome desktop in Ubuntu 22.04 if there are NFS mounted drives (using fstab) and bookmarks are added to those in Files, gnome does some kind of access to those folders before unlocking the screen In specific case if the NFS server goes away when the GNOME screen is locked then it is impossible to unlock the screen, there is no timeout to that process as far as I could measure, in any case, the timeout did not occur in 10 hours' time. even if NFS server comes back online that does not guarantee that the system would be able to unlock (as if the NFS mount goes stale in the meantime nothing helps later) I think it would be ideal to remove the dependency of unlocking the screen on filesystem access The NFS drives do not server any system components or users' home folders, they are for document sharing only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1991665/+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 1991665] [NEW] Ubuntu 22.04 screensaver unlock issue with NFS drives
You have been subscribed to a public bug: When unlocking A screen in gnome desktop in Ubuntu 22.04 if there are NFS mounted drives (using fstab) and bookmarks are added to those in Files, gnome does some kind of access to those folders before unlocking the screen In specific case if the NFS server goes away when the GNOME screen is locked then it is impossible to unlock the screen, there is no timeout to that process as far as I could measure, in any case, the timeout did not occur in 10 hours' time. even if NFS server comes back online that does not guarantee that the system would be able to unlock (as if the NFS mount goes stale in the meantime nothing helps later) I think it would be ideal to remove the dependency of unlocking the screen on filesystem access The NFS drives do not server any system components or users' home folders, they are for document sharing only ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 22.04 screensaver unlock issue with NFS drives https://bugs.launchpad.net/bugs/1991665 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. -- 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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
The attachment "snap.thunderbird.thunderbird.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: In Progress Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
Thanks for the investigation! https://github.com/ubuntu/thunderbird/pull/4 should fix this. ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: In Progress Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1988786] Re: system does not boot after full-upgrade on kinetic
How to reproduce: * Startup 22.10 beta ISO image * Enable "Install third-party software for graphics and Wi-Fi hardware and additional media format" on "Update and Software" step. * Complete installs and reboot * No startup GDM session More simple step: * Install gstreamer1.0-vaapi package on 22.10 and reboot How to recovery: * Select "recovery mode" on GRUB menu * Exec "apt remove gstreamer1.0-vaapi" * Exit recovery mode and reboot system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1988786 Title: system does not boot after full-upgrade on kinetic Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Bug description: Hi, After a full upgrade on a kinetic system, the system no longer boots normally. When I power the computer on, I get a prompt to decrypt my disk. I insert the password, and am redirected to a screen saying a fschk is running. It spend hours in that screen with apparently no activity. Pressing ctrl+C does not help at that point. Booting through recovery mode and then requesting to proceed to boot works fine. A regular fschk also suceeds. Here is what I could extract from my journal: Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 'ca.desrt.dconf' Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 comm="/usr/libexec/gsd-sharing" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service... Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 05 16:10:57 castor systemd[1]: Started Hostname Service. Sep 05 16:10:57 castor kernel: rfkill: input handler disabled Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated successfully. Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor
[Desktop-packages] [Bug 1980839] Re: thunderbird -compose returns error since the 102 snap update?
** Patch added: "snap.thunderbird.thunderbird.patch" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+attachment/5621085/+files/snap.thunderbird.thunderbird.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
** Attachment added: "snap.thunderbird.thunderbird" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+attachment/5621078/+files/snap.thunderbird.thunderbird -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1980839] Re: thunderbird -compose returns error since the 102 snap update?
Hi all, found the bug. Was apparmor after all. For some reason didn't show up in journalctl until I tried the beta, and then found the culprit: thunderbird is trying to bind to a session called org.mozilla.thunderbird plus some identifiers, not sure what they correspond to. However, adding the following to the apparmor profile fixed the bug: dbus bind bus=session name=org.mozilla.thunderbird*, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1980839 Title: thunderbird -compose returns error since the 102 snap update? Status in thunderbird package in Ubuntu: Confirmed Bug description: After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04, it is no longer possible to open mailto links from the firefox snap in thunderbird. When clicking a mailto link in the firefox 102.0.1 snap, thunderbird returns the following error message: "Thunderbird is already running, but is not responding. To use Thunderbird, you must first close the existing Thunderbird process, restart your device, or use a different profile." The issue appears related to the thunderbird update as there was no issue opening links in the previous 91 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1980839/+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 1987523] Re: Pulsaudio crashes once BT microphone is connected
Sorry for the delay. I confirm that the package from -proposed solves the issue on Jammy. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1987523 Title: Pulsaudio crashes once BT microphone is connected Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Bug description: * Impact When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. * Test case - Connect a bluetooth headset to the computer - Try to change the profile to HFP from the desktop settings or the pulseaudio cli -> the profile should get correctly selected, the service shouldn't crash * Regression potential The changes are in the functions handling mSBC packets which handle bluetooth HFP codecs, so any regression would concern bluetooth devices using that profile. --- When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: [51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at ../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). Aborting. Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash report... Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie Aug 24 13:44:24 p14s systemd[1]: Started crash report submission. Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: /var/lock/whoopsie/lock Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully. Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk I've identified the upstream fix for this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e I've built packages with the fix and can confirm that it does solve the problem. Packages are available at: https://launchpad.net/~ivoks/+archive/ubuntu/pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1991678] [NEW] X seems to lag at random intervals
Public bug reported: Hey, I trust you are well. I just noticed odd behaviour probably related to video resources which causes the entire GUI to lag for typing or to transition between screens and apps especially if there's a notification or any other new graphical interaction. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 11:30:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2022-06-09 (116 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0YRH3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/24/2022:br1.19:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0YRH3X:rvrA00:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991678 Title: X seems to lag at random intervals Status in xorg package in Ubuntu: New Bug description: Hey, I trust you are well. I just noticed odd behaviour probably related to video resources which causes the entire GUI to lag for typing or to transition between screens and apps especially if there's a notification or any other new graphical interaction. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 11:30:42 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2022-06-09 (116 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0YRH3X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd03/24/2022:br1.19:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0YRH3X:rvrA00:cvnDellInc.:ct10:cvr:sku0839: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1990113] Re: Increase timeout on test doc-check for RISC-V
@Alexandre, is that actually been an issue on our builder or what's the motivation for the change if not? Also the package is currently in sync with Debian and it would be nice to keep it this way so if it makes sense to have it could you propose the change upstream and/or to Debian? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to json-glib in Ubuntu. https://bugs.launchpad.net/bugs/1990113 Title: Increase timeout on test doc-check for RISC-V Status in json-glib package in Ubuntu: Incomplete Bug description: The doc-check test fails on RISC-V because it is a very slow architecture: fix this by increasing the timeout on this specific test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-glib/+bug/1990113/+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 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
I am experiencing the same issue to this day. I have sent many crash reports about it. Ubuntu 22.04.1 LTS Linux Kernel 5.15.0-48-generic I'm using Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934579 Title: Nautilus crashes when opening places from the dock contextmenu Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+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 1991654] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1986455, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991654/+attachment/5620981/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991654/+attachment/5620983/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991654/+attachment/5620987/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991654/+attachment/5620988/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991654/+attachment/5620989/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991654/+attachment/5620990/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991654/+attachment/5620991/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1986455 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1991654 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() Status in gjs package in Ubuntu: New Bug description: Ubuntu beta 22.10. I opened up system monitor through gnome-shell overlay while all the processor cores were at close to 100% load from a different program. system monitor opened up correctly. After that I possibly touched the activities hot corner and the crash report appeared. It didn't seem as if any of my opened programs crashed/closed because of it. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Oct 4 12:23:30 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2022-08-13 (51 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-10-01 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1991654/+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 1989726] Re: Only a quarter of the screen showing in VirtualBox
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5933 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5933 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5933 Importance: Unknown Status: Unknown -- 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/1989726 Title: Only a quarter of the screen showing in VirtualBox Status in GNOME Shell: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and restarted twice. I've tried Xubuntu and Kubuntu 22.04 and they both work without any errors. Screenshot here: https://i.stack.imgur.com/KI0YO.png To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989726/+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 1990010] Re: VA error: resource allocation failed
Makes sense (assuming the Libva etc. is the same), thanks for
investigating this further!
Since you are the one working on this it is more accurate to transfer
the assignment status to you. If you feel otherwise please let me know.
** Changed in: chromium-browser (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk)
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
https://github.com/intel/media-driver/issues/1498
---
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, using Wayland I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
(NOTE: HW decoding does work with same browser on X11 desktop, using
VDAVideoDecoder.)
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
Yes people should be able to promote a feature advertised during install... While the bug remains open, a workaround is to: 1. Install *without* the third-party option. 2. sudo apt install ubuntu-restricted-extras 3. sudo apt remove gstreamer1.0-vaapi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
I moved all my applications to virtual machines, I use 6 VMs for that purpose. One VM is dealing with all multimedia apps and I need all codecs there. That is, why the Host OS is a minimal install of Ubuntu 22.04 LTS, so without any Apps except Firefox. I can live with my Xorg workaround for 2 reasons: - Normally I prefer LTS releases and I used the other releases only a few times in the last 10 years for better drivers or new ZFS functionality; - I can use Xorg instead of Wayland, since I don't really need 22.10 and for now I installed it mainly out of curiosity and trying to ensure my use case is still OK; Note, that all YouTubers promote to install that third-party software. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: New Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
https://github.com/canonical/apport/pull/2 was merged to main. ** Changed in: apport Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Status in xdg-utils package in Ubuntu: Invalid Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5932 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5932 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5932 Importance: Unknown Status: Unknown -- 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: New Status in GNOME Shell: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can confirm #37, various days already working, thanks! :) -- 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
I am using 22.04.1 and GNOME 42.4, this bug is still there ** Attachment added: "Screenshot from 2022-10-04 14-19-00.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970800/+attachment/5620944/+files/Screenshot%20from%202022-10-04%2014-19-00.png -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-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..02.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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970800/+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 1991624] Re: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied with Pipewire on Ubuntu 22.10 beta
** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** No longer affects: pipewire (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1991624 Title: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied with Pipewire on Ubuntu 22.10 beta Status in PipeWire: New Bug description: Pipewire on Ubuntu 22.10 has these following on errors when systemd logs are examined like org.freedesktop.DBus.Error.AccessDenied error, mod.rt: Can't find xdg-portal and pipewire[2204]: mod.rt: found session bus but no portal. I have been using the SonyWH-1000XM4 and the AAC codec is not showing up in the settings as one of the codecs that it can use and this also the case with my other bluetooth devices that support the AAC codec. To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1991624/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
That makes sense, and I have done the same in the past. Although this bug highlights the fact that those third-party packages behave differently and exercise different code paths in virtual vs real machines. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
I'm using VirtualBox to test upcoming Ubuntu versions using the exact same config and packages that will later be used on several physical machines. So it's pretty important to me to install the third-party packages in VMs as well. But yes, I can live with the workaround for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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
