[Desktop-packages] [Bug 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
** Changed in: upower (Ubuntu) Status: Incomplete => Fix Released ** Summary changed: - [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed + Laptop monitor does not turn off/disconnect when the lid is closed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 ** Also affects: upower via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 Importance: Unknown Status: Unknown ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: Laptop monitor does not turn off/disconnect when the lid is closed Status in Upower: Unknown Status in upower package in Ubuntu: Fix Released Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962276/+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 1962351] Re: login screen shown on inactive monitor
*** This bug is a duplicate of bug 1962276 *** https://bugs.launchpad.net/bugs/1962276 ** This bug has been marked a duplicate of bug 1962276 Laptop monitor does not turn off/disconnect when the lid is closed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor Status in Upower: Unknown Status in upower package in Ubuntu: Fix Released Bug description: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu- dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962351/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: ipywidgets (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: Fix Released Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: Fix Released Status in python-b2sdk package in Ubuntu: Fix Released Status in python-hypothesis package in Ubuntu: Fix Released Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: Fix Released Status in ipywidgets package in Debian: Fix Released Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: Fix Released Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Fix Released Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
Hi Daniel you are correct. I booted into the 5.15.0-18.18-generic and suspend and clam shell mode works as expected. Thanks Rue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+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 1962523] [NEW] [Wayland][Nvidia] gdm default use Xorg in 22.04
Public bug reported: [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: New Bug description: [Steps to reproduce] 1. Download jammy daily build 2. Install nvidia driver by selecting "install third-party packages.." during the installation. 3. Login without selecting modes (e.g. "Ubuntu" or "Ubuntu on Wayland" or enable auto-login during the installation. [Expect result] gdm using wayland [Actual result] gdm using xorg 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy gdm3 gdm3: Installed: 41.3-1ubuntu2 Candidate: 41.3-1ubuntu2 Version table: *** 41.3-1ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Reference: Ubuntu Jammy should use Wayland as default with nVidia https://docs.google.com/document/d/1wK4vGUXaDG2Nd7e3XGI9kDpNzReka_VOHO7sgRqce5s/edit?disco=VxVMzfA To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+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 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
Sure no problem. I will report back -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+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 1962276] Re: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed
I wonder if the new kernel in comment #10 worked /because/ the upower update to 0.99.16-2 arrived at the same time... rue: Please test the Ubuntu kernel again (5.15.0-18.18-generic) ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Changed in: upower (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Bug watch removed: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+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 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
** Tags removed: fixed-in-42.0 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1933186/+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 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xwayland (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: xwayland (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Won't Fix Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Won't Fix Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Invalid Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
From the screenshot in comment #5 and the gnome-shell (v40) source code: Установить обновления и перезапустить Система будет автоматически выключена через %d секунд [✓] Установить отложенные обновления ПО Note that's two major releases behind what is in jammy proposed right now so we should retest with gnome-shell 42 when it's ready. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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] [NEW] failing tests with new sssd, blocks python3-defaults
Public bug reported: adsys has failing autopkgtests on armhf. Demoting the package to -proposed to unblock the python3-defaults transition. ** Affects: adsys (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed ** Tags added: block-proposed -- 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: New Bug description: 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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
This seems to be the same as https://bugs.launchpad.net/ubuntu/+source/evolution-data- server/+bug/1952107 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. Status in Evolution: Unknown Status in Ubuntu MATE: New Status in evolution package in Ubuntu: New Status in evolution-data-server package in Ubuntu: New Bug description: I'm running Ubuntu MATE 20.04; I stick with LTS for this system. I use Evolution for email and calendar. Tonight I got this message: = Failed to connect address book “guy.rouill...@gmail.com : Contacts” Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. == I went to report this on the GNOME bug tracker and found this existing issue: https://gitlab.gnome.org/GNOME/evolution/-/issues/1655 That issue was closed with this comment: == "Andre Klapper Issue found on latest Evolution in Debian 11 (3.38.3-1) That version is ancient and not maintained anymore by GNOME developers. Feel free to file a bug report in your distribution's issue tracker." The version in MATE is even older: 3.36.5-0ubuntu1 So apparently Evolution in MATE is currently not functional. We need to update to a later release. I will update to the newer LTS of MATE when it is released. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-10-05 (1212 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: evolution-data-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Tags: third-party-packages focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+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 1962277] Re: To support Synaptics fp device
** Also affects: libfprint (Ubuntu Jammy) Importance: Medium Status: New ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device Status in OEM Priority Project: Confirmed Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: New Status in libfprint source package in Impish: New Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/4d5e2775b23a65b6b7b41eb98fa5b2c68a805f33 https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/128d809227bbef1d3bd8e7c7e1f9b68a335db252 https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3fb8860dc487568518d69e9074135041296d1e75 This ID is included in upstream. [Impact] * Devices have synaptics fingerprint component will get supported. * Supported list. [06cb:0100] [06cb:00f0] [06cb:0103] [06cb:0123] [06cb:0126] [06cb:0129] [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be more synaptics devices get supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+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 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
To clarify, Alex's upower problem is bug 1962351. For the moment this bug of rue's is a kernel bug. ** No longer affects: upower (Ubuntu) ** No longer affects: mutter (Ubuntu) ** No longer affects: gnome-settings-daemon (Ubuntu) ** Summary changed: - [jammy] Laptop monitor does not turn off/disconnect when the lid is closed + [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [Lenovo ThinkPad X250] Laptop monitor does not turn off/disconnect when the lid is closed Status in linux package in Ubuntu: Confirmed Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962276/+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 1962351] Re: login screen shown on inactive monitor
upower (0.99.16-2) unstable; urgency=medium ** This bug is no longer a duplicate of bug 1760849 Login screen appears on only one monitor and it's not the one I want ** Package changed: gdm3 (Ubuntu) => upower (Ubuntu) ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 ** Also affects: upower via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 Importance: Unknown Status: Unknown ** Changed in: upower (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor Status in Upower: Unknown Status in upower package in Ubuntu: Fix Released Bug description: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu- dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962351/+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 1962351] Re: login screen shown on inactive monitor
Tracking in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 per discussion with Alex. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor Status in Upower: Unknown Status in upower package in Ubuntu: Fix Released Bug description: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu- dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1962351/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
I am typically using Gnome3 with ubuntu 20.04 (standard ubuntu). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
Confirming that this is an issue even with the Dell customized ubuntu 20.04 version for the Dell XPS 13 laptop. I find about 30% cpu useage for gnome-shell when multiload-indicator is running. I also find that high framerate, high res youtube videos stutter when multiload-indicator is running but they run much smoother when multiload-indicator is closed. I am using an intel evo i7 processor and intel Xe graphics card. I am still struggling to understand if there is an update to fix this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
Well, it may or may not be a bug in gnome-shell which implements the dialog; but it is definitely not a bug in update-notifier which is not involved in the communication between gnome-shell and systemd. It is likely a bug in gnome-shell signalling the wrong thing to systemd in this situation. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
As far as I can say, the dialog itself works as intended. The bug is, that the Ubuntu box is rebooting instead of turninging off. -- 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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
In fact, I just searched my system and found these strings in gnome- shell after all, so reassigning back to there. ** Package changed: update-notifier (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/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1952107] Re: Google Contacts API Deprecated
Malfunction still persits (see below). Verbindung zu Adressbuch »xx...@gmail.com : Kontakte« fehlgeschlagen Ungültige Anfrageadresse oder -kopfzeile, oder nicht unterstützter Nicht-Standardparameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1962346] [NEW] Ubuntu reboots instead of powering off if a software updates exists
You have been subscribed to a public bug: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- Ubuntu reboots instead of powering off if a software updates exists https://bugs.launchpad.net/bugs/1962346 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 1962489] [NEW] [UX550VE, Realtek ALC295, Speaker, Internal] fails after a while
Public bug reported: Sound starts for a few seconds, then it sounds as if it were breaking, then it stops completely. If I run "ubuntu-bug audio", after I close the error, the sounds works again, but again only for a few seconds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex882 F pulseaudio /dev/snd/pcmC0D0p: alex882 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 28 19:36:48 2022 InstallationDate: Installed on 2022-02-27 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: feb 28 20:30:40 alex-UX550VE dbus-daemon[657]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=882 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [UX550VE, Realtek ALC295, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1962489 Title: [UX550VE, Realtek ALC295, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Sound starts for a few seconds, then it sounds as if it were breaking, then it stops completely. If I run "ubuntu-bug audio", after I close the error, the sounds works again, but again only for a few seconds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex882 F pulseaudio /dev/snd/pcmC0D0p: alex882 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 28 19:36:48 2022 InstallationDate: Installed on 2022-02-27 (1 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: feb 28 20:30:40 alex-UX550VE dbus-daemon[657]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=882 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [UX550VE, Realtek ALC295, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.307:bd04/19/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962489/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
It passed in s390x, finger crossed about the rest: https://autopkgtest.ubuntu.com/packages/a/adsys/jammy/s390x -- 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: In Progress Bug description: 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 1962170] Re: DEP8 failure with samba 4.15.5
Oh, in my link it was using samba 4.13, need to trigger it with proposed samba. I'll do that. -- 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: In Progress Bug description: 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 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
Thanks Alex, fixed with https://bugs.launchpad.net/ubuntu/+source/upower/0.99.16-2 ** Changed in: upower (Ubuntu) Importance: Undecided => High ** Changed in: upower (Ubuntu) Status: New => Fix Released ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in upower package in Ubuntu: Fix Released Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+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 1962043] Re: libwacom9 : depends on : libwacom-common
could you try to sudo apt remove libinput2? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: Confirmed Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+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 1962327] Re: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER
Bug reported upstream - closing here https://bugs.documentfoundation.org/show_bug.cgi?id=147661 ** Bug watch added: Document Foundation Bugzilla #147661 https://bugs.documentfoundation.org/show_bug.cgi?id=147661 ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1962327 Title: VERTICAL FRACTION FEATURE PRESENT IN FONT NOT APPLIED BY WRITER Status in libreoffice package in Ubuntu: Confirmed Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962327/+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] Re: DEP8 failure with samba 4.15.5
Even where the build passed, the DEP8 tests are failing again (https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/a/adsys/20220228_024008_ead55@/log.gz) -- 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: In Progress Bug description: 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 1588878] Re: CanoScan Lide 220 doesn't work
Fixes have been made upstream: https://gitlab.com/sane-project/backends/-/merge_requests/284 Please test with Ubuntu 20.04 or later. -- 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/1588878 Title: CanoScan Lide 220 doesn't work Status in sane-backends package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04 I used to scan with CanoScan Lide 220, it worked fine. In Ubuntu 16.04 it doesn't work. XSane says "Failed to start scanner: Error during device I/O". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: KDE Date: Fri Jun 3 18:30:53 2016 InstallationDate: Installed on 2016-04-26 (38 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1588878/+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 1588878] Re: CanoScan Lide 220 doesn't work
** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- 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/1588878 Title: CanoScan Lide 220 doesn't work Status in sane-backends package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04 I used to scan with CanoScan Lide 220, it worked fine. In Ubuntu 16.04 it doesn't work. XSane says "Failed to start scanner: Error during device I/O". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: KDE Date: Fri Jun 3 18:30:53 2016 InstallationDate: Installed on 2016-04-26 (38 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1588878/+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 1962043] Re: libwacom9 : depends on : libwacom-common
I'm not able to reproduce this on a chroot upgrade from impish to jammy: (impish-amd64)root@bryant:/# apt install libwacom-bin Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libglib2.0-0 libgudev-1.0-0 libwacom-common libwacom2 Recommended packages: libglib2.0-data shared-mime-info xdg-user-dirs The following NEW packages will be installed: libglib2.0-0 libgudev-1.0-0 libwacom-bin libwacom-common libwacom2 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 1518 kB of archives. After this operation, 5014 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu impish/main amd64 libglib2.0-0 amd64 2.68.4-1ubuntu1 [1424 kB] Get:2 http://archive.ubuntu.com/ubuntu impish/main amd64 libgudev-1.0-0 amd64 1:237-2 [16.3 kB] Get:3 http://archive.ubuntu.com/ubuntu impish/main amd64 libwacom-common all 1.8-2ubuntu2 [49.5 kB] Get:4 http://archive.ubuntu.com/ubuntu impish/main amd64 libwacom2 amd64 1.8-2ubuntu2 [22.2 kB] Get:5 http://archive.ubuntu.com/ubuntu impish/main amd64 libwacom-bin amd64 1.8-2ubuntu2 [5604 B] Fetched 1518 kB in 1s (1702 kB/s) Selecting previously unselected package libglib2.0-0:amd64. (Reading database ... 11558 files and directories currently installed.) Preparing to unpack .../libglib2.0-0_2.68.4-1ubuntu1_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.68.4-1ubuntu1) ... Selecting previously unselected package libgudev-1.0-0:amd64. Preparing to unpack .../libgudev-1.0-0_1%3a237-2_amd64.deb ... Unpacking libgudev-1.0-0:amd64 (1:237-2) ... Selecting previously unselected package libwacom-common. Preparing to unpack .../libwacom-common_1.8-2ubuntu2_all.deb ... Unpacking libwacom-common (1.8-2ubuntu2) ... Selecting previously unselected package libwacom2:amd64. Preparing to unpack .../libwacom2_1.8-2ubuntu2_amd64.deb ... Unpacking libwacom2:amd64 (1.8-2ubuntu2) ... Selecting previously unselected package libwacom-bin. Preparing to unpack .../libwacom-bin_1.8-2ubuntu2_amd64.deb ... Unpacking libwacom-bin (1.8-2ubuntu2) ... Setting up libglib2.0-0:amd64 (2.68.4-1ubuntu1) ... No schema files found: doing nothing. Setting up libgudev-1.0-0:amd64 (1:237-2) ... Setting up libwacom-common (1.8-2ubuntu2) ... Setting up libwacom2:amd64 (1.8-2ubuntu2) ... Setting up libwacom-bin (1.8-2ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu3) ... (impish-amd64)root@bryant:/# sed -i 's/impish/jammy/' etc/apt/sources.list (impish-amd64)root@bryant:/# apt update Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [90.7 kB] Get:3 http://security.ubuntu.com/ubuntu jammy-security InRelease [90.7 kB] Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1411 kB] Get:5 http://archive.ubuntu.com/ubuntu jammy/main Translation-en [515 kB] Get:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [101 kB] Get:7 http://archive.ubuntu.com/ubuntu jammy/restricted Translation-en [14.2 kB] Get:8 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.0 MB] Get:9 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5638 kB] Get:10 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [219 kB] Get:11 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB] Fetched 22.5 MB in 5s (4931 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 142 packages can be upgraded. Run 'apt list --upgradable' to see them. (impish-amd64)root@bryant:/# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: libsemanage1 libwacom2 The following NEW packages will be installed: gcc-12-base libexpat1 libmpdec3 libpython3-stdlib libpython3.9-minimal libpython3.9-stdlib libsemanage2 libsepol2 libssl3 libwacom9 media-types python3 python3-minimal python3.9 python3.9-minimal tzdata The following packages will be upgraded: apt apt-utils base-files base-passwd bash binutils binutils-common binutils-x86-64-linux-gnu bsdutils bzip2 coreutils cpp-10 cpp-11 dash debconf debianutils dirmngr dpkg dpkg-dev e2fsprogs fakeroot g++-10 g++-11 gcc-10 gcc-10-base gcc-11 gcc-11-base gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv grep init-system-helpers libacl1 libapt-pkg6.0 libasan6 libatomic1 libattr1 libaudit-common libaudit1 libbinutils libblkid1 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libcc1-0 libcom-err2 libcrypt-dev libcrypt1 libctf-nobfd0 libctf0 libdebconfclient0 libdpkg-perl libext2fs2 libfakeroot libffi8 libgcc-10-dev libgcc-11-dev libgcc-s1
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
Hum, it seems your patch makes sense and should work on most arch. I saw Michael did an upload with this: https://launchpad.net/ubuntu/+source/adsys/0.8ubuntu1 But it’s failing only on ppcel64: https://launchpadlibrarian.net/588289907/buildlog_ubuntu-jammy-ppc64el.adsys_0.8ubuntu1_BUILDING.txt.gz and passing on other architectures. The issue may be related to the signal installed on libsmbclient: https://github.com/ubuntu/adsys/blob/main/internal/smbsafe/smbsafe.go#L4. This workaround is the only reason of smbsafe (you can’t then exec concurrently subprocesses without cleaning up those signals and the library is doing that at every smb call on your behalf). Another idea is that stderr is not allocated for whatever reason https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L38 but why only on ppcel64? I reastically won’t have the time this week with the sprint to look at this. I hope this gives some hints if you need urgently to have it fixed before next one. -- 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: In Progress Bug description: 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 1962170] Re: DEP8 failure with samba 4.15.5
Hum, it seems your patch makes sense and should work on most arch. I saw Michael did an upload with this: https://launchpad.net/ubuntu/+source/adsys/0.8ubuntu1 But it’s failing only on ppcel64: https://launchpadlibrarian.net/588289907/buildlog_ubuntu-jammy-ppc64el.adsys_0.8ubuntu1_BUILDING.txt.gz and passing on other architectures. The issue may be related to the signal installed on libsmbclient: https://github.com/ubuntu/adsys/blob/main/internal/smbsafe/smbsafe.go#L4. This workaround is the only reason of smbsafe (you can’t then exec concurrently subprocesses without cleaning up those signals and the library is doing that at every smb call on your behalf). Another idea is that stderr is not allocated for whatever reason https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L38 but why only on ppcel64? I reastically won’t have the time this week with the sprint to look at this. I hope this gives some hints if you need urgently to have it fixed before next one. -- 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: In Progress Bug description: 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 1844453]
Can confirm that 2FA does not work. Even the GNOME Settings application
has this feature.
---
Version: 7.2.5.2.0+
Build ID: 20(Build:2)
CPU threads: 24; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
In Progress
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
See this related debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+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 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
This appears to be caused (for me at least) by upower 0.99.16-1 - after upgrading today to 0.99.16-2 things are working again as expected. ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+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 1962043] Re: libwacom9 : depends on : libwacom-common
The cause is that both libwacom2 and libwacom9 depend on libwacom-common in the version identical to the libwacom(number) version. I assume that you have libwacom2 and libwacom-common installed from a previous Ubuntu release, or a older version in Jammy that meanwhile has been superseded. sudo apt install libwacom9 libwacom-common=2.1.0-2 or sudo apt install libwacom9 libwacom2- or sudo apt remove libwacom2 should help. see also https://answers.launchpad.net/ubuntu/+source/libwacom/+question/700653 Eventually a "breaks:libwacom2" clause in libwcom9's control file could help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: Confirmed Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+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 1962133] Re: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5
Hi Loïc Minier (lool), thanks for the quick reply. We have reproduce steps using nvidia gst-v4l2 decoder plugin pipeline on gstreamer-1.0 (version gst-1.14 and ubuntu-18.04) We can provide reproducing pipeline on nvidia platforms for the same if needed. We are looking forward to get this fix backported to default gstreamer-1.0 (version gst-1.14 on bionic ubuntu-18.04) Please let us know the feasibility of mentioned request. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline Status in Gstreamer1.0: Unknown Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 source package in Bionic: New Bug description: Few specific h264 and h265 RTSP input streams sources when used with nvidia specific gst-v4l2 based gstreamer-1.0 (version gst-1.14 and ubuntu-18.04) decode pipeline intermittently yields very low fps (in the range of [~0/1 fps]). Issue seems caused by the gst_video_decoder_drain_out function erroneously getting called inside gst_video_decoder_chain_forward function. Required changes to fix the issue seems available with gst-1.16 and to resolve the issue need to backport the relevant OSS fixes from gst-1.16 to gst-1.14 on ubuntu-18.04. The mentioned issue was reported on with: https://bugzilla.gnome.org/show_bug.cgi?id=796771 Corresponding fix was incorporated with below: https://github.com/GStreamer/gst-plugins-base/commit/62cb08404b9bd055c45cc1d5b71141e927ad748a We need to backport above fix on top of gst-1.14.5 on ubuntu-18.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.14 on ubuntu-18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1962133/+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 1962135] Re: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04
Hi, Any update on this request? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Focal: New Bug description: On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962135/+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 1962021] Re: Make the deb package install the firefox snap
Firefox Snap package still does not work properly. It crashes every time on upgrade which cause data loss, it disappear from the panel but still running on unknown workspace... All this is very annoying to the average user and gives a negative impression of using Ubuntu. I think Firefox Snap is not ready for using in LTS release by default. The same situation with Chromium Snap package, I had to switch to Google Chrome .deb package because I tired from Chromium Snap problems. P.S. All Snap packages which I tried to use have the same issues, I'm tired of riding on square wheels when everyone is riding on round ones. -- 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/1962021 Title: Make the deb package install the firefox snap Status in firefox package in Ubuntu: In Progress Bug description: Canonical and Mozilla are working together to make the firefox snap the only supported package in Ubuntu, thus deprecating the deb package in the archive. This bug tracks the transformation of the firefox package in the archive into a transitional package that installs the snap, much like was done for chromium-browser in Ubuntu 19.10. There are a number of known problems and regressions with the snap compared to the deb (see https://bugzilla.mozilla.org/show_bug.cgi?id=snap and https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap), those are actively being worked on and will be addressed in due time, please refrain from using this bug to point them out. Instead, file separate bugs in the upstream bug tracker (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify this is about the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+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 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on u
Hi Loïc Minier (lool), Thanks for the quick reply. We have observed this issue with nvidia platform for now using the nvidia gst-v4l2 decoder plugin pipeline. Though seems same issue was reported and aknowledged by gstreamer maintainers with fix provided in upstream gstreamer version 1.17.90. Hence we can refer original bug reported to gstreamer maintainers for additional reference of reproducing pipeline on non-nvidia platform/plugins. We can provide reproducing pipeline on nvidia platforms for the same if needed. We are looking forward to get this fix backported to default gstreamer-1.0 version 1.16 on ubuntu-20.04 Please let us know the feasibility of mentioned request. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: New Status in gstreamer1.0 source package in Focal: New Bug description: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+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 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
The problem doesn't appear to be universal. I've just installed jammy 2022-02-28 on a laptop, plugged in a monitor and keyboard and closed the lid. But for me everything works correctly - the laptop screen is no longer part of the desktop. ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+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 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
Just crashed with mutter 41.3-3ubuntu1 https://errors.ubuntu.com/oops/6ced385f-9879-11ec-8797-fa163ee63de6 ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1933186/+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 1962451] [NEW] Libreoffice does not open remote files (over SSH with nautilus)
Public bug reported: With Ubuntu 21.04 LTS I can browse (gnome-files) remote files with SSH and clicking excel-table files will open the tables to Libreoffice. This does not work under Ubuntu 21.10 anymore. Libreoffice banner shows shortly and then nothing happens. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice (not installed) Uname: Linux 5.16.9-051609-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 28 11:14:23 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (138 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1962451 Title: Libreoffice does not open remote files (over SSH with nautilus) Status in libreoffice package in Ubuntu: New Bug description: With Ubuntu 21.04 LTS I can browse (gnome-files) remote files with SSH and clicking excel-table files will open the tables to Libreoffice. This does not work under Ubuntu 21.10 anymore. Libreoffice banner shows shortly and then nothing happens. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice (not installed) Uname: Linux 5.16.9-051609-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 28 11:14:23 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (138 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962451/+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 1962276] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+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 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-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: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+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
