[Touch-packages] [Bug 1879089] Re: Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04
Not sure why I am getting notification even though I am not subscribed. Any way, It is not missing. Gnome removed it. Please search before post. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1879089 Title: Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04 Status in ubuntu-settings package in Ubuntu: New Bug description: The options for selecting a single colour background, or, a colour gradient background, are missing in the settings, after upgrading from 18.04LTS to 20.04LTS. The upgrade was done according to this guide: https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/ Also tried to make a clean install of 20.04LTS on a virtual machine, with the same result, those functions are missing. Kind regards Anton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1879089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879131] [NEW] Relax the dependency of gnome-shell-extension-desktop-icons from Depends to Recommends
Public bug reported: I would like to be able to remove the gnome-shell-extension-desktop- icons without removing ubuntu-desktop. GNOME shell extensions are sometimes buggy, in this case desktop-icons, and I consider the desktop-icons extension an enhancement to the desktop, not a necessity, because no other functionality or packages depend on its behaviour, and there is no loss of data or breakage of another functionality after removing it. So changing the dependency to a Recommends would allow the extension to be installed by default and be removed without removing ubuntu-desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 09:48:49 2020 InstallationDate: Installed on 2020-04-26 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1879131 Title: Relax the dependency of gnome-shell-extension-desktop-icons from Depends to Recommends Status in ubuntu-meta package in Ubuntu: New Bug description: I would like to be able to remove the gnome-shell-extension-desktop- icons without removing ubuntu-desktop. GNOME shell extensions are sometimes buggy, in this case desktop- icons, and I consider the desktop-icons extension an enhancement to the desktop, not a necessity, because no other functionality or packages depend on its behaviour, and there is no loss of data or breakage of another functionality after removing it. So changing the dependency to a Recommends would allow the extension to be installed by default and be removed without removing ubuntu- desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 09:48:49 2020 InstallationDate: Installed on 2020-04-26 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1879131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875483 Title: vulkan failed with ERROR_INITIALIZATION_FAILED Status in mesa package in Ubuntu: Confirmed Bug description: 1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2. The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Установлен: 20.0.4-2ubuntu1 Кандидат: 20.0.4-2ubuntu1 Таблица версий: *** 20.0.4-2ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen run vulkaninfo run vkcube 4. What happened instead $ vulkaninfo ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED $ vkcube vkcube: /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: demo_init_vk: Assertion `!err' failed. Аварийный останов (стек памяти сброшен на диск) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mesa-vulkan-drivers 20.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Apr 27 22:47:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 250/350] [1458:226e] InstallationDate: Installed on 2020-04-23 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A58M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED
Got the same outputs: vulkaninfo /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED vkcube vkcube: /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: demo_init_vk: Assertion `!err' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875483 Title: vulkan failed with ERROR_INITIALIZATION_FAILED Status in mesa package in Ubuntu: Confirmed Bug description: 1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2. The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Установлен: 20.0.4-2ubuntu1 Кандидат: 20.0.4-2ubuntu1 Таблица версий: *** 20.0.4-2ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen run vulkaninfo run vkcube 4. What happened instead $ vulkaninfo ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED $ vkcube vkcube: /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: demo_init_vk: Assertion `!err' failed. Аварийный останов (стек памяти сброшен на диск) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mesa-vulkan-drivers 20.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Apr 27 22:47:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 250/350] [1458:226e] InstallationDate: Installed on 2020-04-23 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A58M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED
** Bug watch added: github.com/KhronosGroup/Vulkan-Tools/issues #403 https://github.com/KhronosGroup/Vulkan-Tools/issues/403 ** Also affects: mesa via https://github.com/KhronosGroup/Vulkan-Tools/issues/403 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875483 Title: vulkan failed with ERROR_INITIALIZATION_FAILED Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: 1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2. The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Установлен: 20.0.4-2ubuntu1 Кандидат: 20.0.4-2ubuntu1 Таблица версий: *** 20.0.4-2ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen run vulkaninfo run vkcube 4. What happened instead $ vulkaninfo ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED $ vkcube vkcube: /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: demo_init_vk: Assertion `!err' failed. Аварийный останов (стек памяти сброшен на диск) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mesa-vulkan-drivers 20.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Apr 27 22:47:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 250/350] [1458:226e] InstallationDate: Installed on 2020-04-23 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A58M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1875483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED
** Changed in: mesa Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875483 Title: vulkan failed with ERROR_INITIALIZATION_FAILED Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: 1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2. The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Установлен: 20.0.4-2ubuntu1 Кандидат: 20.0.4-2ubuntu1 Таблица версий: *** 20.0.4-2ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen run vulkaninfo run vkcube 4. What happened instead $ vulkaninfo ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED $ vkcube vkcube: /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: demo_init_vk: Assertion `!err' failed. Аварийный останов (стек памяти сброшен на диск) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mesa-vulkan-drivers 20.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Apr 27 22:47:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 250/350] [1458:226e] InstallationDate: Installed on 2020-04-23 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A58M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1875483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879089] Re: Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04
*** This bug is a duplicate of bug 1850753 *** https://bugs.launchpad.net/bugs/1850753 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular issue has already been reported and is a duplicate of bug 1850753, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1850753 Ubuntu 19.10 cannot set background to solid color -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1879089 Title: Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04 Status in ubuntu-settings package in Ubuntu: New Bug description: The options for selecting a single colour background, or, a colour gradient background, are missing in the settings, after upgrading from 18.04LTS to 20.04LTS. The upgrade was done according to this guide: https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/ Also tried to make a clean install of 20.04LTS on a virtual machine, with the same result, those functions are missing. Kind regards Anton To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1879089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879144] [NEW] Volume output settings reset on analog surround 4.0
Public bug reported: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Volume output reset settings reset on surround 4.0 + Volume output reset settings reset on pulseaudio surround 4.0 ** Summary changed: - Volume output reset settings reset on pulseaudio surround 4.0 + Volume output settings reset on pulseaudio surround 4.0 ** Summary changed: - Volume output settings reset on pulseaudio surround 4.0 + Volume output settings reset on analog surround 4.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan
In my case, I was following these steps: https://stackoverflow.com/a/60613072/8957293 This lead to a message about an internal error, with a prompt to send details to developers, and it got stuck once I pressed send. I didn't record exactly what package was the issue, but gtk was included in the name. Not much experience reporting bugs on linux - please let me know if more detail is needed. ** Attachment added: "j.txt" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+attachment/5372874/+files/j.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1850966 Title: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Software and Updates 2. Go to "other software" and enable, for example, a repository disabled during upgrade to Eoan which is not updated for Eoan yet 3. Press close and then reload on the dialog that opens. 4. Refreshing software cache dialog is stuck After closing the dialogs by right clicking on the windows and the open apps bar, re opening Software and updates only shows a white square you can't interact with. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879150] [NEW] apport-kde shows 'text' instead of text in message box
Public bug reported: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal patch third-party-packages ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1879150/+attachment/5372875/+files/3e98f10f63f78f74.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: New Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879150] Re: apport-kde shows 'text' instead of text in message box
** Patch added: "apport-kde.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+attachment/5372882/+files/apport-kde.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: New Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879150] Re: apport-kde shows 'text' instead of text in message box
The attachment "apport-kde.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1879150 Title: apport-kde shows 'text' instead of text in message box Status in apport package in Ubuntu: New Bug description: I had some other software crashing and wanting to report a bug, Apport displayed a pretty nonsensical message box (see the screenshot). $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy apport-kde apport-kde: Installed: 2.20.11-0ubuntu27 Candidate: 2.20.11-0ubuntu27 Version table: *** 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 17 14:11:30 2020 InstallationDate: Installed on 2015-12-11 (1618 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-05-15 (1 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-11-21T10:33:51.640107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1879150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879154] [NEW] stack-size option ignored by g++-9
Public bug reported:
I was encouraged to repost my stackoverflow question here
(https://stackoverflow.com/questions/61709726). In case stack-size
option is not implemented for this particular environment, a warning
would be helpful.
-
I'm building a test program with g++ 9.3.0 on Ubuntu 18.04 x64 using
this linker command:
/usr/bin/g++-9 -O3 -DNDEBUG -Wl,-z,stack-size=268435456
CMakeFiles/af.dir/main.cpp.o -o af
I'm testing increased stack requirements with this function:
float f() {
float a[3'000'000];
return a[42];
}
and results indicate a standard 8MB stack regardless of the stack-size
linker option value. What is the way to increase the stack size?
EDIT
The test is as follows:
float a[3'000'000]; causes Segmentation fault (core dumped)
float a[2'000'000]; returns 0 as expected
** Affects: binutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1879154
Title:
stack-size option ignored by g++-9
Status in binutils package in Ubuntu:
New
Bug description:
I was encouraged to repost my stackoverflow question here
(https://stackoverflow.com/questions/61709726). In case stack-size
option is not implemented for this particular environment, a warning
would be helpful.
-
I'm building a test program with g++ 9.3.0 on Ubuntu 18.04 x64 using
this linker command:
/usr/bin/g++-9 -O3 -DNDEBUG -Wl,-z,stack-size=268435456
CMakeFiles/af.dir/main.cpp.o -o af
I'm testing increased stack requirements with this function:
float f() {
float a[3'000'000];
return a[42];
}
and results indicate a standard 8MB stack regardless of the stack-size
linker option value. What is the way to increase the stack size?
EDIT
The test is as follows:
float a[3'000'000]; causes Segmentation fault (core dumped)
float a[2'000'000]; returns 0 as expected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1879154/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
I would say there is probably a missing dependency-/etc/securetty doesn't exist in Ubuntu and looks like it could be a typo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Confirmed Status in pam source package in Groovy: Confirmed Status in pam package in Debian: New Bug description: Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879156] [NEW] Xorg freeze
Public bug reported: freezing the screen when placing applications such as libreoffice in the category of office, games in the category of games, browsers in the category of internet, when renewing an application of the category the screen freezes, it is only the mouse cursor working having to force the shutdown of the notebook. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 09:49:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu ** Description changed: - freezing the screen when placing applications such as libreoffice in the - category of office, games in the category of games, browsers in the - category of internet, when renewing an application of the category the - screen freezes, it is only the cusor working having to force the - shutdown of the notebook. + congelar a tela ao colocar aplicativos como o libreoffice na categoria + de escritório, jogos na categoria de jogos, navegadores na categoria de + internet, ao renovar um aplicativo da categoria a tela congela. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: xorg 1:7.7+19ubuntu14 - ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 - Uname: Linux 5.4.0-29-generic x86_64 - ApportVersion: 2.20.11-0ubuntu27 - Architecture: amd64 - BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' - CasperMD5CheckResult: skip - CompositorRunning: None - CurrentDesktop: ubuntu:GNOME - Date: Sun May 17 09:49:56 2020 - DistUpgraded: Fresh install - DistroCodename: focal - DistroVariant: ubuntu - ExtraDebuggingInterest: Yes, if not too technical - GpuHangFrequency: This is the first time + ProblemType: Bug + DistroRelease: Ubuntu 20.04 + pacote: xorg 1: 7,7 + 19ubuntu14 + ProcVersionSign ature: Ubuntu 5.4.0-29.33-generic 5.4.30 + Uname: Linux 5.4.0-29-generic x86_64 + ApportVersion: 2.20.11-0ubuntu27 + Arquitetura: amd64 + BootLog: Erro: [Erro 13] Permissão negada: '/var/log/boot.log' + CasperMD5CheckR resultado : pular + CompositorRunning: None + CurrentDesktop: ubuntu: GNOME + Data: Sun 17 de maio 09:49:56 2020 + DistUpgraded: Fresh install + DistroCodename: focal + DistroVariant: ubuntu + ExtraDebuggingI interesse: Sim, se não for muito técnico + GpuHangFrequency: Esta é a primeira vez que GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] - InstallationDate: Installed on 2020-05-17 (0 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) - MachineType: ZMAX MOBILE 8100 B - ProcKernelC
[Touch-packages] [Bug 1879158] [NEW] congelamento da tela
Public bug reported: congelamento da tela ao colocar aplicativos como o libreoffice em categoria de escritorio, jogos na categoria de jogos, navegadores na categoria de internet, ao renover um aplicativo da categoria a tela congela, fica somente o cursor do mouse fucionando tendo de forçar o desligamente do notebook. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879158 Title: congelamento da tela Status in xorg package in Ubuntu: New Bug description: congelamento da tela ao colocar aplicativos como o libreoffice em categoria de escritorio, jogos na categoria de jogos, navegadores na categoria de internet, ao renover um aplicativo da categoria a tela congela, fica somente o cursor do mouse fucionando tendo de forçar o desligamente do notebook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
I finally was able to solve this. It turns out, my key was too old and thus kind of disabled as a security measure, I suppose. After creating a new key based off ED25519 and adding the corresponding public key to ~/.ssh/authorized_keys on the server, things are now working again. Can we please do better and inform the user what's wrong instead of silently pretending to be working but dropping the unlocked key? FWIW, even now with the process working again "keychain -l" still lists nothing. I'm not 100% sure but that looks like a bug of its own. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain Status in openssh package in Ubuntu: New Bug description: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) gnome-keyring is running: $ ps -ax|grep key 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 17832 pts/2S+ 0:00 grep --color=auto key ssh-agent is running: $ ps aux | grep ssh-agent leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent $ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 SSH_AGENT_PID=9952 SSH_AGENT_LAUNCHER=gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878327 Title: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output Status in pulseaudio package in Ubuntu: Confirmed Bug description: I had already reported bug #1876238 where internal speakers are not detected but shown as Dummy Output after upgrading Ubuntu from 19.10 to 20.04 LTS Focal. It was solved by this patch: https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 The current PulseAudio update today reversed that again. Internal speakers are not being detected and are shown as Dummy Output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj2016 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 09:02:53 2020 InstallationDate: Installed on 2016-12-20 (1239 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp
Tried with image ubuntu-minimal-2004-focal-v20200501 (systemd 245.4-4ubuntu3). No issues seen. I will then upgrade our project to Focal, which also has LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1874661 Title: networkd sometimes doesn't set mtu received by dhcp Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: New Status in systemd source package in Focal: In Progress Bug description: I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 242-7ubuntu3.7. GCE has mtu 1460, set by dhcp. After having networking issues, I figured out that the mtu on the interface was sometimes incorrectly set to 1500. I manually changed it to 1420 to have a working system again and enabled debugging for systemd-networkd. Log (filtered for ens4, some columns removed for better readability): 09:51:00 ens4: New device has no master, continuing without 09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST 09:51:00 ens4: Link 2 added 09:51:00 ens4: udev initialized link 09:51:00 ens4: Saved original MTU: 1420 09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever) 09:51:00 ens4: Gained IPv6LL 09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Link state is up-to-date 09:51:00 ens4: found matching network '/run/systemd/network/10-netplan-ens4.network' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0' 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0' 09:51:00 ens4: Started LLDP. 09:51:00 ens4: Setting address genmode for link 09:51:00 ens4: Setting address genmode done. 09:51:00 ens4: Removing address 10.164.0.2 09:51:00 ens4: Acquiring DHCPv4 lease 09:51:00 ens4: Discovering IPv6 routers 09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s) 09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 09:51:00 ens4: Setting MTU: 1460 09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 09:51:00 ens4: IPv6 successfully enabled 09:51:00 ens4: Setting MTU done. 09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d) 09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 09:51:00 ens4: Configured 21:50:59 ens4: DHCP lease lost 21:50:59 ens4: Removing address 10.164.0.2 21:50:59 ens4: Setting MTU: 1420 21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0' 21:50:59 ens4: IPv6 successfully enabled 21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1 21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s) 21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Setting MTU done. 21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d) 21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2 21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2 21:50:59 ens4: Configured On dhcp renew (09:51:00), mtu got properly changed to 1460. On next dhcp renew (21:50:59) it got changed back to previous value 1420. In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460. There have been some changes to mtu handling in the past, I assume th
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
Just a quick note to say that I removed the PPA enabled -proposed in my apt sources and rebooted, and networking is all working fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above, but remove ethernets: section. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto static linkdown 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster the bridge no longer has its address after losing carrier: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.sock
[Touch-packages] [Bug 1879156] Re: Xorg freeze
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879156 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: freezing the screen when placing applications such as libreoffice in the category of office, games in the category of games, browsers in the category of internet, when renewing an application of the category the screen freezes, it is only the mouse cursor working having to force the shutdown of the notebook. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 09:49:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879156] Re: Xorg freeze
** Changed in: xorg (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879156 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: freezing the screen when placing applications such as libreoffice in the category of office, games in the category of games, browsers in the category of internet, when renewing an application of the category the screen freezes, it is only the mouse cursor working having to force the shutdown of the notebook. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 09:49:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879170] [NEW] package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2
Public bug reported: i am not able to install unetbooting software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 17 09:01:42 2020 DuplicateSignature: package:cups:2.3.1-9ubuntu1.1 Setting up cups (2.3.1-9ubuntu1.1) ... Can't locate object method "new" via package "Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load "Debconf::Element::Noninteractive::Boolean"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, line 2. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 2 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: cups Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/23/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879170 Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 Status in cups package in Ubuntu: New Bug description: i am not able to install unetbooting software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 17 09:01:42 2020 DuplicateSignature: package:cups:2.3.1-9ubuntu1.1 Setting up cups (2.3.1-9ubuntu1.1) ... Can't locate object method "new" via package "Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load "Debconf::Element::Noninteractive::Boolean"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, line 2. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 2 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: cups Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log pres
[Touch-packages] [Bug 1879170] Re: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879170 Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 Status in cups package in Ubuntu: New Bug description: i am not able to install unetbooting software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 17 09:01:42 2020 DuplicateSignature: package:cups:2.3.1-9ubuntu1.1 Setting up cups (2.3.1-9ubuntu1.1) ... Can't locate object method "new" via package "Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load "Debconf::Element::Noninteractive::Boolean"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, line 2. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 2 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: cups Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/23/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879170] Re: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879170 Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 Status in cups package in Ubuntu: Invalid Bug description: i am not able to install unetbooting software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 17 09:01:42 2020 DuplicateSignature: package:cups:2.3.1-9ubuntu1.1 Setting up cups (2.3.1-9ubuntu1.1) ... Can't locate object method "new" via package "Debconf::Element::Noninteractive::Boolean" (perhaps you forgot to load "Debconf::Element::Noninteractive::Boolean"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, line 2. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 2 ErrorMessage: installed cups package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=666ebde9-f721-457c-95bc-7a8bef50c043 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: cups Title: package cups 2.3.1-9ubuntu1.1 failed to install/upgrade: installed cups package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/23/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
There is a upstream issue: https://github.com/sudo- project/sudo/issues/42 A fixed versions is released, maybe it can be backported to ubuntu. ** Bug watch added: github.com/sudo-project/sudo/issues #42 https://github.com/sudo-project/sudo/issues/42 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container Status in sudo package in Ubuntu: Confirmed Bug description: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: Installed: 1.8.31-1ubuntu1 Candidate: 1.8.31-1ubuntu1 Version table: *** 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status This is not an issue on Bionic: bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1.2 Candidate: 1.8.21p2-3ubuntu1.2 Version table: *** 1.8.21p2-3ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.8.21p2-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages From the redhat bug, the described workaround does clear these messages up: # set disable_coredump false Once I've done that, the error messages go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1868456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
I applied the fix from proposed and I can confirm that it fixed the issue for me too. thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above, but remove ethernets: section. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto static linkdown 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster the bridge no longer has its address after losing carrier: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-network
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
19.10->20.04 the same thing. It is happened not to be a loop but a series of identical messages from different packages. I package name should be included int the messages, to help user better understand the issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879182] [NEW] Sound cuts off and back on randomly during online streaming of videos
Public bug reported: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+attachment/5373017/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: New Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878201] Re: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No playback when selecting "Headset" after headset connection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1878201 Title: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No playback when selecting "Headset" after headset connection Status in alsa-driver package in Ubuntu: Confirmed Bug description: Just upgraded to ubuntu 20, worked fine with 18. When I plug in my hyperX headset, the sound does not work when I select Headset, even if I change back and forth with the speakers in the settings. It works perfectly if I select Headphones, and I can then select my headset microphone as a workaround. Thanks for the great work! Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aurelien 2334 F pulseaudio /dev/snd/pcmC0D0c: aurelien 2334 F...m pulseaudio /dev/snd/pcmC0D0p: aurelien 2334 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 14:19:43 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79+berline+X00 InstallationDate: Installed on 2020-03-03 (69 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago) dmi.bios.date: 02/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0WWHJ2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.product.sku: 0906 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878201] Re: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No playback when selecting "Headset" after headset connection
Following the instructions here https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1575078/comments/17 seems to have worked, at least for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1878201 Title: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] No playback when selecting "Headset" after headset connection Status in alsa-driver package in Ubuntu: Confirmed Bug description: Just upgraded to ubuntu 20, worked fine with 18. When I plug in my hyperX headset, the sound does not work when I select Headset, even if I change back and forth with the speakers in the settings. It works perfectly if I select Headphones, and I can then select my headset microphone as a workaround. Thanks for the great work! Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aurelien 2334 F pulseaudio /dev/snd/pcmC0D0c: aurelien 2334 F...m pulseaudio /dev/snd/pcmC0D0p: aurelien 2334 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 14:19:43 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79+berline+X00 InstallationDate: Installed on 2020-03-03 (69 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Precision 5540, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago) dmi.bios.date: 02/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0WWHJ2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.product.sku: 0906 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1878201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
So if I'm on 20.04, not running Upstart and not experiencing kernel panics, why would I want to install this 'update', re-introducing known security issues? Why is it even pushed to systems running 20.04 without Upstart? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0086 0f10ff6977efbf32 88003d45fe10 8140926b [ 99.996057] 81caddf8 88003d45fea8 88003d45fe98 81195a84 [ 99.996057] 8810 88003d45fea8 88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [] dump_stack+0x6d/0x92 [ 99.996057] [] panic+0xd3/0x227 [ 99.996057] [] do_exit+0xb9d/0xba0 [ 99.996057] [] do_group_exit+0x47/0xb0 [ 99.996057] [] SyS_exit_group+0x14/0x20 [ 99.996057] [] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I've had this issue since 16.04. How is it that we've gone through 3 LTS releases without a fix? What is the technical challenge with getting a Bluetooth LE headset paired for use as a headset? What is going on? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879193] [NEW] folder with applications freezes
Public bug reported: when placing applications in the folder the screen freezes, when removing the folder, the screen freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: - when placing applications in folder the screen freezes, when renaming - the folder the screen freezes + when placing applications in the folder the screen freezes, when + removing the folder, the screen freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xs
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Adding my story here . . . in U-MATE running sources.list as "devel" and
some of the list is ID-ing as "groovy" . . . it is showing as 20.10 . .
. had some issues with the broadcom package not updating in apt, so on
the U-MATE forum with wolfman and he had me look at my "Software &
Updates" data, and while just looking at the items in "edit," and even
though I changed nothing I got the same scenario as norbert in #3 post .
. . where the "cache refresh" window opens, progress bar fills . . . but
then window doesn't close--this time the crash report window opened.
I believe this happened previously and I might have FQd in the GUI . . .
. I sent the crash report and it auto-loaded the dup bug report
#1832057 . . . which linked me here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
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/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871763] Re: Duplicity is not working
I think this can be closed, because it was problem with my python2 installation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1871763 Title: Duplicity is not working Status in Duplicity: New Status in python-defaults package in Ubuntu: New Bug description: Duplicity is failing to make backup. It produces error message: see attached 000_Error_message.png After starting duplicity from terminal, I got much better error message: unim95@ubuntu-BitFenix-Prodigy:~$ duplicity bash: /usr/bin/duplicity: /usr/bin/python2: bad interpreter: No such file or directory After searching system for python2 i found, that there is no python2 executable unim95@ubuntu-BitFenix-Prodigy:~$ locate python2 | grep -v lib | grep -v man | grep -v doc | grep -v include /etc/python2.7 /etc/python2.7/sitecustomize.py /snap/core/8689/usr/share/bash-completion/completions/python2 /snap/core/8689/usr/share/dh-python/dh_python2 /snap/core/8689/usr/share/dh-python/dist/cpython2_fallback /snap/core/8935/usr/share/bash-completion/completions/python2 /snap/core/8935/usr/share/dh-python/dh_python2 /snap/core/8935/usr/share/dh-python/dist/cpython2_fallback /usr/bin/python2-futurize /usr/bin/python2-pasteurize /usr/bin/python2.7 /usr/bin/python2.7-config /usr/bin/waitress-serve-python2 /usr/bin/x86_64-linux-gnu-python2.7-config /usr/share/app-install/desktop/idle-python2.7:idle-python2.7.desktop /usr/share/applications/python2.7.desktop /usr/share/bash-completion/completions/python2 /usr/share/binfmts/python2.7 /usr/share/dh-python/dh_python2 /usr/share/dh-python/dist/cpython2_fallback /usr/share/lintian/overrides/python2.7 /usr/share/lintian/overrides/python2.7-minimal /usr/share/pixmaps/python2.7.xpm Default python is: unim95@ubuntu-BitFenix-Prodigy:~$ python --version Python 2.7.17 Duplicity version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s duplicity Package: duplicity Status: install ok installed Priority: optional Section: utils Installed-Size: 1064 Maintainer: Ubuntu Developers Architecture: amd64 Version: 0.7.17-0ubuntu1.1 Depends: libc6 (>= 2.4), librsync1 (>= 0.9.6), python (<< 2.8), python (>= 2.7~), python-fasteners, python:any (<< 2.8), python:any (>= 2.7.5-5~), python-lockfile (>> 1:0.9), gnupg | gnupg1 Suggests: rsync, python-paramiko, python-pexpect, python-urllib3, python-oauthlib, python-boto, ncftp, python-cloudfiles, lftp, python-gdata, tahoe-lafs, python-swiftclient Description: encrypted bandwidth-efficient backup Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server. Homepage: http://duplicity.nongnu.org/ Original-Maintainer: Alexander Zangerl Python2 version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s python Package: python Status: install ok installed Priority: optional Section: python Installed-Size: 624 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: allowed Source: python-defaults Version: 2.7.15~rc1-1 Replaces: python-dev (<< 2.6.5-2) Provides: python-ctypes, python-email, python-importlib, python-profiler, python-wsgiref Depends: python2.7 (>= 2.7.15~rc1-1~), libpython-stdlib (= 2.7.15~rc1-1) Pre-Depends: python-minimal (= 2.7.15~rc1-1) Suggests: python-doc (= 2.7.15~rc1-1), python-tk (>= 2.7.15~rc1-1~) Breaks: update-manager-core (<< 0.200.5-2) Conflicts: python-central (<< 0.5.5) Description: interactive high-level object-oriented language (default version) Python, the high-level, interactive object oriented language, includes an extensive class library with lots of goodies for network programming, system administration, sounds and graphics. . This package is a dependency package, which depends on Debian's default Python version (currently v2.7). Original-Maintainer: Matthias Klose Homepage: http://www.python.org/ Cnf-Extra-Commands: python Cnf-Priority-Bonus: 3 OS: unim95@ubuntu-BitFenix-Prodigy:~$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic FS used: ext4. To manage notifications about this bug go to: https://bugs.launchp
[Touch-packages] [Bug 1879206] Re: cups hplip not install printer
These problems are highlighted with hplip-gui diagnostics: DeskJet-3630 Type: Printer Device URI: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 PPD: /etc/cups/ppd/DeskJet-3630.ppd warning: Failed to read /etc/cups/ppd/DeskJet-3630.ppd ppd file PPD Description: Printer status: la stampante DeskJet-3630 è inattiva. è stata abilitata da lun 18 mag 2020, 02:12:27 error: Unable to communicate with device (code=12): hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 error: Device not found error: Communication status: Failed -- | PERMISSION | -- Checking Permissions Checking for Configured Queues warning: Fail to read ppd=/etc/cups/ppd/DeskJet-3630.ppd file warning: Insufficient permission to access file /etc/cups/ppd/DeskJet-3630.ppd warning: Could not complete Queue(s) configuration check Checking for HP Properitery Plugin's No plug-in printers are configured. Checking for Printer Status error: 'DeskJet-3630' Printer is either Powered-OFF or Failed to communicate. Turn On Printer and re-run hp-doctor Diagnose completed... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879206] [NEW] cups hplip not install printer
Public bug reported: After upgrading to Ubuntu 20.04 I can't print anymore. Description:Ubuntu 20.04 LTS Release:20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassi
[Touch-packages] [Bug 1879206] Re: cups hplip not install printer
In another partition that I keep for testing, I had made a clean installation of 20.04 and after installing hplip the same printer works without problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
** Attachment added: "Display Settings 2" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879209/+attachment/5373107/+files/Screenshot%20from%202020-05-17%2020-44-29.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879209 Title: Display settings configures dual display resolution incorrectly Status in xorg package in Ubuntu: New Bug description: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 19.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Fill
[Touch-packages] [Bug 1879209] [NEW] Display settings configures dual display resolution incorrectly
Public bug reported: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 19.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xo
[Touch-packages] [Bug 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
The recommended way for doing that is changing the mouse speed in your control panel/settings/whatever GUI. For example, in Ubuntu 20.04 it is: Settings > Mouse & Touchpad > Mouse > Mouse Speed Another option you might like is: gnome-tweaks > Keyboard & Mouse > Mouse > Acceleration Profile = Flat -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] Microsoft Classic IntelliMouse moves way too fast to be usable. [test case] on a bionic system, connect affected mouse and attempt to move pointer, note it moves too fast. [regression potential] as this adds a hwdb entry for a mouse using vendor/product id and name matching, any regression would likely involve incorrectly setting dpi on a different mouse than intended. [scope] fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4 which is included starting in v240, so this is already fixed in Eoan and later. This is needed only for Xenial and Bionic. [original description] Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
As suggested in comment #8, please try disabling voice prompts. That seems to work on a variety of Bose devices: https://www.bose.com/en_us/support/article/disabling-voice-prompts- soundlink-mini-ii.html If you would like to discuss the problem further then it would probably be best to report it to the developers here: BlueZ: https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth PulseAudio: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues No one has yet(?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
** Description changed: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu - (definitely in 19.04 and 19.10) I was able to configure this using + (definitely in 18.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 -1280x1024 60.02*+ 75.02 -1280x960 60.00 -1152x864 75.00 -1024x768 75.0370.0760.00 -800x600 75.0072.1960.3256.25 -640x480 75.0072.8159.94 + 1280x1024 60.02*+ 75.02 + 1280x960 60.00 + 1152x864 75.00 + 1024x768 75.0370.0760.00 + 800x600 75.0072.1960.3256.25 + 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 -2560x1440 59.95*+ -2048x1152 60.00 -1920x1200 59.88 -1920x1080 60.0059.9450.0029.9725.0023.98 -1680x1050 59.95 -1600x1200 60.00 -1280x1024 75.0260.02 -1280x720 60.0059.9450.00 -1200x960 59.90 -1152x864 75.00 -1024x768 75.0360.00 -800x600 75.0060.32 -720x576 50.00 -720x480 59.94 -640x480 75.0059.9459.93 + 2560x1440 59.95*+ + 2048x1152 60.00 + 1920x1200 59.88 + 1920x1080 60.0059.9450.0029.9725.0023.98 + 1680x1050 59.95 + 1600x1200 60.00 + 1280x1024 75.0260.02 + 1280x720 60.0059.9450.00 + 1200x960 59.90 + 1152x864 75.00 + 1024x768 75.0360.00 + 800x600 75.0060.32 + 720x576 50.00 + 720x480 59.94 + 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 - GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] + NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
If you want to +1 bugs, please use the green link near the top left of the page. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
*** This bug is a duplicate of bug 1843982 *** https://bugs.launchpad.net/bugs/1843982 ** This bug has been marked a duplicate of bug 1843982 Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Won't Fix 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.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 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/accountsservice/+bug/1832865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1874217, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879209 Title: Display settings configures dual display resolution incorrectly Status in xorg package in Ubuntu: New Bug description: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 18.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0
[Touch-packages] [Bug 1878953] Re: Display settings is lost when switching between modes with Super+P
I think this is expected. I think Gnome Shell only remembers one configuration per set of attached monitors. But intuitively yes that's annoying if you're only tapping Super+P. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: multimonitor ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878953 Title: Display settings is lost when switching between modes with Super+P Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When switching between modes (built-in only, joint, ...) with Super+P, the display settings are lost. That even occurs when selecting already selected mode (selecting "joint" while being in "joint" mode). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 18:12:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879177] [NEW] Sound cuts off and back on randomly during online streaming of videos
You have been subscribed to a public bug: Sound cuts off and comes back on every 10 or so minutes. I have tried the usual stuff like purging and removing alsa and pulseaudio and restarting, forcing alsa reload, killing pulseaudio and starting again, etc. Here is the output from cat /var/log/syslog* | grep -i pulse gnome-shell[7674]: [8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation is nullptr. I have attached alsa information also as an attachment ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Sound cuts off and back on randomly during online streaming of videos https://bugs.launchpad.net/bugs/1879177 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879177] Re: Sound cuts off and back on randomly during online streaming of videos
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879177 Title: Sound cuts off and back on randomly during online streaming of videos Status in alsa-driver package in Ubuntu: New Bug description: Sound cuts off and comes back on every 10 or so minutes. I have tried the usual stuff like purging and removing alsa and pulseaudio and restarting, forcing alsa reload, killing pulseaudio and starting again, etc. Here is the output from cat /var/log/syslog* | grep -i pulse gnome-shell[7674]: [8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation is nullptr. I have attached alsa information also as an attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately
** Tags added: oem-priority originate-from-1878141 somerville ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878635] [NEW] Intel Titan Ridge TB3 USB Controller prevents system from suspending
You have been subscribed to a public bug: The dmesg log states the following: PM: Device :0f:00.0 failed to suspend async: error -110 When checking lspci this points to the following device: 0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) which is the integrated Thunderbolt 3 Controller of the ITX Motherboard. I will still try suspending without a Thunderbolt 3 Dock attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spyfly 2424 F pulseaudio /dev/snd/controlC3: spyfly 2424 F pulseaudio /dev/snd/controlC1: spyfly 2424 F pulseaudio /dev/snd/controlC2: spyfly 2424 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 17:09:55 2020 HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2 InstallationDate: Installed on 2018-09-06 (616 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.78 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: powermgmt-base (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- Intel Titan Ridge TB3 USB Controller prevents system from suspending https://bugs.launchpad.net/bugs/1878635 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878635] Re: Intel Titan Ridge TB3 USB Controller prevents system from suspending
** Package changed: linux (Ubuntu) => powermgmt-base (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1878635 Title: Intel Titan Ridge TB3 USB Controller prevents system from suspending Status in powermgmt-base package in Ubuntu: Confirmed Bug description: The dmesg log states the following: PM: Device :0f:00.0 failed to suspend async: error -110 When checking lspci this points to the following device: 0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) which is the integrated Thunderbolt 3 Controller of the ITX Motherboard. I will still try suspending without a Thunderbolt 3 Dock attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spyfly 2424 F pulseaudio /dev/snd/controlC3: spyfly 2424 F pulseaudio /dev/snd/controlC1: spyfly 2424 F pulseaudio /dev/snd/controlC2: spyfly 2424 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 17:09:55 2020 HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2 InstallationDate: Installed on 2018-09-06 (616 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.78 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1878635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED
that's not a bug in mesa or anywhere, SI won't migrate to amdgpu so you need to force it manually ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875483 Title: vulkan failed with ERROR_INITIALIZATION_FAILED Status in Mesa: New Status in mesa package in Ubuntu: Invalid Bug description: 1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 2. The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Установлен: 20.0.4-2ubuntu1 Кандидат: 20.0.4-2ubuntu1 Таблица версий: *** 20.0.4-2ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen run vulkaninfo run vkcube 4. What happened instead $ vulkaninfo ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32 ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32 /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477: failed with ERROR_INITIALIZATION_FAILED $ vkcube vkcube: /build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: demo_init_vk: Assertion `!err' failed. Аварийный останов (стек памяти сброшен на диск) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mesa-vulkan-drivers 20.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Apr 27 22:47:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 250/350] [1458:226e] InstallationDate: Installed on 2020-04-23 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A58M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1875483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
